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

Invalid BE1, BE2, BE3 values #119839

Open
Anacron1 opened this issue Jun 17, 2024 · 4 comments
Open

Invalid BE1, BE2, BE3 values #119839

Anacron1 opened this issue Jun 17, 2024 · 4 comments

Comments

@Anacron1
Copy link

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.

2024-06-17 16:01:52.863 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40079 value 0a00 - failed to decode
2024-06-17 16:01:52.864 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40081 value 0d00 - failed to decode
2024-06-17 16:01:52.864 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40083 value 0d00 - failed to decode
2024-06-17 16:01:54.882 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40079 value 0a00 - failed to decode
2024-06-17 16:01:54.883 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40081 value 0d00 - failed to decode
2024-06-17 16:01:54.883 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40083 value 0d00 - failed to decode
2024-06-17 16:01:56.853 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40079 value 0a00 - failed to decode
2024-06-17 16:01:56.854 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40081 value 0d00 - failed to decode
2024-06-17 16:01:56.854 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 40083 value 0d00 - failed to decode

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

@home-assistant
Copy link

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!

Code owner commands

Code owners of nibe_heatpump 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 nibe_heatpump 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)


nibe_heatpump documentation
nibe_heatpump source
(message by IssueLinks)

@elupus
Copy link
Contributor

elupus commented Jun 17, 2024

My guess is you have them in a LOG.SET file. We have never gotten them to work with data from those files.

@elupus
Copy link
Contributor

elupus commented Jun 17, 2024

Either that or your pump switched wordswap setting for some reason.

@Anacron1
Copy link
Author

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.

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