• General
  • Release 554 - issue with Agile scheduler leading up to midnight - resolved

There was an issue with our Agile Octo scheduler, which caused an outage of a few hours leading up to midnight.

This should now be resolved om Release 554 - 00:12 on 12th of April.

Apologies for the inconvenience - all other Agile schedules with start date/time from here on should be actioned this AM.

    ID. lonely-sister

    just happened to wake up and checked my charging as you do, but my charge schedule did not start so had to kick it in manually

    Same for me the pre selected agile slots from midnight did not apply overnight

    admin should selected slots after this resolution have activated ? I had every slot selected until 5:30 and none did.

      Same here . Not much sun today but luckily there is a raft of free slots available early afternoon for a manual charge .

      rjmoore if you had a continuous block from 00:00, they would not have, because the start time was prior to the fix and therefore ‘missed’.

      Only if there was a gapped slot after 00:00 at some stage, it would have been picked up after the next deselected gap.

      Does that mean that in the future its wise to leave a blank slot at night in case it malfunctions ?

        Can I ask when the instruction is sent? I have mine set to charge from 11.00 into the negative dip so that I can charge the EV but there isn't anything on the growatt schedule yet?

        Thanks!

          Not sure if it's related to this issue. My 10:30 pm Agile slot worked okay. I'm sure during the day I had deselected some early morning slots because my battery would still be 40% charged at sunrise and there were a bunch of sub-zero charging slots set for during the day. But when I checked this morning, I had 3 slots that had been active in the early morning.
          I have had WW underestimating solar forecast for the last couple of days when setting export, so I changed direction of my solar array from Southwest to south east. Would that change have reset the Agile schedule as I didn't look after the change?
          Growatt ID: awful-priority

            felmer It does look like at 22:40 last night, your 22:00-8:30 Agile window had no selected slots in it.

            As such, it was then populated, which included a continuous block between 2:30-04:00.

            Oh yeah, that all empty slots in schedule window caught me out again! Please add some notification of this when clearing all export slots in configured charge window.

              felmer Right - yeah we'll see what we can do to make sure people know what's going on.
              Maybe we should say something like: "When deselecting all slots in an active charge window, your slots will be auto populated."