Repository navigation
feat(discovery): recognise the headless X32Link (ESP-035) - #9
Merged
Merged
Conversation
"I see kstouch. not the headless." The X32Link was powered, on the network, and following the Link session, and the app showed nothing. Adding `x32link` to the hostname prefix list is the small half of this. The real cause was in the firmware: that unit had NO mDNS WHATSOEVER -- it never advertised, so no matcher on this side could have found it, and `dns-sd` could not see it either. Fixed in link-devices (ESP-035), where it now announces `x32link-<mac>` like the rest of the fleet and serves the shared /status and /config.json. The prefix list stays a documented HEURISTIC, not a guarantee -- a TXT record is still the fix that would make identity a fact. Tests pin both halves: the headless is one of ours, and a stranger's box at a venue still is not. Verified against the real unit: both devices now appear in the list, live BPM. Claude-Session: https://claude.ai/code/session_01F7YsQgso3KNpeXbP5vNVj6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The X32Link was powered, on the network, and audibly following the Link session — and the app showed nothing.
Adding
x32linkto the hostname prefix list is the small half of this. The real cause was in the firmware: that unit had no mDNS whatsoever. Not a stale name, not a wrong service type — none. It never advertised, so no matcher on this side could have found it, anddns-sdcouldn't see it either. That's fixed in link-devices ESP-035, where it now announcesx32link-<mac>like the rest of the fleet and serves the shared/statusand/config.json.Pair with that PR — this one alone does nothing.
The prefix list remains a documented heuristic, not a guarantee. A TXT record is still the thing that would make identity a fact rather than a guess, and a stranger's box at a venue is exactly the false positive prefix-matching cannot prevent. Tests pin both halves: the headless is one of ours, and
brother-printer/x32-mixerare not.Verified on real hardware
Both units now appear in the list with live BPM:
Full suite green.
https://claude.ai/code/session_01F7YsQgso3KNpeXbP5vNVj6