Unneccessay updates to inverter

[rszemeti]

Describe the bug
Looking through the logs I see:

6140 | 2025-05-04 11:05:15.770579: Inverter 0 Updated start and end charge window to 23:59:00 - 12:30:00 (old 23:59:00 - 12:30:00) -- | -- 6139 | 2025-05-04 11:05:15.770421: Successfully pressed button button.solis8_update_discharge_times on Inverter 0 6138 | 2025-05-04 11:05:11.671597: Successfully pressed button button.solis8_update_charge_times on Inverter 0 6137 | 2025-05-04 11:05:07.483607: Inverter 0 write_and_poll_value: No write needed for charge_end_minute: 30 == 30 fuzzy 0 6136 | 2025-05-04 11:05:07.483543: Inverter 0 write_and_poll_value: No write needed for charge_end_hour: 12 == 12 fuzzy 0 6135 | 2025-05-04 11:05:07.483472: Inverter 0 write_and_poll_value: No write needed for charge_end_time: 12:30:00 == 12:30:00 fuzzy 0 6134 | 2025-05-04 11:05:07.483413: Inverter 0 write_and_poll_value: No write needed for charge_start_minute: 59 == 59 fuzzy 0 6133 | 2025-05-04 11:05:07.483344: Inverter 0 write_and_poll_value: No write needed for charge_start_hour: 23 == 23 fuzzy 0 6132 | 2025-05-04 11:05:07.483268: Inverter 0 write_and_poll_value: No write needed for charge_start_time: 23:59:00 == 23:59:00 fuzzy 0 6131 | 2025-05-04 11:05:07.483128: Adjust demand (idle) time computed is 12:30:00-23:59:00 6130 | 2025-05-04 11:05:07.482717: Adjust idle time, charge 23:59:00-12:30:00 discharge 00:00:00-00:00:00

So ... it has written and polled some values ... and all of them got "No Write Needed" ... so at the end of the process, no button press was needed, yet, it still triggered a button press.

Expected behaviour
If no values are written, dont trigger a button press.

Predbat version

current, atest

Environment details

• Solis, but whatever

Screenshots
If applicable, add screenshots to help explain your problem. The most useful ones can be your battery chart, the Predbat HTML plan and your current settings in HA.

Log file
Can you capture a log file from the time of the issue, debug mode is not normally required.

Predbat debug yaml file
Enable debug mode and let Predbat run for one cycle. Look in the 'debug' directory under the Predbat add-on and take the .yaml file for the time period in question.
Rename the predbat_debug_XX_XX_XX.yaml to predbat_debug_XX_XX_XX.yaml.txt and upload it to Github. This will allow your plan to be reproduced and also stores all your settings for review.