Network error when launching the zigbee suite

Kirjy commented 11 months ago

What happened?

Hi, I have the same problem as specified in there : https://github.com/Koenkk/zigbee2mqtt/issues/18090 When I'm starting the docker, I get the following error. It used to work correctly on my raspberry pi 4 under raspberry pi OS 64 bits. But now I'm trying to migrate to a mini pc with an Intel N100 running on Ubuntu server. It seems that the problem in the first post was also on this mini pc. That's why I'm specifying it.

Attaching to z2m-ha, z2m-mosquitto, z2m-zigbee2mqtt
z2m-mosquitto    | chown: /mosquitto/config/mosquitto.conf: Operation not permittedz2m-mosquitto    | 1699186615: mosquitto version 2.0.18 starting
z2m-mosquitto    | 1699186615: Config loaded from /mosquitto/config/mosquitto.conf.z2m-mosquitto    | 1699186615: Opening ipv4 listen socket on port 1883.
z2m-mosquitto    | 1699186615: Opening ipv6 listen socket on port 1883.
z2m-mosquitto    | 1699186615: Opening websockets listen socket on port 9001.
z2m-mosquitto    | 1699186615: mosquitto version 2.0.18 running
z2m-ha           | s6-rc: info: service s6rc-oneshot-runner: starting
z2m-ha           | s6-rc: info: service s6rc-oneshot-runner successfully started
z2m-ha           | s6-rc: info: service fix-attrs: starting
z2m-ha           | s6-rc: info: service fix-attrs successfully started
z2m-ha           | s6-rc: info: service legacy-cont-init: starting
z2m-ha           | s6-rc: info: service legacy-cont-init successfully started
z2m-ha           | s6-rc: info: service legacy-services: starting
z2m-ha           | services-up: info: copying legacy longrun home-assistant (no readiness notification)
z2m-zigbee2mqtt  | Using '/app/data' as data directory
z2m-ha           | s6-rc: info: service legacy-services successfully started
z2m-zigbee2mqtt  | Zigbee2MQTT:info  2023-11-05 13:16:56: Logging to console and directory: '/app/data/log/2023-11-05.13-16-56' filename: log.txt
z2m-zigbee2mqtt  | Zigbee2MQTT:info  2023-11-05 13:16:56: Starting Zigbee2MQTT version 1.33.2 (commit #9996c93)
z2m-zigbee2mqtt  | Zigbee2MQTT:info  2023-11-05 13:16:56: Starting zigbee-herdsman (0.21.0)
z2m-zigbee2mqtt  | Zigbee2MQTT:info  2023-11-05 13:16:59: zigbee-herdsman started (resumed)
z2m-zigbee2mqtt  | Zigbee2MQTT:info  2023-11-05 13:16:59: Coordinator firmware version: 'undefined'
z2m-zigbee2mqtt  | Zigbee2MQTT:error 2023-11-05 13:17:09: Failed to start zigbee
z2m-zigbee2mqtt  | Zigbee2MQTT:error 2023-11-05 13:17:09: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
z2m-zigbee2mqtt  | Zigbee2MQTT:error 2023-11-05 13:17:09: Exiting...
z2m-zigbee2mqtt  | Zigbee2MQTT:error 2023-11-05 13:17:09: Error: get network parameters Error:TIMEOUT
z2m-zigbee2mqtt  |     at DeconzAdapter.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1002:35)
z2m-zigbee2mqtt  |     at Controller.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:360:44)
z2m-zigbee2mqtt  |     at Zigbee.start (/app/lib/zigbee.ts:113:62)
z2m-zigbee2mqtt  |     at Controller.start (/app/lib/controller.ts:101:27)
z2m-zigbee2mqtt  |     at start (/app/index.js:107:5)

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

Launching my docker compose. It can be found here : https://github.com/Kirjy/DockerizedRaspberryPi/tree/main/z2m

Zigbee2MQTT version

1.33.2

Adapter firmware version

deCONZ_ConBeeII_0x26780700

Adapter

Conbee 2

Debug log

No response

YewTreeWeb commented 10 months ago

I'm also having this issue on a mini PC running a Intel N100 CPU. Z2M also ran perfectly fine on my Raspberry Pi 4. However I'm running a Proxmox VM. My error message is:

