Without any logfile it’s hard to say.
Hi everyone. Got a new solaredge PV installation with optimisers, SE6000H inverter, EV charger, Hot water immersion heater diverter and solaredge modbus. Followed the excellent guidance here as to how to get the TCP modbus enabled on the inverter and integrated into Home Assistant. All working fine so firstly thanks for all the posters above, massive help. My remaining problem is however i dont seem to be getting any reading from the immersion heater solar diverter (its a solaredge diverter and the wattage shows in the app when active. I am on single phase so only ticked M1 in the integration config…anyone got any ideas? thanks. Then i am off to grafana to make a good looking dashboard.
I’m having the same issue, did you resolve it?
I left the
solaredge_modbus:
name: ‘SolarEdge Modbus’
host: 192.168.1.160
port: 1502
scan_interval: 2
read_meter1: true
out of the config.yaml file, updated in HACCS and had all the entities availeble again, i guess i had the older version where you needed to specify to read meter 1.
I have integrated this component and now I can collect data from inverter and also from the external meter.
Fantastic.
But… I still don’t understand if it is possible to get data from the battery (LG RESU) like remaining capacity, charge/discharge power… and the total power generated by the panels.
All these info are visible in the app and in the portal (2sec refresh rate) but not available in the integration.
Is there a way to get them?
Thank you!
@galbip Hej,
i have/had the same issue and currently looking at this fork on github: GitHub - Tapematch/home-assistant-solaredge-modbus: Home assistant Component for reading data locally from Solaredge inverter through modbus TCP
The author added support for multiple inverters AND reading storage (aka battery) power and charge level.
Haven’t tried it yet, but looks promising.
Thanks Tobias,
will give a try and share.
@galbip
I’m in the same yr situation. According to Solaredge service, modbus is giving only the data’s according to sunspec protocol… and battery info’s are not…
did you try the python script to extract them?
working quite well and shows battery SOC and other info’s
@roberto59
wow! Thanks… This is very interesting although more challenging for me to integrate in HA. 
@etobi
it works!
my setup:
- Inverter SE3500H
- Storage LG Chem 16Kwh
- External Meter
- Modbus enabled on the inverter as per awulf procedure.
Now I can see info from Inverter, external meter and LG storage! 
btw… also the component is well designed; when adding it through HA lovelace UI you can select how many inverters, how many ext. meters and if there is a battery connected. I guess this to avoid to report hundreds of undefined sensors.
What kind of external meter do you have?
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
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
Is there any way integrating the modbus monitoring into the new HA energy meters?
The dropdown says “No matching statistics found”.
Can you give more insight on this?
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
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.
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!
