This is yet another example of why Modbus XXX is a time sink.
No one can refute this.
No one can refute this.
It seems that the WiFi module and Aqua Temp app may already communicate MQTT to the vendor's cloud server. Many cloud servers have API's that allow other devices and clouds access to the data. On the Home Assistant forums, it seems someone has written a script to do exactly this.Since the App is terrible and slow, I have no problem removing the Wi-Fi module. Would have been nice with a direct MQTT output though
I'm guessing this is exactly what David was attempting to figure out way back in post #151. Please confirm that there is only one and only one RS-485 port on this heat pump.
2. Please confirm that the Wi-Fi access point is connected to a USB/485 dongle which is connected to the one and only one RS-485 port.
Just a massive thank you for posting the modbus address table for this heat pump, and for determining the correct CN13 connector for connecting to the heat pump as a modbus slave - This thread has saved me hours of snooping/reverse engineering! You all rock!Again some progress, the modbus slave software works with you settings, I can see data on the 2011 to 2080 registers. But that is on slave id 3. So before setting it to 2 ( instead of the WiFi module ) I wanted to be sure what the other register data I need to put in the slave software.
So I disconnected the datalines of the display, leaving it powered on. I tried to read the 3001 registers and up. The only data it gives is the same as the 2001 register. So the status information of the heatpump. Reading the 1011 register to 1178 works and gives met the settings of the heatpump. On / off, setpoint and so on. So that works also.
So should I put the data from the master readout in the slave software also in register 1011 to 1178 ? As the 3001 and up do not contain any settings of the device. I am not sure what to use where now. Before I destroy the settings of the device with the incorrect registers. I have a backup of the value's now. But then I have to enter everything in the display by hand...
I have added a document with the registers according to the company that build the heatpump. The settings in that list are correct with the 1011 registers I have read from the display with the master software on id 1. I have added those values in the PDF to verify everything.
@gimespam You are very welcome. We got it working with the help from this forum, so I'm glad you also could benefit from it.Just a massive thank you for posting the modbus address table for this heat pump, and for determining the correct CN13 connector for connecting to the heat pump as a modbus slave - This thread has saved me hours of snooping/reverse engineering! You all rock!
I'm going to build a MODBUS RTU serial to MODBUS TCP gateway (or maybe an MQTT client) using an ESP32 and connect using NODE-RED running on my Raspberry Pi. I'll send a link to a github repo when done - Or reply to this post if you've already got your ESP32 up and running ;-)
Hi @mrwee@gimespam You are very welcome. We got it working with the help from this forum, so I'm glad you also could benefit from it.
I'm only using basic features for the heatpump, like on/off inlet/outlet temp via a Moxa IP/Serial gateway. But it ideal solution for me, would be a ESP32 with MQTT and auto discovery for Home Assistant. That would be soooo cool
|Thread starter||Similar threads||Forum||Replies||Date|
|T||Help with Modbus RTU||Modbus||3|
|Modbus Communication Address For Hydrovar HVL 4.022 VFD||Modbus||2|
|J||How to establish ModBus TCP connection Between an Elpro 415E Master Radio and S7 1200/1500 Siemens PLC||Modbus||0|
|P||Mitsubishi Inverter FR A 800 E-Series controlled over modbus||Modbus||3|
|Read energy meter via Modbus||Modbus||2|