October 4, 20232 yr Hi There Thanks for this great HA integration. Is anyone know why there is not PV2 voltage and current? Apologies my bad , "READ THE DOCUMENTATION" lesson Edited October 6, 20232 yr by GarySS Did not read documentation
October 5, 20232 yr @Dunc your port is wrong - it tried to connect to an IP on port 502. This is typically the port that the mbusd addon would expose, but no mention that you use it? Set the port to an empty string - "" then use the DEBUG_DEVICE to select the usb port
October 5, 20232 yr Like @Dunc, I'd be interested in the Sunsynk Dongle option... Is there any work being done on this? Or is there a fundamental reason why it can't work? I don't really have one to experiment with and everyone out there only integrates via the cloud (not ideal in my view)
October 5, 20232 yr Author I don't really have one to experiment with and everyone out there only integrates via the cloud (not ideal in my view) I don't trust the cloud for anything except maybe as a bit of a backup on my long term data
October 10, 20232 yr On 2023/09/25 at 6:31 PM, Dunc said: I'm just taking a flyer here - have not done anything like this myself... But is it correct that you have "active: false" in customize at the bottom of that image?
October 10, 20232 yr On 2023/10/05 at 5:30 PM, kellerza said: I don't really have one to experiment with and everyone out there only integrates via the cloud (not ideal in my view) Agreed. I'm only starting out with HA, and slow-going getting time between "life". For now, I have a few things running dependent on cloud access, but I definitely want to move toward HA being able to run without any internet. The only thing I'll want to support is for the HA app to talk to my instance when I'm out and about. I'm using Gary Waterworth's Integration to the Sunsynk Cloud service at the moment. It's been a great start for me, and I have visibility of what's going on now. I send myself alerts for high temperatures and battery state. I calculate how much time I can run my geyser in the early morning hours using excess remaining power in the battery. Ideally, I hit 20% SoC at about 7:30am, at which time the Sun starts charging me up again. I have PV forecasting (Meteorologisk Institutt) which is interesting, but I have not used it for any automations yet. What I have not yet tackled is an integration to fetch the loadshedding schedules and factor those into the planning. But I definitely want to "go local". When I have the necessary time (and when I see that @Dunc has enjoyed some success with the RS485), I'll be following suit. And I'll be able to keep the automations I have done, just adjusting them as necessary to use the local integration instead. Thanks to you guys here for doing the 'dirty work' for us!!! Kudos @kellerza and @Sc00bs .
October 10, 20232 yr A Question re the RS485 option: My inverter in the garage is a fair distance away from my HA instance in my study. A cable would probably be a run of 20-25m. I seem to recall seeing a comment that the cable cannot be so long. I think that was in the context of an RS485 to USB converter, and hence a limitation on the length of the USB cable. I'm not sure. Does anyone here know what my limits would be?
October 10, 20232 yr 1 hour ago, Patrick OReilly said: A Question re the RS485 option: My inverter in the garage is a fair distance away from my HA instance in my study. A cable would probably be a run of 20-25m. I seem to recall seeing a comment that the cable cannot be so long. I think that was in the context of an RS485 to USB converter, and hence a limitation on the length of the USB cable. I'm not sure. Does anyone here know what my limits would be? Depends on baudrate. At 9600 you could easily cover >1.2km using twisted pair and termination resistors. So your 25m even for higher baud rates can easily be covered. But you must still use shielded twisted pair, with the shield grounded at ONE side only. And terminate the RS485 with 150R resistors.
October 10, 20232 yr 4 minutes ago, BritishRacingGreen said: Depends on baudrate. At 9600 you could easily cover >1.2km using twisted pair and termination resistors. So your 25m even for higher baud rates can easily be covered. But you must still use shielded twisted pair, with the shield grounded at ONE side only. And terminate the RS485 with 150R resistors. For these type of distances its preffered to have isolation on both ends. Inverters and battery BMSs rs485 driverd are isolated. A raspberry pi rs485 driver is typically not. Isolation is expensive though, so make sure you at least put RS485 surge protector very close to the pi.
October 10, 20232 yr Thanks for the info @BritishRacingGreen . When I get to this I’ll dig deeper to make sure I do it right. I might be reaching out to you… 😊👍
October 16, 20232 yr Hi I am struggling to connect with a USB-RS485 adapter to my sunsynk 8kva inverter. I have the new sunsynk dongle so I cannot use the solarman integration. Have a pi4 running home assistant connected to the inverter but just can't seem to get the MQTT connection working. Anyone have any idea why?
October 16, 20232 yr On 2023/09/20 at 8:50 PM, Sc00bs said: I am doing the easy stuff :-), @kellerza does all the heavy lifting 🙂 Maybe just buy a USB - RS485 adapter, is dead easy to set up I am having a similar problem. Bought a usb rs485 adapter. Connected it to my pi 4 but can’t seem to pick it up on the Mqtt mosquito. If you don’t go via solarman do you need the esp32 integration? thanks for the assistance and great videos @Sc00bs
November 16, 20232 yr On 2023/10/10 at 3:43 PM, BritishRacingGreen said: For these type of distances its preffered to have isolation on both ends. Inverters and battery BMSs rs485 driverd are isolated. A raspberry pi rs485 driver is typically not. Isolation is expensive though, so make sure you at least put RS485 surge protector very close to the pi. On 2023/10/10 at 3:35 PM, BritishRacingGreen said: Depends on baudrate. At 9600 you could easily cover >1.2km using twisted pair and termination resistors. So your 25m even for higher baud rates can easily be covered. But you must still use shielded twisted pair, with the shield grounded at ONE side only. And terminate the RS485 with 150R resistors. This is very good advice! The raspberry Pi PSU also floats somewhat, and since its not isolated it's important to wire the GND on the USB-RS485 adaptor (this is not the shield). In my setup I have non-shielded solid-core CAT5e (RS485 on one twisted PAIR !!) and GND. Around 15m with <1m in close proximity to the AC. The twisted pair helps, but if you have longer runs in close proximity to AC/DC then you must go shielded. The Waveshare USB adaptor I link in the docs has everything except optical isolation: Support USB to RS485 bidirectional conversion Onboard Original FT232RL and SP485EEN chip. Fast communication, stable and reliable, better compatibility Onboard TVS (Transient Voltage Suppressor), effectively suppress surge voltage and transient spike voltage in the circuit, lightningproof & anti-electrostatic Onboard resettable fuse and protection diodes, ensures the current/voltage stable outputs, provides over-current/over-voltage proof, improves shock proof performance
December 8, 20232 yr Hi @kellerza... Not sure if (a) this has been asked before, or (b) it's a real n00b question, so apologies in advance... Does your SS/DY Inverter Add-on (with the new Solarman capability enabled) depend in any way on Stephan Joubert's Solarman integration? If not, is there any problem with running both at the same time? Thanks for the great work!
December 29, 20232 yr Hey, I just tried to install the mttq integration to my home assistant. - I hit a snaque... after following instructions in the above video - the mosquito starts well but after configuration in the video there is 1 device and was it 61 entities - I have no devices nor entities... - can not check states and so on... - I think something went wrong. Any hints / suggestions? I am a bit newbie in here so bare with me ;( I have Deye hybrid inverter which I am trying to control according to electricity price.
December 29, 20232 yr 1 hour ago, VIlle said: Hey, I just tried to install the mttq integration to my home assistant. - I hit a snaque... after following instructions in the above video - the mosquito starts well but after configuration in the video there is 1 device and was it 61 entities - I have no devices nor entities... - can not check states and so on... - I think something went wrong. Any hints / suggestions? I am a bit newbie in here so bare with me ;( I have Deye hybrid inverter which I am trying to control according to electricity price. after restart moquette log: 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 cont-init: info: running /etc/cont-init.d/mosquitto.sh [15:34:28] INFO: SSL is not enabled cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0 cont-init: info: running /etc/cont-init.d/nginx.sh cont-init: info: /etc/cont-init.d/nginx.sh exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun mosquitto (no readiness notification) services-up: info: copying legacy longrun nginx (no readiness notification) [15:34:28] INFO: Starting NGINX for authentication handling... s6-rc: info: service legacy-services successfully started [15:34:28] INFO: Starting mosquitto MQTT broker... 2023-12-29 15:34:28: Warning: Mosquitto should not be run as root/administrator. 2023-12-29 15:34:28: mosquitto version 2.0.18 starting 2023-12-29 15:34:28: Config loaded from /etc/mosquitto/mosquitto.conf. 2023-12-29 15:34:28: Loading plugin: /usr/share/mosquitto/go-auth.so 2023-12-29 15:34:28: ├── Username/password checking enabled. 2023-12-29 15:34:28: ├── TLS-PSK checking enabled. 2023-12-29 15:34:28: └── Extended authentication not enabled. 2023-12-29 15:34:28: Opening ipv4 listen socket on port 1883. 2023-12-29 15:34:28: Opening ipv6 listen socket on port 1883. 2023-12-29 15:34:28: Opening websockets listen socket on port 1884. 2023-12-29 15:34:28: mosquitto version 2.0.18 running 2023-12-29 15:34:28: New connection from 127.0.0.1:46570 on port 1883. 2023-12-29 15:34:28: Client <unknown> disconnected due to protocol error. [15:34:29] INFO: Successfully send discovery information to Home Assistant. [15:34:29] INFO: Successfully send service information to the Supervisor. 2023-12-29 15:34:29: New connection from 172.30.32.1:55855 on port 1883. 2023-12-29 15:34:29: New client connected from 172.30.32.1:55855 as 1OupFbHC8NdTTkpD9icdDa (p1, c1, k60, u'mqtt_user'). 2023-12-29 15:34:50: New connection from 172.30.32.2:44746 on port 1883. 2023-12-29 15:34:50: Client <unknown> closed its connection. So this seems ok - right?
December 30, 20232 yr 22 hours ago, VIlle said: Hey, I just tried to install the mttq integration to my home assistant. - I hit a snaque... after following instructions in the above video - the mosquito starts well but after configuration in the video there is 1 device and was it 61 entities - I have no devices nor entities... - can not check states and so on... - I think something went wrong. Any hints / suggestions? I am a bit newbie in here so bare with me ;( I have Deye hybrid inverter which I am trying to control according to electricity price. Sorry folks - my stupidity... Port configuration was mistyped... now it works
January 22, 20242 yr I can't get it to work. I followed all the steps in the video, but I get an error. With port 8899 writes: 14:39:16 INFO Connecting to tcp://192.168.1.20:8899 14:39:16 INFO Reading startup sensors Prog2 Time, Battery Low Capacity, Prog6 Time, Prog4 Time, Prog1 Time, Prog3 Time, Serial, Prog5 Time, Rated power 14:39:16 ERROR Error retry attempt(0): The data address received in the request is not an allowable address for the server. So I should have located the correct port 80, because typing 192.160.1.20:80 in the browser correctly enters the inverter configuration, but he writes: 14:40:59 INFO Connecting to tcp://192.168.1.20:80 14:40:59 INFO Reading startup sensors Serial, Prog1 Time, Prog3 Time, Prog4 Time, Battery Low Capacity, Rated power, Prog5 Time, Prog6 Time, Prog2 Time 14:40:59 ERROR Error retry attempt(0): Connection already closed How do I understand which data is wrong?
February 23, 20242 yr Hi Everyone, thank you for the info and efforts. I am using 4 x 50kw Deye Invertors, I am new to home assistant. I tried connecting my Master (M1) as per the video. Getting a lot of warnings 😬 Anyone has experience on getting this to work with inverters in parrallel ?
August 12, 20241 yr On 2024/02/23 at 3:44 PM, HannesVenter said: Hi Everyone, thank you for the info and efforts. I am using 4 x 50kw Deye Invertors, I am new to home assistant. I tried connecting my Master (M1) as per the video. Getting a lot of warnings 😬 Anyone has experience on getting this to work with inverters in parrallel ? Hello Hannes, I gave up with KellerZA integration with the Deye or Sunsynk 50kW units. The integration kept crashing from the errors. From what I understand is that you need to connect each inverter separately to a RS485 module to get the data from all the inversters. I believe that the comms does not work with the daisy chain even with a termination resistor. @kellerza, do you have any suggestions here. I have posted on other discussion asking about the the Sunsynk 50kW units. It would also be great if you could explain how to configure your integration to work with inverters in Parallel in the documentation. Been wanting to setup your solution for my parents with their two 12kW 3phase units.
October 8, 20241 yr Hi All, I have installed the Add On and configured as per the video linked above but when i start it i get the following in the log I have a chase megarevo inverter https://www.voltex.co.za/product/megarevo-chase-technologies-hybrid-inverter-ess-8kw-8kl1/ i comes with a solarman dongle which i have installed and connected to any advice would be welcome 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 07:54:07 INFO Loading configuration: /data/options.json 07:54:07 INFO sunsynk library version: 0.6.4 07:54:07 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 | * | 15 | 60 | 80 | | | | kwh | | 300 | 300 | | | | | any_unit | | 15 | 300 | | | | | no_unit | | 15 | 300 | | | True | +-----------+-----+------+--------+-----------+----------+------------+ 07:54:07 INFO Using Single phase sensor definitions. 07:54:07 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial 07:54:07 INFO Connecting to tcp://192.168.69.198:8899 Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/pysolarmanv5/pysolarmanv5_async.py", line 78, in connect self.reader, self.writer = await asyncio.open_connection( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/streams.py", line 48, in open_connection transport, _ = await loop.create_connection( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1085, in create_connection raise exceptions[0] File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1069, in create_connection sock = await self._connect_sock( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/base_events.py", line 973, in _connect_sock await self.sock_connect(sock, address) File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 634, in sock_connect return await fut ^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 674, in _sock_connect_cb raise OSError(err, f'Connect call failed {address}') OSError: [Errno 113] Connect call failed ('192.168.69.198', 8899) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 79, in <module> main() File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 74, in main loop.run_until_complete(main_loop(loop)) File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete return future.result() ^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/__main__.py", line 39, in main_loop await ist.connect() File "/usr/local/lib/python3.11/site-packages/ha_addon_sunsynk_multi/a_inverter.py", line 114, in connect await self.inv.connect() File "/usr/local/lib/python3.11/site-packages/sunsynk/solarmansunsynk.py", line 55, in connect await self.client.connect() File "/usr/local/lib/python3.11/site-packages/pysolarmanv5/pysolarmanv5_async.py", line 83, in connect raise NoSocketAvailableError( pysolarmanv5.pysolarmanv5.NoSocketAvailableError: Cannot open connection to 192.168.69.198 [07:54:11] WARNING: Halt add-on with exit code 1 s6-rc: info: service legacy-services: stopping 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
October 11, 20241 yr After some tests and research and testing, I think the dongle I have (LSW-5) is not supported. I did a port scan on the dongle and only port 80 is open no others and no response from 8899 logging in to port 80 i get an admin interface Seems i have the ability to configure a secondary server to receive data, no idea of how to set that up With the solarman app on my phone I can do a local connection via Bluetooth, and get all the stats and update the settings of the inverter. Edited October 11, 20241 yr by regbes
October 16, 20241 yr Hi everybody. I was able to install this according to the video, using Solarman dongle and Deye hybrid inverter. Thank you very much, I have searched for months!! Some of the readings from the dongle seems to have decimal errors. My battery voltage is 52.6V, but is shown to be 526.7V. PV power are 312W(no sun), but the app show 3120W. Also when changing the power in TOU with the app, for example changing from 5000W to 4900W, the actual value in the inverter will be 490W. The log shows this: Quote 2024-10-16 12:17:40,354 DEBUG sunsynk.sensors prog4_power=50000W (5000,) Quote 13:03:06 INFO Queue update prog6_power=4900 13:03:07 INFO Writing sensor prog6_power=4900 Registers:{159=0x01ea} Is there anyway to fix this problem? My mistake, under "Sensor definitions" I choose "three-phase-hv" instead of correct "three-phase". Edited October 16, 20241 yr by Kristian55 Solved
October 19, 20241 yr Would appreciate some help getting it working please. Sunsynk Inverter with splitter on CAN port. Confirmed that I can still communicate with batteries USB to RS485 plugged into splitter at one end and connective to this device at the other (connected three wires to points on this device). USB device plugged into Home Assistant server MQTT addon configured. MQTT integration says 'core-mosquitto' but not devices/entries Sunsynk/Deye Inverter Add-on (multi) add on configured as below pymodbus single-phase Inverters as below. Modbus ID is 01 on the inverter. - SERIAL_NR: "2xxxx" HA_PREFIX: SS MODBUS_ID: 1 DONGLE_SERIAL_NUMBER: "0" PORT: tcp://homeassistant.local:502 Confirmed host/username/password Addon logs say the following. [19:47:02] 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 19:47:08 INFO Loading configuration: /data/options.json 19:47:08 INFO sunsynk library version: 0.6.5 19:47:08 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 | +-----------+-----+------+--------+-----------+----------+------------+ 19:47:08 INFO Using Single phase sensor definitions. 19:47:08 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial 19:47:08 INFO Connecting to tcp://homeassistant.local:502 19:47:08 INFO PyModbus 3.7.2 tcp: homeassistant.local:502 19:47:08 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 19:47:08 INFO ############################################################ 19:47:08 INFO Could not connect to tcp://homeassistant.local:502: 19:47:08 INFO ############################################################ 19:47:08 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. Not sure I understand enough of how MQTT works and the flow to understand where I might be going wrong. Any assistance greatly appreciated
November 3, 20241 yr On 2024/10/19 at 9:52 PM, mdeakin said: Would appreciate some help getting it working please. Sunsynk Inverter with splitter on CAN port. Confirmed that I can still communicate with batteries USB to RS485 plugged into splitter at one end and connective to this device at the other (connected three wires to points on this device). USB device plugged into Home Assistant server MQTT addon configured. MQTT integration says 'core-mosquitto' but not devices/entries Sunsynk/Deye Inverter Add-on (multi) add on configured as below pymodbus single-phase Inverters as below. Modbus ID is 01 on the inverter. - SERIAL_NR: "2xxxx" HA_PREFIX: SS MODBUS_ID: 1 DONGLE_SERIAL_NUMBER: "0" PORT: tcp://homeassistant.local:502 Confirmed host/username/password Addon logs say the following. [19:47:02] 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 19:47:08 INFO Loading configuration: /data/options.json 19:47:08 INFO sunsynk library version: 0.6.5 19:47:08 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 | +-----------+-----+------+--------+-----------+----------+------------+ 19:47:08 INFO Using Single phase sensor definitions. 19:47:08 INFO Added hidden sensors as other sensors depend on it: Rated power, Serial 19:47:08 INFO Connecting to tcp://homeassistant.local:502 19:47:08 INFO PyModbus 3.7.2 tcp: homeassistant.local:502 19:47:08 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 19:47:08 INFO ############################################################ 19:47:08 INFO Could not connect to tcp://homeassistant.local:502: 19:47:08 INFO ############################################################ 19:47:08 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. Not sure I understand enough of how MQTT works and the flow to understand where I might be going wrong. Any assistance greatly appreciated Not sure if this will help you, but may help someone When using the RS485 to USB method, the port needs to be changed to /dev/ttyUSB0 (substitute the 0 with 1 or 2 or 3 or however many USB ports you have) I was lucky and it picked it up as USB0. My report looks like this now: 09:42:57 INFO Connecting to /dev/ttyUSB0 09:42:57 INFO PyModbus 3.7.2 Serial: /dev/ttyUSB0 09:42:57 INFO Reading startup sensors Prog4 Time, Prog3 Time, Prog5 Time, Rated power, Prog2 Time, Battery Low Capacity, Prog1 Time, Serial, Prog6 Time 09:42:58 INFO ############################################################ 09:42:58 INFO Inverter serial number '****4190' 09:42:58 INFO ############################################################ 09:42:58 INFO MQTT: Connecting to Mqqt_user@core-mosquitto:1883 09:42:58 INFO MQTT: Connection successful 09:42:59 INFO Read every (inverter 1) +-----+----------------------------------------------------------------------------------+ | s | Sensors | +-----+----------------------------------------------------------------------------------+ | 5 | prog6_power, prog4_time, prog6_charge, prog5_time, grid_l2_power, prog1_time, | | | prog2_capacity, prog5_charge, essential_power, load_limit, battery_low_capacity, | | | non_essential_power, prog1_power, pv2_power, prog2_charge, prog5_capacity, | | | prog4_charge, prog4_power, prog3_power, prog3_time, prog1_capacity, pv1_power, | | | prog1_charge, inverter_power, prog3_capacity, prog6_time, grid_power, | | | grid_ct_power, prog4_capacity, aux_power, prog2_power, prog6_capacity, | | | use_timer, battery_power, prog5_power, prog2_time, prog3_charge, priority_load | | 15 | grid_connected, load_frequency, pv1_voltage, battery_voltage, pv1_current, | | | overall_state, battery_soc, battery_current, inverter_current, pv2_voltage, | | | grid_voltage, grid_frequency, pv2_current | | 300 | day_battery_charge, day_load_energy, day_pv_energy, total_grid_import, | | | day_grid_import, day_grid_export, total_pv_energy, day_battery_discharge, | | | total_battery_discharge, total_battery_charge, total_grid_export | +-----+----------------------------------------------------------------------------------+ 09:42:59 INFO Report every (inverter 1) +-----+----------------------------------------------------------------------------------+ | s | Sensors | +-----+----------------------------------------------------------------------------------+ | 60 | non_essential_power, pv2_power, grid_power, aux_power, battery_power, pv1_power, | | | grid_l2_power, inverter_power, essential_power, grid_ct_power | | 300 | day_load_energy, prog6_power, pv1_voltage, prog4_time, battery_voltage, | | | prog6_charge, overall_state, prog5_time, total_pv_energy, prog2_capacity, | | | pv2_voltage, prog1_time, prog5_charge, battery_low_capacity, load_limit, | | | prog1_power, day_battery_charge, prog2_charge, day_grid_export, | | | inverter_current, prog5_capacity, grid_frequency, prog4_charge, prog4_power, | | | prog3_power, day_pv_energy, load_frequency, total_grid_import, pv1_current, | | | prog3_time, battery_soc, prog1_capacity, prog1_charge, prog3_capacity, | | | grid_voltage, pv2_current, prog6_time, grid_connected, prog4_capacity, | | | prog6_capacity, prog2_power, day_grid_import, use_timer, prog5_power, | | | battery_current, prog2_time, day_battery_discharge, total_battery_discharge, | | | total_battery_charge, prog3_charge, total_grid_export, priority_load | +-----+----------------------------------------------------------------------------------+ The next step is actually getting this info into the Sunsynk card, as it still doesn't show any data.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.