Since updating my C8 hub to 2.4.2.158, when doing a reboot with a database rebuild sometimes the DB size goes up instead of down. Then the DB size is constant for several hours until my reboot RM rule sees an event that the DB size is high and does a reboot with a database rebuild. This time the DB size goes down.
Have logs and Watchtower trends showing this response.
After a rebuild, the DB is typically about 35 mb. The Scheduled Backup ran at 4:20 am this morning and did a rebuild at that time. At 8:50 pm the DB is 133 MB. I have raised the limit for my Reboot RM rule to 165 MB. Hopefully, the growth will slow down so it will make it to the next Scheduled Backup run at 4:20 am tomorrow morning.
The Reboot rule runs at 5;20 am. If the DB is small after the Scheduled Backup, the rule will just reset the high and low variables for CPU %, CPU temperature, free memory and DB size.
I have about 30 ZWave devices, 10 Zigbee devices and 8 Matter devices. Also about 40 hub variables.
After a week, the database consistently grows to about 160MB each day and then the Scheduled Backup does a database rebuild to get the size down to about 35MB. Edit The increasing size appears to be due to logging limits that I have set so I can see at least the last 30 hours in the log.
It's very interesting that I can dismiss both local and cloud backups in Scheduled Backup and it still does the database rebuild every day. When I change the scheduled time the database rebuild is done at that time. So I am sure the Scheduled Backup runs the database rebuild. @gopher.ny is it possible to turn off the database rebuild that's done by Scheduled Backup? I'd like to see how large the database grows. It seems to be log entries that increase the DB size.
My RM rule for rebooting the hub checks for the database size greater than a limit (200MB) and for Free Memory less than a limit (100MB). If either event occurs the rule executes a reboot with a database rebuild.