C8 Pro with about 44 zigbee devices. Have been working well for some time now. Over the last 3 days or so they have become completely useless.
I.e. In a scene with 8 bulbs, maybe 4 will turn on and off. Motion and door sensors not reporting, etc.
I have tried rebuilding the network. Switched channels and upped power. I haved tried repairing just offending devices, as well as EVERY single zigbee.
The only new addition was the Sonoff SNZB-06P sensors, but everyrhinfg worked with those for a few days, and it doesnt seem that devices routed through them correlate with failing devices.
Not sure what "tentative" gray connections mean, but I have a lot of them from my hub. Is that something to investigate.
Also should add I shutdown the hub, disconnected power, waited, then powered back on. Different devices are the problem each time, but always have about half being useless.
I suggest to add more mains-powered router devices to increase the robustness of your Zigbee network. I see that you have only 3 router devices that service most of the battery-powered devices.
If you're not against using community apps, you can try the [RELEASE] Zigbee Map app to get a better picture of your network. Maybe it will help to better investigate the problem. Disclaimer: I'm the developer of that app.
If this is still happening after a shutdown power off/on then if it was me I would remove the batteries from these so that they are not on your network.
At least it would prove if these devices are causing your issue.
There are a lot of red and purple lines between the Hub to the direct routers, which usually means the connection quality (LQI) is quite low. I guess that something is interfering with the radio signal, or they are too far.
But why would this suddenly become a problem? I had weeks of good results (no maps because I wasn't troubleshooting, but good results)
A scan of WiFi channels shows stuff on 1 and 6, and my ZigBee is on 25, so I'm doing what I can to deconflict there. The house is not that big so I don't think I should be pushing the limits that way. And with your app you can see there are a fair number of routers
I tried it without the new SNZB-06P (since they do act as routers.) Still having problems.
Is it odd that the neighbors map gets everything I would expect (everything except the disconnected motion sensors and the door contact sensors). But the routes map only gets 27 of 36, with 10 of those showing as "unknown". Is that indicative of low LQI or something weird?
Just my 2 cents but a couple of years ago when I was having issues the one thing I tried was changing channels.
That takes 24-48 hours to get the mesh and the devices all talking on the new freq.
So, changing it and seeing if it helps in an hour doesn't happen; that test is a patience game.
IMHO
In my experience, when a Zigbee network suddenly undergoes issues, an important thing to check is competing networks.
use a wifi analyzer program (on a smartphone) to check to see if there are any wifi networks (including your own) operating on the same frequency as your zigbee network.
use the network scanner feature to see if there are any Zigbee networks on the same frequency (these may be amazon alexa devices).
Please note: If you do decide to change channels, not all devices make the jump, even after 24-48 hours. These devices may have to be re-paired.
I've been having a few zigbee issues recently after working flawlessly for a couple of years. @jtmpush18's note above sparked a thought in my tiny mind to check my routers wi-fi channel. I have it fixed on 1.
Went in and checked and somehow my router setting had changed to channel optimisation enabled. (Maybe a router update ). It was using channel 11.
I've just changed it back to fixed on channel 1.
Just goes to show how things external to the HE hub can cause issues.
#3 True.
While I was away we had a power outage.
I had quite a few ZB go AWOL.
I find, in the last few months, that ZB repairing never works.
HE always says Device Found and re-paired but they never work again.
I have to delete them, re-add, and put them back into all the apps.
Case in point. I have an ST motion sensor that i had to delete as the re-pair did nothing.
I then spent 30 minutes trying to get it back - New device found and initializing everytime but never completes using all 3 methods (plain text, no repeaters and next to the hub).
I got it to pair once. It came back with all the old Current States before it was deleted and still didn't work.
Very odd. Todays project after the lawn.
In these cases I factory reset the device then re-pair it without deleting it.
This seems to work 100% of the time for me and saves having to repopulate all rules/pistons that the device is using.
I always factory reset and re-pair without deleting but nada.
I just finished with the ST motion and a Sengled light today. They wouldn't finish pairing until I deleted them.
I also found that the ST one from last night only paired after I shut down the hub and unplugged it for 10 minutes.
Still have these wayward devices to go after the outage even though they all still function.
May I also suggest another thing to do when you have this kind of issue?
(This is from my own personal experience.)
After I get a Zigbee mesh to some sort of stability, I use an excellent program from @dandanache (Thank you!), called Zigbee Map, and I select the first option Zigbee Neighbors App.
This excellent visual representation of my Zigbee mesh, shows repeaters, and weather or not they are alive and working.
Follow up on all repeaters that are coloured "magenta" - they are not responding for some reason.
Also, click on each repeater, and if you have a repeater whose links are all "red" - that's an issue to be followed up as well.
You should definitely do this, for me it picked up stuff that I didn't know about and allowed me to move my Zigbee to a better channel. It's in the settings then zigbee then scan channels.
I did, nothing to deconflict from and I was already deconflict from the wifi.
No idea why or how but my hubitat locked up entirely. After a power cycle it came back and now runs like it should (which is weird because I power cycles the hub during the troubleshooting, it's like locking up was the key)
). It was using channel 11.
