UPDATE! Help! Hubitat is becoming eratic! Database 543m and growing!

Chromecast polling has to be explicitly enabled in the app for the new code to run, is it enabled?

Can you ping me your hub's id? I can take a closer look at it.

With 2.2.8, a shutdown invokes database defrag and compact routines. That's why the message suggests rebooting first. I found that in many cases, a reboot is enough to get it back on track.

1 Like

I did try that first.
Shutdown, disconnect power, restart.

I did a reboot as well but it still came up with the warning. I do have the Chromecast polling on at 300 seconds.
Soft reset and restore worked.

My database size is down to 32 minnows and the temperature is only 96.8. I guess the soft reset and restore fixed a few things.

3 Likes

Do you have a link to instructions for Hubigraph?

I can't get to here:

Hub continues to behave erratically.

Temperature now 120 degrees F.

Database size only 7 minnows.

120 is on the higher side for a C7 but isn’t unusual for a spike. If it stays there you may want to see if something is in the way of the airflow, but in of itself not generally an issue. When I first got my C7 it stayed around 98-102F, now it seems to be a little higher (I may need to power it down and see if there is some dust that can be blown out).

1 Like

I was following this as my DB size was at 150mb and I could not figure out how to reduce it.

I had both my event history and state history set to 10 and it didn't make a difference.

I then found this URL,

http://[HUBIP]/hub/advanced/maxEventAgeDays --> set to 365
http://[HUBIP]/hub/advanced/maxDeviceStateAgeDays --> set to 7

I modified the maxEventAgeDays and set it to 30.

http://[HUBIP]/hub/advanced/maxEventAgeDays/30

After rebooting the hub, my database size dropped from 150 down to 21.

I'm not sure how this differs from the settings I had set in the runtime stats but it looks like it actually works.

Just dropping this here in case others find it helpful.

3 Likes

gopher.ny is on it.

Thanks!

1 Like