I’m still having to reboot my v3 hub after every firmware update in order to get the hub connected devices out of disconnected status in the new app. Anybody want some logs before I do it again this time?
After the previous update I started experiencing problems with a few of my SmartSense (specifically my Iris sensors zigbee sensors seem to be working fine.) motion and contact sensors disconnecting and not being able to reconnect (I use the classic app).
And after the current beta push even more of them have disconnected.
I’m not sure if it is related to the beta firmware update or something unrelated.
I sent an email to support a couple of days ago but haven’t heard back.
It so far is only affecting my SmartSense specific devices and only affecting zigbee devices.
I’m generally pretty good at troubleshooting but am really struggling to keep up with so many of them being offline and just not staying connected even after resetting the devices.
Is anyone else experiencing something similar and/or have any thoughts about what might be causing my problems?
I do not believe the regular ST support can assist when you are running beta firmware. I believe this is the appropriate forum along with centercode where you can open a ticket on this issue.
Out of a couple hundred devices only one of my locks went offline but I am not sure it is related to the update as I was already having some issues (it was not reporting lock/unlock so I excluded it and included it, then changed DTH to “local” one).
I believe @johnconstantelo had posted that he had lots of devices go offline and that he needed to reboot the hub… or something like that. John?
One thing you could try is to unplug the hub for 10 minutes. That should cause the zigbee mesh network to redefine the routes. It is the equivalent of a zwave network repair. I believe the hub has a limit of 32 or so zigbee devices. To add more, you need repeaters, so if routing is off, or a repeater is dead, I would expect similar issues. Just a shot in the dark…
There appears to be an issue with either OneApp or cloud services that causes devices to show up as disconnected in OneApp when they are connected in the Classic app and the Graph IDE. The issue doesn’t seem to be related to 0.25.x firmware, and the respective engineering teams are investigating.
Cool, I bet that will do the trick for you. You could also replaced some wall switches with GE’s zigbee wall switch. I have tons of those and they’re outstanding devices. Super fast, and extremely reliable.
I will probably do that although many of my switches are already the GE Z-wave in wall switches that said there are a few bedrooms that I could add them as well.
Thanks for the help… hopefully it works to improve my Zigbee Network.
(www.rboyapps.com - Making SmartThings Easy!)
Bulbs are like regular devices. They are specifically designed not to repeat because many folks turn off the main switches to the bulb sockets and if they acted like repeaters then it would disrupt communications as repeaters need to be online constantly. For that reason they intentionally do not repeat.
There’s nothing else in the hub’s event log to indicate anything going offline, or any other weird behavior. I wasn’t running a zwave repair either. Everything leading up to this were just a lot of pings, and then all of these messages, and then back again to a bunch of pings.