Zooz 800 series Zen 15 Not Reporting kWh Accurately

[bgreet]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
Zwave JS UI to home assistant is reporting a falsely elevated kWh report. It records a device using much more kWh than it should and this reporting jumps over 5 minutes instead of what would normally be seen with a slow upward curve.

I have 8 Zen15 800 series and it seems to affect all of these devices. Older Zen15 on 700 series chip does not seem to be affected (two are on my network).

What did you expect to happen instead?
Accurate data reporting

Steps to reproduce the behavior:

1. Include Zen 15 800 series with S2 security
2. Update to latest firmware (though also happens with older firmware)
3. Plug in device and monitor kWh over time

Anything else we should know?

Please see below picture examples of reporting on 8/12/24:

Utility output room zen15 inaccuracy occurred at 725pm to 730pm. It is node 002 in zwavejs UI. 800 series zen15 Firmware 2.10

Electric Freezer zen15 is node 054. Inaccuracies occurred sampling between 08:25am and 08:30am and 8:05 to 8:10pm. 800 series zen15 Firmware 2.10

3D printer switch is node 014. Error in reporting occurred between 0725 and 0730am. 800 series zen15 Firmware 2.0

Software versions

ZWAVE JS UI run as docker container, Home Assistant run as docker container

zwave-js-ui: 9.17.0.4f4bb9d
zwave-js: 13.1.0
Z wave controller: Zooz ZSET39 LR Firmware 1.40

Device information

Manufacturer: Zooz
Model name: Zen15 800 series
Node ID:
002
003
013
014
054
074
075
091

The device nodes given in this example, however, are nodes 002, 014 and 054

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwavejs_2024-08-12.zip

[AlCalzone]

You'll have to make a different log if we want to prove this is a device issue. The problem is that the encrypted payload is never logged in plaintext, so decoding the meter reading by hand isn't possible. To do so, execute the following driver function:

process.env.NODE_ENV = "development"

This will enable plaintext logging of several encryption-related things. If you look at the written logfile, you should see the plaintext being logged, similar to this:

└─[Security2CCMessageEncapsulation]
  │ sequence number: 79
  │ security class:  S2_Authenticated
  │ plaintext:       0x...

Afterwards, keep Z-UI running until you've captured such an event again. Once you're done, unset the env variable again:

process.env.NODE_ENV = ""

You may want to send me that logfile privately, so I can remove sensitive information before uploading it.

[bgreet]

Thank you so much for looking into this. Will look to get you this tonight when I get home from work

…

On Thu, Aug 15, 2024, 2:38 AM AlCalzone ***@***.***> wrote: You'll have to make a different log if we want to prove this is a device issue. The problem is that the encrypted payload is never logged in plaintext, so decoding the meter reading by hand isn't possible. To do so, execute the following driver function <https://zwave-js.github.io/zwave-js-ui/#/usage/driver_function?id=examples> : process.env.NODE_ENV = "development" This will enable plaintext logging of several encryption-related things. If you look at the written logfile, you should see the plaintext being logged, similar to this: └─[Security2CCMessageEncapsulation] │ sequence number: 79 │ security class: S2_Authenticated │ plaintext: 0x... Afterwards, keep Z-UI running until you've captured such an event again. Once you're done, unset the env variable again: process.env.NODE_ENV = "" You may want to send me that logfile privately, so I can remove sensitive information before uploading it. — Reply to this email directly, view it on GitHub <#7111 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJCO3J7L4DLSEITDUQXLMTDZRRLFRAVCNFSM6AAAAABMROO3O2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZUGQ4DGNI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[dualtronic]

Bump. This is still an active problem (test on zen15 ver 2.1 with 800 series chip). Zooz isn't responding to my support request. I don't know if they are stalling or expecting some type of evidence that zwave-js isn't the cause.

[AlCalzone]

I don't recall ever having received a log like I requested in my previous comment.

[peterfares]

I also have this issue with ZEN15 800
I have two of the devices, both initially on 2.0.1
Only one of them has this issue, where it randomly jumps up. I tried updating it to 2.10.0 and it is still having the issue.
Seems like it might be an issue with the device itself though, doesn't the Energy Consumption number come directly from the device?

[AlCalzone]

It does