[APP][Pro] SolarEdge + Growatt TCP modbus

Yes, I will.
I’m not sure which values from the inverter are mapped to which capability in Homey, can you let me know what inverter value from the newer protocol is mapped to which capability?

So, what is mapped to:

  • Solar Power
  • Solar Input
  • Grid Output

etc.

    inputPower: [1, 2, 'UINT32', 'Input Power', -1],
    outputPower: [35, 2, 'UINT32', 'Output Power', -1],

    gridOutputPower: [40, 2, 'UINT32', 'Grid Output Power', -1],

    pv1InputPower: [5, 2, 'UINT32', 'pv1 Power', -1],

Thanks. I’ve made the flows. Problem is, the sun seems too low to get usable data, everything is returning zero.

I’ll check it tomorrow when there’s more sun and I can check the returned values.

1 Like

Hi!
this looks really promising but before installing the Homey - Will this work with the SolarEdge SEXXK-XXXXXBXX4 over TCP Modbus via WIFI or will I need a wired connection?

Thanks

Hi Edwin. Since my energy dongle is acting up, could you please add the following two EMMA values when you get a chance?

then i could replace all data directly from EMMA and and my energy dongle can finally retire :slight_smile:
thx in advance

Hi! I have a Sigenergy system, and the THEN “Remote EMS Enable/Disable” card no longer works. Sigenergy recently updated the battery firmware, so that could be related. However, the THEN “Remote EMS Control Mode” is still working, so it’s not a complete breakdown.

Is anyone else experiencing the same issue or has a suggestion about what the cause could be?

do we have some updated modbus doc with this change? release notes and can you ask them

I wasn’t able today to have a look, I’ll look at it tomorrow.

1 Like

Actually, they seem to have fixed this in the background. Unfortunately, they have now introduced a requirement to manually disable AI Mode, which results in you not being able to control the mode settings via Homey if you want to use AI Mode (which you probably do).

UPDATE:

Actually, Homey can control the Sigenergy when you manually change the setting in Homey by switching the device in Remote EMS mode. It’s just the ‘Remote EMS’ card that doesn’t work.

Hi Edwin,

Sorry for the delay, it turned out I had to spend some time on my own app due to it no longer working correctly because Ring made some changes to their API but that’s fixed now so I can get back to this.

Here’s the flow reading the holding registers:

Which results in this data:

Here’s the flow reading the yield from the strings:

Which results in this data:


Personally I’m only interested in the Total and Total day yield, not really in the separate yields per string.

Reading the temperature and current:

Data:

Voltages and power flows:

Data:

The voltages per string doesn’t really interrest me, same as the power per phase. I am interested in the total power output, especially for the Homey Energy Dashboard :slight_smile:

I hope this helps, if you want me to get some more registers, just let me know.

1 Like

I always let Homey send a message with the morning yield at the highest sun position. Today suddenly a very strange yield that can’t be right.



May i ask how you did that?

There are ways to generate nice info..

on 12:01 and 12:02 I will try to reset the daily counter , maybe at that time homey was busy. What was the total of the day before. maybe the 2 will give you this value.

It is working now again. Thanks for you answer.
And it was indeed the total of two days.

1 Like

I know this might be a bit off topic but I just switched my wi-fi network from 7 year old Netgear Orbi to Google wi-fi Pro. I can’t seem to get my modbus up and running again. Could someone help me out with this, possibly via DM?

This is by far my most used app as a ton of flows control my Growatt inverter :slight_smile:

Thanks in advance :slight_smile:

Did you try to keep homey on the same mesh root or node and did you select the same wifi channels for the mesh.

I had tons of problems with my mesh, although it is draytek, but the problem sounds similar ..

My guess would be: you’d create a separate 2.4GHz wifi network, but unfortunately Google wifi is one of the few wifi devices which doesn’t have that option.
Next, make sure the inverter can’t hop between access points.

I went from a 192.168.1.XXX to 192.168.86.XXX beacuse Google doesn’t support Vlan tagging on it’s own.
So for now It’s just a matter of:

  1. How do i get access to the web interface for the Modbus which is connected via LAN cable to the Google Access Point.

  2. What should the seetings be like once i get access to the modbus?

Thanks for getting back btw :slight_smile: