Replies: 2 comments 6 replies
-
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. |
Beta Was this translation helpful? Give feedback.
-
Any thoughts @kellerza when you have a moment (let me see if there is a 'buy me a coffee' link for your help) |
Beta Was this translation helpful? Give feedback.
-
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)
HA_PREFIX: SS
MODBUS_ID: 1
DONGLE_SERIAL_NUMBER: "0"
PORT: tcp://homeassistant.local:502
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.
Beta Was this translation helpful? Give feedback.
All reactions