[20:59:39] INFO: Preparing to start...
[20:59:39] INFO: Socat not enabled
[20:59:39] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:error 2023-11-23 21:00:11: Failed to start zigbee
Zigbee2MQTT:error 2023-11-23 21:00:11: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-11-23 21:00:11: Exiting...
Zigbee2MQTT:error 2023-11-23 21:00:11: Error: get network parameters Error:TIMEOUT
    at DeconzAdapter.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1002:35)
    at Controller.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:360:44)
    at Zigbee.start (/app/lib/zigbee.ts:113:62)
    at Controller.start (/app/lib/controller.ts:101:27)
    at start (/app/index.js:107:5)

Kirjy commented 10 months ago

As I couldn't make it work, I tried a few things : 1 - running deconz instead of zigbee2mqtt works 2 - running zha also works 3 - running zigbee2mqtt with a sonoff key works too 4 - running it on a pi 4 works with zigbee2mqtt and a conbee 2 key

That makes the reason even more weird to me.

anthosz commented 10 months ago

Same issue here:

Latest version of zigbee2mqtt docker image (previously reproduced with an image from beginning of 2023)
Key well found via lsusb: Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
On my previous mini pc, all was ok (Debian + Docker) -> switched to N100 (like @YewTreeWeb ) + Ubuntu + Docker *> didn't works anymore

anthosz commented 10 months ago

Small update:

after few restart of the docker container, "Coordinator firmware version" is well found but "Error: get network parameters Error:TIMEOUT" continue.
I kept the docker compose up all the night (so basically, auto restart of container once stopped) -> issue was "fixed" during the night and z2mqtt was finally up... but with several "empty" interval during the night (like 1h without any state). After a restart of the container, the issue remain.

anthosz commented 10 months ago

Finally it worked during 1 week (until now)... I tried to add a new device & boom, error is back since 1h

x3ntr0 commented 9 months ago

The solution is trivial :) Service is already running, stop it and start it again. VM: zigbee2mqtt $: sudo systemctl stop zigbee2mqtt $: npm start

Kirjy commented 9 months ago

The solution is trivial :) Service is already running, stop it and start it again. VM: zigbee2mqtt $: sudo systemctl stop zigbee2mqtt $: npm start

Sounds good, doesn't work. I tried all trivial solutions. This make the solution I need not trivial.

anthosz commented 9 months ago

The solution is trivial :) Service is already running, stop it and start it again. VM: zigbee2mqtt $: sudo systemctl stop zigbee2mqtt $: npm start

It's not the same error. In my case, npm is not running at all so docker restart...

anthosz commented 9 months ago

In addition, like mentioned 2 weeks ago.

All worked well after few hours of restart, z2mqtt was stable during few days. Tried to allow pairing:

Zigbee2MQTT:error 2023-12-15 21:13:33: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:debug 2023-12-15 21:13:34: Error: APS TIMEOUT
    at Driver.processApsBusyQueue (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:723:28)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:162:56)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)

10 sec later:

UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "TIMEOUT".

10 sec later, it's back:

Zigbee2MQTT:debug 2023-12-15 21:13:55: Loaded state from file /app/data/state.json
Zigbee2MQTT:info  2023-12-15 21:13:55: Logging to console and directory: '/app/data/log/2023-12-15.21-13-55' filename: log.txt
Zigbee2MQTT:debug 2023-12-15 21:13:55: Removing old log directory '/app/data/log/2023-12-09.10-51-26'
Zigbee2MQTT:info  2023-12-15 21:13:55: Starting Zigbee2MQTT version 1.34.0 (commit #aae7312)
Zigbee2MQTT:info  2023-12-15 21:13:55: Starting zigbee-herdsman (0.25.0)
Zigbee2MQTT:debug 2023-12-15 21:13:55: 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","path":"/dev/ttyACM0"}}'
Zigbee2MQTT:info  2023-12-15 21:13:58: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-12-15 21:13:58: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:error 2023-12-15 21:14:08: Failed to start zigbee
Zigbee2MQTT:error 2023-12-15 21:14:08: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-12-15 21:14:08: Exiting...
Zigbee2MQTT:error 2023-12-15 21:14:08: Error: get network parameters Error:TIMEOUT
    at DeconzAdapter.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1017:35)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at processTimers (node:internal/timers:512:7)
    at Controller.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:360:44)
    at Zigbee.start (/app/lib/zigbee.ts:113:62)
    at Controller.start (/app/lib/controller.ts:101:27)
    at start (/app/index.js:107:5)

