Alternate Predbat runs take twice as long

[Ashpork]

Describe the bug
Alternate Predbat runs take twice as long. And the longer runs appear to fire the charge/discharge services twice.

Expected behavior
On each run, only fire the charge_start_service, charge_stop_service and discharge_start_service once. Be consistent between runs

Predbat version
v8.5.1

Environment details
SE, 1 inverter, 1 battery
Predbat ran as an Addon

Screenshots
Compare the two log files attached.
longLog.txt
shortLog.txt

[gcoan]

Alternate predbat runs will take differing run times, if you look at the logfile, by default predbat runs every 5 minutes to execute the plan (as the plan is at 5 minutes granularity), but Predbat only recalculates the plan every 10 minutes.

So you will get a shorter execution run then a longer run. You can change these frequencies if you want

[Ashpork]

Of course, just spotted the configuration in the apps.yaml. Apologies.

However why trigger a inverter service action at the end of the plan execution, and then again at the end of the recalculation of the plan?

[springfall2008]

Essentially after the re-plan the execute is called again in case it has changed.

Probably the enhancement here is not to repeat the service if it was called already with the same values