Closed kucharskim closed 3 days ago
Does z2m crash completely?
Yes, node.js exits.
I actually hit another problem after deleting (unpairing a device):
Zigbee2MQTT:info 2024-01-31 19:19:09: Removing device '0xa4c1389250e329e0' (block: false, force: false)
Error: {"address":22109,"clusterId":32773,"sequence":167} after 10000ms
at Timeout._onTimeout (/data/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
All those crashes look similar in nature. I request an action, action times out because device is offline or not that easily reachable and z2m/node.js crashes with a timeout.
Please check again with tomorrows new release, if it still crashes, provide the herdsman debug log of it.
See this on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.
Sure, will wait for a release and check again.
When it crashes, it's gone:
# pgrep -x node | wc -l
0
@Koenkk seems like I have same problem - when trying to (re-)join some devices - z2mqtt just crashes. Using HASS addon. Log starting from device join request
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
What happened?
Clicked to check for updates for all devices (
Check all
button) and found nodejs crashed like this:What did you expect to happen?
Not crash.
How to reproduce it (minimal and precise)
It's random and rare, but it does happen.
Coordinator type: EZSP v8 Coordinator revision: 6.10.3.0 build 297 Zigbee-herdsman-converters version: 18.9.0 Zigbee-herdsman version: 0.30.0 Frontend version: 0.6.151
Zigbee2MQTT version
1.35.1 commit: 3c962042
Adapter firmware version
6.10.3.0 build 297
Adapter
ITEAD SONOFF Zigbee 3.0 USB Dongle Plus V2
Setup
PC Engines APU3, OpenBSD -current, node-18.19.0
Debug log
No response