Now, just need to wait few hours and z2mqtt will be back.. But no way to pair new devices :(

anthosz commented 9 months ago

Tried also on different USB port (with or without cable): same issue Tried with a DB reset (reset the z2mqtt conf): same issue Tried to check on bios what goes wrong: no idea (only cpu stuff can be modified) Do you have any idea @Koenkk ? It seems we are several peoples impacted and majority switch to another solution :/

I'm available for any test/debug but at this time, I'm out of ideas

Koenkk commented 9 months ago

Looks like some bug in the Deconz integration, @chrishae could you take a look at this?

anthosz commented 9 months ago

Workaround at this time: switched zigbee2mqtt to raspberry (docker) and all works in addition of the N100 mini computer (HA/mosquitto)...

thomaszub commented 9 months ago

Hi,

same issue here with an Intel N100 and ConBee 2 (works in RPi 4). The issue

Zigbee2MQTT:info 2023-11-05 13:16:59: Coordinator firmware version: 'undefined'

vanished for me with updating the ConBee 2 firmware to the latest version, but the Timeout remains. If you need more logs or some testing, you can just ping me.

ChrisHae commented 9 months ago

Does the problem only occur in Docker or Proxmox? Does deCONZ also run in Docker when it works and does it run on a Raspberry Pi natively or also in Docker?

Can anybody share a log of sudo dmesg?

Docker has a problem with reconnecting USB devices that causes them to not be passed through correctly.

Haerteleric commented 9 months ago

like ChrisHae said we gonna need a dmesg log of the Host, that handles the USB-Connections to pin down the issue.

I also discovered in your docker-compose, that the tty-handle of the ConBee is passed through to 2 different Containers:

https://github.com/Kirjy/DockerizedRaspberryPi/blob/main/z2m/compose.yml :18 and :57 afaik this could cause issues, when both containers try to interact with the Device.

Kirjy commented 9 months ago

Hello. Thanks for your answer. As I migrated to sonoff I don't have logs anymore. Can someone who has the same problem provide them? I have indeed 2 containers linking the key but I also tried with only the good one. The second is when I forgot to remove this link when trying to integrate it through zha directly without using z2mqtt.

thomaszub commented 8 months ago

Happy new year :)

I get the following dmesg logs (running zigbee2mqtt in a container):

[  154.126479] usb 1-1: new full-speed USB device number 4 using xhci_hcd
[  154.268553] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[  154.268571] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  154.268578] usb 1-1: Product: ConBee II
[  154.268582] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[  154.268586] usb 1-1: SerialNumber: DE2410227
[  154.285997] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[  154.286036] usbcore: registered new interface driver cdc_acm
[  154.286039] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[  157.762328] usb 1-1: USB disconnect, device number 4
[  158.129750] usb 1-1: new full-speed USB device number 5 using xhci_hcd
[  158.271783] usb 1-1: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[  158.271802] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  158.271808] usb 1-1: Product: ConBee II
[  158.271812] usb 1-1: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[  158.271816] usb 1-1: SerialNumber: DE2410227
[  158.276989] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[  223.043574] br-578da946cd5e: port 1(vethb19dde4) entered blocking state
[  223.043581] br-578da946cd5e: port 1(vethb19dde4) entered disabled state
[  223.043591] vethb19dde4: entered allmulticast mode
[  223.043930] vethb19dde4: entered promiscuous mode
[  223.045173] br-578da946cd5e: port 1(vethb19dde4) entered blocking state
[  223.045182] br-578da946cd5e: port 1(vethb19dde4) entered forwarding state
[  223.046369] br-578da946cd5e: port 1(vethb19dde4) entered disabled state
[  223.240202] eth0: renamed from vethf615533
[  223.260656] br-578da946cd5e: port 1(vethb19dde4) entered blocking state
[  223.260673] br-578da946cd5e: port 1(vethb19dde4) entered forwarding state
[  223.311773] br-578da946cd5e: port 2(vethb9a8449) entered blocking state
[  223.311791] br-578da946cd5e: port 2(vethb9a8449) entered disabled state
[  223.311805] vethb9a8449: entered allmulticast mode
[  223.311998] vethb9a8449: entered promiscuous mode
[  223.312129] br-578da946cd5e: port 2(vethb9a8449) entered blocking state
[  223.312134] br-578da946cd5e: port 2(vethb9a8449) entered forwarding state
[  223.333370] br-578da946cd5e: port 3(vethabd9ebe) entered blocking state
[  223.333715] br-578da946cd5e: port 3(vethabd9ebe) entered disabled state
[  223.333737] vethabd9ebe: entered allmulticast mode
[  223.333815] vethabd9ebe: entered promiscuous mode
[  223.333969] br-578da946cd5e: port 3(vethabd9ebe) entered blocking state
[  223.333974] br-578da946cd5e: port 3(vethabd9ebe) entered forwarding state

