This morning I find that my Giv AIO has not fully charged as instructed. Capped at 90% not 100% as required so more mildly irritating than infuriating. The logs show that the WW instructions were sent and acted upon, then some external force interfered. I have not seen this before. No other services were running (not WW IOG, not a 3rd party app, no settings deployed on the Giv portal). The 'source' of the interference says 'Server' and the instruction was 'Enable AC Charge Upper % Limit'.
Has anyone else on Giv had this? How have you identified the cause?
quarterly-position

    JayC well, I started using WW here...

    So, for 15 months, nothing, then about 40 "Server" messages since, always in the middle of a WW sequence, with the exception of Date/Time set due to daylight saving (sunshine saving is what I need). Nothing that's caused any issues, but I'm curious to know what they are too. @admin

      MrMessy It's a change to Giv's API and or firmware where it detects that another 3rd party (like WW or Octopus) has updated a register, that's it really. It looks like it simply reads the new value.