The % of busy just ranks your apps most busy to least. That is not total CPU utilization.
The top stat line shows your hub was only busy with apps 8% of its total runtime. So of that 1h 17mins of "busy time", ActionTiles accounted for 51% of that.
I am guessing ActionTiles is getting every state change sent to it from the hub and possibly also polling the hub for updates. The only way to reduce its use would be to share less devices with it.
Another way of looking at that number is that ActionTiles was active 4.08% of the total time (0.08 * 0.51) which is pretty much just chilling.
Yes this is a c8
I understand , makes sense now. I think a lot of people look at these stats and kinda freak out because they don’t understand them. At least I did, however now that I understand it , it’s not a real big issue as I thought. Thanks
IIRC the default warning is at 300, So just enough to generate the warning. If it’s a one time occurence probably not a problem; if it continues you may want to look at why it is generating so many or just raise the limit slightly.
It’s a Zooz energy plug zen15 as I heard they can be chatty . I turned off most of the other features . Kept the power reporting to 30 seconds should I raise it up ?
@jtp10181 Thoughts?
Every power reporting device can be chatty -- it's just that some are better than others about giving you control over reporting parameters.
Zooz's devices are far better than most in that regard -- you can get very granular in how & when you want events reported.
With any power-reporting device, you should use whatever options you have to minimize the reporting down to just what you need.
Is having this Z15 report the dryer's 1%-incremented power status every 30" during the entire cycle really the best way to monitor it, or is there perhaps a way to do it that would require less reporting?
30 minutes would be fine as long as you don’t have dozens of them going. But do you need a power update every 30 minutes? Why not use a threshold?
30 minutes? Did you mean 30 seconds?
Unfortunately im not knowledgeable enough to know better. I know i set it all up in RM and its been working very well for two weeks. Im afraid if i change setting it will mess something up.
Yes I meant 30 seconds.
Understood thanks
Show us your rule and what you want it to do and maybe someone can improve it.
Is this known as polling? Also if i enter a new number/time do i have to save then click configure or just save ? Also will it delay my automations?
Also remember that the "Power Reporting Interval" and the "Power Report Percent Change" are different functions and report differently. Power consumption of devices fluctuates allot and as such a 1% change good generate multiple zwave messages a second.
A Cloths dryer is a high power consumption device. Have you graphed any of this data to know what the typical power usage trend is for the device.
What driver are you using @jtp10181 has great advanced drivers for many of the Zooz products you may want to take a look at that since it sounds like you are using a Zen15.
You need to really think about what is the least amount of reporting to get what you need and what settings are needed to accomplish that task. Adjust the potential power reporting settings to reflect that.
1% change seems very agressive and 30 seconds though doable may not be the best option either. I would suggest using one of the community tools for graphing to get a better picture of your actuall power usage and then find the best option s with that knowledge to enable the best settings.
Yes i have watched the power on the device many times. It normally sits around 200 - 300 watts with small peaks of 700-800 watts . Here is my rule
Also for my virtual device which is for echo announcement.
Why 200 in one and 280 in the other.
I think I would minimize the use of the %change value and set it to use something like the "Power (Watts) Reporting Threshold". It posts changed when the power changed by a certain amount. If you know your power usage is going to be around 200-300 you could set that value to 75 or 100 Watts and likely minimize the reporting considerably. It would still give you the needed reports to know when your devices goes over 200 Watts. Here are my settings on my Zen15 for my Washing machine. I trigger on 10 because it does allot of stuff in around 15 watts or so. Those preferences are with @jtp10181 advanced driver.
The sacrifice is always just the time it takes for the update to occur in Hubitat. Smaller changes may not trigger updates, but based on your rules you may not needed them.
Download the Hubitat app
