Hub Keeps Crashing

Anywhere from once a month to every other week, the hub stops responding. Can't ping it, doesn't respond to commands. I have to power cycle it to get it back. It only started happening since we got the new hub model. It's becoming more frequent and more disruptive. Anyone have any thoughts or is experiencing the same thing? Thanks!

There are a bunch of threads on the forum covering the same types of issues.

So since you said new hub model I assume you have a C8.

When it goes down, can you connect to the diagnostic tool on port 8081? You log in with the ethernet MAC (on sticker on bottom).

Need to know what platform/firmware hub is running.
How is it connected? Ethernet / Wifi?
How is it being powered.
Brief explanation of network topology.
Brief explanation of firewall / DNS / DHCP services.
How many devices total (approx). How many of those are LAN/IP/Cloud based?
How many (and what exactly) user / custom integrations are you using (especially for any LAN/IP/Cloud based connections).

Oh also, the VERY FIRST THING to do would be go to Settings > Backup. Take a local backup and download it, then immediately restore. This does a soft reset at the same time as the restore. It will clear out any database issues from pulling power or just garbage. This has been shown to also solve some memory issues that cropped up in 2.3.6 firmware.

2 Likes

Thanks for the prompt reply! I'll try the backup and restore first, then check the diags when/ if it happens again. I'll gather the other info as well in the meantime.

Platform Version
2.3.6.146

Hardware Version
C-8

Usb power, network is pretty basic, wired hub,
dhcp and dns via router. About 85 devices, mix of zw and zig. Pretty sure they are all lan/local (outlets and dimmers,a few relays and buttons. No real custom integrations or apps, just Alexa.

Plugged into the supplied block, or..?

Zwave and Zigbee are not LAN. Sounds like you may not have any IP/LAN based devices?

Supplied block, yes. Sorry, I just meant local. Correct, no wifi or wired devices.

Well you just knocked out about 90% of the usual angles on this.
Try the backup/restore, and if it happens again try to access the diagnostic port 8081. That tells us if the main OS locked up, or the entire hub went offline due to a networking issue or something.

Also, when it locks up, do any automations that don't rely on internet connectivity still work? (Sometimes the hub is still running but just gets knocked offline)

I don't believe they work, buttons that run routines don't work, and usually what I notice first are that the outdoor lights don't turn off at 1am on their usual schedule. Thanks again!

1 Like

While I can appreciate that method, it seems we've been chasing memory issues, in one form or another, for quite some time and it would seem the central issue has not been 100% fixed. Would you agree?

Yes they have been chasing memory issues of various types, but no I won't agree that there is a "central issue" that isn't getting fixed.

I would also say that not everyone is affected by these memory issues. Some have severe issues, and others never any issues. Why the difference?

I think that is the problem, exactly what device, app, or combination thereof is bombing some people out? There are so many combos that it is nearly impossible to track down a root cause, if one even were to exist.

2 Likes

How is this related to the OP’s issue?

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.