home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.76k stars 30.87k forks source link

Wiffi integration Pulscounter Values not correct (m3) for Gas and Water #116908

Closed fastsonic closed 3 months ago

fastsonic commented 6 months ago

The problem

Hi, i use a Pulscounter to measure water and Gas The Pulscounter deliver m3 so its not possible to use with Enery dashboard. its use m³ So i custimoize the Value in Yaml. but after every restart of HA the Values seems to have a short 0 so the Dashboard count new and i have negative Jump of the Countervalue and Back to the Normal value. i also have a mail to stall.biz to fix the m3 - m³ problem. Maybe that will arready fix the Problem with the Jumping values or ? regards Sascha

What version of Home Assistant Core has the issue?

core-2024.5.1

What was the last working version of Home Assistant Core?

i only test the last 3 and every have the same Problem

What type of installation are you running?

Home Assistant OS

Integration causing the issue

WIFFI

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

customizing the Counter from Wiffi:
homeassistant:
  customize:
    sensor.w_counter_1_3:
      unit_of_measurement: "m³"
      device_class: gas
      state_class: total_increasing

    sensor.w_counter_2_3:
      unit_of_measurement: "m³"
      device_class: water
      state_class: total_increasing

    sensor.w_counter_3_3:
      unit_of_measurement: "kWh"
      device_class: energy
      state_class: total_increasing

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 6 months ago

Hey there @mampfes, mind taking a look at this issue as it has been labeled with an integration (wiffi) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `wiffi` 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 wiffi` 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)


wiffi documentation wiffi source (message by IssueLinks)

mampfes commented 6 months ago

Please try if the short 0 values could be fixed in the PulsCounter. The Wiffi integration just takes the values from the device and forwards them to HomeAssistant. So, there is no easy possibility to add a filter or so. Same for the unit-of-measure. The Wiffi integration justs forwards the unit-of-measure. In case it doesn't fit, you have to customize (as you already did).

issue-triage-workflows[bot] commented 3 months ago

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.