Help with getting setup working

[mdeakin99]

Any ideas where I might start based on the error

Configuration

Sunsynk Inverter Dongle (192.168.1.149). Splitter connected to CAN port. Confirmed working as inverter is communicating with batteries.
Other port on splitter connected to https://www.amazon.co.uk/dp/B081NBCJRS?ref=ppx_yo2ov_dt_b_fed_asin_title via network cable (believe I rewired it correctly) which then connects to Home Assistant running on an odroid.
Sunsynk/Deye Inverter Add-on (multi)

• set to pymodbus
• Tried both 192.168.1.149 and homeassistant.local in the Sunsynk/Deye Inverter Add-on (multi) configuration
• SERIAL_NR: "SerialNumberOfInverterHere"
  HA_PREFIX: SS
  MODBUS_ID: 1
  DONGLE_SERIAL_NUMBER: "0"
  PORT: tcp://homeassistant.local:502
• MQTT host/username/password match the mqtt addon/integration in HA.

Log

[20:12:12] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun sunsynk (no readiness notification)
s6-rc: info: service legacy-services successfully started
20:12:18 INFO Loading configuration: /data/options.json
20:12:18 INFO sunsynk library version: 0.6.5
20:12:18 INFO Schedules:
+-----------+-----+------+--------+-----------+----------+------------+
| Key | src | Read | Report | Change by | Change % | Change any |
+-----------+-----+------+--------+-----------+----------+------------+
| date_time | | 60 | 60 | | | True |
| rw | | 5 | 300 | | | True |
| enum | | 5 | 300 | | | True |
| w | * | 5 | 60 | 80 | | |
| kwh | | 300 | 300 | | | |
| any_unit | | 15 | 300 | | | |
| no_unit | | 15 | 300 | | | True |
+-----------+-----+------+--------+-----------+----------+------------+
20:12:18 INFO Using Single phase sensor definitions.
20:12:18 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial
20:12:18 INFO Connecting to tcp://homeassistant.local:502
20:12:18 INFO PyModbus 3.7.2 tcp: homeassistant.local:502
20:12:19 WARNING Failed to connect Multiple exceptions: [Errno 111] Connect call failed ('172.30.32.1', 502), [Errno 111] Connect call failed ('172.30.232.1', 502), [Errno 111] Connect call failed ('192.168.1.102', 502), [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument, [Errno 22] Invalid argument
20:12:19 INFO ############################################################
20:12:19 INFO Could not connect to tcp://homeassistant.local:502:
20:12:19 INFO ############################################################
20:12:19 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

[mdeakin99]

I changed the port to tcp://homeassistant.local:1883 (the mqtt port) and now it seems to have go further. I reduced Read_sensors_batch_size to 8 but still get the message below.

21:10:33 INFO Using Single phase sensor definitions.
21:10:33 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial
21:10:33 INFO Connecting to tcp://homeassistant.local:1883
21:10:33 INFO PyModbus 3.7.2 tcp: homeassistant.local:1883
21:10:33 INFO Reading startup sensors Prog2 Time, Prog5 Time, Prog6 Time, Serial, Prog3 Time, Battery Low Capacity, Rated power, Prog4 Time, Prog1 Time
21:11:17 ERROR timeout reading 5 registers from 3; timeout reading 2 registers from 16; timeout reading 1 registers from 219; timeout reading 6 registers from 250

[mdeakin99]

Any thoughts @kellerza when you have a moment (let me see if there is a 'buy me a coffee' link for your help)

[mdeakin99]

Tried modbus and I get the following. Slightly different start to the message but looks like the same issue. I will try modbus app to see how I get on.

The splitter I purchased from solarassistant site. The part of the splitcable that goes to the batteries is still working ok so guessing it isnt the splitter. Will take a look at the fault finding.

14:12:24 INFO Using Single phase sensor definitions.
14:12:24 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial
14:12:24 INFO Connecting to tcp://homeassistant.local:502
14:12:24 INFO PyModbus 3.7.2 tcp: homeassistant.local:502
14:12:24 INFO Reading startup sensors Prog6 Time, Prog4 Time, Battery Low Capacity, Rated power, Serial, Prog5 Time, Prog2 Time, Prog3 Time, Prog1 Time
14:12:41 ERROR OSError reading 2 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 5: failed to read register 5 - function code: 131; OSError reading 1 registers from 7: failed to read register 7 - function code: 131; OSError reading 2 registers from 16: failed to read register 16 - function code: 131; OSError reading 1 registers from 219: failed to read register 219 - function code: 131; OSError reading 2 registers from 250: failed to read register 250 - function code: 131; OSError reading 2 registers from 252: failed to read register 252 - function code: 131; OSError reading 2 registers from 254: failed to read register 254 - function code: 131
14:12:59 ERROR OSError reading 2 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 5: failed to read register 5 - function code: 131; OSError reading 1 registers from 7: failed to read register 7 - function code: 131; OSError reading 2 registers from 16: failed to read register 16 - function code: 131; OSError reading 1 registers from 219: failed to read register 219 - function code: 131; OSError reading 2 registers from 250: failed to read register 250 - function code: 131; OSError reading 2 registers from 252: failed to read register 252 - function code: 131; OSError reading 2 registers from 254: failed to read register 254 - function code: 131
14:13:16 ERROR OSError reading 2 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 5: failed to read register 5 - function code: 131; OSError reading 1 registers from 7: failed to read register 7 - function code: 131; OSError reading 2 registers from 16: failed to read register 16 - function code: 131; OSError reading 1 registers from 219: failed to read register 219 - function code: 131; OSError reading 2 registers from 250: failed to read register 250 - function code: 131; OSError reading 2 registers from 252: failed to read register 252 - function code: 131; OSError reading 2 registers from 254: failed to read register 254 - function code: 131
14:13:16 WARNING Retrying individual sensors: ['prog6_time', 'prog4_time', 'battery_low_capacity', 'rated_power', 'serial', 'prog5_time', 'prog2_time', 'prog3_time', 'prog1_time']
14:13:18 ERROR OSError reading 1 registers from 255: failed to read register 255 - function code: 131 Prog6 Time
14:13:21 ERROR OSError reading 1 registers from 253: failed to read register 253 - function code: 131 Prog4 Time
14:13:23 ERROR OSError reading 1 registers from 219: failed to read register 219 - function code: 131 Battery Low Capacity
14:13:25 ERROR OSError reading 2 registers from 16: failed to read register 16 - function code: 131 Rated power
14:13:32 ERROR OSError reading 2 registers from 3: failed to read register 3 - function code: 131; OSError reading 2 registers from 5: failed to read register 5 - function code: 131; OSError reading 1 registers from 7: failed to read register 7 - function code: 131 Serial
14:13:34 ERROR OSError reading 1 registers from 254: failed to read register 254 - function code: 131 Prog5 Time
14:13:36 ERROR OSError reading 1 registers from 251: failed to read register 251 - function code: 131 Prog2 Time
14:13:38 ERROR OSError reading 1 registers from 252: failed to read register 252 - function code: 131 Prog3 Time
14:13:40 ERROR OSError reading 1 registers from 250: failed to read register 250 - function code: 131 Prog1 Time
14:13:40 CRITICAL Could not read sensors: ['Prog6 Time', 'Prog4 Time', 'Battery Low Capacity', 'Rated power', 'Serial', 'Prog5 Time', 'Prog2 Time', 'Prog3 Time', 'Prog1 Time']
14:13:40 INFO ############################################################
14:13:40 INFO No response on the Modbus interface tcp://homeassistant.local:502, see https://kellerza.github.io/sunsynk/guide/fault-finding
14:13:40 INFO ############################################################
14:13:40 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

[mdeakin99]

There is a project called open modscan which you can use on the PC to monitor the modbus traffic from your PC with the USB-RS485 adaptor.

Is the cable using stranded core or solid core. When using stranded please use ferrules. When using solid core you should remove the resin coating to ensure proper electrical contact.

Removed the coating on the cable to make sure it's only the wire that connecting to the points on the waveshare.

Downloaded MODSCAN64 on my laptop. I connected an ethernet cable to the laptop and the splitter at the other end of the cable. I tried a few settings but couldnt get it to connect. To be honest though, not sure what to put in 'Connect Using' in the modbus app. I tried both COM1 and Remote modBus TCP Server (I put in the IP address of the sunsynk dongle but pretty sure this is the wrong thing. Any pointers here greatly appreciated.

[mdeakin99]

Would a solarman dongle perhaps fix the issue if the splitter/cable/waveshare is currently the problem? I appreciate it means I lose remote access via Sunsynk app but I can work with that

[kellerza]

Just use a laptop with a modbus app & short wire. First simplify things

[mdeakin99]

Network cable directly from laptop to inverter correct? or have I understood incorrectly