Skip to content

Use raydriver's HTTP probes for discovery - #736

Open
knipknap wants to merge 1 commit into
feat/probe-censusfrom
feat/http-probes
Open

knipknap wants to merge 1 commit into
feat/probe-censusfrom
feat/http-probes

Conversation

@knipknap

Copy link
Copy Markdown
Contributor

Implements Phase 11 of the driver-migration plan (raydriver side: barebaric/raydriver#42). Stacked on #735.

  • GrblNetworkDriver.DISCOVERY fingerprints generic _http._tcp announcements with raydriver's HttpFingerprint (GET [ESP800] + case-insensitive body match in Rust) instead of the local aiohttp probe; grbl_fingerprint.py and its test are deleted.
  • XtoolNetworkDriver.probe uses raydriver.xtool.query_machine_type — the machine-type handshake the Rust session already performs on connect — instead of the local aiohttp GET; the 8080-port fallback and the setup error are unchanged.

aiohttp remains in the machine module only for OctoPrint. Behavior is unchanged: the discovery engine claims on truthiness only, so the previous fingerprint's MDNSService return value was already discarded.

57 discovery/xtool/network tests pass.

The ESP800 fingerprint of GrblNetworkDriver becomes raydriver's
HttpFingerprint, and the xTool machine-type query of the wizard
probe becomes raydriver's query_machine_type — both were the last
aiohttp users in the machine module outside OctoPrint.

This branch was successfully deployed

1 active deployment
pypi — ccd02d01 Deployed Nov 18, 2026 by knipknap via Build and Publish Wheel #2747
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant