Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support the new/upcoming generic ZHA Zeroconf discovery? #11

Open
Hedda opened this issue Sep 30, 2024 · 1 comment
Open

Support the new/upcoming generic ZHA Zeroconf discovery? #11

Hedda opened this issue Sep 30, 2024 · 1 comment

Comments

@Hedda
Copy link

Hedda commented Sep 30, 2024

puddly is working on a new new/upcoming generic Zeroconf discovery for the ZHA integration in Home Assistant to allow it to discover new network-attached Zigbee Coordinator adapters without code changes to the ZHA component in Home Assistant core. Please look into adding support for this Zeroconf discovery formatting, see:

home-assistant/core#126294

The goal with this is that code changes to the ZHA component in Home Assistant core but it puts some new requirement on the firmware site where the manufacturer need to enter unique metadate for each new type and model of network-attached Zigbee Coordinator adapter. This will eventeully also make the old disovery method obeslete:

https://www.home-assistant.io/integrations/zha#discovery-via-usb-or-zeroconf

PS: Alternative is to use the old method but it is likley that new patches to Home Assistant core will be accepted once support for this new formallting/method has been implemented.

@Hedda
Copy link
Author

Hedda commented Jan 20, 2025

Bump since this "generic ZHA Zeroconf discovery" feature has been merged into Home Assistant's core

"I'm introducing a new service type: _zigbee-coordinator._tcp.local.. This will allow all future TCP coordinators to be supported without an explicit PR to ZHA. The only expected properties are radio_type (one of ezsp, znp, etc.) and serial_number (must be unique per device and not derived from any Zigbee information, like the Ethernet MAC address). The service name will be shown as-is."

puddly posted comments there and elseware stating that this become the new default for discovering Zigbee Coordiantors.

Tip is to check out code from tube0013 since read that he helped puddly beta test it so also first to implement this feature:

Noted that he is using get_mac_address and convert that into a serial_number in order to make the serials unique for each device:

PS: Off-topic but you might also be interested to check out his customized version of the uart component which enable hardware flow control for ESP32 boards:

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

No branches or pull requests

1 participant