All Zigbee Devices Have Disconnected

Configuration
1

Hi all
Running HA in Docker, Ubuntu 20.02.

Yesterday I was playing around with getting zigbee2mqtt to work. Long story, but I ended up backing out the changes (or so I thought) and returning to the configuration as it was 24hours ago.
However HA is no longer detecting any zigbee devices via my Conbee II.

The devices are all listed, but are unavailable.
Nothing has changed hardware side - Conbee stick is still in the same USB port it always has been, but it is as if the stick itself is not being picked up by HA now.

Hoping I don’t need to go through the whole process of adding them again, but any ideas where I might have broken something?
Initial thoughts are that sharing the same USB device with zigbee2mqtt has created access issues but I have removed all traces (as far as I know) of z2m and performed multiple restarts.

In the process of troubleshooting, I have also noticed that Ubuntu always reports the USB is being in the same port regardless of me physically plugging it in somewhere else (i.e. it is ALWAYS ttyACM0 in the print out below). This doesn’t seem like correct behaviour?

user@server:/opt$ ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jun 14 00:11 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2447455-if00 -> ../../ttyACM0

My core.config_entries has the following:

            {
                "entry_id": "a32c78449bcdf2e6b54f6408fd96f456",
                "version": 3,
                "domain": "zha",
                "title": "ConBee II - /dev/ttyACM0, s/n: DE2447455 - dresden elektronik ingenieurtechnik GmbH - 1CF1:0030",
                "data": {
                    "radio_type": "deconz",
                    "device": {
                        "path": "/dev/ttyACM0"
                    }
                },
                "options": {
                    "custom_configuration": {
                        "zha_options": {
                            "consider_unavailable_mains": 7200,
                            "enable_identify_on_join": true,
                            "consider_unavailable_battery": 21600
                        },
                        "zha_alarm_options": {
                            "alarm_failed_tries": 3,
                            "alarm_arm_requires_code": false,
                            "alarm_master_code": "1234"
                        }
                    }
                },
                "pref_disable_new_entities": false,
                "pref_disable_polling": false,
                "source": "usb",
                "unique_id": "1CF1:0030_DE2447455_dresden elektronik ingenieurtechnik GmbH_ConBee II",
                "disabled_by": null
            },

With docker-compose.yaml looking like this:

  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - /opt/homeassistant/config:/config
      - /etc/localtime:/etc/localtime:ro
    devices:
      - /dev/ttyACM0:/dev/ttyACM0 #zigbee USB
    restart: unless-stopped
    privileged: true
    network_mode: host
2

Also, going through the logs, it doesn’t look like all of the zigbee devices went offline simultaneously. They seem to drop off over the course of 30mins or so from 17:40 to 18:10 yesterday evening.

3

Attach it to a USB extension cable and see if that helps

4

Did you actually pair devices while using z2m? If so then most likely you will have to repair them. Pairing a device sets a few things including an encryption key and a channel. The device then broadcasts it’s messages on that channel and encrypts them with that key.

Uninstalling things or changing config doesn’t change what was paired to the end devices. Only repairing does.

1 Like
6

This seems to be exactly it.
Putting the devices in to pairing mode, and they get detected again with all their names/dependencies intact.
Minor faff of running around the house pressing buttons, but at least integrations don’t need re-doing.
Thanks!

1 Like