Sunsynk + Home Assistant

Doesn't have to involve a Pi if you can run a cable directly to your Home Assistant box.

So cheap cheap as well. Just Ethernet + Ethernet to USB adaptor.
have you managed this with 2 inverters on one RS485 bus?
 
Haven’t done it personally but the add-on supports it as they talk to each other as of one unit.
yes, i see that it supports setting the modbus ID for each device. I tried with separate twisted pairs connected (in one ethernet cable) connected to one usb/RS485 converter. it worked briefly but then stalled.

i currently have 2 separate usb/RS485 converters but still using the single ethernet cable. it works most of the time but get timeouts and CRC errors. see attached the two inverter PV power traces. the second inverter readings get stuck.

I've bought some ethernet splitter (1-2) adapters and am going to try daisy chain them this weekend to see if that works more reliably). I don't think you're meant to run RS485 in parallel, so hoping this solves the problem.

the RS485 run is probably around 30m.
 

Attachments

  • sunsynk.png
    sunsynk.png
    67.7 KB · Views: 24
yes, i see that it supports setting the modbus ID for each device. I tried with separate twisted pairs connected (in one ethernet cable) connected to one usb/RS485 converter. it worked briefly but then stalled.

i currently have 2 separate usb/RS485 converters but still using the single ethernet cable. it works most of the time but get timeouts and CRC errors. see attached the two inverter PV power traces. the second inverter readings get stuck.

I've bought some ethernet splitter (1-2) adapters and am going to try daisy chain them this weekend to see if that works more reliably). I don't think you're meant to run RS485 in parallel, so hoping this solves the problem.

the RS485 run is probably around 30m.

Yeah that just sounds like problems.

I would run a single connection and let the add-on split it out.
 
So the Pi option seems to be the middle ground between affordability and complexity (Not looking to get into soldering for ESP 32).

1. A Pi 3b should be sufficient to run a Modbus TCP to RTU/serial gateway? https://www.raspberrypi.com/products/raspberry-pi-3-model-b/
2. It looks like in addition to the Pi I need a USB to RS485 Converter and then a standard RJ45 cable wired to the correct pins?
3. Any recommendations on where to get the converters? This place is out of stock, maybe I should wait until new year: https://www.robotics.org.za/W17286
 
Are you referring to these guys ? The E-Linter being the current included option. I'm not aware of any different hardware revisions of the E-Linter ( please correct me if I'm wrong )

View attachment 1633549

If you're looking at the site or app, data is always delayed 3 - 5 mins. The dongle seems to be sending data continuously when physically looking at the traffic LED. I reckon all that data is rolled up server side and turned into all those pretty metrics that we like to see. That takes some processing time. And not having all Sunsynk owners the world over ogling real-time data saves them a ton of bandwidth ( read money ) ;)
Incorrect
The sunsynk dongle is capable of 60second updates
Solarman is a minute

I have looked at the tcp traffic and the dongle only sends data every minute
 
Doesn't have to involve a Pi if you can run a cable directly to your Home Assistant box.

So cheap cheap as well. Just Ethernet + Ethernet to USB adaptor.
I actually have a RS485 -> USB cable. Been debating looking at the Pylontech batteries
 
Incorrect
The sunsynk dongle is capable of 60second updates
Solarman is a minute

I have looked at the tcp traffic and the dongle only sends data every minute
I should have said by default it's a few minutes behind yes. Still too slow to create automations against if load kicks up

If memory serves, you can only change that on the portal ?
 
Last edited:
Yeah that just sounds like problems.

I would run a single connection and let the add-on split it out.
What do you mean the "add
Yeah that just sounds like problems.

I would run a single connection and let the add-on split it out.
When you say "single connection" do you mean connect only one inverter or connect to first inverter and then daisy chain to second inverter?
 
Doesn't have to involve a Pi if you can run a cable directly to your Home Assistant box.

So cheap cheap as well. Just Ethernet + Ethernet to USB adaptor.
Agreed. I'm thinking most folks HA box isn't close to their inverter. So suggested Pi becomes the relay agent ( using either mbusd or MQTT ).
 
Last edited:
I should have said by default it's a few minutes behind yes. Still too slow to create automations against if load kicks up
I get my data off the sunsynk website for my HA. Normally a delay of 30 to 60 seconds. I use it to preempt load shedding, making sure I have a minimal charge in Batteries etc for loadshedding . 1 or 2 minute delay is fine for that type of thing.

You will never get realtime updates no matter the solution. Even with CAN there is a slight delay.
If you run automations to manage load that need split second reaction , then you have the wrong solution. To some extent it is better to probably use Essential/Non Essesntial setups
 
What do you mean the "add

When you say "single connection" do you mean connect only one inverter or connect to first inverter and then daisy chain to second inverter?

I'm assuming the two are connected in parallel here.

So yes you just connect to the Master unit which talks to the Slave unit and the Add-on in Home Assistant then gets the data from both.


I say this by massive assumption but I think @kellerza hangs out here so might be able to confirm directly.
 
Agreed. I'm thinking most folks HA box isn't close to their inverter. So suggested Pi becomes the relay agent ( using either mbusd or MQTT ).

Ethernet cable would in almost all events still be cheaper and less complicated than a Pi regardless of distance.
 
Ethernet cable would in almost all events still be cheaper and less complicated than a Pi regardless of distance.
Easiest option is to swop the dongle for a Solarman dongle. That integrates direct with HA with 30sec refresh rate.
 
So the Pi option seems to be the middle ground between affordability and complexity (Not looking to get into soldering for ESP 32).

1. A Pi 3b should be sufficient to run a Modbus TCP to RTU/serial gateway? https://www.raspberrypi.com/products/raspberry-pi-3-model-b/
2. It looks like in addition to the Pi I need a USB to RS485 Converter and then a standard RJ45 cable wired to the correct pins?
3. Any recommendations on where to get the converters? This place is out of stock, maybe I should wait until new year: https://www.robotics.org.za/W17286

There's also a new ESP option which doesn't involve a soldering iron. Nice !


A Pi 3b will be more than sufficient
 
I get my data off the sunsynk website for my HA. Normally a delay of 30 to 60 seconds. I use it to preempt load shedding, making sure I have a minimal charge in Batteries etc for loadshedding . 1 or 2 minute delay is fine for that type of thing.

You will never get realtime updates no matter the solution. Even with CAN there is a slight delay.
If you run automations to manage load that need split second reaction , then you have the wrong solution. To some extent it is better to probably use Essential/Non Essesntial setups
Agreed. I'd never fly that close to the sun ( vicious solar pun ).

I've done the essentials / non-essential split, and use the real time data on a dash that the Mrs. can see so that we don't trip the inverter ( again ) during load shedding when turning on the kettle...aaaand the coffee machine....aaaand the microwave. You know the deal ;)
 
Top
Sign up to the MyBroadband newsletter
X