Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PAB01 energy meter module does not update sensor values #108878

Closed
clase30 opened this issue Jan 25, 2024 · 8 comments
Closed

PAB01 energy meter module does not update sensor values #108878

clase30 opened this issue Jan 25, 2024 · 8 comments

Comments

@clase30
Copy link

clase30 commented Jan 25, 2024

The problem

ZIP-PAB01 energy meter module does not update sensor values. The module sends the value (reflected in the log) every time it detects a 5% variation in consumption, but Home Assistant does not change the value of the sensors, they remain frozen.

In this forum some users report the same problem: https://forum.hacf.fr/t/pab01-pas-de-remonter-automatique-des-valeurs/15028

(Z-wave JS work fine because reports are received and shown in the log, and the expert said that the error was from home assistant core zwave-js/node-zwave-js#6600)

What version of Home Assistant Core has the issue?

core-2024.1.3

What was the last working version of Home Assistant Core?

it never worked before

What type of installation are you running?

Home Assistant OS

Integration causing the issue

z-wave JS

Link to integration documentation on our website

No response

Diagnostics information

zwavejs_2024-01-10 (2).log
(Node 034)

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Node 34 is reporting data, but sensor data doesn't change.

Additional information

image

@home-assistant
Copy link

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)

@kpine
Copy link
Contributor

kpine commented Jan 26, 2024

Please attach the device diagnostic file (attach file to comment, not copy and paste). You can download the diagnostic file by going to Settings -> Devices & services -> Z-Wave "Devices" -> The Device -> Device info -> ... -> Download diagnostics.

@clase30
Copy link
Author

clase30 commented Jan 26, 2024

@kpine
Copy link
Contributor

kpine commented Jan 27, 2024

This looks like a Z-Wave JS bug to me. I added a comment to zwave-js/node-zwave-js#6600.

@kpine
Copy link
Contributor

kpine commented Jan 27, 2024

Also, if you included this device in an older version of Z-Wave JS, make sure you have re-interviewed the device in case there were any driver fixes since then.

@jluc2808
Copy link

jluc2808 commented Feb 4, 2024

same problem, no report with the electric consumption [20-50-1-value-66049] Electric Consumption [W] _ always 0w - rather the cumulated one[ 20-50-1-value-65537] Electric Consumption [kWh] which is 2.64Kwh and was 257 Kwh few time before.

@clase30
Copy link
Author

clase30 commented Feb 6, 2024

same problem, no report with the electric consumption [20-50-1-value-66049] Electric Consumption [W] _ always 0w - rather the cumulated one[ 20-50-1-value-65537] Electric Consumption [kWh] which is 2.64Kwh and was 257 Kwh few time before.

Please check this thread where a solution is being given:
zwave-js/node-zwave-js#6600

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants