admin
‘Hold charge’ is a good way of thinking about it, and hopefully something that would be relatively straightforward to implement.
It could though get more complicated over time 
. For example, I have just seen an earlier discussion which suggested being able to charge up to and hold a specified % of battery capacity - chosen to cover expected consumption over a peak period.
admin
Another twist on this. Last night I was due to charge from 4.30 to 7.00. But because the battery was already 95% full, this slot was skipped. The effect was that the battery discharged in this low cost period rather than being preserved until after 7.00 when the rate is higher.
‘Hold charge’ would be much better than skipping the slot altogether.
I like the hold charge idea, but stress to everyone not to rely on automation too much, every morning you need to check what slots are needed for the circumstances and check yourself throughout the day how your battery is holding out. Depending on the weather etc. If you rely on Automation you will get knock backs more often than not, at least until human like AI comes into it.
The more code you add, the more things can and will go wrong.
That’s true in the short term, whilst the users are enthusiasts. But the mass market needs a fully automatic solution, accepting that it will not be 100% optimised.
Reload the whole page, and use 01:00 in the To slot instead of 1.00.
Shouldn’t cause an error like this though. We’ll check the logs.
Thanks for reporting it.
Mat can you refresh and use a colon instead of a dot/period?
Right - I think I know what's happening - correct time validation not being applied there. Reload and use 01:00 and you should be good.
Needs a proper validation message like on normal schedules.
Fixed as per release 339. https://community.wonderwatt.com/d/96-wonder-watt-release-notes
Was there any issues last night? A big block of charge for me from 0330 to 0600 was missed. It correctly charged a couple of earlier half hour slots and the activity log says a charge instruction was set but it didn't charge?
Is it because the charge instruction was sent after the slot had started?
Is it because the charge instruction was sent after the slot had started?
Ooh - interesting. Is that how it works on Giv? If you set/enable a slot shortly after its start time, the whole thing never gets actioned?
What does your Giv log say? Could you have encountered multiple Inverter Timeouts?
I've just opted in to today's Savin Session with Octopus. It will be my first export using the WW scheduler
admin Remember you must have a minute between off and on times. End 17:00 and then export at 17:01 or it might not work. This bug was pointed out in another post somewhere.
Gazzagreen You're right, this was an issue for Giv.
This might actually be OK for Growatt, but yeah, good point, better to use a min margin either side, will change it now, don't want Growatt failing on my export session!
