Zigbee Power Plug High Percent of Busy Time

[laurie.street]

I have a C-8 on 2.4.3.133 and several power plugs - I have 6 Z-Wave plugs and 6 zigbee plugs.
the 6 Zigbee plugs are the top 6 of the '% of busy' with 19.6% -> 10.7% and the next highest is 1.3%. For what it's worth the next 6 devices sorted by '& of busy' are the zwave power plugs.

Is this normal? Is this something I should worry about and try and change or fix?
I have followed the doco on the zwave plugs in trying to reduce information sent to the hubto stop over-processing.

Cheers!

[hydro311]

I'm guessing you're talking about power-reporting plugs?

If so, then yeah, they can definitely be troublesome in terms of overwhelming chattiness if their reporting parameters aren't well-pruned.

If you don't need the power-reporting features, then disable what you can (or just get non-pwr-reporting hardware versions). If you do need the reporting, then take advantage of any possible parameter settings to minimize the reporting down to your basic needs.

If the plugs don't offer options to hone down the reporting, I'd replace them with better-featured versions that do.

[Ranchitat]

@laurie.street

Is this something I should worry about

Is everything working as expected?
If it's working, it's fine.

Hub Stats: When is "Busy" too Busy

My general rule, if the hub isn't "busy", and everything is running smoothly then the numbers don't matter, i.e. 47% of 1% is 0.47%. Now if your hub is consistently sitting at 75% busy or more, then maybe we start looking to see what we can do to free up some resources.

[RELEASE] Hub Information Driver v3

Driver is a large scale rewrite of the original driver and brings added flexibility in the gathering of ~60 attributes related to general operation of the hub. Driver allows the assignment of these attributes to one of 4 user selectable polling queues and intervals in an effort to allow the impact of the data polling to be minimized (I average around 0.12% of total or less), and the generation of an html attribute for display on a dashboard (template is a text file that may be edited to allow …

[laurie.street]

@hydro311

I'm guessing you're talking about power-reporting plugs?

Yes - power reporting plug. I would prefer sort fairly accurate data - which I guess means busyness on the hub.

@Ranchitat

Is everything working as expected?

Mostly, like 90% of the time, maybe even higher. Every once in a while automation's won't trigger. Lights won't turn on or stop responding to on/off commands from mobile device(s) and need to be physically turned on/off. Last night the physical switch for a light didn't work but the module still responded to toggle from a mobile device.

I have since updated and rebooted the hub but haven't tested that physical switch out just yet.

Just doing some prelim investigation - the hub has been working well, rebooting almost exclusively when it's updated.

Cheers!

[MrFarmer]

Hi,

For power reporting you should aim to keep the reporting frequency under once per minute to avoid load issues. I know having a lot of updates give an idea of control and can trigger some automation's but after some initial monitoring that typically becomes less important and a one minute delay for most triggers is not an issue. As well the attention typically moves to monitoring the energy used (my 10 year experience) rater than power.

I also have some automation's where the current power usage is relevant, however this is typically just for a few minutes. For example after turning a device on. For those scenarios I add a Refresh command and a short wait to get a current power reading. The rest of the day power updates are much less frequent, but also not needed.

So with some tweaking and creativity you can avoid this high usage and more important occasional trigger misses.

Cheers René