Thank you … anybody else having this?
Interesting fact…I turned remote control off for a day and all the data was available in the app again. Even from a few days ago (when it stopped displaying). Turned remote control back on, still all fine now.
Here the data from the last two days also came back - however today‘s data is still behind around 15hours. Right now, 7:30pm, it shows the data from 4:30am.
Same thing here. Last data shown is from 05:45, current local time is 20:45.
Strange behavior - I didn’t implement the Solaredge integration. Will start working on it in the next few days.
So, probably something going on at solar edge. Integration is working fine and still providing all correct data. Just the solar edge app shows some quircks… Will be fine in a few days or so.
1 Like
Before I went completely over to Home Assistant controlling things, I was using the SE web platform to set TOU profiles to charge the battery. I would get pretty basic production/consumption charts in the MySE app. When I switched completely over to HA, I set the storage default mode to maximise self consumption and the storage control mode to remote control. I then started getting the more detailed consumption/self-consumption/production breakdown, but it would still take a day or two to change from the basic chart. The MySE app was recenty updated and now gives a much better chart straight away. These are my charts for today:
Blockquote
DAVSDavid Shaw
– ISSUE —
Dashboard will remain blank unless ‘edit dashboard’ - ‘raw configuration editor’ are selected and the editor is closed. Any suggestions as to why this occurs?
Blockquote
Bump, to see if this can be solved…
Another bump, as this keeps getting missed…
Have you solved the issue of commands being reset?
Every time I switch the battery off to avoid discharge when doing an overnight EV charge, after exactly 1hr the battery is set back to Maximise Self Consumption.
I figured it was related to the command timeout, so set that to 10800 seconds, which it does set to but, alas, after 1hr it reverts back to Maximize Self Consumption.
Not managed to find a method yet to change ‘select.solaredge_i1_storage_command_mode’ to anything and have it stay until I change it 
Hello fellows
I have newly installed Solar panels, and a SolarEdge inverter (I think it’s called inverter… ?).
I’m trying to understand the needed steps to configure Modbus, and then activate Modbus on the device.
I have figured out how-to enable Modbus over the wifi AP http://172.16.0.1 
I added the “SolarEdge Modbus” integration through HACS, and configured it. But all entities show “Unavailable”.
The log show that the IP address of the inverter gives “no response”.
Q; 
-
Does the settings for Modbus affect other settings on the inverter?
-
What specific settings do I need for seeing the relevant data from my inverter? My priority is solar effect produced right now.
Thanks for all help!
If you scroll back up to my post on Storage settings you’ll see that the storage command timeout is set to 6300s, or 1hr 45mins. You need to understand how the storage timeout works and what it does.
From the Solaredge Power Control Open Protocol document:
Remote Control Command Timeout sets the operating timeframe for the charge/discharge command sets in Remote Control Command Mode register. When expired, it reverts to the default mode defined in Storage Charge/Discharge default Mode register.
The default is 3600s, or 1hr, and as far as possible, the value should be left at that. If you change the Storage Command Mode to anything other than the Storage Default Mode, which in my case is Maximize Self Consumption, the timeout timer will start running and automatically return the Storage Command Mode to Maximize Self Consumption once timer has run down.
So it’s all about the settings. The Storage Control Mode has to be set to Remote Control and the Storage Default Mode should be set to whichever mode you use most often. Then, if you set the Command Timeout to a value higher then 3600s and change the Storage Command Mode to anything other than the Storage Default Mode (in that order) it’ll stay there until the timeout timer runs down then revert back to default. Once the timeout timer runs down it resets to 3600s, which is why it should be left there as much as possible. Trying to keep it at any other value for extended periods beyond what you need if for will lead to issues when it eventually runs down.
I had all sorts of seemingly random issues with this until I finally understood how it works and what it does. I hope this helps you.
G’ah! Schoolboy error highlighted. 
Thanks Dave 
Even though I’d formulated what you’d written in my mind when I put the Automation together, I’d still managed to set Storage Command Mode prior to setting Command Timeout, so the default timeout would have registered as 3600s at the time of the command, instead of 10800s.
Fixed, so should run the full length of the cheap rate window without issue 
Just to fix my blank Solar Dashboard next 
1 Like
Here’s a variation on @Remko and other’s hard work of taming all those modbus sensors. Thank you so much for all the calculations in the back end of this.
This solar system is a 6 inverter 3phase setup W/O batteries in a commercial environment. The display is basic, and not really meant for all the detail that is available. It’s meant for the general public just walking in the door.
The display lives on a 55" 4k screen in the front lobby of the business.
2 Likes
Hello,
How to change the IP address of the invertor? Mine changed it and now the integration cannot connect but cant find where to change it:
Retrying setup: Could not open Modbus/TCP connection to 192.168.100.35
How to change the IP address of the invertor?
If you have access to the inverter through SetApp, you can change the IP address there. Best to set a static IP address in the inverter and then create an IP reservation in your router settings.
If you haven’t got access through SetApp, you an access the inverter using a Web browser. The instructions for how to do so are here
So, following on from various attempts at sorting out the power flows for any given scenario, such as:
Charging the battery from the grid
Discharging the battery to the grid
Discharging the battery to the house while also discharging the battery to the grid
I’ve finally cracked it!
The basic config would invariably do some weird and whacky things when the system was doing any of the above three actions. I had various failed attempts at sorting each power flow to make the flows work.
After weeks of amending and testing code for each of the following power flows:
solar_battery_to_grid_w
solar_battery_to_house_w
solar_panel_to_grid_w
solar_panel_to_house_w
I now have a fully working power flow card 
Rather than post each individual flow here, you can see the whole thing at
If anyone would like a more detailed walk-through the process I used, let me know (there were a few gotchas along the way) . For now, all the usual caveats apply. My system is 2 inverters and 1 battery. So check the config fits your system before implementing any of it.
The v2.3.3 release will add support for Repair Issues in Home Assistant. If a connection to the inverter fails (such as if the IP address changes), a repair issue will be raised asking you to verify the configuration.
A pre-release is available now for testing.
1 Like
I think it’s safe to say this is the most complete set of calculations for any solar/alt energy setup. It occurs to me that the next step is to clean up some of the SolarEdge specific stuff and make it more universal. I’m seeing that the community has started getting local access into the v7.x firmware of enphase lately.
Enphase even has local data per panel (per microinverter). I’m going to take a swing at adapting @Remko 's energy.yaml over to enphase named sensors. I’ll probably start with @P6Dave 's work on refining the power flow calcs.
If anyone is interested in joining or collaborating let me know and we can start a new thread.
Can’t get HA to connect to SolarEdge Inverter
I have a rather simple setup
- Inverter - Router (wifi)
- HA - Router
- The inverter has a static IP on my router.
- I can ping the Inverter from within (Addon\Terminal) Home Assistant (HA)
What is it that Im doing wrong here…
I’ve tried all sorts of combinations regarding RS485-1 and 2.
All screenshots are attached.
As far as I know modbus doesn’t work over wi-fi.
Thanks for the credit. Please note that I now have the full configuration on GitHub. I recommend you start there.