[Bug]: setting charge/discharge times/current is temperamental

[SzosszeNET]

Describe the bug

I'm using predbat to automate charge/discharge and since the last couple updates seeing inconsistencies when predbat is setting schedules resulting in discharging the battery or not charging when expected as the time windows overlap. Sometimes when manually settings schedules through the solax integration (and predbat disabled) the schedule changes are discarded (despite pressing the set button within seconds ) but no errors nothing that would point into the direction of some possible issues.

Integration Version

2024.8.13

Homeassistant core version

2024.8.3

Inverter brand

Solis

Plugin used

plugin_solis.py

Serial prefix

603102

Connection Method

modbus

Detailed Error Log

No response

Additional context

No response

[bryanajwells]

I'm seeing the exact same thing. Sometimes the times are passed through 100% no issues, othertimes bits are missed. For me my setup is as per https://github.com/alienatedsec/solis-ha-modbus-cloud

Method of reproducing: I add timed_charge_start_hours, timed_charge_start_minuts, timed_charge_end_hours and timed_charge_end_minutes to a dash board along with the button Inverter Update Charge/Discharge Times

I set the start/end time to 01:02 03:04 press the update button

Then dialing into the soliscloud interver control page I check the charge date/times match what was set.

Then set the times to something else (usually 00:00 / 00:00), check the soliscould again

Repeat, eventually one or more of the 4x digits doesn't set.

I think there may be a corrolation to the 0/5/10/15 etc. minute intervals of the hour, but there is no real pattern.

Note: not related to predbat, just really exposed by it.

[timstephenson20]

Our setup here is different in that I have HA talking Modbus direct to the datalogger and ditched SolisCloud but when getting automations running I did notice that unless I included a delay of at least 2 seconds between setting timed charge hour/minute/current values and triggering the update button, it didn't always work. Sounds like a similar problem to what you're seeing in that times wouldn't always be set properly.

Don't know if you immediately trigger the update after setting values but might be worth trying adding a delay to see if that helps.

[bryanajwells]

@timstephenson20 - My controls are on a dashboard so there would be a natural delay between setting all 4 numbers and pressing the update button. However how much time between the last number and the update would be quite small I guess. I'll experiment with adding a delay.

[timstephenson20]

Ah, was working on the basis you were running this in a script/automation somewhere. It was quite fussy if memory serves - think I'd assumed at the time the issue was down to the natural latency between submitting values in HA, HA sending them to the Datalogger and the Datalogger then writing them to the inverter - give it a couple of seconds for everything to happen and the problem went away.

[SzosszeNET]

Yes but bottom line it became an issue with the latest releases, went back all the way I could 2024.04.3 (potentially could go higher) and not experiencing the issue.

[j47996]

Also seeing this; used to work before a recent version update