Closed Anacron1 closed 4 months ago
Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration (nibe_heatpump
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
nibe_heatpump documentation nibe_heatpump source (message by IssueLinks)
My guess is you have them in a LOG.SET file. We have never gotten them to work with data from those files.
Either that or your pump switched wordswap setting for some reason.
You're right. I have these values in LOG.SET. I also try to change setting of wordswap (from unchecked to checked). After this, values were OK, but still sometimes N/A and also they were updated once per approx. 1,5 min. I tried to upload same LOG.SET to heatpump again and now it works perfect. Values are valid and updated every 2 seconds. But I'm afraid that sooner or later the problem will come back.
The problem
Approx. one week ago, NIBE VVM320 starts providing incorrect BE1, BE2, BE3 values of energy consumption (approx. 20 000 A and more) or the entity is not available. It seems that consumption is OK, but like 20 000 times higher. For example, once heat pump starts working, values rises from 25 000 A to 150 000 A.
Values were OK until power outage. Once HA booted again, values where non-sense. I am using nibegw running on LilyGo T-CAN485. Values on the VVM320 display and myuplink are OK.
I got similiar problem after initial boot of nibegw, but values gets fine after approx. one hour, but now the problems persist for a week.
What version of Home Assistant Core has the issue?
core-2024.6.3
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
Nibe Heat Pump
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nibe_heatpump
Diagnostics information
home-assistant_nibe_heatpump_2024-06-17T14-03-42.791Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response