-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Nibe Integration: Entity toggling between value and Unavailable every few minutes #128818
Comments
Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) nibe_heatpump documentation |
Could you remove these registers from your logset file? My guess something is wrong with that data. |
Also could be due to all invalid wordswap setting on your pump. |
Word swap checkbox is checked in the pump. If it was wrong, wouldn't then the value never be correctly shown. I added a screen shot in Diagnostic information, which shows that it toggles every now and then. |
@elupus I manually edited nibegw.py to match with yozik04/nibe@ed3ef0c and restarted HA. I restarted HA at 16:37 and since then compressor starts remains stable (now at 33922) |
@elupus But I saw now an issue with other coils. I also use HACS MyUplink (https://github.com/jaroschek/home-assistant-myuplink) and both 44298 and 44300 are now showing much smaller values in your integration compared to HACS MyUplink. Previously they always showed exact same value. Seems yozik04/nibe@ed3ef0c is not ok. |
You did not try what i asked you? Disable the parameters in your LOGSET file. |
But. Nice that you tested that patch! Not sure i can merge that though |
@elupus I removed 43416, 44298 and 44300 from LOG.SET and reloaded the Nibe integration. |
The problem
I notice since I have set up the Integration (1-2 months ago) that Nibe F1245 coil 43416 (Compressor starts EB100-EP14) toggles between a correct value and
Unavailable
every few minutes.I use LilyGo T-CAN as MODBUS40 replacement.
HA logs contain huge amount of warnings like
[nibe.nibe.connection.nibegw] Ignoring coil 43416 value 8184 - failed to decode
but also other coils
What version of Home Assistant Core has the issue?
core-2024.10.3
What was the last working version of Home Assistant Core?
unknown/never
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Nibe Heat Pump
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nibe_heatpump
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I patched ESPHome NibeGw.cpp lines 151 ff to allow ESPHome logs of LilyGo device to show the bytes received via MODBUS from F1245-8 E EM Firmware: 9699R7 (myUplink)
and in ESPHome YAML
and then tried to find the hex bytes that HA Nibe Integration failed to decode:
matches with NibeGw.cpp logs:
[08:42:12][W][nibeGW:155]: 87 bytes from pump: 5C 00 20 68 51 44 9C 84 00 48 9C 34 01 4D 9C E1 01 4E 9C B9 01 4F 9C 0E 01 50 9C FB 00 59 9C E1 00 5A 9C E8 00 5C 5C 9C EB 00 5D 9C EE 00 EC 9F 00 00 ED 9F 00 00 01 A8 21 01 98 A9
81 84
FF FF 00 00 0A AD20 9F
FF FF 00 00 0C ADF7 5D
FF FF 00 00 EA AC 00 00 AFThe text was updated successfully, but these errors were encountered: