Incorrect power reporting by a factor of ×10 (blue series dimmer)

Product Support
, , , , , ,
1

Greetings,

I have a few blue series dimmers connected to Home Assistant. All but one of them have been used before connected to Hubitat. Now that I have switched to Home Assistant, I am receiving incorrect power values. They appear to be incorrect by a multiplier of 10. I have one dimmer that is reporting 351W when there only is 35W on that circuit. Another is reporting 410W and similarly there only is 41W of load on that circuit. Power reporting when off is correct (0.0W). Other blue series dimmers in the same house connected in the same manner report the exact correct values. All of these are installed single pole with neutrals. Firmware is v2.18 (on all dimmers in the house in fact).

I have tried factory default resetting them and that has no effect. I also have tried adjusting various settings (using Z2M in HA here) including the power calibration and that has no effect. One of the dimmers is new, never used, and purchased only one month ago.

Has anyone seen this? What can I do to correct this issue? I do use power reporting as a way of roughly measuring energy efficiency so having this work correctly (and without an after the fact mathematical correction) is important to me.

Thanks,
Richard

*Perhaps a coincidence but in the same installation I have a similar ×10 error factor around a different value: Incorrect ramp timing by a factor of ×10 (blue series dimmer)

2

There was a divide by 10 error that was corrected early on in the Hubitat and ST Edge drivers. Probably the same issue never corrected on the HA side.

3

It’s weird that it affects only dimmers and not others? How would I pursue a fix?

4

@chack should be able to point you in the right direction!

1 Like
5

I know this should be working as expected with ZHA, but unfortunately I don’t have a lot of familiarity with Z2M. I’ll take a look at the converter and see if I can find anything glaring though.

Edit - @rohan looks like he’s made some updates in the last few months, tagging him here if he’s got a quicker solution :slight_smile:

2 Likes
6

I’ve been doing a lot of cleanup to the converter in Z2M. As part of that, I moved power monitoring to use the defaults provided by querying the switch rather than the custom configuration that was present. Assuming the multiplier wasn’t fixed in the firmware, that may have broken it.

Let me take a look and circle back in a day or so.

2 Likes
7

I confirmed with @EricM_Inovelli that the firmware bug was fixed a long time ago and the switch should be reporting correctly and no longer needs the custom configuration. I also checked a couple of my switches running firmware 2.18 on Z2M and they are fine. Can you confirm that you’re running Z2M version 2.1.1 and then “reconfigure” one of the switches and see if that sorts it out?

2 Likes
8

I can confirm Z2M of v2.1.1. I can confirm that reconfiguring corrects the issue. This is surprising since I attempted reconfiguring a few times before but it was unsuccessful. Was this a fix that was part of Z2M v2.1.1? I recently applied that update and I have not tried to fix this since.

Edit: @rohan with a bit of optimism I thought to try a similar fix to my other ×10 problem (Incorrect ramp timing by a factor of ×10 (blue series dimmer)) but in this case a reconfigure did not fix the issue.

9

I added some logic to the converter that does a refresh of every single parameter when the reconfigure is done. It went out in Z2M v2.1.1.

My best guess is something was stuck in Z2M and the reconfigure sorted it out.

I do not know about your other 10x issue. But it doesn’t sound like a coordinator problem.

2 Likes
10

@rohan this is helpful and I really appreciate the quick response (and fix). Thanks so much! :rocket:

1 Like
11

This topic was automatically closed 67 days after the last reply. New replies are no longer allowed.