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.

    Mat This is now doable if you configure an active Agile charge window with 0 slots to fill. It will not select any regular 'lowest cheap slots', but the rule for 30 min slots below the pence value specified in Advanced settings will kick in.

    • Mat replied to this.

      Gazzagreen

      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.

      admin I can't set a charge window without the message at the bottom of the page coming up, as shown in the attached photo

      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 replied to this.

        admin still doing the same with 01.00

          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

          • Mat replied to this.

            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?

              admin I entered 01:00 as the end time and 0 slots as you said and it allowed this. When I scholled down, slots had been allocated under the 9.8p I'd set for my max. Success! Thanks.

              Jeff

              @admin me too!

              Same slot, same issue.

              Have just set second 5 slots in 11:30 - 16:00 if you want to check functionality?

                Jeff

                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?

                Jeff OK - so we dug into this a little more.

                Your charge slot wasn't actioned as we got a Giv Response back saying your inverter was Offline. See logs here:

                We just need to make sure we correctly log this so you know what's gone on.

                • Jeff replied to this.

                  admin ohhh hadn't looked to be honest, just did my usual wake up, see what the battery is charged up to. I don't know why it would have been offline. I'll see if the next charge goes through ok. Thanks for looking into it!

                  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!

                      So do you get more money exporting in the saving hour?

                        Gazzagreen Yep - as the delta will be calculated between what your regular use is in that time slot versus what it will be now.

                        And because you can export, this is effectively your 'saving'.