discere

Just to close up this thread, thank you to everyone who helped. Great community here! My system is working as I wanted it to now, with data pulling into HA and I've got some automations configured to run based on current PV power, headroom etc.

Just an update here. I purchased a USR-TCP gateway and the system now works, thanks! https://www.robotics.org.za/USR-TCP232-410S?search=usr

I believe that this is the issue I'm dealing with. Even if I use another tool to try to interact with the gateway, anything to do with Modbus doesn't seem to work.

The correct address of the RS485 gateway is .201. I've subsequently removed the server address from the gateway's config. This seems to be for some other sort of configuration where the gateway is connecting to another server (?). Removing this value doesn't change anything in the HA logs. HA reports that it connected to the gateway, but after that the Modbus portion of the equation seems to fail. Could be? 1. Gateway doesn't operate with Modbus. In the manual for the gateway it mentions that it does support Modbus RTU: 2. Wrong pinout has been used? See recent logs below: 2023-02-06 10:13:18,308 INFO Loading HASS OS configuration 2023-02-06 10:13:18,312 DEBUG could not patch umodbus: numpy not found 2023-02-06 10:13:18,314 INFO ############################################################ 2023-02-06 10:13:18,314 INFO Sensor deprecated: total_pv_power -> total_pv_energy 2023-02-06 10:13:18,314 INFO ############################################################ 2023-02-06 10:13:18,314 DEBUG last unit:kWh, id:total_pv_power 2023-02-06 10:13:18,314 DEBUG last unit:kWh, id:total_battery_charge 2023-02-06 10:13:18,314 DEBUG last unit:kWh, id:total_battery_discharge 2023-02-06 10:13:18,315 DEBUG last unit:kWh, id:total_grid_export 2023-02-06 10:13:18,315 DEBUG last unit:kWh, id:total_grid_import 2023-02-06 10:13:18,315 DEBUG last unit:%, id:battery_soc 2023-02-06 10:13:18,315 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2023-02-06 10:13:18,315 DEBUG Using selector: EpollSelector 2023-02-06 10:13:18,318 INFO Reading startup sensors rated_power, serial 2023-02-06 10:13:18,320 DEBUG open connection (#1) 2023-02-06 10:13:18,325 DEBUG <asyncio.TransportSocket fd=8, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.30.33.2', 34034), raddr=('192.168.0.201', 502)> connected to 192.168.0.201:502: (<_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>>, <sockio.aio.StreamReaderProtocol object at 0x7fdc00c09760>) 2023-02-06 10:13:28,332 ERROR Timeout reading: 2023-02-06 10:13:28,332 INFO ############################################################ 2023-02-06 10:13:28,332 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2023-02-06 10:13:28,332 INFO ############################################################ 2023-02-06 10:13:28,332 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically. 2023-02-06 10:13:58,363 DEBUG Close <_UnixSelectorEventLoop running=False closed=False debug=True>

Adding DEBUG level 2 logs: 2023-02-06 09:40:16,004 INFO Loading HASS OS configuration 2023-02-06 09:40:16,018 DEBUG could not patch umodbus: numpy not found 2023-02-06 09:40:16,020 INFO ############################################################ 2023-02-06 09:40:16,020 INFO Sensor deprecated: total_pv_power -> total_pv_energy 2023-02-06 09:40:16,020 INFO ############################################################ 2023-02-06 09:40:16,020 DEBUG last unit:kWh, id:total_pv_power 2023-02-06 09:40:16,020 DEBUG last unit:kWh, id:total_battery_charge 2023-02-06 09:40:16,021 DEBUG last unit:kWh, id:total_battery_discharge 2023-02-06 09:40:16,021 DEBUG last unit:kWh, id:total_grid_export 2023-02-06 09:40:16,021 DEBUG last unit:kWh, id:total_grid_import 2023-02-06 09:40:16,021 DEBUG last unit:%, id:battery_soc 2023-02-06 09:40:16,021 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2023-02-06 09:40:16,021 DEBUG Using selector: EpollSelector 2023-02-06 09:40:16,026 INFO Reading startup sensors serial, rated_power 2023-02-06 09:40:16,031 DEBUG open connection (#1) 2023-02-06 09:40:16,040 DEBUG <asyncio.TransportSocket fd=8, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.30.33.2', 34886), raddr=('192.168.0.201', 502)> connected to 192.168.0.201:502: (<_SelectorSocketTransport fd=8 read=polling write=<idle, bufsize=0>>, <sockio.aio.StreamReaderProtocol object at 0x7f8468d607c0>) 2023-02-06 09:40:26,042 ERROR Timeout reading: 2023-02-06 09:40:26,042 INFO ############################################################ 2023-02-06 09:40:26,042 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2023-02-06 09:40:26,042 INFO ############################################################ 2023-02-06 09:40:26,042 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.

I'm going to continue my debug checking in this thread. I believe the issue may be related to the pinout/wiring differences between SunSynk 5 and 8.8kw inverters as mentioned here. I am not sure how to interpret this really. Is this the serial output? 🤔 EG: RS485 requires a twisted pair, this works with CAT5 network cable and RJ-45 connectors. If the RJ-45 connector on the inverter side is crimped according to T568A, you can use the pinout in the following table. RJ45 Pin (inverter side) Wire Color (when using T568A) RS485 pins 1 Green-White B/D- 2 Green A/D+ 3 Orange-White GND

Okay ignore previous, it seems there is no data available at my gateway 😕 2023-02-06 09:22:03,818 INFO Loading HASS OS configuration 2023-02-06 09:22:03,823 DEBUG could not patch umodbus: numpy not found 2023-02-06 09:22:03,824 INFO ############################################################ 2023-02-06 09:22:03,825 INFO Sensor deprecated: total_pv_power -> total_pv_energy 2023-02-06 09:22:03,825 INFO ############################################################ 2023-02-06 09:22:03,825 INFO Filter *last used for battery_soc, total_battery_charge, total_battery_discharge, total_grid_export, total_grid_import, total_pv_power 2023-02-06 09:22:03,830 INFO Reading startup sensors serial, rated_power 2023-02-06 09:22:13,842 ERROR Timeout reading: 2023-02-06 09:22:13,842 INFO ############################################################ 2023-02-06 09:22:13,842 INFO No response on the Modbus interface, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc 2023-02-06 09:22:13,842 INFO ############################################################

@Sc00bs Would you happen to know what I'd need to set for the device? I am also not sure PORT should contain the IP address of the gateway, but there is no other place to input the gateway location. 😕

🙏 Thanks very much let me go and look into this.

Awesome, thanks for the pointer. I assumed that there was something along those lines, haha. Good analogy. As a more introverted person myself that makes perfect sense. I've been watching the gateway expecting the ACT light on the serial side to flash and it to translate and relay the message over TCP/UDP for me to listen to. I guess an analog would be GET vs POST... I've been expecting a POST, but I think I need to do a GET for the data. Perhaps this is a challenge for ChatGPT to educate me, too. 🤣

Hey everyone, I was hoping that someone could help me with an integration between my SunSynk 8kw inverter and home assistant. Due to the distance to my garage where my inverter is installed I have opted for an RS485-to-ethernet adapter to get the data out of the inverter and into HA. Components: DIEWU Ethernet to RS485 server SunSynk 8kw inverter: SW Ver.：M 6.0.1.4 / S 1.7.2.4 / C E.4.2.4 Home Assistant: HAOSOVA 7.4 VM within a Proxmox cluster Steps Taken: I have wired up the RS485 gateway to the SunSynk via an RJ45(ethernet) plug to the SunSynk inverter using the pinout from kellerza's GitHub: I have configured the RS485 gateway with the following settings: I've used a Modbus TCP client to connect to the gateway, or rather listen to its output. Although it can connect, no data is present. I am not sure where to go from here, although now I am definitely up against a knowledge gap with how Modbus is configured. I'd appreciate some help with: Troubleshooting whether or not I've made an error in the connection between the SunSynk and the RS485 gateway and the config of the RS485 gateway. Setting up the RS485 gateway correctly. Setting up HA to ingest the data from the RS485 gateway. I suspect that the issue is: a hardware incompatibility between the SunSynk inverter and the RS485 gateway, RS485 gateway misconfiguration, a misunderstanding on my behalf of how RS485 and Modbus topology's work, any of the above + others, 🤣 Any help would be greatly appreciated. I am not sure how to proceed from here.

Also only have Unbind on the SunSynk or PowerView platforms (both are essentially the same).

4790122C26R After disabling static ip mine is still up and running.

So I've fixed the issue by trying a method I saw elsewhere; 1. Remove WiFi logger from inverter. 2. Wait 30 secs. Plug it back in. 3. Quickly connect to the WiFi logger's hotspot. 4. Deselect the option for setting a static IP. The WiFi logger should request an IP via DHCP instantly, provided it is connected to a WiFi network in which a DHCP server is running. I reckon someone responsible for packaging the final firmware update file forgot to tick a box or two 😂 Frustrating.

I have a Sunsynk 8k inverter and have the same issue. A do have an additional symptom where I am unable to connect to the logger via WiFi as it just keeps failing. I've tried my phone, laptop and tablet for good measure. Something interesting is that the green light flashes the moment the connection fails. I suspect hardware, but I'm hoping firmware. How, if the loggers arent now able to connect, is Sunsynk proposing to update the firmware?