I’ve been working on integrating my Alpha Innotec Split 12 heat pump with Home Assistant using the Nibe GW. While the setup seemed straightforward, I encountered an error: ‘Error on read request from pump. Verify your Remote read port or Remote address’. After some troubleshooting, here’s what I discovered and how I resolved it.
**Steps I Took:**1. Checked Modbus Settings: I confirmed that Modbus was enabled on the heat pump and that the remote read port was correctly configured. The default Modbus port is usually 502, but it’s essential to verify this in the heat pump’s settings.
-
Verified IP Addresses: I made sure that both the Nibe GW and Home Assistant were on the same network. The Nibe GW IP was set to 192.168.1.25, and Home Assistant was running on 192.168.1.28. Double-checking these addresses helped eliminate network-related issues.
-
Firewall and Port Settings: I reviewed the firewall settings on both devices to ensure that port 502 wasn’t being blocked. Sometimes, firewalls can inadvertently block necessary traffic, so it’s crucial to allow Modbus communication through this port.
-
Nibe GW Configuration: I revisited the Nibe GW configuration to ensure that it was correctly set up to communicate with the heat pump. This involved checking the slave ID and ensuring that the read/write settings were appropriate for my setup.
-
Testing with a Modbus Tool: To isolate the issue, I used a third-party Modbus testing tool. This helped me determine whether the problem was with the Nibe GW or Home Assistant. The tool successfully communicated with the heat pump, indicating that the issue was likely with the Home Assistant integration.
-
Reinstalling the Integration: After identifying that the integration might be faulty, I uninstalled and reinstalled the Nibe GW integration in Home Assistant. This process reset any incorrect configurations and allowed me to start fresh.
-
Consulting Documentation and Forums: When I was stuck, I referred to the official Nibe documentation and community forums. Others had encountered similar issues, and their solutions provided valuable insights.
**Final Solution:**The error was due to an incorrect slave ID configuration in the Nibe GW settings. Once I corrected this, the integration worked seamlessly. It’s a reminder that even small misconfigurations can lead to significant issues.
Takeaways:- Always double-check your device configurations, especially IP addresses and port settings.
- Use diagnostic tools to isolate issues between hardware and software.
- Don’t hesitate to consult community resources; someone might have already encountered and solved your problem.
I hope this helps anyone else facing similar challenges with their Nibe heat pump integration!