Ok, willdo.
1 Like
OK, after several weeks of stability, I had the behavior happen again. The last activity I see from the hub in the log was 11-07 09:00:54.035. When I checked this evening, there was no response from the GUI nor to pings of the IP address. Nobody has been at the property since around 18:00 on Sunday evening (11-06), so nobody pressing buttons or doing anything.
I remotely power cycled at 18:38 this evening, and the hub came back up. Any suggestions for further troubleshooting?
Since the last time the issue occurred, I had updated the device to 2.3.3.140.
I also added the hub information driver, although i had not done much with setting up a database, i see activity at 11-07 09:02:00 but nothing after that
Just a point to note. Power cycling as opposed to a controlled shutdown or reboot can cause database corruption. That corruption itself could potentially cause the hub to lockup necessitating a soft reset and restore to clean the database.
As it’s remote you might want to set up a VPN so you can troubleshoot. Even when the hub gui is not responsive you may be able to access the diagnostics page at hubipaddress:8081. That would allow you to reboot it, restore it.
4 Likes
Please be careful. Power cycling the hub like that can lead to corruption in which you will have to soft reset and restore again.
3 Likes
Understood, however, since there is no response either from the primary GUI or the diagnostics page at 8081, and the device's network interface is not pingable, it is unclear what the next steps are with a device that appears to be inert other than drawing power. I am open to suggestions.
What color is the light on the hub?
If it's green then hub is booted. I would press and hold the reset button on the bottom of the hub for 7 seconds. (It's the only round hole out of all the square ones) using a paper clip or toothpick. This will ONLY reset the network settings, not the hub. Then see if you can get to the hub.
1 Like
The device is physically remote, but the network involved is part of my larger private WAN, so network access is not an issue. No response to GUI, no response on the diagnostic port, and it is not pingable. At the moment, the device is in test/staging with a couple of buttons for evaluation purposes and is not yet deployed for active use. Given the trivial nature of this setup, its very concerning that the lockup behavior is occurring repeatedly.
Lockups can be caused by a few reasons. Rogue devices, badly written 3rd party drivers. Badly written 3rd party apps. Devices spamming the mesh because they're paired with s0 encryption (especially zooz stuff). Over power reporting by devices. A notorious offender is the zen 25. Also database corruption will cause lockups
I would still hit that reset button just to eliminate the issue
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
