March 13, 20224 yr I have installed the software according to the link from kellerza https://github.com/kellerza/sunsynk But i get no communication to home assistant via the rs485-usb converter. I have installed Modbus TCP to Modbus RTU Gateway Add-on but get the following message: 15:48:14] INFO: Starting mbusd -d -L - -v 2 -p /dev/ttyS0 -s 9600 -m 8N1 -P 502 13 Mar 2022 15:48:14 mbusd-0.5.1 started... 13 Mar 2022 15:48:14 tty: trying to open /dev/ttyS0 (speed 9600 mode 8N1) 13 Mar 2022 15:48:14 conn_init(): can't open tty device /dev/ttyS0 (I/O error) 13 Mar 2022 15:48:14 conn_init() failed, exiting... have configured /dev/ttyS0 to be the device have tried all of them but still no connection:- please if anybody can help me
March 13, 20224 yr Your usb converter is almost certainly not mounted at /dev/ttyS0; it should be /dev/ttyUSB0 (or more). It might be that the usb converter is not picked up, or the config is incorrect. If you look at: https://github.com/kellerza/sunsynk/blob/main/hass-addon-mbusd/config.yaml You will see it pointing to /dev/ttyUSB0. If you don't have /dev/ttyUSB0 then your USB converter is not being picked up correctly. Edited March 13, 20224 yr by P1000
March 13, 20224 yr Author I get the following when trying to connect: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-03-13 18:19:56,507 INFO Loading HASS OS configuration 2022-03-13 18:19:56,514 DEBUG could not patch umodbus: numpy not found 2022-03-13 18:19:56,517 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-03-13 18:19:56,518 INFO Connecting to serial:///dev/ttyUSB0 2022-03-13 18:19:56,525 ERROR Read Error: (1,3,5) [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' 2022-03-13 18:19:56,526 INFO ############################################################ 2022-03-13 18:19:56,526 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2022-03-13 18:19:56,527 INFO ############################################################ 2022-03-13 18:19:56,528 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart if i do ls -l /dev/ttyUSB* ubuntu does display ttyUSB0 Sunsynk Inverter Add-on Current version: 2022.03.04-0.1.4
April 3, 20224 yr Author I bought this device but I have seen comments that it is not good quality - should I may be buy the more expensive units?
April 7, 20224 yr [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-03-13 18:19:56,507 INFO Loading HASS OS configuration 2022-03-13 18:19:56,514 DEBUG could not patch umodbus: numpy not found 2022-03-13 18:19:56,517 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-03-13 18:19:56,518 INFO Connecting to serial:///dev/ttyUSB0 2022-03-13 18:19:56,525 ERROR Read Error: (1,3,5) [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' How are you running Home Assistant? If you're running it in a container (i.e. docker). if so, you'll need to map /dev/ttyUSB0 -> the container, or be running in privileged mode. I think the default install will map devices, but I need to check. Home Assistant also likes devices to be plugged in after its running. So boot up first make sure HA is running, *then* plugin the USB ,and see if it can see ttyUSB0 inside the container. If still no luck, then manually check inside the container to see if its seeing the device. I'd also check outside to see if it see's it. eg - inside the os dmesg grep usb ls /dev/ttyUSB* within the container that runs HA - dmesg grep usb ls /dev/ttyUSB* You'll need some cli experience - i.e. with ssh and docker. you'll need to check that the OS see's the device. Worst case can assist further Edited April 7, 20224 yr by shanghailoz
April 9, 20224 yr Author Home Assistant is running in a Virtual Box on Linux Ubuntu I get the following messages in home assistant terminal: and on the log file i get 2022-04-09 10:40:03,525 INFO Loading HASS OS configuration 2022-04-09 10:40:03,532 DEBUG could not patch umodbus: numpy not found 2022-04-09 10:40:03,535 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-04-09 10:40:03,536 INFO Connecting to serial:///dev/ttyUSB2 2022-04-09 10:40:03,543 ERROR Read Error: (1,3,5) [Errno 2] could not open port /dev/ttyUSB2: [Errno 2] No such file or directory: '/dev/ttyUSB2' 2022-04-09 10:40:03,544 INFO ############################################################ 2022-04-09 10:40:03,544 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2022-04-09 10:40:03,545 INFO ############################################################ 2022-04-09 10:40:03,545 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. have also tried USB0 and USB1 The config file is as follows PORT: serial:///dev/ttyUSB0 DRIVER: umodbus SUNSYNK_ID: '2***********' SENSOR_PREFIX: '' SENSORS: - total_pv_power - total_battery_charge - total_battery_discharge - total_grid_export - total_grid_import - battery_soc PROFILES: [] MODBUS_SERVER_ID: 1 MQTT_HOST: core-mosquitto MQTT_PORT: 1883 MQTT_USERNAME: hass MQTT_PASSWORD: '' DEBUG: 0 On Ubuntu terminal I do get /dev/ttyUSB0
April 9, 20224 yr Author Found the problem - I am running home assistant on an ubuntu server under virtualbox. You need to enable usb under virtualbox otherwise no usb device will be seen in Home Assistant Thanks Edited April 10, 20224 yr by MV SOLAR
April 10, 20224 yr Author But still not reading the data get the following logging data: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-04-10 11:06:33,585 INFO Loading HASS OS configuration 2022-04-10 11:06:33,614 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-04-10 11:06:33,624 INFO Protocol made connection. 2022-04-10 11:06:33,625 INFO Connected to /dev/ttyUSB0 2022-04-10 11:06:43,631 ERROR Timeout reading: 2022-04-10 11:06:43,632 INFO ############################################################ 2022-04-10 11:06:43,633 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2022-04-10 11:06:43,634 INFO ############################################################ 2022-04-10 11:06:43,634 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. [cmd] ./run.py exited 0 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. 2022-04-10 11:07:40,854 INFO Protocol made connection. 2022-04-10 11:07:40,856 INFO Connected to /dev/ttyUSB0 2022-04-10 11:07:40,917 INFO ############################################################ 2022-04-10 11:07:40,918 INFO Inverter serial number '2111255555' 2022-04-10 11:07:40,918 INFO ############################################################ 2022-04-10 11:07:40,918 INFO MQTT: Connecting to mqtt_user@core-mosquitto:1883 2022-04-10 11:07:40,954 INFO MQTT: Connection successful 2022-04-10 11:07:51,980 ERROR Timeout reading: 2022-04-10 11:07:51,982 INFO Retrying individual sensors: ['Total PV Power:last', 'Total Battery Charge:last', 'Total Battery Discharge:last', 'Total Grid Export:last', 'Total Grid Import:last', 'Battery SOC:last'] 2022-04-10 11:08:02,017 ERROR Timeout reading: Total PV Power 2022-04-10 11:08:12,055 ERROR Timeout reading: Total Battery Charge 2022-04-10 11:08:22,090 ERROR Timeout reading: Total Battery Discharge 2022-04-10 11:08:32,125 ERROR Timeout reading: Total Grid Export 2022-04-10 11:08:42,159 ERROR Timeout reading: Total Grid Import 2022-04-10 11:08:52,195 ERROR Timeout reading: Battery SOC 2022-04-10 11:09:02,220 ERROR Timeout reading:
April 20, 20224 yr On 2022/04/10 at 11:12 AM, MV SOLAR said: But still not reading the data get the following logging data: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-04-10 11:06:33,585 INFO Loading HASS OS configuration 2022-04-10 11:06:33,614 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-04-10 11:06:33,624 INFO Protocol made connection. 2022-04-10 11:06:33,625 INFO Connected to /dev/ttyUSB0 2022-04-10 11:06:43,631 ERROR Timeout reading: 2022-04-10 11:06:43,632 INFO ############################################################ 2022-04-10 11:06:43,633 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2022-04-10 11:06:43,634 INFO ############################################################ 2022-04-10 11:06:43,634 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. [cmd] ./run.py exited 0 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. 2022-04-10 11:07:40,854 INFO Protocol made connection. 2022-04-10 11:07:40,856 INFO Connected to /dev/ttyUSB0 2022-04-10 11:07:40,917 INFO ############################################################ 2022-04-10 11:07:40,918 INFO Inverter serial number '2111255555' 2022-04-10 11:07:40,918 INFO ############################################################ 2022-04-10 11:07:40,918 INFO MQTT: Connecting to mqtt_user@core-mosquitto:1883 2022-04-10 11:07:40,954 INFO MQTT: Connection successful 2022-04-10 11:07:51,980 ERROR Timeout reading: 2022-04-10 11:07:51,982 INFO Retrying individual sensors: ['Total PV Power:last', 'Total Battery Charge:last', 'Total Battery Discharge:last', 'Total Grid Export:last', 'Total Grid Import:last', 'Battery SOC:last'] 2022-04-10 11:08:02,017 ERROR Timeout reading: Total PV Power 2022-04-10 11:08:12,055 ERROR Timeout reading: Total Battery Charge 2022-04-10 11:08:22,090 ERROR Timeout reading: Total Battery Discharge 2022-04-10 11:08:32,125 ERROR Timeout reading: Total Grid Export 2022-04-10 11:08:42,159 ERROR Timeout reading: Total Grid Import 2022-04-10 11:08:52,195 ERROR Timeout reading: Battery SOC 2022-04-10 11:09:02,220 ERROR Timeout reading: I'm having the same issues with my DEYE 8kw inverter. I eventually just gave up. Pretty much getting the same as what you are getting above. I get this 1st as per below. ############################################################ "No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc" ############################################################ and then i sometimes get the below with my inverter serial number ############################################################ Inverter serial number '2315xxxxxx' ############################################################ I wonder if this info below would make any difference? I don't know anything about the coding or if it is even relevant to the code, but they are saying there are differences between the 5KW and the 8KW. maybe the code has to read each one differently????? Who knows. I have an 8KW inverter. "Another confusion is that the 5.5kw and the 8.8kw does not use the same markings for connecting up the GEN/GRID/LOAD." 8.8kw is GRID/GEN/LOAD 5.5kw is GEN/LOAD/GRID 8.8kw is X/N/L 5.5kw is L/N/E
June 10, 20224 yr Same issue here. Been bashing my head against it for 3 days and not getting anywhere! 2 x 8KW Inverters in parallel, a PI3 and this RS485 converter: https://www.robotics.org.za/RS485-3P Managed to get a serial number out of the inverter but nothing else - just timeouts. Chopped the RS and USB cable to 30cm just in case - still no joy. ---------------------------------------------------------------------------- [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-06-10 18:28:10,130 INFO Loading HASS OS configuration 2022-06-10 18:28:10,164 DEBUG could not patch umodbus: numpy not found 2022-06-10 18:28:10,174 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-06-10 18:28:10,177 INFO Connecting to serial:///dev/ttyUSB0 2022-06-10 18:28:10,301 INFO ############################################################ 2022-06-10 18:28:10,302 INFO Inverter serial number 'XXXXXXXXXX' 2022-06-10 18:28:10,302 INFO ############################################################ 2022-06-10 18:28:10,304 INFO MQTT: Connecting to user@core-mosquitto:1883 2022-06-10 18:28:14,910 INFO MQTT: Connection successful 2022-06-10 18:28:25,906 ERROR Timeout reading: 2022-06-10 18:28:25,908 INFO Retrying individual sensors: ['Total PV Power:last', 'Total Battery Charge:last', 'Total Battery Discharge:last', 'Total Grid Export:last', 'Total Grid Import:last', 'Battery SOC:last'] 2022-06-10 18:28:35,957 ERROR Timeout reading: Total PV Power 2022-06-10 18:28:46,001 ERROR Timeout reading: Total Battery Charge ---------------------------------------------------------------------------- Anyone have any ideas? I'm out!
July 26, 20224 yr On 2022/06/10 at 7:11 PM, Maniac said: Same issue here. Been bashing my head against it for 3 days and not getting anywhere! 2 x 8KW Inverters in parallel, a PI3 and this RS485 converter: https://www.robotics.org.za/RS485-3P Managed to get a serial number out of the inverter but nothing else - just timeouts. Chopped the RS and USB cable to 30cm just in case - still no joy. ---------------------------------------------------------------------------- [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-06-10 18:28:10,130 INFO Loading HASS OS configuration 2022-06-10 18:28:10,164 DEBUG could not patch umodbus: numpy not found 2022-06-10 18:28:10,174 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-06-10 18:28:10,177 INFO Connecting to serial:///dev/ttyUSB0 2022-06-10 18:28:10,301 INFO ############################################################ 2022-06-10 18:28:10,302 INFO Inverter serial number 'XXXXXXXXXX' 2022-06-10 18:28:10,302 INFO ############################################################ 2022-06-10 18:28:10,304 INFO MQTT: Connecting to user@core-mosquitto:1883 2022-06-10 18:28:14,910 INFO MQTT: Connection successful 2022-06-10 18:28:25,906 ERROR Timeout reading: 2022-06-10 18:28:25,908 INFO Retrying individual sensors: ['Total PV Power:last', 'Total Battery Charge:last', 'Total Battery Discharge:last', 'Total Grid Export:last', 'Total Grid Import:last', 'Battery SOC:last'] 2022-06-10 18:28:35,957 ERROR Timeout reading: Total PV Power 2022-06-10 18:28:46,001 ERROR Timeout reading: Total Battery Charge ---------------------------------------------------------------------------- Anyone have any ideas? I'm out! Did you manage to get this resolved?
July 27, 20224 yr On 2022/06/10 at 7:11 PM, Maniac said: 2 x 8KW Inverters in parallel, From studying the implementation a bit, RS485 cannot really have multiple masters... well not unless there is some form of collision detection like Modbus tcp. I would assume that the master inverter (in parallel configuration) drives the bus (the modbus not a putco one). So I am not sure you will be able to connect and talk to the inverters over modbus (RS485) when there is already a master. A workaround might be to implementing the comms on a CAN-bus. Since it allows multiple masters. In theory you should be able to daisy chain all the devides together eg. BMS, Inverter, smart shunt etc and be able to talk to all of them from the Pi or Esp
August 3, 20223 yr On 2022/07/27 at 2:07 PM, Speedster said: Why don't you just use the solarman ingtegration for HA? The newer Sunsynk inverters come with a Synsunk dongle instead of the older Solarman dongle. This obviously does not work with Solarman.
September 15, 20223 yr I have also bumped my head for 2 days now. This is my Log: Any help would be greatly appreciated. Thank you. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. 2022-09-14 18:22:18,054 INFO Loading HASS OS configuration 2022-09-14 18:22:18,207 DEBUG could not patch umodbus: numpy not found 2022-09-14 18:22:18,213 DEBUG last unit:kWh, id:total_pv_power 2022-09-14 18:22:18,214 DEBUG last unit:kWh, id:total_battery_charge 2022-09-14 18:22:18,215 DEBUG last unit:kWh, id:total_battery_discharge 2022-09-14 18:22:18,215 DEBUG last unit:kWh, id:total_grid_export 2022-09-14 18:22:18,216 DEBUG last unit:kWh, id:total_grid_import 2022-09-14 18:22:18,217 DEBUG last unit:%, id:battery_soc 2022-09-14 18:22:18,217 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2022-09-14 18:22:18,218 DEBUG Using selector: EpollSelector 2022-09-14 18:22:18,220 INFO Connecting to serial:///dev/ttyUSB0 2022-09-14 18:22:18,779 WARNING Executing <Task pending name='Task-2' coro=<Sunsynk.read_sensors() running at /usr/local/lib/python3.9/site-packages/sunsynk/sunsynk.py:52> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x7fb08debe0>()] created at /usr/local/lib/python3.9/asyncio/base_events.py:424> cb=[_release_waiter(<Future pendi...events.py:424>)() at /usr/local/lib/python3.9/asyncio/tasks.py:416] created at /usr/local/lib/python3.9/asyncio/tasks.py:462> took 0.234 seconds 2022-09-14 18:22:28,554 ERROR Timeout reading: 2022-09-14 18:22:28,555 INFO ############################################################ 2022-09-14 18:22:28,555 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2022-09-14 18:22:28,556 INFO ############################################################ 2022-09-14 18:22:28,556 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. 2022-09-14 18:22:58,590 DEBUG Close <_UnixSelectorEventLoop running=False closed=False debug=True> [cmd] ./run.py exited 0 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. Dongle that I use: https://www.robotics.org.za/W17286 Modbus Log when rs485 dongle is removed from RPi4 USB: 15 Sep 2022 09:34:46 tty: trying to open /dev/ttyUSB0 (speed 9600 mode 8N1) 15 Sep 2022 09:34:46 tty_reopen(): can't open tty device /dev/ttyUSB0 (No such file or directory) Modbus Log when rs485 dongle is present in the RPi4 USB: 09:42:48] INFO: Starting mbusd -d -L - -v 2 -p /dev/ttyUSB0 -s 9600 -m 8N1 -P 502 15 Sep 2022 09:42:49 mbusd-0.5.1 started... 15 Sep 2022 09:42:49 tty: trying to open /dev/ttyUSB0 (speed 9600 mode 8N1) So it looks like the USB is "seen" by the RPi4 HA (running in a docker) ?
September 15, 20223 yr 6 minutes ago, BigFan said: So it looks like the USB is "seen" by the RPi4 HA (running in a docker) ? Yes, docker won't have access to the USB unless you explicitly give it access: https://stackoverflow.com/questions/24225647/docker-a-way-to-give-access-to-a-host-usb-or-serial-device
September 15, 20223 yr Thank you P1000 I now sit with another problem... When I go into Terminal (HA) and type login, it prompts me for a login and password!!! I have not seen this before. What do I do now? Any idea? Not to worry.... I came right. It's working now, but get lots of timeouts? 2022-09-15 16:33:49,179 DEBUG Request registers: [72, 73, 74, 75] glen=4. Response [480, 0, 408, 0] len=4. regs={72: 480, 73: 0, 74: 408, 75: 0} 2022-09-15 16:33:59,126 ERROR Timeout reading: 2022-09-15 16:35:08,394 ERROR Timeout reading: 2022-09-15 16:36:17,676 ERROR Timeout reading: 2022-09-15 16:37:17,007 DEBUG Request registers: [72, 73, 74, 75] glen=4. Response [480, 0, 408, 0] len=4. regs={72: 480, 73: 0, 74: 408, 75: 0} 2022-09-15 16:37:17,058 DEBUG Request registers: [78] glen=1. Response [469] len=1. regs={78: 469} 2022-09-15 16:37:17,118 DEBUG Request registers: [80, 81, 82] glen=3. Response [0, 0, 0] len=3. regs={80: 0, 81: 0, 82: 0} 2022-09-15 16:37:17,170 DEBUG Request registers: [96, 97] glen=2. Response [1197, 0] len=2. regs={96: 1197, 97: 0} 2022-09-15 16:37:26,948 ERROR Timeout reading: 2022-09-15 16:38:26,282 DEBUG Request registers: [72, 73, 74, 75] glen=4. Response [480, 0, 408, 0] len=4. regs={72: 480, 73: 0, 74: 408, 75: 0} 2022-09-15 16:38:36,231 ERROR Timeout reading: 2022-09-15 16:39:35,570 DEBUG Request registers: [72, 73, 74, 75] glen=4. Response [480, 0, 408, 0] len=4. regs={72: 480, 73: 0, 74: 408, 75: 0} 2022-09-15 16:39:35,622 DEBUG Request registers: [78] glen=1. Response [469] len=1. regs={78: 469} 2022-09-15 16:39:35,682 DEBUG Request registers: [80, 81, 82] glen=3. Response [0, 0, 0] len=3. regs={80: 0, 81: 0, 82: 0} 2022-09-15 16:39:35,733 DEBUG Request registers: [96, 97] glen=2. Response [1197, 0] len=2. regs={96: 1197, 97: 0} 2022-09-15 16:39:45,515 ERROR Timeout reading: 2022-09-15 16:40:44,845 DEBUG Request registers: [72, 73, 74, 75] glen=4. Response [480, 0, 408, 0] len=4. regs={72: 480, 73: 0, 74: 408, 75: 0} 2022-09-15 16:40:44,895 DEBUG Request registers: [78] glen=1. Response [469] len=1. regs={78: 469} 2022-09-15 16:40:44,956 DEBUG Request registers: [80, 81, 82] glen=3. Response [0, 0, 0] len=3. regs={80: 0, 81: 0, 82: 0} 2022-09-15 16:40:45,008 DEBUG Request registers: [96, 97] glen=2. Response [1197, 0] len=2. regs={96: 1197, 97: 0} 2022-09-15 16:40:54,793 ERROR Timeout reading: 2022-09-15 16:41:54,133 DEBUG Request registers: [72, 73, 74, 75] glen=4. Response [480, 0, 408, 0] len=4. regs={72: 480, 73: 0, 74: 408, 75: 0} 2022-09-15 16:41:54,185 DEBUG Request registers: [78] glen=1. Response [469] len=1. regs={78: 469} 2022-09-15 16:41:54,246 DEBUG Request registers: [80, 81, 82] glen=3. Response [0, 0, 0] len=3. regs={80: 0, 81: 0, 82: 0} 2022-09-15 16:42:04,077 ERROR Timeout reading: Edited September 15, 20223 yr by BigFan
January 14, 20233 yr Hi All. So I got my SunSynk to connected to HA. I see there is a sensor .py file to get more of the system but I have no idea where to put it in my HA? Please can someone guide me?
January 24, 20233 yr I had the same issue and the issue still exist. As a work around, I installed "Modbus TCP to Modbus RTU Gateway Add-on" and used the pymobus serial connection DEVICE: /dev/ttyUSB0 BAUDRATE: 9600 MODE: 8N1 TIMEOUT: 5 LOGLEVEL: 2 PORT: xx.xxx.xxx.xxx:502 DEVICE: /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0 DRIVER: pymodbus
January 27, 20233 yr On 2023/01/24 at 8:39 PM, No Name said: I had the same issue and the issue still exist. As a work around, I installed "Modbus TCP to Modbus RTU Gateway Add-on" and used the pymobus serial connection DEVICE: /dev/ttyUSB0 BAUDRATE: 9600 MODE: 8N1 TIMEOUT: 5 LOGLEVEL: 2 PORT: xx.xxx.xxx.xxx:502 DEVICE: /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0 DRIVER: pymodbus Tried this route thanks. Both ways work for me but i get initial Data to mqtt and then just no new data. Almost stale. @kellerza Not sure if there is an issue.
January 27, 20233 yr 2 minutes ago, Jack Kitley said: Tried this route thanks. Both ways work for me but i get initial Data to mqtt and then just no new data. Almost stale. @kellerza Not sure if there is an issue. 2nd attempt was using umodbus and this also times out it seems.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.