Custom Component solaredge-modbus-multi

Do you happen to have an example of calling the storage control mode and changing it to remote control, for example in node-red or automation?

My calls.simply are not going through. It doesn’t change but I can change it in the UI from the integration . :pray:

edit: OK so it works from automations in HA but not from node red using select.select_option odd

edit2 :

i discovered the issue :slight_smile:

  • Original Node: entityId is a string. Doesn’t work
"entityId": "select.solaredge_i1_storage_control_mode"
  • New Node: entityId is an array.
"entityId": ["select.solaredge_i1_storage_control_mode"]

This is the node that worked for me - hopefull this helps others too:

{
  "id": "3a36fa5639176568",
  "type": "api-call-service",
  "name": "",
  "server": "f9088194.9ff3a",
  "version": 5,
  "domain": "select",
  "service": "select_option",
  "entityId": ["select.solaredge_i1_storage_control_mode"],
  "data": "{   \"option\": \"Remote Control\" }",
  "dataType": "json",
  "x": 1310,
  "y": 820,
  "wires": [
    []
  ]
}

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)

It’s in the release notes:

I recently upgraded my Solaredge inverter with display, to display with Setapp.

Since then the ‘Solaredge multi’ integration from time to time ‘freezes’ and all the entities become unavailable.

I use a modbus proxy for years without issues, and my other integrations (EVCC) keep working.

I assume it has something to do with the new setapp inverter, but still it is strange… anybody has experienced this before?

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.

I have uploaded some logs on github

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.

Is this even possible?
Thx

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).

Great idea! Unfortunately I don’t have a sensor / switch yet. But I’m considering to buy an outdoor Zigbee smart plug for this use case :slight_smile: