Closed patsch9 closed 1 year 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)
Any errors in log?
Any errors in log?
no there are no error from the integration. I have enabled debug logging but there are no errors too.
Maybe this is relevant? I'm also using esphome-nibe and entities show as unavailable since the last HA update.
Log Details (ERROR)
Logger: homeassistant.components.nibe_heatpump
Source: helpers/update_coordinator.py:215
Integration: Nibe Heat Pump ([documentation](https://www.home-assistant.io/integrations/nibe_heatpump), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+nibe_heatpump%22))
First occurred: March 5, 2023 at 9:28:32 PM (1 occurrences)
Last logged: March 5, 2023 at 9:28:32 PM
Error fetching Nibe Heat Pump data: Failed to update: Failed decoding response for freeze-protection-status-43013: Failed to decode freeze-protection-status-43013 coil from raw: 00000100, exception: Mapping not found for freeze-protection-status-43013 coil for value: 0
Yes that could be relevant. One failing update like that could break the queue of updates. So disable that sensor for now.
i added the heat pump as a new instance, after enabling the required entities, the entities are available in the new integration instance. Unfortunately, I had to find out individually which entities I had activated and had to name them again the way I wanted, which was quite a lot of work. After that I was able to delete the old instance of the integration and everything is running again.
Before i did this i have tested to disable an re enable the entities in the broken integration instance, that have not fixed the issue.
disable that sensor for now.
Just disabled it and the other data came back. Then enabled it again and the data became unavailable. Apparantly something has changed in HA or this integration w.r.t to exceptions upon receiving data packets that are not yet properly decoded. In the case of freeze protection, at least for my F370 it seems as if the only valid values are 1 and 0, but the bits 00000100 would be 4. I don't know what that really means.
I'm experiencing the same issue:
2023-03-08 11:41:58.572 WARNING (MainThread) [nibe.nibe.connection.nibegw] Ignoring coil 47340 value 0a000000 - failed to decode
2023-03-08 11:41:58.575 DEBUG (MainThread) [homeassistant.components.nibe_heatpump] Some coils failed to update, and may be unsupported: Failed decoding response for cooling-with-room-sensor-47340: Failed to decode cooling-with-room-sensor-47340 coil from raw: 0a000000, exception: Raw value 10 is out of range for coil cooling-with-room-sensor-47340
Disabled the entity, but the other data is not coming back and the logs keep coming. This specific sensor was broken by my PR: https://github.com/yozik04/nibe/pull/81
The problem
After the Update to 2023.3.0 a part of the activated entities from Nibe Heatpumps interfration are shown as unavailable. I use the NibeGW on ESP32 from this repo https://github.com/elupus/esphome-nibe
What version of Home Assistant Core has the issue?
2023.3.0
What was the last working version of Home Assistant Core?
2023.2.5
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
nibe heatpumps
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nibe_heatpump/
Diagnostics information
there are no error logs
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response