Sonoff Zigbee Dongle-E in docker environment - cant get it up and running

[SkipperDo]

Hello Guys...

I Currently use Z2M in Docker-compose with an ConBee2 Stick for 1 and a half year now.. - Everything works well.. except some little stability problems..

That's Why i ordered the Sonoff Zigbee 3.0 USB Dongle Plus Modell: ZBDongle-E

So i backup my Z2M Installation and modify my Z2M config:

homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.1.21:1883
serial:
  port: /dev/ttyACM0
  # ConBee2 Stick
  # adapter: deconz
  # baudrate: 38400
  # Sonoff Zigbee 3.0 USB Dongle E
  adapter: ezsp
  # baudrate: 460800
advanced:
  network_key:
    - some numbers
  frontend: true
  log_level: debug
  log_syslog:
    app_name: Zigbee2MQTT
    eol: /n
    host: localhost
    localhost: localhost
    path: /dev/log
    pid: process.pid
    port: 123
    protocol: tcp4
    type: '5424'
  output: attribute_and_json
  last_seen: ISO_8601_local
frontend:
  port: 8080
  host: 0.0.0.0
devices:

for bind the Sonoff Stick to the Container i modified my docker-compose file: (only the Z2M part)

 zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt:latest
    restart: always
    privileged: true
    volumes:
      - /home/me/container/zigbee2mqtt_test:/app/data
      - /run/udev:/run/udev:ro
    ports:
      # Frontend port
      - 8080:8080
    environment:
      - TZ=Europe/Berlin
    devices:
      # old Config using ConBee 2 Stick
      #- /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2472781-if00:/dev/ttyACM0
      # new Config using Sonoff Zigbee 3.0 USB Dongle E
      - /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231008103424-if00:/dev/ttyACM0
    #depends_on:
      #- mosquitto
    networks:
      - SmartHomeNetwork

Looks everything correct to me, but Z2M will not start at all...

Log of Z2M:

debug 2024-01-04 13:08:49: Loaded state from file /app/data/state.json
info  2024-01-04 13:08:49: Logging to console and directory: '/app/data/log/2024-01-04.13-08-49' filename: log.txt
info  2024-01-04 13:08:49: Starting Zigbee2MQTT version 1.35.0 (commit #b5a90e9)
info  2024-01-04 13:08:49: Starting zigbee-herdsman (0.30.0)
debug 2024-01-04 13:08:49: 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":"ezsp","path":"/dev/ttyACM0"}}'

Nothing else in the log... Container every time creates a ton of identical logfiles like the shown..

Im out and need help to get this Sonoff Stick up & running...
Any suggestions?

[dwndmr]

I know it sounds dumb... but try to rebuild the container WITHOUT having any configuration ready.
It will generate a small default one that will work :)

[SkipperDo]

Yeah!
You are right...

[SkipperDo]

The migration from ConBee2 to Sonoff Stick is now complete...
But i have some trouble...
Some Devices won't pair... e.g. aqara Motion Sensors, aqara door / window contacts...
I used the same Network Key with the Sonof stick like before, could this be the reason of this trouble, maybe?

Like the divices "say": "uh, its the same Network key, i don´t need to pair again..." ?

[chris-1243]

I would try to use the "Permit join via a specific device" and to use a router as close as possible of your aqara sensors.

Is your conbeeII completely off ? If not, you might be facing some issues especially if you're using the same parameters (channel included).

Otherwise, some end devices/routers are known to be hard to pair with your Sonoff Dongle-E unfortunatelly...

[SkipperDo]

The ConBee2 Stick is back in the Box who delivered in...

I tried to shutdown the whole system for a couple of minutes... After that i was able to pair some - not all - of the Devices..
And i currently have the "permit: true" setting (permanent allow to pair) active... In this case the pairing is possible via all connected routers...

[chris-1243]

Have a look to this post in HA community. You may find some useful advises (factory reset your sensors...)

I still recommend to force your sensors to pair via a designated router which is as close as possible. End devices do not always choose the best router with the "pairing all". Have a look at your network map and you might find some surprises.

[tomdavidson]

I have the same trouble and confirmed that zigbee2mqtt service has write access to the device.

[tomdavidson]

Thanks for the help - looks like it was magical. The docker-compose.yaml file is valid yaml.

The mount is to /dev/ttyACM0 and the other devices do not exist in the container:

container

