Can you show the settings for the dryer sensor? You didn't include them in your screenshots. You seem to be getting excessive temperature reports for some reason.
What is the light switch brand and model number for the second screenshot?
I think the brand of light switch in the screen shot in the previous post is GE. Can the brand be determined by the "inClusters" or "manufacturer" number listed in the device settings?
I am not sure if anything else is reporting power.
Here is another strange thing. I just looked in the logs and it states that subwoofer power is off [physical]. Does that mean that it was physically turned off? I did not physically switch it off and nobody else in my house did either.
To my slightly experienced eye, you have some weird things going on there. Why are you getting 4 subwoofer "Ons" in about a tenth of a second? Your dryer sensor is reporting every 30 seconds or so even when you have it set to 4 minute reporting?
I would love to see a longer log of everything that happens in say 20 or 30 minutes. I bet that some device or devices are just slamming your hub for some reason.
It does look like that one switch is a GE/Jasco dimmer. What are the rules associated with this dimmer? It appears that you have this associated with at least 3 rules or more? (plus the paused rule) What exactly are these rules and how are you using button controller?
That dryer sensor is producing a lot of logs and duplicate events. That is usual connected to weak mesh and or device issue. I think you should remove it and see if things improve.
Secondly what is app 2? It's spamming the hub and it doesn't know what it is, that sounds like cloud based a app or driver that you have removed from HE but not removed HE from the cloud location.
That is the same things I said above. Not sure the reluctance to investigate that. These little log snippets and partial screenshots are making it hard to get the whole picture.
@hughlipham you are going to have to try some stuff and help us out by providing better data. I can see why you likely aren't getting anywhere with support, they are probably having the same hard time that we are getting information from you.
I also changed the driver for the Aeon-Labs Smart Energy Switch DSC06106 to a different stock driver, Aeotec Smart Energy Switch, so now there are a lot of log entries for power reporting. Similar to the dryer sensor, which is now removed, the Aeotec switch is reporting energy three times per minute and I have the device details set up to report every 5 minutes.
Thanks for all of the ideas, everyone. I'll let it ride with the changes made in the last 12 hours and see if anything changes. I have also enabled debug logging and descriptiveText logging for all of my devices (only 27 devices).
This should turn it self off in 30mins which is good because that kind of logging is likely to big the hub down more. I tend to turn off ALL logging and only turn on with the device I am working with/ investigating. This at least allows you to see the wood through the trees in the logs aswell.
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.