Adehslev Hi. I’m new to WW and my agile slots aren’t charging. Does work on manual. Have I missed something! fine-kitchen Thanks
KristianS Adehslev Always state your Your WattID when requesting assistance. It can be found on the Advanced Settings page. I had the same issue overnight https://community.wonderwatt.com/d/519-no-entry-in-my-activity-log-for-charge-slots-which-failed-to-run
admin Adehslev This would be the reason for your agile slots not charging last night: So toggle your Pause off here: https://app.wonderwatt.com/pause
admin Huey There was a Giv maintenance window early in the night/morning, which affected lots of Giv users. But some of your slots charged though. See 3:00 - 3:30 instruction here:
Diabloj Think everyone on GE has it. Suspect it's to do with the GE update last night. One of my slots worked, so it charged to 34%
KristianS steve_phillippo I hear you Steve, but this is most unusual. I have been using WW for months - while this is not the first time, it is very rare.... there will be a reason and a response I suspect, will be forthcoming soon. Bear with
Adehslev steve_phillippo I’m also new and mine didn’t charge the night before either. Two out of two failed. Trial not going well 😢
admin steve_phillippo Likely Giv maintenance which has affected a ton of users. Send us your WattID (under Advanced section) and we can diagnose the exact reason in your case.
johalareewi admin ikely Giv maintenance which has affected a ton of users. WW would still have tried to action the charge slots so there should be activity in the WW log?
johalareewi WW missed Agile charge slots from 00:00-01:30. Nothing in WW activity log either so looks like WW didn't even try. The 03:00 and later slots worked ok as did the 22:30-23:00 slot. WW log neighboring-volume
admin johalareewi It did try, but failed prior to setting instruction, getting SOC/Plant details failed and it wasn't logged. We'll fix that so it will log in Activity log in future.
johalareewi admin Ok. Just got used to seeing failed connection messages in the actvity log. I guess the try the next slot in 30 minutes got bypassed too?
