VZM31-SN reporting 10x actual power

[Automat]

I just installed a blue series dimmer (VZM31-SN) in smart bulb mode with the load feeding 8 Hue recessed lights (for power reporting & ability to cut power if needed).

Most things are working as expected with zigbee2mqtt + Home Assistant, but the power reporting is wrong. Within z2m I’m seeing ~600W, but the load should be ~60W. It appears to be the same 10x factor as reported below, but I’ve not been able to fix it with a reconfigure or interview.

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

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 di…

Switch firmware = 2.18
Zigbee2mqtt version = 2.6.0

[Bengineer]

Hi there! This same issue is acknowledged as an issue in the following thread: VZM30-SN Power vs Energy Bug with HA Z2M - #11 by notsobright

It sounds like an engineer has been assigned to look into the issue and deploy a fix as needed.

[rohan]

This doesn’t look like the same issue. The VZM31 had an issue in the firmware that was fixed roughly ~1.5 years ago. I just checked a handful of my VZM31’s with Z2M and on firmware 2.18 and Z2M 2.6, I am not able to reproduce the issue.

Are you seeing this with multiple switches? Or just one switch?

[Automat]

I only have one Inovelli switch.

[Automat]

I tested again by removing the switch from the network, factory resetting, and pairing again. Still the same ~600W report.

[Bengineer]

Thanks for catching that @rohan! I didn’t notice that this involved the instantaneous power rather than the accumulated energy.

@Automat how are you measuring the real load or is this an assumption based on the expected load of the 8x Hue lights?

[Automat]

Both expected load as this model’s spec sheet states 8.5W (which would be 68 W max), and real load from monitoring whole house usage and toggling everything on/off.

[Automat]

It would also appear that (with default settings) neither active nor periodic power or energy reports are getting sent. Neither value changes unless I manually refresh it in z2m.

[rohan]

Sounds like your reporting settings didn’t get set correctly. Did you see any errors when adding the switch?

This is what the reporting settings look like on my switches:

[Automat]

Yes, I’ve seen the error below when joining:

2025-08-06 11:49:04z2m: Failed to configure '0x8c8b48fffe245c6a', attempt 1 (Error: ZCL command 0x8c8b48fffe245c6a/1 manuSpecificInovelli.read(["defaultLed6ColorWhenOn","defaultLed6ColorWhenOff","defaultLed6IntensityWhenOn","defaultLed6IntensityWhenOff","defaultLed7ColorWhenOn","defaultLed7ColorWhenOff","defaultLed7IntensityWhenOn","defaultLed7IntensityWhenOff","fanTimerMode","doubleTapClearNotifications"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4655,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:372:28) at Endpoint.zclCommand (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:1005:26) at Endpoint.read (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:481:29) at chunkedRead (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/inovelli.ts:2243:9) at configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/inovelli.ts:2344:13) at Object.configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/index.ts:363:21) at Configure.configure (/app/lib/extension/configure.ts:123:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:252:17))
2025-08-06 11:49:20z2m: Failed to configure '0x8c8b48fffe245c6a', attempt 2 (Error: ZCL command 0x8c8b48fffe245c6a/1 manuSpecificInovelli.read(["defaultLed6ColorWhenOn","defaultLed6ColorWhenOff","defaultLed6IntensityWhenOn","defaultLed6IntensityWhenOff","defaultLed7ColorWhenOn","defaultLed7ColorWhenOff","defaultLed7IntensityWhenOn","defaultLed7IntensityWhenOff","fanTimerMode","doubleTapClearNotifications"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4655,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:372:28) at Endpoint.zclCommand (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:1005:26) at Endpoint.read (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:481:29) at chunkedRead (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/inovelli.ts:2243:9) at configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/inovelli.ts:2344:13) at Object.configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/index.ts:363:21) at Configure.configure (/app/lib/extension/configure.ts:123:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:252:17))

And yes, I have a lot less reporting auto-generated:

[Bengineer]

This is just a guess, can you show us how the switch is bound to the coordinator in Z2M? A binding issue should have been cleared with the resets that you did but it’d be good to rule out something going on there. I remember reading some posts back in the day where certain clusters were not binding to the coordinator as expected.

Here’s an example from my network:

[Automat]

I checked each attribute in that error message, and it’s fanTimerMode that errors out.

[2025-08-06 19:55:01] z2m: Publish 'set' 'read' to 'Downstairs office switch' failed: 'Error: ZCL command 0x8c8b48fffe245c6a/1 manuSpecificInovelli.read(["fanTimerMode"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4655,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')'

[Automat]

@Bengineer

how the switch is bound to the coordinator in Z2M

[rohan]

Yep, that’s what I was expecting when I asked you about errors. This is an attribute that we just added to Z2M in the current month’s release since it was missing. It turns out that while the specs say it should be included in the VZM31, it’s currently missing on that device. I have a branch removing it temporarily from the VZM31 that I’ll push up shortly. I’ll link it here when it’s ready.

Edit: https://github.com/Koenkk/zigbee-herdsman-converters/pull/9756 is the change. Once that’s merged in, if you switch to the Z2M Edge/dev branch, and then reconfigure the device, it should set itself up correctly and fix the reporting and the multiplier setup. Since Z2M releases once a month, the next production release that will have this fix in it will be released on September 1st, 2025.

[Automat]

That did the trick. I pulled the edge addon once the appropriate commit was merged, reconfigured successfully, and was able to switch back to the stable addon without losing the correct power & energy readings. It now showed the expected 60W and properly reports when the lights are turned off.