I'm running a C7, and updated to 2.5.0.123, between 17-22 days ago based on release dates.
Since updating, an automation that triggers if a contact sensor is open, and causes a light to blink, has not worked, because the light "blinks" so slowly it is not possible to tell that it is actually blinking, and the hub load becomes severe.
Automation has worked fine for about a year, and the issue seems to correlate with updating to 2.5.0.123. What happens now is the "blinking" is so slow and the hub load gets severe. First the log shows 100's of errors (if I click on the red error, it calls out the Jasco plug dimmer), then an attempt to turn off the light via the plug dimmer (I guess the off part of the blink) fails, then the light is slowly dimmed, so the log looks like the below and then it does the same in reverse...:
I've not changed anything related to this action so the only thing I can imagine is impacting it is the update to 2.5.0...
Any suggestions to fix this?
(I'm updating to 2.5.0.136, but did not see anything in the release notes that looks to me like it addresses this type of issue).
Every now and then one of my hubs will have high CPU after a firmware update. It doesn’t happen with every update. Rebooting with a database rebuild usually solves it, though sometimes a second reboot with database rebuild is necessary.
I just always save a copy of the databse to both cloud and pc before every update, and then follow the update with a reboot with rebuild as part of my usual process.
That said, I have also noticed that my memory gets lower faster on the most recent update (C7 also). I have had to do two reboots with rebuild SINCE the update because memory was getting low.
It always seems to be after something integrated with Home Assistant (over MakerAPI and/or HADB) for me. Right now, it is just in the anecdotal information phase for me. Nothing I can reproduce.
Same here on a C5. I rolled back to 2.4.4.156 and the memory leak is back to "normal." Memory will stabilize and no reboots required for weeks or months. With the 2.5.5 series I was having to reboot every couple of days. I was wondering if it was only me....
Update: Rebooted with a database rebuild about 4+ hours ago, and ever since things seem to be MUCH quicker, and seem to be working. The caveat is that the contact sensor was closed so the blinking light did not need to trigger. Tomorrow, if I can remember, I'll purposely have the contact sensor open to trigger the blinking light and see how that goes.
Update: I purposely left the contact sensor open to trigger the blinking light, and the automation worked, so the reboot/rebuild database processs seems to have (at least temporarily) fixed the issues I was experiencing.
