-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A LOT of traffic and errors after 1.35 upgrade - "No network route (205)" and timeouts #20526
Comments
Pushed a fix, let me know if it works! If not, provide the debug log. See this on how to enable debug logging. |
Same here. I just switched to Z2M Edge 10 minutes ago to solve the problem but the problem still exists. E.g. the covers are not responding, or just after 2-5 minutes. And I get a lot of red boxes in Z2M like this TUYA switch: |
@Koenkk Thanks for the feedback, unfortunately the fix did not help. Here is 5min debug log: |
Here are some other error logs: |
Same here. Tons of errors (no network route (205) or undefined (25)).
This is a single IKEA bulb being switched off then on to force a reconnect. |
Same issues with 1.34 - network completely down 😭 Sample log entries
|
@Koenkk Unfortunately, the issue is still here with newest commits and 20221226 firmware. Here is the log: zigbee2mqtt_daemon_dev_20221226.log BTW, before this issue I had firmware 20210120 - so it occurs also with that version. |
@Koenkk Funny thing, initially it has not start with
However, it started after restart, but the issue still persist. Below is the log: |
I want to add myself to this thread after getting alot.of the problems described in here lately. Normal HAOS with Z2M and Mosquitto MQTT. Collapses easily and with no warning. No indication other than zwitches.and sensors just hanging in their state. Only a full reboot will resolve things for a day or so befor things creep to a hault again. |
@nefh I see you are sending a lot of messages like |
@Koenkk These messages seems to coming from homebridge zigbee2mqtt integration. After turning off homebridge entirely, the log is much better. However, homebridge integration was working fine before, it would be nice if it could still work. :) Of course, homebridge and integration were on the newest versions now. |
@Koenkk Intresting, I've cleared the cache on homebridge, and on first glance it looked ok.
P.S. There seem to be problems noted also on homebridge-z2m github: |
@Koenkk I have a problem with running debug:
|
@Koenkk This time, I had to run dev version much longer to have any timeouts appear and automation after even that time are still responsive. I will run it longer to see if eventually will it freeze. In meantime, logs from ~10min with 1.34 and over an hour of dev version. log_herdsman_1.34.txt |
What devices are |
ToaletaLampa: Lonsonho QS-Zigbee-S05-LN |
|
My network seems affected as well. Network completely down.
If I try to configure any of the device then i get this
|
Weird. I'm seeing these same messages for random devices that are bound to Inovelli Blue switches, but everything in my mesh is working fine (including the switches and devices participating in the binding from the error message). When I attempt to manually reconfigure the device, I just get another error log:
This device is a ThirdReality 3RSP019BZ plug with no binding at all to another device, only back to the coordinator (which is a Tubeszb USB dongle). |
@Koenkk I've run the dev build long run. Good news is it hasn't freezed at all. However, there are few more errors in the logs. Below I paste list of error messages filtered from duplicates and unused devices.
Device list: Actual logs: Hope it helps! |
@ilbarone87 I spent most part of a day trying to get my network back online. Unfortunately, the only way forward was to roll back to 1.34 and revert the coordinator firmware (20221226 on zzh) as well. Once that was done, I deleted the whole device database and re-paired all 100+ devices. 95% IKEA (lights, switches), a couple of Sonoff relays and a couple of tuya curtain motors. |
@nefh these errors look like general network issues, I do not expect that 1.35.1 has an effect on it (only the configure part changed here), are you sure these errors didn't occur with 1.34.0? |
i am in the same boat. 1.35 has been causing lots of issues. How do I downgrade back to 1.34 ? i am using the HA add-on. |
Hi all. |
Hi, I also experienced a big network blackout but recovered almost all my devices after a hard reboot. Two of my devices are still "no network route". Those devices are very similar (TS0502B and YSR-MINI-01_dimmer). EDIT: The two devices mentioned had power issue. Nothing to do with Z2M. Everything’s fine now. |
Comment here to see solution, got this issues in both fw 1.34 and 1.35 |
I found this thread because I was having similar issues. A bunch of my devices go offline for extended periods. Removing them and trying to pair didn't work - they wouldn't pair. I rebooted my rock pi, it had power issues on boot, a usb drive kept clicking on and off. Changed power supply, no dice. Unplugged a google coral device that wasn't even in use and everything started working again. The coral was in a usb3 port next to the usb2 port my coordinator was plugged into. I suppose i should plug the coral back in and see if it causes an issue again, corals have two power/clock settings so I could try it on the lower one. I dont need it atm as I'm using the NPU onboard for frigate. |
I am running 1.36 Z2M - I integrated a Sonoff ZBMINIL2 and get lots of errors when I give commands either on Z2M web GUI or from H.A. Sometimes the command is executed after few minutes, sometimes never. The device is "disabled" in Z2N dashboard. 2024-03-20 15:50:43Error: Command 0x84ba20fffecf16d5/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 30569 - 1 - 24 - 6 - 11 after 10000ms) at Object.start (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:63:23) at EZSPAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:492:47) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.command (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:746:28) at Object.convertSet (/app/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:46:17) at Publish.onMQTTMessage (/app/lib/extension/publish.ts:259:36) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17) |
Mine is also like this arter updating to latest z2m . Does not work to roll back to earlier backup. Did somebody found a fix for this? |
Same here - happens for me with Edge as well as 1.36.1-1 |
I disconnected all electronics near my raspberry and coordinator. Moved my ssd drive away and restarted it and seems ok again. Updated to latest zigbee2mqtt and seems to work fine. So it seemes to bee some interference |
Hey there! I need to try downgrading my Z2m from 1.36.1 to 1.34.X so I can generate comparable logs, but here's debug logs (including herdsman) that show the problem: https://gist.github.com/evanfoster/7de176651bffba5df5b4d725d6f01d15 At 18:55:28, I double pressed Interestingly enough, it seems like the Here are all of the versions/about page info of all components in the critical path:
EDIT: I realize the LQI between the repeater plug and the plant light is low, so I'm poking my network to remove that as a factor. EDIT: I was having an irritatingly hard time improving things, so I'm going to get logs from another plug with an LQI of 148 that's doing the same thing. |
I had these same messages after CC1352P2 firmware update (CC1352P2_CC2652P_launchpad_coordinator_20240710.hex) on both TubesZB and SONOFF Universal Zigbee 3.0 USB Dongle Plus (ZBDongle-P) It may take some time for the network to stabilize after the update. Instead of waiting, I turned off all the devices in the entire house to force start completely. A couple of them appeared "offline" but had LQI value, sending several commands (on, off...) they appear again without problem |
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?
After upgrade to 1.35.0 there is really A LOT of traffic and errors on z2m and mqtt protocol. The UI error messages keeps spamming constantly. Eventually, it will reach 100% CPU thread utilization and automation stops responding. I've upgraded to newest firmware on CC1352P2, the issue persist.
I've cut 5 minutes of logs on 1.34 and 1.35 for comparison, 1.35 is twice as long in the same time on info level.
Here is just initial 10 lines containing 'error':
What did you expect to happen?
Work as usual.
How to reproduce it (minimal and precise)
Run 1.35.0 on CC1352P2.
Zigbee2MQTT version
1.35.0 commit: 3d8f0fc
Adapter firmware version
20230507
Adapter
CC1352P2
Debug log
zigbee2mqtt_daemon_1.34.log
zigbee2mqtt_daemon_1.35.log
The text was updated successfully, but these errors were encountered: