You should change the Watts reports. Normally you want to select ONE but not all of the following. Disable the other two.
Minimum Watts Change
Minimum Watts Percent change
Seconds for Watts change
If you have all 3 on like your screenshot, you will get 3 or more reports. I would turn off Percentages and Time reporting and see what happens.
Same for your subwoofer, why is is giving dozens upon dozens of reports with unchanged values? You must have something configured very badly to have that amount of traffic. The watts didn't change in the 3 or so hours of these logs, so why do you need that many reports? That is totally wasted data at best, and at worst bogging down the hub.
Again, I would urge you to look at any devices that report power usage, and disable it or be extremely selective about what reports you are asking for.
So yesterday the hub was unresponsive as usual so I rebooted it through the diagnostic tool. This morning a rule that was supposed to turn on lights when the hub was in morning mode did not fire. I am about at my wit's end with this thing. I appreciate all the suggestions that I am receiving, but I feel like I'm getting nowhere fast.
The events show that it didn't fire today. Note that there should be modes for morning, day, evening and night every day and that these modes do not show up every day:
What else can I try to make my hub stop locking up so I can't access it on a daily basis? And if it would fire the rules that it is supposed to fire, that would be great as well.
I share your pain. Maybe something in this thread may help you. I've tried everything I know and still get regular slowdowns and issues (2 unprompted reboots today, one after the other)...
Have you tried powering it off Does it still freeze/lock up?
In seriousness though the C5 seems to have a hardware level issue that may very well be a heating issue as was identified early on by others but other than strapping a fan onto the unit there's no official stance or fix for this.
My C5 hub is on top of a table, open air, nothing hot around it. To your point, though, it doesn't have a fan blowing on it.
I will say that this is only the 2nd or 3rd time my dev C5 hub has locked up solid. Granted, I reboot it weekly on a schedule, and it is super lightly loaded - so it shouldn't EVER lock up... But it is what it is.
I believe my C5 experience to be the exception, not the rule, for the record.
For the first time (ever) in a full year I’ve managed to leave my hub running for a full week.... and it’s still running fast.
You know why, I’m doing absolutely no logic on the hub anymore. Lol! Which means, no apps besides maker, Hubitat package manager, and a couple custom drivers.
And like I said, this is only the 3rd time this has happened in the 4-5 months I've had this particular C5 (my previous one was defective, so I don't blame Hubitat for that ).
So it hasn't been a "big" problem or anything. I will flip it over when I get back home though, because - why not?
You need to do something about that subwoofer. Again, why do you have it reporting the same exact thing literally hundreds of times without even 0.01 Watt change? That shouldn't be happening. There is something grossly misconfigured with that device, or there is something wrong with it.
I will have to defer to @bobbyD or someone else about that damaged database warning, and those java.sql warnings.
Makes no difference. I turned mine over 2 days before this latest double reboot. Oh, maybe that's what caused it! See, we go round and round in circles with this...
That is EXACTLY what happened to my C5 - it was sitting on top of a smooth plastic surface (Sonos Connect) and would get lockups.. flipped it over and issues went away. Have a similar setup like @JasonJoel - no ZB/ZW, some virtual devices, no rule apps, maker api and alexa.
edit: that hub is no longer sitting on the Connect (now Port) but beside it on my desk, still upside down and functioning normally.
You don't want that temp stuff spamming your network anyways. Z-wave operates in the 800-900Mhz frequency range so the protocol doesn't have much bandwidth in the first place and it's just going to slow your stuff down. Zigbee is in the 2.4Ghz range operating in 2MHz channels and can have interference issues with other 2.4Ghz devices if you have a lot of them and a busy network. These channels aren't very wide either so it too is limited in the ammount of traffic it can handle. The lower the frequency the better it can penetrate but the less traffic it can handle.
The hub failed to trigger evening or night modes today. This is after rebooting the hub this morning and removing the questionable Aeotec smart outlet this afternoon that was reporting power often.
Here is an update and a copy of what I just emailed Bobby:
I am writing to follow up on this and provide updates on changes I have made.
I deleted the Aeotec "subwoofer" outlet.
I deleted the Leviton dining room dimmer switch. There were debug posts associated with it and I have no idea what they are about. I have four more of the exact same switch in the house and the others are working okay as far as I know.
The hub is not changing modes correctly. I manually changed to night mode the change from the web interface and it should have triggered lights to turn off, but that did not happen. So even if it does go into night mode, rules are not firing.
Right now it is 3:10 pm and the hub is still on night mode.
My Samsung zigbee buttons are not working as they should. The MBR Button (device) triggers through the MBR Lamp Button rule in RM. Last night I pressed the button one to turn the lamp off and the lamp dimmed, but then brightened again. It would never turn off with the button. The button has been working fine for months without issue until recently.
There is still a message on the web interface saying that the database is corrupted and was restored. It's been there for a day or two.
New debug issues from yesterday. Could they be related to a device I removed? None of the devices for force removed.
