…that would explain…
So, definitely don’t try “all sorts of combinations” since most assuredly those will be wrong.
Everything you need to know about getting modbus/tcp enabled is in the wiki for solaredge-modbus-multi. You should start there because it literally tells you step by step how to do it. I recommend putting everything back the way your installer set it up. Never just randomly change inverter settings then wonder why something doesn’t work.
Wifi can work depending on firmware version, but wired Ethernet always works.
Hi
The wiki is great, but I have looked and looked, and I can’t find any clear steps for when you have one inverter only…
It’s literally the first three configuration steps with screenshots.
If it’s not clear enough maybe someone can help or make a suggestion how to improve it, because it’s as clear as I can personally imagine it to be.
Till 2 Dys i’ve got a 2nd Inverter and want to use these config.
In this Thread sometimes people asked for Config for a 2 Inverter Setup.
What is the best to start with? I tried @P6Dave config from GitHub - Daverover66/Daverover66: This is mainly Home Assistant stuff. but having issues if the consumption is only getting from master Inverters battery.
Earlier in this thread i read about issues using @Remko config with small adjustments - @sirpreis are your having a working Full config getting the exact consumptions?
perhaps @P6Dave and @sirpreis we could also creae an Github Repo and working together only an enhancement to @Remko repo and having “same” Code-Base?
br
sash
Does anyone have this setup to control the battery based on Forecast.Solar anticipated production the next day? I have 7 hours of cheap electric each night in which to charge the battery but I often find I either charged it (even partially) when I did not need to because we had lots of sun the next day or I have not charged it when I should have. I’m not looking looking for anything super accurate just automating a sliding scale of 25% blocks or better.
I’m unable to make use of the current control options as most seem to be unavailable. I’m using ‘WillCodeForCats’ and Remo’s superb code. Latest version, am I missing something to be enabled somewhere?
Many thanks in advance.
Hey, I’m happy to contribute, but I think the Remko/ryanm101 repo serves most users. I don’t know if yet another repo might not confuse people 
If someone wants to take this on then fine, I’m happy to contribute.
Storage Control Mode has to be “Remote Control” to use the other storage control options.
Time of Use mode uses an internal pre-programmed profile.
I am looking for a simple config which feeds the normal power dashboard, so basically house consumption, solar production, battery and grid. I can get the battery and grid directly from the Solaredge modbus multi setup.
I have 2 inverters and a battery. Would you be able to add such a sample?
Have you looked at my config here?
I have a 2 inverter 1 battery installation, all Solaredge.
This is my power and energy dashboard:
1 Like
Thanks, but I can’t take all the credit for this. It’s my development of the dashboard created by @Remko with my own formatting of the cards. The config for this is not yet in my GitHub repo, only the backend energy.yaml used to create the sensors. Check out Remko’s original dashboard config elsewhere in this thread and if you want any of my card config let me know.
Nope. sensor.solar_panel_production_w is zero between sunset and sunrise the next day.
Hello, I am looking to port over from the Modbus Single to the Modbus Multi but I noticed it’s missing these sensors which is stopping me.
sensor.solar_panel_production_daily
sensor.solar_house_consumption_daily
sensor.solar_imported_power_daily
sensor.solar_exported_power_daily
Has anyone created something similar for the multi modbus, if so care to share? Thank you much appreciated
These sensors are actually not part of modbus specification, so you would need to create them locally with entity helpers.
Settings → Devices & Services → Helpers → Create Helper → Utility Meter
1 Like
Depending on your own config you might also need to use the integration helper to convert power (kW) into energy (kWh). Something like this:
sensor:
- platform: integration
source: sensor.solar_panel_production_w
method: left
unit_prefix: k
name: solar_panel_production_kwh
Then use the Utility Meter Helper to record daily, weekly production etc like this:
utility_meter:
solar_panel_production_daily:
source: sensor.solar_panel_production_kwh
name: Solar Panel Production Daily
cycle: daily
Do this for each metric you want to track.
1 Like
Brilliant, didn’t know about this, thank you very much!
Hi Dave, thanks for the tip earlier, took me a while to crack it but it was just the case of replacing the existing sensors with the new multimod sensors, and magic!
How did you manage to crack the:
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
Only have 1 inverter and 1 battery, is it overly complicated to adjust on this setup compared to yours?
When you say
Do you mean how did I amend the sensor template to show these flows or how have I set up automations to do this?
If the former, well, if you have a look at the template sensors I’m using for these flows in my GitHub repo, you’ll see how it’s done. While I have 2 inverters and 1 battery, that 1 battery is connected to 1 inverter. So to all intent and purposes, whenever the battery is discharging, that process only involves 1 inverter, ie the one the battery is connected to. Also, generally speaking, most people will charge the battery from the grid at night when it’s dark and there’s no solar production. So again, only 1 inverter in that process.
Absolutely not. Just note that anywhere I use both inverters output in a template sensor, just use the one you have.