I see a lot of posts about this issue, but very few solutions.
I am not using any zigbee bulbs directly connected to Hubitat. I have hue lights but they are connected through the hue hub.
I have two TRĂ…DFRI outlets in my mesh (three now). I have a bunch of Tuya mmwave sensors that are plugged in and act as repeaters. I have 3 Xiaomi devices and a Tuya Soil sensor.
First, is there a solution or something obvious that I should be doing?
Second, if not, is there a way that I can can get it back up other than a reboot?
Third, how can I set up a notification so that I know that I have to reboot?
Make sure the 2.4 ghz channel on your router is 6 or below and that the zigbee channel on your hub is 20 or above.... Wifi and zigbee run on the same spectrum so wifi being more powerful can knock out zigbee.
Look at your logs and app stats and device stats. See if anything is a bit too chatty.
May I also suggest looking at an app commonly found on the android play store called "wi-fi analyzer" (I'm sure there is an IOS equivalent).
Look at the 2.4 spectrum, channel graph, which will show you all of your wifi channels in the area.
Are any overlapping your wifi with your pick for Zigbee?
Is there a strong conflicting signal on your choice for Zigbee channel?
Could my SmartThings or Hue hubs be impacting this? If so, is it a matter of proximity? (i.e. would increasing the separation for the hubs make a difference?
I tried this....
If anything it is worse.
I also tried to shut off the HE hub for 20 minutes to let the other devices "panic" and that did not fix the issue.
The mmWave sensor are chatty-ish, but I don't think it is excessive. What would you consider excessive?
Here are the logs from the most recent Zigbee shutdown...
I still have the "end" devices (non-repeaters) shut off (no batteries) so that I can identify the issue with the zigbee network without too many variables.
Note that the TRĂ…DFRI repeaters (in purple) seem to be struggling as much as the Tuya mmWave sensors. So, I do not believe that this is device related.
If they are on the same channel, yes. If they are on different channels unlikely (for zigbee anyway) There has been anecdotal evidence that z-wave interference between to close hubs can happen. For zigbee make your hub channel 20, make your hue bridge 25 and make your wifi 6 or under. If you're not using z-wave on your ST, is it possible to turn off the radio?
Last Saturday, I removed my 2 remaining mains-powered (repeater) ZigBee devices that weren't ZigBee 3.0...
Since then, my C8's ZigBee had been blissfully solid - this is the best stretch of ZigBee performance I've had thus far with my C8 (and I probably just jinxed it!)
Since going all ZB3.0 repeaters, all devices have all stayed online through numerous restarts, reboots, rebuilds etc -- that's a welcome change.
Previous things I did that helped were switching from channel 15 to 25, and dropping radio power to 4. This forced most devices through a repeater, which did help a little -- but I still routinely had devices eventually drop.
My 2.4 wifi (Eero) hangs out in lower channels and my Hue bridge is on ch 20.
This seems to indicate no interference with HE on channel 20.
No, but I am close to eliminating that.
Is there any easy way to tell what devices are 3.0 and which devices are not?
Knock wood, man! For God's sake, KNOCK WOOD!
@kkossev has two Tuya radars that are solid. So, I don't think that this is s device issue.
My channels don't seem to be overlapping. So, I don't think that this is an interference issue.
That leaves me with either
My HE is defective (or)
My HE is too close to something that is causing the repeaters to not reach it.
Unfortunately, I don't think there's anything in the UI that can tell you. I just know based on product descriptions. My (mains-powered) 3.0 repeaters are Inovelli Blues, a bunch of Innr plugs, 1 Aeotec Xi and a couple directly-paired new-generation Hue bulbs.
The 2 older devices I removed were Halo smoke detectors - those never gave me a problem, but they weren't ZB3.0 (I don't think?) and they were nearing EOL anyway.
If the problem lies in pre-3.0 repeaters, this still isn't good news for me. I'm not going to shell out $$ to placate a finicky hub. I appreciate all of the troubleshooting that you are all doing, but the cost of migrating to a C8 for established users seems to be skyrocketing!
Roger that, I hear ya -- I'm certainly not advocating everyone dump their powered pre-3.0 stuff, since this all may very well be just a happy coincidence. I'm still a loooong way from declaring victory, to say the least.
But if there is something to it, perhaps that nugget helps HE staff (and SiLabs?) get to the bottom of a firmware fix. Fingers crossed!!
These logs are not normal... You should not have 'motion is active' duplicated INFO logs. Seems like two instances of the driver are processing one and the same message from the device. I haven't seen something like that so far.
If you press Control-F to search for ""4 in 1" in HE Drivers Code page, do you see more than one driver named 'Tuya Multi Sensor 4 In 1' like in this screenshot?