infamousdimsum commented 8 months ago

Actually don't restore a backup from Home Assistant. Someone said restoring a full backup would bork the port from reading properly. Did a clean install again without restoring the full backup and it works again just like with the Pi4. serial: port: /dev/ttyACM0 adapter: deconz

Need to figure out a easy way to backup the zigbee2mqtt data file from Portainer. Don't want to re-pair everything again.

anthosz commented 4 months ago

Hello,

Do we have any workaround excluding rpi for this issue?

Kirjy commented 4 months ago

Hello,

Do we have any workaround excluding rpi for this issue?

Hello, My workaround was to buy a sonoff dongle. I've got no problem with this one on a N100 computer. I couldn't figure how to make the conbee 2 work.

Grigorek commented 2 months ago

Hi, same issue here with proxmox and HassOS installation on zigbee2mqtt 1.39 installed via addon store. I have installed earlier on my QNAP Nas on docker and it was working fine and now that I wanted move it to mini pc with Intel N100 I am facing this issue. It can recognize firmware but it get Timeout anyway and on another attempt it gets firmware undefined and there was also one attempt when if succesfully connected to Conbee but couldn't connect to any zigbee device.

[2024-07-24 13:01:06] info:     z2m: Logging to console, file (filename: log.log)
[2024-07-24 13:01:06] info:     z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)
[2024-07-24 13:01:06] info:     z2m: Starting zigbee-herdsman (0.50.1)
[2024-07-24 13:01:06] info:     z2m: zigbee-herdsman started (resumed)
[2024-07-24 13:01:09] info:     z2m: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
[2024-07-24 13:01:19] error:    z2m: Failed to start zigbee
[2024-07-24 13:01:19] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-07-24 13:01:19] error:    z2m: Exiting...
[2024-07-24 13:01:19] error:    z2m: Error: get network parameters Error:TIMEOUT
    at DeconzAdapter.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1015:35)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at processTimers (node:internal/timers:512:7)
    at Controller.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:379:44)
    at Zigbee.start (/app/lib/zigbee.ts:125:62)
    at Controller.start (/app/lib/controller.ts:139:27)
    at start (/app/index.js:154:5)
[13:08:47] INFO: Preparing to start...
[13:08:47] INFO: Socat not enabled
[13:08:47] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-07-24 13:08:49] info:     z2m: Logging to console, file (filename: log.log)
[2024-07-24 13:08:49] info:     z2m: Starting Zigbee2MQTT version 1.39.0 (commit #unknown)
[2024-07-24 13:08:49] info:     z2m: Starting zigbee-herdsman (0.50.1)
[2024-07-24 13:08:52] info:     z2m: zigbee-herdsman started (resumed)
[2024-07-24 13:08:52] info:     z2m: Coordinator firmware version: 'undefined'
[2024-07-24 13:09:02] error:    z2m: Failed to start zigbee
[2024-07-24 13:09:02] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-07-24 13:09:02] error:    z2m: Exiting...
[2024-07-24 13:09:02] error:    z2m: Error: get network parameters Error:TIMEOUT
    at DeconzAdapter.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/adapter/deconz/adapter/deconzAdapter.ts:1015:35)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at processTimers (node:internal/timers:512:7)
    at Controller.getNetworkParameters (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:379:44)
    at Zigbee.start (/app/lib/zigbee.ts:125:62)
    at Controller.start (/app/lib/controller.ts:139:27)
    at start (/app/index.js:154:5)

I can provide logs etc.

Koenkk / zigbee2mqtt