Isaver pool pump speed control MODBUS => Waveshare USB to RS485

Configuration
1

Hello,

Im currently trying to connect my Isaver pool pump speed controller through MODBUS with Home Assistant.
We received the information of the RS485 protocol and i bought a Waveshare USB to RS485 to connect with the RPI.

USB controller: Waveshare RS485
Speed regulator info: Isaver 1100 +
Speed regulator manual: Manual (page 8)
Information MODBUS protocol: Modbus RS485 protocol

This is the first time i have to program something with these protocols and i was wondering if you guys would want to help me get started how to write the code?

Thx alot for helping :sweat_smile:

2

I am exactly in the same situation, looking for any help on how to control the ISaver+ from RS485. I’ll share the info here if I find it elsewhere.

3

Hello, thx for the reply.

At the moment i am testing this code,but doesn’t work:

modbus:
    name: "iSaver"
    type: serial
    baudrate: 9600
    bytesize: 8
    method: rtu
    parity: N
    port: /dev/ttyUSB0
    stopbits: 1
    retry_on_empty: true
    retries: 20
    close_comm_on_error: false
    delay: 5
    timeout: 5
    sensors:
    - name: iSaver_error
      slave: 3
      address: 2001
    - name: iSaver_status
      slave: 3
      address: 2002
    - name: iSaver_speed
      slave: 3
      address: 2003
    - name: iSaver_power
      slave: 3
      address: 2004
      unit_of_measurement: Watt

The respond is: 2023-06-26 10:07:34.742 ERROR (SyncWorker_3) [homeassistant.components.modbus.modbus] Pymodbus: iSaver: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 4 bytes (0 received)

4

Any progress? I´m also trying using ESPHome component with out any luck.

5

After testing every possible combination ive contacted the importer in Belgium.

They have deactivated the MODBUS feature :scream:

6

NO! This was not god information.
Any reason why?

7

So given the last few posts this thread went dead.
I can give some major good news on these units after many weeks of frustration and research.

I recently bought an iSaver+ unit (the iSaver, Madimack and other brands are all the same unit). All these units are manufactured by Aquagem in China.

When I queried my supplier in the UK they also told me that the RS485 Modbus protocall was disabled on these units. This turns out to be completely false.

Aquagem have actually been fantastic. There is a support member there called Allen who has been giving me excellent information and helping me work out getting a modbus response from the unit. The manufacturer has confirmed the RS485 CANNOT be disabled on these units. If you have one of these ignore what the supplier tells you, the RS485 is always enabled.

So despite my supplier telling me there is no RS485 and it was disabled i am now receiving RS485 data from my unit (using a rough set up with a ESP32, RS845 Max module and esphome)

I will post more details once I’ve got this all set up properly and creating all the sensors and controls properly.

oh, and by the way after weeks of frustration it turns out the rs485 modules are very very flaky which caused a lot of my problems. Reading on other forums a 70% failure rate for these boards is very common and right in line with my recent experience.

1 Like
8

oh and the modbus protocol was changed slightly by the manufacturer. Here is the updated version

9

Thanks ! I’m also trying to figure this out !!

10

Hi, would you mind to post your last/final ESPhome config? [Nerver mind found your post Post ]
I’m currently thinking of either using the digital pins to be triggered by a custom relay board or using rs485.
But I have no real clue where to start etc… any help is more than appreciated.

Kind Regards,
Dieter

11

@DeWaFre Did you or any other manage to create anything? Did you to get it to work? I’m stuck… :roll_eyes: I got the same gateway, the Waveshare RS485. Manage to connect to the gateway with Node-Red but can’t get hold of any data reading the registrar address. Also the Modbus seem strange, kind of their own… reading from the protocol description.
If you have any hints or anything to share, please do. I’ll share if I manage to get any further but now I’ve hit the wall. Completely.

Also, any other that got the device/unit ID to 170??? (slave address 0xAA ) Strange

Cheers.

12

Hello,

After contact with the importer Isaver about this problem, they let me know that they disabled this function :face_with_raised_eyebrow:

13

Thats not correct. Look at this: Modbus - iSaver+ Pool Pump Inverter - Custom Commands Issue - Response mising bytes

I am in contact with the manufacturer. Problem is that the protocol is no standard and esphome does it not support by default I think.

14

@NightWatcher Hi, did the manufacturer get back to you?

I failed to get any data into my RS485 bridge at my first test. Have to investigate further.

Wonder if I got the wiring wrong.

  • The plus and minus connections isn’t that difficult to figure out. However the ground from the iSaver isn’t obvious. Or is it? There is one on the board next to the plus and minus. That would be the one… However not on the same bridge but that could be a simple construction choice. Didn’t get any data.
    There is another digital ground that got my attention, however its on the second row of the connectors. So I will try that.*

Curious on what you others can find out.

15

He did, but without any solution. At the moment, i have other things to do. Maybe i find my 5 minutes in the winter time to try it again.

Which plus and minus are you searching? The rs485 pinout is documented in the manual. You only need this 2 lines.

16

@NightWatcher Thanks for letting me know. So did they confirm the RS485 was activated or not? Has been confirmed once so hope it is the case.

I found the plus and minus, wasn’t a problem. Easy to identify. I failed to communicate with the unit and started to investigate why. Did some research and found some notes about the GND. Nothing that I had an issue with before. The note said that in some cases the GND is needed with RS485. The information on this in the documentation is very limited. Thought it was worth a try.

Well, there is never enough time to calibrate.

17

They confirm, that the rs485 is activated. And for me it is. Only the problem is the crc I think.

1 Like