U thx - Auto-Detect Additional Entities that was it. But I didn’t manually turned off this option.
Anyway big thank you for this info (and naturally also for the component itself)
Yes, the same here.
My log is full with multiple daily errors of not connecting, connection errors which results in unavailable entities in the dashboards… Quite annoying as it was stated to me that solaredge_modbus_milti should’ve been more stable than the core one… Although, it’s still a mess and do not seem to have a stable connection at all…
I use my own integration and would not release something that doesn’t meet my own standards. I do not see connection issues with my own inverters.
The usual advice applies: make sure nothing else is trying to conect to the inverter (it only allows one connection), and using wifi is known to cause problems (wired connection is better).
I develop the integration on SetApp inverters, but I don’t use any proxies, only a direct connection. I would recommend trying a direct connection without the proxy to see if the connection problem continues or not. What proxy are you using?
My integration can coexist with others as long as everything is using polling and the timing isn’t too fast (and the keep connection option is disabled). I don’t use EVCC to know if it holds the connection open for itself.
You can also upload debug logs and diagnostic file at the time the problem occurs.
Yeah I tried direct without any other connections and I had the same problems.
Maybe it has something to do with the latest setapp firmware
I will try to find logs.
Hi, does somebody know how I can prevent my inverter and battery setup to stop discharging the battery?
Background: At the moment I have a simple 230V charger for my hybrid car and I don’t want it to be charged from my home battery. Best would be to charge it with the current solar power and the grid.
Do you have a sensor / switch for the 230 V charger? If yes, you can make a simple automation, that sets the Discharge Level to 0 W as soon as the car charges and back to 5000 W when it is finished. You also need to adjust the timeout time, because otherwise with the default settings the discharge level will get reset after 3600 seconds (= 1h).
The requirements file was incorrectly set without an upper version limit. Pymodbus 3.8.0 introduces breaking API changes that are not backwards compatible. Without an upper limit in the requirements, HA will download the latest version of pymodbus which will cause a failure the next time you restart or upgrade Home Assistant. The integration has been tested with pymodbus 3.6.6 through 3.7.4.
UPDATE: Release v3.0.4 removes the dependency on the class removed by the API change.
This release updates the internal config entry unique ID to allow multiple device hubs when used with modbus proxy on one IP address with different port numbers for each hub.
A warning about flash wear has also been added since it appears in some SolarEdge official documentation. For more information see Discussion #727.
New to HA, not a programmer/developer. Got modbus multi installed and communicating but absolutely lost with making templates that’ll work with the energy dashboard.
@WillCodeForCats I really enjoy using the integration, it offers so many possibilities and is truly an added value. Thanks!
My setup consists of solar panels, a battery, an inverter, and a charging station, all from SolarEdge. The interaction with the battery and inverter works perfectly, but there is no integration for the charging station yet. It would be interesting to start, stop, or pause the car charging. Additionally, adjusting the charging power to regulate the load would be ideal.
I saw on the GitHub page that there is already a serious thread about this, but no solution yet. Apparently, there is a test script available that could be used as a starting point, does anyone have experience with it?
I’m not the best software developer, but I’m eager to learn. Does anyone have an idea of what is needed to get this working? Or how can we help to get this into the integration? That would be fantastic.
I am having an issue where I have 2 LG Chem batteries (one 9.8kW, one 16.04kW). Each battery is connected to a different inverter (B1 connected to I1, and B2 connected to I2). Solaredge-modbus-multi, however only sees the first battery (B1) and does not see/find the second battery. I1 has modbus device ID 1 and I had modbus device ID 2 and both are found when configuring aolaredge-modbus-multi with settings to look for device ID 1,2.
In addition, I have checked the boxes on the configuration to look for additional elements and to look for batteries.