Connection error on triggering automation

[jovana]

I have run multiple automations that change the settings for the inverter.
In some cases, it needs to set 4 selections to have the correct configuration:

If the automation triggers changing the settings the inverter gives the error: "Error: Connection to inverter ID 2 failed".

Now I have set 10 seconds in the "Inverter command delay" option.

But it does not seem to help, because the automation is not always fully triggered.
Now have added a 15-second delay between each action, this seems to work.

Not a real issue, but the automation takes a long time to complete in this setup.

Quest: how can I solve this in a better and more cleaner way? Do you have any suggestions how to solve this?

Many thanks!
Jovana

[deqw]

Can't see what you are doing in your automations, but anyway don't change Storage Control Mode each time. Set and leave to Remote Control once and do your automations.

[jovana]

I have firmware: 0004.0020.0036

[deqw]

I am running 0004.0021.0019 at the moment, but that is still a beta version. But I know someone who has 4.20.36 and is using Time of Use. Your mySolarEdge app is up to date?

[deqw]

This: "Please note that the "Time of Use" feature is a beta version which is still undergoing final testing before its official release, is not yet available for all users and is offered on a pilot basis for select system owners."

Found that here.

[jovana]

Yes I have updated the app also. I think this feature is not release for this inverter. Need to wait for the next firmware update.
there is a release 4.21.103 already: https://www.solaredge.com/en/support/setapp-inverters-firmware

[deqw]

That one is only for the short string inverters. Just wait a bit or contact SE and ask to be included in the test already.

[deqw]

Yes it does that. I attach a screenshot. You see the discharging yesterday evening and it just started charging on solar. SE says there is some AI involved so let it do its thing for a while.

[jovana]

This is very nice!!
SE keeps working on improvements. A few months ago they didn't have this. I remember the launched in January to optimize for the dynamic energy plans.

I will keep an eye on this feature to release for my inverter also.

thanks again for the info!!!

[deqw]

What you also see in the graph is that it depleted the battery a bit too early last night. Still learning probably ;o)

[deqw]

The last nine days it worked actually quite well. You see it dumping into the grid when there is room. Yesterday is a bit off probably because I messed with it myself. What I did not see yet is charging from the grid eg. at night. But they know daytime solar will be sufficient for the day so charging at night will not be necessary. I also see my daily profits rising somewhat.

[jovana]

Well 20 hour yesterday was a good moment to return the energy, the price was at the highest.

[jovana]

@WillCodeForCats Is it possible to have some sort of debounce mechanism for changing values for inverts? Or combinding changes in one command?

I have two inverters (master / slave setup). And changing settings is almost any time an issue and get not go through. Basically, I change values for "Storage Command Mode", "Storage discharge limit" and "Storage Default Mode". I have now added delays for many minutes, but even then the inverters became unresponsive. The first command is always set, the second of third are not. Can we send one command containing the changes we need like:

In pseudo-code:
{
"storage_command_mode": option_a,
"storage_default_mode": option_b,
"storage_discharge_limit": 5000,
}

Probably there is also a way to send the info combined multiple values using yaml?

      - device_id: 281e1152847b69adcc6bd792904ac578
        domain: select
        entity_id: 705d87b43ec72ba5ba74b2cc724b0918
        type: select_option
        option: Maximize Self Consumption

      - device_id: 281e1152847b69adcc6bd792904ac578
        domain: number
        entity_id: f3b21bd8dcee5703ef14d0e99a563bbd
        type: set_value
        value: 0

      - device_id: 281e1152847b69adcc6bd792904ac578
        domain: select
        entity_id: 1e87c6f44ed6c6ff21632286dbdf9f0b
        type: select_option
        option: Maximize Self Consumption

[deqw]

Do you push "button.solaredge_i1_commit_power_settings" somewhere in your automations? This command typically takes 5 to 10 seconds for the inverter and is not necessary for what you try to accomplish. So avoid that too.

[jovana]

No, I do not use this commit option. I did not understand why this button exists if we can not setup registers first and then commit settings.

[WillCodeForCats]

The documentation says to use the commit for some settings, such as changing Reactive Power Mode.

[WillCodeForCats]

The docs also say Current Limit and Power Reduce also fall under settings that use commit.

These are different from Active Power Limit which is documented as dynamic.

The difference between dynamic and "committed" settings the documentation says dynamic commands are not saved when the inverter restarts.

However, none of my inverters accept commands so I can't personally confirm this.

[Mougli]

@jovana I was encountering the same issue trying to do something similar to you.

I have access to the Time of Use mode, but it doesn't let you set a reduced rate window, so it doesn't charge when energy is the cheapest so I had to go manual instead.

In the end, what's fixed it for me is to tick the "Keep Modbus Connection Open" box in the integration's configuration (I also set the inverter command delay to 10 seconds, but haven't checked if that's really necessary).

Then all my automation need to do is change the storage command mode (no refresh or commit required).

Note that you might want to adjust the storage command timeout, as after that duration, the inverter will revert to whatever mode is set in Storage Default Mode.

So if you want to charge for an hour max, your one time setup would be:

• Storage Control Mode: Remote Control
• Storage Command timeout: 3600s
• Storage Default Mode: Maximise self consumption.

Then you just need an automation that changes the Storage Command Mode to "Charge from Solar and Grid", and when it triggers, it will revert back to MSC on its own after an hour.