I have a C7 that keeps dying. I checked the logs and found the Tuya integration was hogging a lot of time and so was my HousePanel app, so I removed both and rebooted. It kept dying so I am stumped. Any advice on what to look for?
What color is the light when it dies?
do you have jumbo frames turned on anywhere in your network?
When did this start happening?
Light stays green. I don’t know what jumbo frames are so guessing I don’t use them. This started about 4 weeks ago. I travel a lot so troubleshooting has been difficult. My wife unplugs and replugs it to bring it back to life and then I check things remotely. Everything looks normal and it works great and then just dies again about a week later. I’m coming home today and plan to focus on troubleshooting so ideas are welcome.
I got home, rebooted the hub and started monitoring logs. Nothing looks out of the ordinary. No errors and no hogging devices or apps. The only one that is above 10% is the Rachio community app at 21% and a light automation in my bedroom where I walk in and out of a lot at 24%. Everything else is mid to low single digits. And all the device stats are mid to low single digits. Nothing weird in hub events either. This hub has most of my WiFi integrations including Bond, Rachio, Sonos, Harmony, and Maker API for Node Red so I wonder if that is giving it fits, but it shouldn't.
I'm on an slightly older firmware version 2.3.8.140 so next I'll try upgrading to the latest 2.3.9.154 to see if that helps. My last resort will be to dump the hub and try to squeeze everything onto my good hub which is a new C8 Pro so it should be able to handle it.
with all that unplugging (dirty shutdown) I would do a soft reset and restore first before anything.
Note: Some routers turn on jumbo frames by default.
Or a reboot with a database rebuild.
he's on 2.3.8. I would do the soft reset before updating to 2.3.9
Thought we had it under 2.3.8 but I could be wrong (seems to happen more frequently as the number of revolutions around the sun increases 
)
I think 2.3.7 introduced the rebuild DB with reboot, for sure it was in 2.3.8
Only possible issue with 2.3.8 was the runaway z-wave debugging log which eventually leads to false database corruption errors. 2.3.8.140 was supposed to fix and clean it up, but to be extra safe if having issues a Soft Reset with the Log Purge would be an extra safety measure to clear out any old logs. I am not sure if the reboot / log purge option cleans the same logs since the instructions from staff was to do the soft reset method.
2 Likes
Thanks all. I updated to the latest and will now do a rebuild. The update to the problem hub went great. The update to my good hub went bad... really bad. I no longer have access to it, so something went really wrong. I can't log into the main page anymore. What can I do? In the meantime I will proceed with a DB rebuild on the other hub.
I can't even get to the :8081 diagnostics page
What the heck do I do?
You updated from 2.3.8.140 to current and now its offline?
Are you on site or is it remote?
I would want to know the LED color and also, I would try to power cycle it.
If it was on anything below 2.3.8.140 it possibly had the runaway log file and got stuck, but the diag tool should still be working.
yes, and light is green.
power cycling now.
Hub set to Static IP or DHCP?
If Static you could do a network reset to get it back on DHCP. I think there were some cases where updates broke the static IP config.
1 Like
That is what happened... I rebooted and reset my IP and now I'm back. I was on WiFi and had to go back to wired to get back online.
1 Like
Good news. The Wifi config must have gotten broken with the update somehow.
Is your SSID hidden? Someone else reported issues with a hidden SSID and I asked some questions but they never followed up again.
1 Like
My SSID isn't hidden but i have eero routers which have weird behavior sometimes. I am back to wired for now which is fine. Now I'm back to fixing the C7 hub doing the rebuild and log purge suggested above. Thanks for that advice. I am hopeful that will fix the frequent dying. I'll report back in a week or so with progress.
2 Likes
One more update just to fully close the loop on this topic, and then I'll mark one of the above as the solution. My hub has been up and stable for the most part since rebooting, upgrading, and rebuilding the database - once I sorted out the wonky eero IP issue. One final issue I'm having is the Homebridge built-in integration has stopped a few times on me, but it came back both times after I did a hub reboot. I have no clue what is causing it and I've poured over the logs without any clues. As this point I'm concluding that the C7 hub just isn't as robust as the C8 Pro so I may upgrade to the C8 Pro for good measure, since these hubs are not that expensive relative to the investment in devices and time. I'm grateful to this community to be on this multi-year smart home journey with me.
3 Likes
The 8Pro is a noticable step up from the 7/8 in terms of processing smoothness and speed - you'll dig it!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
