ViCare sensor data does not match data from the fuel cell

[stefansiegl]

The problem

Hi folks,

First: Thanks for creating the integration with ViCare. The installation was a blaze.

Unfortunately there seems to be a mismatch between the data on gas consumption in homeassistant with data from the fuelcell itself.

sensor.vicare_energy_consumption_of_hot_water_gas_heating_current_day shows 0.6m^3 in Homeassistant and 1.1m^3 in the fuel cell sensor.vicare_heating_gas_consumption_current_day day shows 0.5m^3 in Homeassistant and should be 1.0m^3 according to the fuel cell.

Is that a known issue?

What version of Home Assistant Core has the issue?

2023.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Viessmann ViCare

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vicare/

Diagnostics information

config_entry-vicare-9b956afa464dfd640d0ba529b29130d6.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

unfortunately not

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of `vicare` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign vicare` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[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.