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

Viessmann heatpump electricity consumption values frozen #138979

Open
fishter opened this issue Feb 21, 2025 · 2 comments
Open

Viessmann heatpump electricity consumption values frozen #138979

fishter opened this issue Feb 21, 2025 · 2 comments

Comments

@fishter
Copy link

fishter commented Feb 21, 2025

The problem

There are a few sensors in my device entry that get "stuck". The electricity consumption measurements called "DHW electricity consumption today", "Electricity consumption total today" and "Heating electricity consumption today". Around 1 am the measurement stops increasing despite the heatpump continuing to consume electricity. After rebooting the communications module of the VitoCal (via the ViCare app), the values become live again. The value is correct and I can see that the consumption is still being measured during the "freeze", but it's not getting reported.

I've tried the wifi on/off automation trick, but this didn't seem to have an effect.

Image

Other values from the heatpump are generated normally throughout the period.

Image

Diagnostic data is attached.

What version of Home Assistant Core has the issue?

core-2025.2.4

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-01JM38GN3656MB7RQX6DWJRJY9.json

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

Hey there @CFenner, 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 Renames 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.
  • @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)


vicare documentation
vicare source
(message by IssueLinks)

@CFenner
Copy link
Contributor

CFenner commented Feb 21, 2025

This is a known issue and you are able to workaround by resetting the outside world connection of the gateway (restart, disable wifi) in the night.

Please get help in the other issue. Just to be sure, the consumption continues to update in the ViCare app, right? It's just broken in HA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants