Failed to start zigbee: zigbee2mqtt + Docker + Conbee II

Configuration Zigbee
1

Hi,

I messed up but don’t know what I did wrong.
I’ve updated both the ConbeeII stick and Ubuntu Server, and now zigbee2mqtt gives the following error when starting Docker Compose:

Attaching to zigbee2mqtt
zigbee2mqtt  | Using '/app/data' as data directory
zigbee2mqtt  | Zigbee2MQTT:info  2024-05-01 09:43:35: Logging to console and directory: '/app/data/log/2024-05-01.09-43-35' filename: log.txt
zigbee2mqtt  | Zigbee2MQTT:info  2024-05-01 09:43:35: Starting Zigbee2MQTT version 1.36.1 (commit #ffc2ff1)
zigbee2mqtt  | Zigbee2MQTT:info  2024-05-01 09:43:35: Starting zigbee-herdsman (0.40.3)
zigbee2mqtt  | Zigbee2MQTT:error 2024-05-01 09:43:46: Error while starting zigbee-herdsman
zigbee2mqtt  | Zigbee2MQTT:error 2024-05-01 09:43:46: Failed to start zigbee
zigbee2mqtt  | Zigbee2MQTT:error 2024-05-01 09:43:46: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
zigbee2mqtt  | Zigbee2MQTT:error 2024-05-01 09:43:46: Exiting...
zigbee2mqtt  | Zigbee2MQTT:error 2024-05-01 09:43:46: undefined
zigbee2mqtt exited with code 0

For troubleshooting:

ls -l /dev/serial/by-id:

lrwxrwxrwx 1 root root 13 May  1 09:33 usb-0658_0200-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 May  1 09:33 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2128773-if00 -> ../../ttyACM1

docker compose file contains:

  zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt
    restart: unless-stopped
    volumes:
      - /opt/zigbee2mqtt/data:/app/data
      - /run/udev:/run/udev:ro
    ports:
      - 8080:8080
    environment:
      - TZ=Europe/Brussels
    devices:
      - /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2128773-if00:/dev/ttyACM0

zigbee2mqtt/data/configuration.yaml:

homeassistant: true
frontend: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://10.27.27.24:1883
  user: admin
  password: xxxx
serial:
  port: /dev/ttyACM0
  adapter: deconz
  disable_led: false
  baudrate: 115200
  rtscts: false
advanced:
  network_key:
    - 28
    - 52
    - 208
    - 181
    - 104
    - 3
    - 126
    - 190
    - 120
    - 20
    - 66
    - 237
    - 110
    - 20
    - 185
    - 88
  log_level: info

Any idea?

2

That error usually means a problem with the broker comms. Can it reach the broker on that IP? Do those details work in something like MQTT Explorer?

3

MQTT seems to be up and running:

Screenshot 2024-05-01 125952
Screenshot 2024-05-01 1259521007×705 21.8 KB

4

Maybe set log level to debug.

5

I might be wrong, but one place you are pointing to ttyACM1 and another ttyACM0, might that be the issue?

6

Thx, some more info in debug-log:

debug 2024-05-01 13:08:59: Loaded state from file /app/data/state.json
info  2024-05-01 13:08:59: Logging to console and directory: '/app/data/log/2024-05-01.13-08-59' filename: log.txt
debug 2024-05-01 13:08:59: Removing old log directory '/app/data/log/2024-05-01.13-05-26'
info  2024-05-01 13:08:59: Starting Zigbee2MQTT version 1.36.1 (commit #ffc2ff1)
info  2024-05-01 13:08:59: Starting zigbee-herdsman (0.40.3)
debug 2024-05-01 13:08:59: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"deconz","baudRate":115200,"path":"/dev/ttyACM0","rtscts":false}}'
error 2024-05-01 13:09:10: Error while starting zigbee-herdsman
error 2024-05-01 13:09:10: Failed to start zigbee
error 2024-05-01 13:09:10: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
error 2024-05-01 13:09:10: Exiting...
error 2024-05-01 13:09:10: undefined
7

Try adding

 privileged: true

to your docker-compose

8

Changed to ttyACM1:

  zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt
    restart: unless-stopped
    volumes:
      - /opt/zigbee2mqtt/data:/app/data
      - /run/udev:/run/udev:ro
    ports:
      - 8080:8080
    environment:
      - TZ=Europe/Brussels
    devices:
      - /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2128773-if00:/dev/ttyACM1

serial:
  port: /dev/ttyACM1
  adapter: deconz

Gives this error:

debug 2024-05-01 13:20:20: Loaded state from file /app/data/state.json
info  2024-05-01 13:20:20: Logging to console and directory: '/app/data/log/2024-05-01.13-20-20' filename: log.txt
debug 2024-05-01 13:20:20: Removing old log directory '/app/data/log/2024-05-01.13-17-19'
info  2024-05-01 13:20:20: Starting Zigbee2MQTT version 1.36.1 (commit #ffc2ff1)
info  2024-05-01 13:20:20: Starting zigbee-herdsman (0.40.3)
debug 2024-05-01 13:20:20: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"deconz","baudRate":115200,"path":"/dev/ttyACM1","rtscts":false}}'
error 2024-05-01 13:20:30: Error while starting zigbee-herdsman
error 2024-05-01 13:20:30: Failed to start zigbee
error 2024-05-01 13:20:30: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
error 2024-05-01 13:20:30: Exiting...
error 2024-05-01 13:20:30: undefined
9

And did you add the docker user to the dailout group ?

10 
privileged: true

Same error

And did you add the docker user to the dailout group ?

How do i do that? I run as root (i think)

11

and

https://www.xmodulo.com/change-usb-device-permission-linux.html

12

Fixed: I tested the stick with the official Phoscon App, and I saw Firmware: Not connected. I must have done something wrong during the firmware update I suppose.

Thanks Tinkerer, fleskefjes and francisp. I’ve learned some new things today.

2 Likes