Ok using Homey Bridge for my controllers and the homey is SHS on Pi.
So after the upgrade to 12.12.0, all zigbee devices failed. As mentioned, my device controller is using the Homey Bridge. All other devices work, like zwave, matter, wifi…. Just Zigbee. I shut down both the PI-5 box and the Bridge for 10 minutes, removed power from several zigbee devices and then turned it back on. Same result.
In the docker logs I see the following - any one know what to do.
eb 26 15:25:20 homey-pi docker[5576]: Homey [err][ManagerZigbee] Failed to send ZCL frame Zigbee Node Unreachable: ZNwkNoRoute
Feb 26 15:25:20 homey-pi docker[5576]: zigbee:controller:node:b0:ce:18:14:03:53:44:70 route discovery skipped (per-node debounce)
Feb 26 15:25:21 homey-pi docker[5576]: zigbee:controller:node:b0:ce:18:14:03:53:54:76 route discovery skipped (per-node debounce)
Feb 26 15:25:21 homey-pi docker[5576]: zigbee:controller:node:b0:ce:18:14:03:53:44:70 route discovery skipped (per-node debounce)
Feb 26 15:25:21 homey-pi docker[5576]: Homey [err][ManagerZigbee] Failed to send ZCL frame Zigbee Node Unreachable: ZNwkNoRoute
Feb 26 15:25:21 homey-pi docker[5576]: Server HTTP GET /manager/devices/device
Feb 26 15:25:21 homey-pi docker[5576]: Server HTTP GET /manager/devices/device → Success 200
Feb 26 15:25:21 homey-pi docker[5576]: zigbee:controller:node:b0:ce:18:14:03:53:54:76 route discovery skipped (per-node debounce)
Hi, I have exactly the same problem, after the update of Homey SHS to 12.12.0 the zigbee devices became unreachable but Homey Bridge was showing as if it was ok on Homey app. If I rebooted Homey Bridge everything worked for 2-3min, then dead again. Today, Homey Bridge appears disconnected, if I reboot it joins my Wifi network and a few minutes later drops connection and goes offline. I have no more ideas, I will report malfunction and return it. Zero reliability, bought it 1 month ago and fails at the first software update? I was planning on using Homey on some clients but I’m affraid now.
The issue sounds like an untested mismatch with SHS & Bridge zigbee stack.
Often the good old “did you restart it” still is a good starting point:
To reset the bridge → power it up whilst out of reach to it’s known wifi / or temporary disable wifi.
After a while, when it can’t connect, it restarts with factory settings.
Odd. When OTA firmware updates go south, it’s most probably due to network hickups. Apparently there’s no verify functionality onboard.
Yes you probably would have to re-pair your zigbee devices after performing a factory reset.
They’re still there @ Homey, so when they’re repaired, all settings and flows (flowcards) should be back.
So for the question that was asked why I upgraded? It is the latest stable version and even when you go into support it states “You are not at the latest stable version upgrade first”. So I did.
So I reset the Homey Bridge as suggested and of course all zigbee devices we unreachable. I tried to do a repair, but it came up with device paired to another network. So I had to do a full reset of each device. I tried two of them and it worked, but even though named same thing, the object was# is different so the cards in the basic flows did not work and had to reset them also. This was going to be a pain as I have 27 zigbee devices.
Another strange thing, going into the developer portal, I see all the unpaired zigbee devices, it shows recent last seen values, I can even ping them and interrogate them getting a valid JSON package back. Which is odd as if they had a different network key, then they should not be accessible.
Also, 4 days after submitting the issue with my devices down, no response from support just the customary 3-4 days response time email. Since the only reason I have the bridge is to connect to my zigbee devices, I’ll switch them all to matter and pull the bridge. This is the second time since moving to homey from HA which worked great just was a huge overhead. I have several matter devices now (WiFi not Thread) and they paired easily and work great. Mainly lights, power and a couple of presence sensors.
Bottom line, the upgrade code should prevent errors like this. If the firmware does not update properly, then a fall back should occur.
My bridge now only has a white ring…totally useless. I ended up using a Sonoff Dongle Max with MQTT installed on docker. Everything is working. @Garrett_Gauthier1 next time use this code on the developer tools webpage: .gitignore · GitHub
It replaces the old IDs with the new ones to fix the flows. (don’t forget to put softRun=false).
Updated SHS to 12.12 and all Tuya Zigbee sockets are now offline. Thats most if my house. Ive tried with one and the Repair function is failing.
Ive deleted one to re-add it. It fails.
Ive taken snapshots of my vm before update but this sucks.
They obviously form the backbones of my zigbee network so i cant have them all going offline as it will affect the end devices.
Anyone else had this?
I have a support ticket in, its been 3 weeks. Ive checked on its status today when going to submit a ticket for this zigbee issues and its closed with no reply at all.