#  ls -las /dev/ttyACM0 
     0 crw-rw----    1 root     dialout   188,   0 Jan 25 17:41 /dev/ttyACM0

host

root@iot-things:~# ls -las /dev/serial/by-id/
0 lrwxrwxrwx 1 root root  13 Jan 24 22:55 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231118155043-if00 -> ../../ttyACM0
0 lrwxrwxrwx 1 root root  13 Jan 24 22:54 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_18d15b18aa45ed11a200c58f0a86e0b4-if00-port0 -> ../../ttyUSB0
0 lrwxrwxrwx 1 root root  13 Jan 24 20:28 usb-Zooz_800_Z-Wave_Stick_533D004242-if00 -> ../../ttyACM1

root@iot-things:~# ls -las /dev/ttyACM*
0 crw-rw---- 1 root dialout 166, 0 Jan 24 22:55 /dev/ttyACM0
0 crw-rw---- 1 root dialout 166, 1 Jan 24 20:28 /dev/ttyACM1

oooh so now it starts with v2...
First grouping is "fresh" after the volume purge. Second group is just a restart because I didnt believe it. I seriously, have not changed any of the config or the docker-compose.yaml from before. Besides the data purge (which has been done at one time or another but maybe there was stale data from prior attempts) the only think I think that is different is right now both adapters are plugged in (but only v2 mounted in the container).

[Logs]    [2024-01-26T00:57:03.835Z] [zigbee] Using '/app/data' as data directory
[Logs]    [2024-01-26T00:57:22.559Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:22: Logging to console and directory: '/app/data/log/2024-01-25.17-57-22' filename: log.txt
[Logs]    [2024-01-26T00:57:22.634Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:22: Starting Zigbee2MQTT version 1.35.1 (commit #9eaaa0f)
[Logs]    [2024-01-26T00:57:22.646Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:22: Starting zigbee-herdsman (0.30.0)
[Logs]    [2024-01-26T00:57:26.817Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:26: zigbee-herdsman started (reset)
[Logs]    [2024-01-26T00:57:26.825Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:26: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
[Logs]    [2024-01-26T00:57:26.981Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:26: Currently 0 devices are joined:
[Logs]    [2024-01-26T00:57:26.989Z] [zigbee] Zigbee2MQTT:warn  2024-01-25 17:57:26: `permit_join` set to  `true` in configuration.yaml.
[Logs]    [2024-01-26T00:57:26.992Z] [zigbee] Zigbee2MQTT:warn  2024-01-25 17:57:26: Allowing new devices to join.
[Logs]    [2024-01-26T00:57:26.999Z] [zigbee] Zigbee2MQTT:warn  2024-01-25 17:57:26: Set `permit_join` to `false` once you joined all devices.
[Logs]    [2024-01-26T00:57:27.004Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:27: Zigbee: allowing new devices to join.
[Logs]    [2024-01-26T00:57:27.285Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:27: Connecting to MQTT server at mqtt://mqtt:1883
[Logs]    [2024-01-26T00:57:27.717Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:27: Connected to MQTT server
[Logs]    [2024-01-26T00:57:27.725Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:27: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[Logs]    [2024-01-26T00:57:28.103Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:28: Started frontend on port 0.0.0.0:5000
[Logs]    [2024-01-26T00:57:28.111Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:57:28: Zigbee2MQTT started!


[Logs]    [2024-01-26T00:59:12.312Z] [zigbee] Zigbee2MQTT:error 2024-01-25 17:59:12: Error while starting zigbee-herdsman
[Logs]    [2024-01-26T00:59:12.319Z] [zigbee] Zigbee2MQTT:error 2024-01-25 17:59:12: Failed to start zigbee
[Logs]    [2024-01-26T00:59:12.325Z] [zigbee] Zigbee2MQTT:error 2024-01-25 17:59:12: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[Logs]    [2024-01-26T00:59:12.332Z] [zigbee] Zigbee2MQTT:error 2024-01-25 17:59:12: Exiting...
[Logs]    [2024-01-26T00:59:12.603Z] [zigbee] Zigbee2MQTT:error 2024-01-25 17:59:12: Error: Failure send version:{"type":"Buffer","data":[1,0,1,0,0,8]}
[Logs]    [2024-01-26T00:59:12.604Z] [zigbee]     at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:562:23
[Logs]    [2024-01-26T00:59:12.605Z] [zigbee]     at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
[Logs]    [2024-01-26T00:59:17.188Z] [zigbee] Using '/app/data' as data directory
[Logs]    [2024-01-26T00:59:29.902Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:29: Logging to console and directory: '/app/data/log/2024-01-25.17-59-29' filename: log.txt
[Logs]    [2024-01-26T00:59:29.981Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:29: Starting Zigbee2MQTT version 1.35.1 (commit #9eaaa0f)
[Logs]    [2024-01-26T00:59:29.993Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:29: Starting zigbee-herdsman (0.30.0)
[Logs]    [2024-01-26T00:59:34.082Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: zigbee-herdsman started (resumed)
[Logs]    [2024-01-26T00:59:34.088Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
[Logs]    [2024-01-26T00:59:34.098Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: Currently 0 devices are joined:
[Logs]    [2024-01-26T00:59:34.103Z] [zigbee] Zigbee2MQTT:warn  2024-01-25 17:59:34: `permit_join` set to  `true` in configuration.yaml.
[Logs]    [2024-01-26T00:59:34.106Z] [zigbee] Zigbee2MQTT:warn  2024-01-25 17:59:34: Allowing new devices to join.
[Logs]    [2024-01-26T00:59:34.111Z] [zigbee] Zigbee2MQTT:warn  2024-01-25 17:59:34: Set `permit_join` to `false` once you joined all devices.
[Logs]    [2024-01-26T00:59:34.117Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: Zigbee: allowing new devices to join.
[Logs]    [2024-01-26T00:59:34.388Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: Connecting to MQTT server at mqtt://mqtt:1883
[Logs]    [2024-01-26T00:59:34.765Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: Connected to MQTT server
[Logs]    [2024-01-26T00:59:34.771Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:34: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[Logs]    [2024-01-26T00:59:35.069Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:35: Started frontend on port 0.0.0.0:5000
[Logs]    [2024-01-26T00:59:35.075Z] [zigbee] Zigbee2MQTT:info  2024-01-25 17:59:35: Zigbee2MQTT started!

Side question, now that I have both versions, do you recommend that I use v2 E for matter and thread and v1 P for zigbee or sale the v1 P or would that require another instance of z2m?

[SkipperDo]

@tomdavidson
I recommmend nothing like that... Its your Choice...

I only can tell you the dongle-E is able to do both... Zigbee & even thread & Matter... But only with the MultiPAN FW installed...

But therefore, there is an additional Container required, that handle all of that shit...
But i don´t know which one and how to setup this guy...
This would be verry interesting... But currently i don´t really care about, because i only have ZigBee Devices, some ESP32 via ESPHome and 1-3 WLAN devices..

But your ls output looks a little strange to me...
this is mine - in compare...

ls -ls /dev/serial/by-id/
insgesamt 0
0 lrwxrwxrwx 1 root root 13 25. Jan 19:19 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2472781-if00 -> ../../ttyACM0
0 lrwxrwxrwx 1 root root 13 25. Jan 18:28 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231008103424-if00 -> ../../ttyACM1

take a look to the permissions...

I don´t really know if mine is bad.. - maybe? But it works fine... ;) (of course only on the ConBee2 Stick - currently... This one will be unplugged in the next days to merge it to the Sonoff)

[chris-1243]

@tomdavidson

You could not mount two dongles in the same container. You normally need one container for a dongle.

To have the E version working with matter/thread, it requires the silab multi protocol tools available as an addon in homeassistant or via docker. If doing that way, be aware of all your zigbee network as to be created from scratch. Have a look to this well done article.

Both P and E version have their pros and cons. It is up to you to choose the one which would suits more your need.
I am personnaly running the P version in prod and i am quite happy with it. I fisrt tried the E version but at that time, z2m was not so stable with it. Now it is better but as an advice "don't touch a running system unless it is not stable...". I do keep the E version for testing and they are really good router if flashed with the router firmware

[SkipperDo]

This Silabs Multiprotocol add-on sounds nice...
You have any informations about it?
How to use it with docker?

[chris-1243]

@SkipperDo

Check this.
As far as I read, Silabs has a container for arm64 only. You may build it by your own or use the great job made by the HA community (check the link above).
No idea how to configure it as I do not plan to use matter/thread on RCP firmware for the time. Too experimental for me and my zigbee network is perfectly running and stable. Be aware, you will have to build from scratch your zigbee network if using the same stick for both...