We now have support built in for the days of week to run a schedule on, see below. Available in version **v0.3.186** and higher. [URL=https://i.imgur.com/u746LFw.png][IMG]https://i.imgur.com/u746LFwh.png[/IMG][/URL] Please give it a whirl, and if you spot anything out of the ordinary, let us know!

Multiple Schedules and Days of Week

admin

We now have support built in for the days of week to run a schedule on, see below. Available in version v0.3.186 and higher.

Please give it a whirl, and if you spot anything out of the ordinary, let us know!

SilverArt

admin Brilliant, well done, thank you. This may be personal preference but could I suggest that the instruction should just read:

Select the day(s) of the week that you want this schedule to Start

and if possible even shortening the 'From (hh:mm):' entry box and putting the day selection to the right of it (with the day selection below the day marker if space is tight so that it will fit)? This would also focus it as being start time dependant.

admin

SilverArt Great suggestion on the text change! Simplification. Change is being made.

Crunching days up under the From might leave less space and with labels under the checkboxes might look more messy.

Makes sense to keep the From and To times together, also in terms of aesthetics.

SilverArt

admin Thank you. OK about positions, I can see both sides of the argument.

I'm having trouble though. I've just tried to change my charge schedule for tonight from 00:00 to 07:00 so I've deselected 'Fri' and saved the schedule as Active.
I've set up another schedule and only selected Fri but it won't let me save it as Active, inactive is OK..
I've tried changing the start time to 23:30 and the day to Thu and that fails as well.

Making the 'normal' schedule as inactive, makes it possible to set the new one to Active.

admin

SilverArt Apologies, there was an issue with the validation for active schedules, should be sorted now.

SilverArt

admin No problem. Still not quite correct though.

It still doesn't validate the midnight straddle.
I set up Friday as an unchecked day in my normal daily charge schedule (00:00 to 07:00).
I set up a new 'Friday' routine of 00:30 to 07:00, Selected 'Fri' - That validated and went Active

Then I Deselected Friday, Selected Thursday and set the Start time to 23:30 - That will not validate and go Active

admin

SilverArt Thanks for that.

We've tweaked the validation logic and added a bunch of unit tests (that are now all succeeding) for various scenarios including schedules bleeding into the next day.

This is looking fine from our end now in v0.3.192 . (Famous last words!)

SilverArt

admin Well done, that worked fine thank you. The straddle schedule validated OK after the change and I'm pleased to report this morning that it worked OK.

SilverArt

Suddenly struck me last evening that when day selection schedule is being used the action should be set to disabled after the schedule has run otherwise it would be repeated the following day even if that day is not selected, or the timing is later. This of course means it needs to then be enabled for the next schedule.

admin

SilverArt Yeah, good point. The enabling for the next schedule is not an issue as this will kick in just prior. But we need to disable it afterwards for schedules that have specific day selections.

We'll get onto that next week.

SilverArt

admin I was having a play with Export today as it was a suitable solar day. I'd already tried one session and decided to run another one, almost straight away, so I may well have missed the problem I had when the second one finished.
When the second session finished it kept on importing from the grid. It just looked as if ECO hadn't kicked in but it was showing as Enabled. Tried disabling/re-enabling it - made no difference so I did a 'Reset to Defaults' and reset.
The one thing in the log that looked odd to me was the top two, I expected 'Enable DC Discharge' to be after ' Enable ECO' in the list. i.e. enabling ECO being the last thing done.

07/01/24 16:28 You Enable DC Discharge Written Successfully TRUE FALSE FALSE API - Inverter Presets
07/01/24 16:28 You Enable Eco Mode Written Successfully FALSE TRUE TRUE API - Inverter Presets
07/01/24 15:25 You Enable DC Discharge Written Successfully FALSE TRUE TRUE API - Inverter Presets
07/01/24 15:25 You DC Discharge 1 End Time Written Successfully 14:30:00 16:30:00 16:30:00 API - Inverter Presets
07/01/24 15:25 You DC Discharge 1 Start Time Written Successfully 14:00:00 15:30:00 15:30:00 API - Inverter Presets
07/01/24 15:25 You Enable Eco Mode Written Successfully TRUE FALSE FALSE API - Inverter Presets

As it's too cold for the golf course tomorrow, I'll try again then...

SilverArt

SilverArt Tried again yesterday and it worked OK thank you.
I also ran the 'straddle schedule' last night and that worked OK as well, resetting the timings to 00:00 - 00.01 so thanks for that as well.

best-game

HI guys.
Last night I set a one off export for 12:00 to 12:55 and one of import for 13:00-13:59. I only ticketed the Thursday box so it would run just today.
The schedule was completely ignored and nothing mentioned in the logs to say it tried and failed.
When I tick all the boxes for all days, things are fine.
Am I missing a trick?
Thanks

Tim

admin

best-game Your export at 13:00 failed due to a timeout error we received from the Growatt API:

There is an error in the activity log for it as well.

best-game

admin Thank you

best-game

admin

Just did a further test scheduling for 19:01 to 19:06 Saturday only and again this has been completely ignored:

Nothing in the activity log either

Any thoughts?

Thanks

admin

best-game You seem to have left Stop Export at blank, which is causing the issue.

best-game

admin Thank you. Yes I've finally worked that out.
Could that be a mandatory field, please? IE it won't let you save your schedule until a valid entry is included.
I wrongly assumed a non-entry meant 0% and was unfortunately able to save my schedule.

Thanks again

admin

best-game Yeah, this escaped our validation routine, we’ll fix it, thanks!

Edit: now fixed in Release 710.