core: zha and ConBee using new integration will not work at all

Home Assistant release with the issue: 0.87.1

Last working Home Assistant release (if known): First installation of zha

Operating environment (Hass.io/Docker/Windows/etc.): Ubuntu - Hass.io running in dockers

Component/platform: zha with ConBee stick

Description of problem: I have tried twice (restored snapshot between the two attempts) to install zha using a ConBee stick

It fails to work at all. I tried to check access to the device. The device can communicate in a Windows machine

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant): None - used the integration

Traceback (if applicable): Log attached.

Additional information:

I have nevert run Deconz on the machine with Home Assistant so I cannot turn it off because it is not there.

Device registry says

        {
            "area_id": null,
            "config_entries": [
                "02f494cd398e4163800700f4d933347e"
            ],
            "connections": [
                [
                    "zigbee",
                    "00:21:2e:ff:ff:03:27:e4"
                ]
            ],
            "hub_device_id": null,
            "id": "fac3269369eb4d589e2f71b65d06b6f5",
            "identifiers": [
                [
                    "zha",
                    "00:21:2e:ff:ff:03:27:e4"
                ]
            ],
            "manufacturer": "ZHA",
            "model": "Deconz",
            "name": "Zigbee Coordinator",
            "sw_version": null
        } 

and core config entry file says

        {
            "connection_class": "local_push",
            "data": {
                "radio_type": "deconz",
                "usb_path": "/dev/ttyUSB0"
            },
            "domain": "zha",
            "entry_id": "02f494cd398e4163800700f4d933347e",
            "source": "user",
            "title": "/dev/ttyUSB0",
            "version": 1
        } 

Home Assistant Log entries from before and after restart

zha-conbee.log

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (13 by maintainers)

Most upvoted comments

This should be fixed with the following PR: #12

The upcoming release will include the fix.