8000 Declare deCONZ as "not recommended" in zha and zigpy until join via "Install Code" with ConBee is confirmed working? · Issue #447 · zigpy/zha · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Declare deCONZ as "not recommended" in zha and zigpy until join via "Install Code" with ConBee is confirmed working? #447
Open
@Hedda

Description

@Hedda

Indirectly related to #436

Suggest that zha developers declare deCONZ based radios as "not recommended" in zigpy and Home Assistant’s downstream ZHA integration documentation until can confirm that "Install Code" joining fully work for sure with ConBee 2 and ConBee 3 radio, or?

Today the downstream ZHA integration in Home Assistant not only list ConBee III as compatible but actually "recommended" for use with ZHA:

Reason for asking is seen recent reports that it does not work to commission Zigbee 3.0 devices via "Install Code" / "QR Code" in ZHA with ConBee:

Also note that ZHA docs still list this as a ZHA limitation (or more specifically that it is only supported with 'ezsp' and 'znp' radios):

**Support for commissioning Zigbee 3.0 devices via "Install Code" or "QR Code" via the `zha.permit` action:**

- This has so far only been implemented for 'ezsp' (Silicon Labs EmberZNet) or 'znp' (Texas Instruments) radio type in ZHA.
- Other radio types are missing support in their respective [radio libraries for zigpy](https://github.com/zigpy/) or manufacturer's firmware commands/APIs.

PS: I no longer own one so can not test but seen recent reports that joining via install codes do not work in ZHA, nor in Z2M where issue is open:

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

      0