Just looked at my HE and it appears to have ceased many functions since midnight.
Log shows countless errors on many devices and looks serious to me.
Have not done any firmware updates in months. Done a reboot and waiting to see what happens now.
Appears to have lost comms with the internet. I have several http posts sending data to a web-server which have also failed. Have also rebooted my router.
Any ideas whats going on here?
Using the Diagnostic Menu, you should be able to reboot to Safe Mode. Logs would then show you if this continues. It works by shutting the Apps. You can reboot and use the disable column in Apps to do much the same thing. Once you've found, in a 'big hammer way' what's causing it, you can start to re-enable slowly and narrow down to the fault.
There's a grey X that, when clicked, turns red and...
... adds a Disable column:
You may find that a Restore to a days old backup might provide a clue or two.
My guess is some of those devices got into a bad state, started hammering requests, and the hub clamped them down because of high resource utilization (the latter part is not a guess; that's what the logs are telling you).
I would disable the devices, reboot the hub, then re-enable them one by one making sure they come up properly.
This happened to the hub of a client of mine.
A reboot will retrieve the lost memory.
I suggest putting in the the following rule machine that will do a reboot automatically if the memory gets to be too low:
(Please note: this requires the Hub Information device available from HPM)
If the reboot did not fix it, try shutting down and pulling power for 30 seconds then boot back up.
I would guess that all those devices generating errors are LAN/Cloud integrations and not Z devices?
My guess too. I have this happen with some MagicHome RGB controllers. Once the driver stops talking to the device, the driver will continuously try to reconnect eventually leading to the same errors. By the time I find it, I have to go through the process I mentioned above to get the hub to relax.
thanks everyone.
A reboot appears to have cleared the issue.
The unit has been running for hundreds of days without issues.
Could it be an accumulation of logs eating up the memory?
Is it good practice to do a reboot every so often to clear out the cob-webs?
thanks again everyone
The MagicHome drivers must have especially bad error handling. I had those same drivers killing someone elses hub I was working on. Ended up just removing them as he was not using the devices anymore. Hence the errors, devices were offline but driver just kept trying over and over again forever.
How can we inspect/check the memory status to see if its running low?
And what would be considered a dangerously low amount?
Am i correct in thinking that old logs get purged?
Is this based on the size of the log-memory or purged by time/date?
I would suggest the community app Hub Information Driver.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
