Skip to content

Support the new generic Zeroconf discovery for the ZHA integration in Home Assistant #3

@Hedda

Description

@Hedda

Is your feature request related to a problem? Please describe.

Please consider adding support the new (or at least recently added) generic Zeroconf discovery for the ZHA integration in Home Assistant. See:

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

"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."

This is a feature request; puddly has implemented a new 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 new standard of Zeroconf discovery formatting for ZHA,

Describe the solution you'd like

FYI, this "generic ZHA Zeroconf discovery" feature has been merged into Home Assistant's core. The goal with this is that code changes to the ZHA component in Home Assistant core but it puts some new requirements on the firmware side where the manufacturer needs to use a standardized MDNS domain name + provide both radio type as well as unique serrial number as metadata for each device of a network-attached Zigbee Coordinator adapter. This will eventually also make the old/legacy discovery methods obsolete:

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:

Describe alternatives you've considered

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

Additional context

Disclaimer; This is just an FYI; I can not add or test this myself since I do not have any XZG based Zigbee Coordinator.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions