• General
  • Dual AIO - Quick Schedule sometimes fails (and logs are missing)

Something is not right with the Quick Schedule mechanism with my dual AIO setup and Octopus Agile.
This morning, I made changes to my "midday topup" schedule, disabling three slots that were automatically selected between 14:30 and 16:00 (as they were over 18p) and hit save to store the revised schedule.
This doesn't appear to have worked and the slots were requested via the API to the inverter.

Interestingly, these calls are not visible in the Wonder Watt API Activity Log.

Edit: This has worked in the past, so it might be one of the recent changes that has distrupted this functionality.

    DualAIO Is this for WattID mortified-test? It looks like the instruction was correctly sent for that, but you also have another account with WattID some-attention active which ran an end Agile schedule 2 mins after the charge instruction was sent for mortified-test.

    So it didn't fail, the schedule was cancelled by the other active account you created.

    Might be best to Pause the schedules on some-attention.

      admin The plot thickens then! I was wondering why the commands were being called twice recently and that was going to be a future question.

      As you are aware, there are issues with the SOC not being available from the GivEnergy servers, which caused problems setting the schedules (you've fixed this to use an assumed value of 20%). Around the same time as the issue, I found that when I logged into Wonder Watt, it was asking me to setup my account again. I left it and tried again the following day, but it still didn't have any settings, so I assumed that for some reason related to the API issues with GivEnergy, my details had been lost - so I setup the details again. It now transpires that this appears to have created a new/separate account.

      I login using Google and my email was recently updated from @googlemail.com to @gmail.com (I can't recall when, but it should have over a week before the 25-Sep), so I'm not sure if this might have caused the problem, but I've just tried to login using both emails in different browsers and they both connect to the newer "some-attention" account. I don't appear to have anyway to access the older "mortified-test" account. Suggest that we delete that one!

      What's more interesting is that when I setup the newer Wonder Watt account, I revoked the original token and created a new one, so I'm not sure how the old "mortified-test" account is still able to send API calls!

      So to be clear:
      mortified-test is my original account (which I can't access).
      some-attention is the newly created account which I can access.