Background info.
I noticed the odd zigbee device issue not reporting yesterday which led me to investigate what was happening.
I noticed an outlet was power reporting constantly which I assumed was the issue.
The device is a Salus SP600 which is using the Generic Zigbee Outlet.
On the device page it still showed an option for power reporting configuration.
This snapshot is from another SP600 that is still behaving OK.
I changed the device to another driver and then back to Generic Zigbee Outlet.
The power reporting option is now not available to configure.
The device still kept reporting power constantly though.
I changed the driver to a custom driver that will only report power every 2 minutes and things seem to have settled down again.
Long winded I know but now to my question for @support-agent .
Has this driver changed?
I've had a rummage through available Generic Zigbee drivers and cannot find one that gives a power reporting option.
Many Thanks.
I cannot speak to changes but can confirm that the Generic Zigbee Outlet driver is used on both power reporting and non-power reporting outlets. The difference I can see is the device data section where the powerCluster attribute is populated with a value on outlets that report power. Outlets that don’t have none.
Given it is Zigbee I would recommend resetting the device itself and repair it and hopefully the proper configuration will get updated in the device.
Thanks for the reply.
The issue as I see it is that before, the power reporting was configurable. It could be set to disabled and from 1W up to 500W at various steps up to that value.
Now it is not configurable, so if it is an outlet that reports power, it cannot be disabled and if it is particularly chatty, floods the zigbee network.
As said above, I have a custom driver that can be configured and seems to have done the trick.
I'm just wondering if there are now other people who are getting zigbee problems and it could be done to this driver change. Who knows.
Thanks again for the response.
As a mere data point, I am not having this issue. I have 7 outlets using the driver. My powerCluster is 0B04 on all. They are a mix of old Smartthings and Iris plugs but I'm pretty sure they are all Centralite made. C-8 on latest release.
I have 14 devices using the Generic Zigbee outlet driver
Iris - made by Centralite and support power reporting
Third Reality - model doesn't support power reporting
Innr - no power reporting
SmartThings - supports power reporting
Those that do support power reporting have a powerCluster value of 0B04 and those that don't have a value of none. When powerCluster is none the power reporting preferences do not show up.
Again if you haven't reset the zigbee device and pair again I would try that. Since it is Zigbee it will fall back into place with the linked device and not break your rules and apps. Hopefully that solves the issue. If not @mike.maxwell is the HE Zigbee expert.
Well that's interesting.
I have left the SP600 on my custom driver and did a factory reset and re-pair.
It is reporting at the interval I have set, every 2 minutes, and the powerCluster is showing as none.
It is reporting as I can see the power value change every 2 minutes.
It must be something to do with these devices and maybe the custom driver polls the power value. Not sure as I didn't write the driver. There is nothing for 'poll' in the scheduled jobs though.
I think I'll move all my SP600's to the custom driver in case the others start playing silly beggars.
I'll mark this as solved as I now know, thanks to @ritchierich, that the power preference only appears if the powerCluster is populated correctly.
The generic outlet driver runs some initial device testing when joined that includes reading the values of the various power reporting attributes, should these attributes report back then the powerCluster value is set, which enables the reporting preference.
Its not clear why the SP600 you have isn't responding to this as intended.
Hi @mike.maxwell and thanks for the info.
Since your message I've been having a play and it seems that the device in question is 'probably' going down the pan. I'm not completely sure but I've done a couple of power downs/factory reset/re-pair and it just doesn't pull down the powerCluster config. It always shows none.
I've tried the same with another device and this one does what it should.
Many thanks again to yourself and all of the above responses.
