One thing I have noticed from your list of devices is that you may not have any ‘mains-powered’ zigbee devices acting as repeaters/routers. It looks like all of the zigbee devices that are direct-connected to the ST Hub (not the Hue Bulbs, as they use their own bridges) may be battery powered. Also, I believe there is a 32 device limit within Zigbee that you may be hitting if you don’t have any zigbee repeaters/routers.
Actually, when you said about Zigbee repeaters I realized one pattern change @JDRoberts was asking earlier. I recently added 6-7 new outlets to use as a zwave repeaters, 8 new motions detectors (only motion detectors are now over 25) and 5 water leak sensors (and this was roughly around 10 days ago) Since I already have old ones in place just added more of the same, I did not consider this as a pattern change
Actually, this might be it. I was for some reason only thinking about z-wave and totally missed the zigbee.
I will immediately get some zigbee repeaters because YES I DON’T have any electric powered ones.
I will do my research but any personal favorites (for repeater/routers)??/
Thank you @ogiewon
The 32 device limit is the total number of battery-powered zigbee devices (plus Sengled Element lightbulbs). Not just one device class. But every mains powered zigbee device ( except again Sengled element lightbulbs which are in the other group because they don’t repeat) can take some of the burden off of the hub.
The Lowe’s Iris smartplug 3210-L Is popular because of the unusual fact that it includes both A zigbee repeater and a zwave repeater.
I use a few Centralite based Zigbee outlets as repeaters. One is an original SmartThings outlet, the other is a more modern Lowes Iris outlet. These seem to work pretty well for me. I also have about 5 zigbee bulbs (Cree and GE Link) directly paired with the Hub. These might also be acting as Zigbee HA repeaters, but I am not 100% certain.
This kept happening to me a while back, but it was mostly my zigbee devices. My ST Presence Sensor and other devices kept going haywire or becoming unreachable at roughly the same time every night. It turned out that it was because my wife was turning on a 2.4 GHZ wireless headsets to watch TV at the same time. So if there is consistency in the times that it is happening, check to see what devices (even outside of the Smartthings environment) that might be using a 2.4 GHZ radio might be turning on at that time. Some examples are wireless headsets, microphones, RC cars/drones, microwaves, wifi cameras, etc. This at least speaks to the zigbee devices and possibly even your cameras.
Same for me, usually around 4:15am for about a minute most, but not all days. So far I can’t figure out what might be happening at that time other than perhaps my Internet is doing some quick reset. As it’s early morning hours I do not notice if any other devices are suffering.
Are you referring to the Wi-FI band they are connected to? Whether she makes calls or not, her phone being on 2.4GHz Wi-Fi is a red herring here. Any phone associated with Wi-Fi will connect to that Wi-Fi while it’s in range, regardless of calls being made. And then, unless you are using Wi-Fi calling, any calls are actually going via the cell network anyway.
Anyway, it’s unlikely the phone on 2.4 is an issue or just about everyone’s Zigbee network would be trash.
No, Which is why I have said since you first posted your device list that the problem you have described is not just a zigbee problem.
The problem you have described is the hub being unavailable for anything connected to the hub whether it is Z wave or zigbee or LAN, But your cloud to cloud devices still working fine.
There may be a lot of things you can do to improve the efficiency of both your Z wave and zigbee, and you’ve gotten lots of good suggestions about that, but none of those will help with your described problem of all your directly connected devices, regardless of protocol, all becoming unavailable at about the same time each night for four days in a row. And that included your Hue bridge and your Sonos speakers.
That’s not a Wi-Fi problem, it’s not local interference, it’s not a lack of repeaters. It’s the hub becoming unavailable.
So you need support to take a look at it, figure out what’s causing that, and get that fixed.
Then you can go ahead and work on all the other improvements that people are suggesting. But the basic issue where you have to reboot your hub every night Is not going to have anything to do with what Wi-Fi devices you have, in part because Wi-Fi doesn’t interfere with zwave.
And to add more targets to the dartboard if support hasn’t already gotten you squared away, take a look at the hub events in the IDE and see if there are any odd entries. Try to figure out which ones are a result of your manual reboots and which are not. Radio events, excessive pinging, no pinging for long periods, update attempts, etc.
(Jason "The Enabler" as deemed so by @Smart)
I’ve got six zigbee repeaters in my two story home… Things work great. I have around 50 to 60 zigbee devices that run on batteries.
The past week I have been having issues with hue bulbs not coming at all on or coming on at 10%… tonight for example I have to ask google 4 times to turn a lamp on… ST events on the app show all 4 events… for reference google links to ST and not the hue hub…
I’ve been hoping that the platform improved so I didn’t have to migrate to the other platform but when all you are asking for is lighting to come on when you ask and the platform can’t even manage that then you have to question the commitment of the team behind it…
I work in IT and I would have been fired by now if I had delivered a platform with this track record