Perfekt.
Thanks for your Response!
I don’t really have an answer for the “connection unexpectedly closed” errors or any ideas what I could really do about them. They are coming from pymodbus, so it could be a networking problem. Wireless and powerline extenders are often reported to be unreliable with modbus.
A bit of an update. It seemed to improve when I reduced the polling frequency (currently 30) and ticked Keep Modbus Connection Open. However it is still going offline now I’m getting the following errors from pymodbus.logging…
failed: time out
[Errno 111] Connection refused
I’m going to try turning off Keep Modbus Connection Open as it was a bit more reliable without that.
Strangely it does seem to recover sometime, so perhaps a network issue. I’m going to put a wifi extender in the loft to see if that helps.
Usually the problem is wireless, and the solution is a wired Ethernet connection.
I am looking for help with an issue I can’t duplicate.
There is an issue report (Cannot import name 'host_valid' from 'custom_components.solaredge_modbus_multi.helpers' · Issue #337 · WillCodeForCats/solaredge-modbus-multi · GitHub) for release v2.3.3 where it’s reported to not load that I can’t duplicate on any of my live or test systems: is anyone else having a problem loading with the v2.3.3 release or does it work for you?
Does anyone else have SE Energy Battery and use battery energy counters for import/export energy dashboard history?
How to workaround problem with battery counters resets or short report zero values described in issue #273 Fault tolerant reset battery energy counter · Issue #273 · WillCodeForCats/solaredge-modbus-multi · GitHub ?
Recently I have add 2 more inverters with batteries and now unable to proper calculate energy at all, because problem repeats every day.
Thx, installed and testing.
But I’m wondering if anyone else have same problem also? Is this counter resets specific only to my particular installation, or no one else using these counters? I opened ticket about this problem at SolarEdge support, but have no answer yet.
It is a common issue (see Battery Energy section):
There is saying “SolarEdge Energy Bank batteries have been reported to use lifetime counters correctly.”
I’m talking about SE batteries only.
This is the first report I can recall that SolarEdge branded batteries also don’t use lifetime counters correctly, that’s new information. I was aware LG batteries always had that problem.
So in that case the answer is any battery may or may not use lifetime energy counters correctly. And the only real solution is SE fixes that in their firmware. Anything else is workarounds. I’ve seen people using the integral integration helper to smooth out the battery energy, but it’s not perfect.
Hey @WillCodeForCats, Awesome integration. Thanks so much ! I want to control my inverter. You say in instructions to enable advanced power mode on inverter. I don’t have that option and in the power control manual ( https://knowledge-center.solaredge.com/sites/kc/files/application_note_power_control_configuration.pdf) I also can’t see that option. Could you please clarify what I need to do here ? Many thanks
Open your integration and click Configure:
Turn on “Power Control Options” then choose the controls you want.
I don’t know where you’re reading “enable advanced power mode on inverter” is, can you provide a link?
1 Like
Hello and thank you for superb addon. I have 3 inverters. First is a master. Second and third are slaves. master communicates with them using Modbus. On monitor portal everything shows ok (all 3 inverters). But using your addon I can see only Master and one slave. Could you point me where should I start investigating what could be wrong? Thank you.
Start here:
I have been running ‘SolarEdge Modbus’ successfully.
I would really like to use your ‘Modbus-multi’ for the battery support but it is just not detecting the batteries. I have configured it to enable auto-Detect Batteries and I’ve tried the all the power cycling tips to no avail.
My question is - is it possible to manually configure the batteries somehow?
They are on the modbus because it all works in in the original ‘SolarEdge Modbus’ just not being auto detected here…
Use the latest pre-release version.
Perfect! Thanks
It’s been reported that recent firmware changes on SolarEdge inverters altered some of the identification information that was being used to detect batteries, so starting with Release v2.4.2-pre.2 the detection method was changed to try and account for this.
There is no manual configuration because of the large number of possible inverter/battery combinations. While I think it’s unlikely for someone using Home Assistant to have 32 inverters + 64 batteries, but that’s what the specifications say and that many config options in the HA UI is impractical. I do know there are a couple installs using my integration that are larger commercial installations though, so it’s not impossible.
Release v2.4.2 contains this change.
Release v2.4.5 is a required update for Home Assistant 2023.9.1
Home Assistant 2023.9.1 now uses pymodbus 3.5.1, which has changes that are not backwards compatible with older releases.