Ok, I haven't added anything but the Denon built in device for 2 zones, about 2 weeks ago, but it's now running out of memory daily. Sometimes it needs a reboot by pulling the plug.
This seems to get worse with each update I apply.
Please help!
T.
Mind me asking how do you know it's running out of memory?
Also, do you see anything in the Logs (past Log) that might explain what could be eating your hub's memory? Additionally, Device stats and Apps Stats tabs could tell you more details about what might be going wrong.
1 Like
It asks me to reboot
The past log showed an aquara vibration sensor, I don't use, making a LOT of events and, my Denon (that isn't connected) was making the second most on the list.
I erased the IP address from it and hopefully it will stop polling it. (The Denon is undergoing repair.)
I'll watch it for the next 24 hours. If you don't hear back from me on this subject, it is case closed.
1 Like
What is the rock bottom lowest the hub will go on memory? I'll set up a reboot at that stage.
A better question might be what is the memory level that triggers the reboot suggestion?
That is a better way to say it
An even better question is what causes the hub to panic? The reboot suggestion is to prevent a database lock (aka curruption). A hub shouldn't reach the "rock bottom" unless something is severely going wrong. Eliminating the problem, eliminates the need to reboot.
@abuttino what hub model do you have?
C7. Why does C8 have more memory?
No, but the C-8 has a different version of Java whose memory consumption profile differs from Java version on the C-7.
1 Like
What is the difference between the Java versions? x86 and x64?
No. It’s a newer version of Java. Both hubs have the same ARM processor.
2 Likes
Why don't they just match the versions then?
Take a local backup and then restore it right away. This also does a soft reset as part of the restore. This has fixed memory decline issues for myself and a bunch of others. Seems to be an issue that came up with 2.3.6 firmware but not sure what is causing it. So far since my soft reset weeks ago it has not returned.
4 Likes
I was really thinking about doing that. Glad to know I'm not alone. 
The newer version wasn’t available when the C-7 was released. And platform updates only update the platform JVM. Not Java itself or the underlying OS.
1 Like
Makes sense.
Thanks for the answer.
However the question just got buried.
What is the 'rock bottom' number where I should reboot
Usually the low memory is a sign of other underlying issues so the low limit ends up being different for everyone. Some people have reported other issues happening after getting down to 200mb which makes no sense since the hub still has plenty free to work with. So something else is going on that is causing the memory to drop and impact performance.
I would say getting down in the 100-150 range should be rare and is probably not a bad time to reboot. Juts be careful using a rule, you may want to us the 15 min avg number in case there is a large dip that is quickly recovered.
Still suggest the backup/restore as the first measure, it will likely solve the immediate problem.
1 Like
Personally I have mine reboot on 120k but I've been lower. That said, as @bobbyD says, find the issue that is causing the low memory condition. You've had to pull the plug several times. This alone can cause database corruption which can contribute to low memory. I would start with doing a soft reset and restore. This will ensure you have a clean database. Then disable any 3rd party apps. You also mention the aqara sensor. Possibly disable that too. Watch how things are. Use @thebearmay 's Hub Information Driver.
2 Likes
Well, I had to do the backup-restore, rebooted very late last night (4am) and woke up this morning to another warning on the notification section of Hubitat.
Still watching closely because, it hasn't been that long since a restore (3 or less months, I'm guessing)
On the first reboot after a soft-reset; does "Loading Apps" take a little extra time?
How is the best way to find this?
