awalsum
commented
2 years ago I have managed to solve the problem. First I tried reinstalling nodejs and npm, but that didn't help. After various attempts, I thought the cause might be due to a corrupted Zigbee stick. Maybe the problems with the old PC also had an effect on the stick (even though the SSD has no problems). I decided to reflash the stick, but that in turn left me with another sort of error. A "network commissioning error" .
With this new error I decided to look into what could be causing that. I felt I was drifting further and further away from a working system and had even considered looking into some other means of communicating with all the switches and sensors (35 devices). Because I wanted to eliminate bad hardware (the stick), I ordered a new one online.
Last night, I thought I would try changing the Zigbee channel in the configuration.yaml file. I was on the default channel 11. I changed it to 15 and when I tried starting Zigbee2MQTT, all of a sudden it worked without any errors. I changed it back to 11 (because all my devices were set to 11 initially) and it gave me errors again and wouldn't start.
Now I'm on channel 15 and after re-pairing all the devices, it seems to be working again. The new USB stick should arrive in the mail tomorrow, so I guess I'll have a spare.
The only issue I'm still having is that the re-pairing of TUYA TS011F plugs didn't go well. For some reason I can't switch them in Domotics.I am getting power readings etc. In the Zigbee2MQTT frontend everything is fine. The TS0121 plugs are fine.
github-actions[bot]
What happened?
My PC crashed last week. It was a Ubuntu 20.04 LTS, i7, 8GB ram PC fitted with a 128GB SSD. I took the SSD out and connected it with a SATA to USB cable to another PC and found it was still working. Something in the power circuit in de PC had died and did not damage the SSD in any way.
I fitted the SSD to a replacement PC, a Dell i5 with 4GB Ram. Everything is up and running again in Domoticz, except for ZIGBEE2MQTT.
I keep getting Error: AREQ - ZDO - stateChangeInd after 60000ms. I have the Slaesh CC2652RB USB stick and that has served me well over the past year or so.
I have spent the last two night shifts desperately trying to get it up and running, but cannot find the problem.
What did you expect to happen?
After mounting the SSD into another PC, everything would be business as usual.
How to reproduce it (minimal and precise)
I have since reinstalled nodejs and npm. I am on version: npm: 8.11.0 node: v16.15.1 Installed the latest version of ZIGBEE2MQTT (1.25.2) After typing npm start, I get:
Zigbee2MQTT:info 2022-06-06 04:13:07: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2022-06-06.04-13-07' filename: log.txt Zigbee2MQTT:info 2022-06-06 04:13:07: Starting Zigbee2MQTT version 1.25.2 (commit #a252914e) Zigbee2MQTT:info 2022-06-06 04:13:07: Starting zigbee-herdsman (0.14.34) Zigbee2MQTT:error 2022-06-06 04:14:17: Error while starting zigbee-herdsman Zigbee2MQTT:error 2022-06-06 04:14:17: Failed to start zigbee Zigbee2MQTT:error 2022-06-06 04:14:17: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions Zigbee2MQTT:error 2022-06-06 04:14:17: Exiting... Zigbee2MQTT:error 2022-06-06 04:14:17: Error: AREQ - ZDO - stateChangeInd after 60000ms at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:559:17) at processTimers
(node:internal/timers:502:7)Zigbee2MQTT version
1.25.2
Adapter firmware version
Cannot reach frontend
Adapter
Slaesh CC2652RB
Debug log
log.txt