Zwave Spiking Energy Usage

[Aimtjie]

trafficstars

The problem

I'm not sure if this is a core issue or a visual issue from displaying data in the DB.

This issue seems to be occurring occasionally after a home assistant core restart. The power usage spikes from 0 to X amount depending on the last (Total?) usage of the device

This only seems to be affecting my zwave devices, all of which are aeotec. There is a thread on the forum of the same issue

The device in question is only using 20W when active.

What version of Home Assistant Core has the issue?

2024.2.0b4

What was the last working version of Home Assistant Core?

2024.2.0b4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zwave JS UI

Link to integration documentation on our website

https://github.com/zwave-js/zwave-js-ui

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[ronvl]

Same here...

[hellomj1976]

Same here

[joshuascott94]

Same here.

[josy1024]

same here. sometimes spike Problems on aeotec zwave switch with energy monitoring. ZW132 (only have 3 zwave devices) it shows runaway values in /developer-tools/statistics (had no realistic high value!)

WORKING WORKAROUND = FILTER

 - platform: filter
    name: "Energie SW23 (Smooth)"
    entity_id: sensor.sw23_electric_consumption_kwh_3
    filters:
      - filter: outlier
        window_size: 10
        radius: 5

[onkytonk]

I’m having the same issue with aeotec zw096 switches. Apart from using a filter, hoping for a more permanent solution.

[brettcp]

Same issue here with an Aeotec DSB28 energy meter. I'll have 2-3 weeks of valid data where its reporting my usual 1kWh to 1.9kWh typical usage, then all of a sudden I'll get one reading of a number 2000x higher than it should be (saw a recent spike reported 3,681kWh). It seems to happen at random intervals every 2-3 weeks or so.

I just applied the workaround/filter @josy1024 mentioned and will keep an eye on it.

Is anybody seeing this issue on non-Aeotec devices, or does this seem to be an issue specific to Aeotec?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ronvl]

I stopped using them for PM purposes so can't tell you if resolved btw I was using CAM Zwave devices

[blazarmilkywayflybee]

Can confirm issue is still present in 2024.08.03

[jkaberg]

+1 to the previous comment and in addition I'd like to mention an possible "universal" solution that didn't get much traction

[HereticBG]

Also having this issue with my zen15 device

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[shahzebs]

Issue still persists in 2024.11.2

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[Thyraz]

Any chance you guys don’t use S2 for inclusion of this devices?

in this case Zwave is very prone to transmission/checksum errors. beside erroneous spikes this is often seen in new entities that populate even that the device doesn’t support this class (e.g brightness in lux on pure temperature sensor).

In this case, HA can’t do anything about it. Filter it out on your own, or re-include with S2 (which brings a better integrity check together with the encryption).

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.