The only setting that looks odd is "Min. SOC" - it's the minimum level the battery is allowed to reach for it to stay "on grid", which I understood as the lowest level it will discharge at. Seems irrelevant when you're trying to charge, but it might be worth changing... These settings work for me running on Version_Master 0.23:
Attachments:
I’ve deleted the old schedule and copied those settings to see if that helps. Ticket in with Fox either way.
Still not working. 
If I change the remaining time work mode to forced charge it starts right away, so it’s just ignoring my schedule. Brilliant.
Hopefully fox respond to tickets quickly.
If I change the remaining time work mode to forced charge it starts right away, so it’s just ignoring my schedule. Brilliant.
Hopefully fox respond to tickets quickly.
Pesky firmware! Hopefully Fox respond quickly...
I’m going to give this set up a ho, just in case it’s struggling with just one window.
Failing that and intervention by Fox, I’ll try setting the two schedules as self sufficient and then set remaining time slots as force charge to see if that makes a difference.
Setting remaining time as force charge this morning triggered the charge to happen straight away.
Failing that and intervention by Fox, I’ll try setting the two schedules as self sufficient and then set remaining time slots as force charge to see if that makes a difference.
Setting remaining time as force charge this morning triggered the charge to happen straight away.
Attachments:
I have had a response from Fox. I have attached a screenshot below. I don’t really know what it means but I’m hoping it fixes the issue!
Attachments:
Bit cryptic, yes! Something connected to one of the previous schedulers I guess. The API has three scheduler versions - the current one is V3... Nice quick response though!