Validation Error: Timeout on Writing to Nibe Heat Pump During Configuration about core HOT 8 OPEN

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)}}

from core.

Are you using the lilygo t-can485 board?
Which revision of it?
Do you have any firewalls or routers between the devices?
The data might looks corrct, more used to it in hex.

from core.

Actually. The pump looks to actually be responding to the request. It rejecting it. That might actually be a valid response. Either that or we have the wrong parameter number for that pump.

from core.

Which exact model heat pump is it?

from core.

Are you using the LilyGO T-CAN485 board? Which revision of it?
Yes, but I would need to disassemble it again to find out the revision. Where can I find the revision information?

Do you have any firewalls or routers between the devices?
Yes, it's a Unifi network, but the UDP packets from the last screenshot were from the terminal inside Home Assistant. So, I guess at least on the way back from the heat pump, everything seems to be normal.

Which exact model heat pump is it?
It's a Nibe F1255-6 E EM with an FLM ventilation system. Could the FLM be causing the issue?

Or is it because i updated on the 04.06.2024 to the new software Version: 9699R4 from the Heatpump?

from core.

Ok. Lets try something weird.. :). Go into the extra settings on the pump and enable the RMU40 accessory. This should cause your pump to go into alarm. Dont clear it, but try to add the system in HA while the pump is showing an alarm on screen.

This might work, if the pump is rejecting the write request to clear alarms when there are none. Worth a shot.

The you can disable the RMU40 accessory again and clear any alarms.

from core.

As I was writing this, I reset the Nibe back to software version 9443R7. Guess what, that fixed it! However, Nibe wanted me to upgrade because of the change from Nibe Uplink to MyUplink. I thought they wouldn't touch the Modbus, but reverting the software made it pass on the first try. I've now been working on it for 2 days 😄

Do you know if Nibe changed something with the modbus with the shift to MyUplink? I didn't read anything in the changelog.

---old text---
Sadly, that didn't help. I activated the first RMU in the menu and tried multiple times to activate it via HA. Unfortunately, the error message in the log remained the same.

from core.

Oh! So they changed some behavior there. I was afraid they might.

Crap i need to take the time and update my pump and see what others stuff they might have broken.

from core.