Custom Component: SolarEdge Modbus TCP

Share your Projects!
228

@galbip thx lot!

229

Is there any way for this integration to work with the new HA functionality, showing energy production/consumption graphs? unfortunately I do not see entities generated by integrations in the data sources that can be selected.

1 Like
230

you can work around that with the utility meter integration. If you feed that with the dailty total, the utility sensor will be seleectable

1 Like
231

Is there any way integrating the modbus monitoring into the new HA energy meters?
The dropdown says “No matching statistics found”.

232

Can you give more insight on this?

233

it should be possible if the maintainer adds the needed changes in code. One thing is statistics and the other thing is a ‘daily reset’ required. I’m working on ECU from APS integration to have the same applied (see here: APsystems APS ECU R local inverters data pull - #353 by ksheumaker) , so i dont need the utility meter anymore (although it works).

the utility meter is to be added in configuration yaml:

utility_meter:
  daily_solar_energy:
    source: sensor.[put your dailty kwh counter name here]
    cycle: daily
234

It is also possible to use the official solaredge integration next this modbus one. There is a lifetime counter in there that can be coupled to the solar production in the energy panel. Note that all these sensors used in the energy panel must be recorded as well. So if you did exclude stuff, be sure to add those otherwise the sensors will report 0.

235

I’ve partially been able to use this. I’ve got a SE12.5K-ER-01-ITA (lcd) and can get production data just right.
Btw I have a consumption meter (can see live consumption via SolarEdge cloud), but can’t get any consumption data via this component. I’ve just:

  • enabled Modbus TCP on inverter
  • used the default configuration.yaml of component (the one available on github page) with read_meter1: true

I’m I missing something? This is the only entity I get about consupmtion. All production data is ok!
image

236

I worked quite a bit on this topic and managed to integrate everything quite nicely. Next up is the Tesla Style card with the battery.

I shared my entire configs in this post:

3 Likes
237

What did you use to make the bottom graph showing Self Consumption, Solar Production, and Consumption? Is that a different card?

238

Just used the standard history graph card. Added from lovelace view.

image
image2304×966 181 KB

2 Likes
239

Which integration should I install now ?
I have a Solaredge battery inverter, 2 RS485 power meters and an LG Prime battery…

240

Just installed

which seems to be working for 2 power meters and the battery :slight_smile:

242

Does that work automatically with the new energy dashboard?

243

Did you ever work this out ?

I have a SE8k (3phase) and do not get data from the meter
In my case I think its as its identified as 201 instead of 203 when querying modbus
I’m still talking to my installer about trying to get this sorted as well

"meters": {
    "Meter1": {
        "c_manufacturer": "WattNode",
        "c_model": "WND-3Y-400-MB",
        "c_option": "Export+Import",
        "c_version": "31",
        "c_serialnumber": "xyz",
        "c_deviceaddress": 1,
        "c_sunspec_did": 201,

But there are p1/2/3 registers?

        "p1_current": -32768,
        "p2_current": -32768,
        "p3_current": -32768,
244

You should be able to add them yes.

245

I had this working fine until I had an LG Chem battery installed, then SolarEdge reporting was only intermittently uploading.

Once I disabled this integration it immediately was able to upload. Since then I have been unable to get Modbus reporting over TCP again, I tried the trick listed above but still nothing.

Anyone have any ideas?

Edit: Definitely getting a connection refused error or a timeout. I have tried various combinations of reboots and turning on and off TCP MODBUS.

247

Replying to myself incase it helps anyone else

Solaredge have remotely reconfigured by setup (via my installer)
Now getting meter data

"meters": {
    "Meter1": {
        "c_manufacturer": "WattNode",
        "c_model": "N/A",
        "c_option": "Export+Import",
        "c_version": "0",
        "c_serialnumber": "0",
        "c_deviceaddress": 1,
        "c_sunspec_did": 203,
248

How do people find the reliability of the modbus connection?

Can I setup the beefy dashboard to fall back to the online API if the local one is not available?

249

The reliability will also depend on your internal network I think. But over here I have had zero problems in a couple of months.
You can have modbus and the ‘official’ integration running the same time.

1 Like