Imaginary-risk
On logging in earlier this morning I noticed that the system time had changed appropriately for my computer and was in synch with WW. My invertor was showing off-line when I used Shineapp with a 0% on battery.

On using the web app the battery had been charged and was 96%. I got the invertor back on line and correct settings were restored. I minimised then paused all WW processes while this was going on
During the process I tried unsuccessfully to do a Quick discharge but it seemed that no such instruction was being activated.

After cancelling the pause and waiting for a decent interval c.0600 I tried again to initiate a quick 30 minute discharge with no errors or action being initiated. Can you set me straight?
Thanks

    No. The existing schedules do not result in any communication with the activity to suggest they are registered. Selected slots are ignored as are
    The invertor time incremented by 1 hour (I.e UTR+1) without my intervention. Iam further adjusting (c. 4 ) minutes to synch it exactly with system time.
    Tks

    An update.
    No advice for existing schedules we’re on the log.
    Most of today’s slots would in any case have been disregarded as SOCs were > 96. However the last 2 slots on the schedule appear to have resulted in a small but consistent rise reaching 100% at 1552 this afternoon. No notes in activity log re skipped slots. The day has been dominated by high solar and I do not anticipate taking any further actions for today.
    The quick discharges (2x this afternoon) were acknowledged but did not result in actions.
    I will report tomorrow morning and check out the quick charge/discharge options with logs and discrepancies. Many thanks for your help.

      @"admin"#p7 Tks.

      All now seems to be ok.

      Many thanks for your efforts.

      I have looked at my activity log.
      It has no entry for 09:58 on 30/3 which would have indicated a ‘paused’ procedure. Had I known this I would have been alerted to the problem.

      Earlier on I had paused procedures whilst making changes to the schedules on the back of the clock change and apparently failed to unpause it for which I apologise.

      Once again thank you for your efforts.