GhostOfClayton
Standard Member
- Joined
- Sep 9, 2021
- Messages
- 28
- Reaction score
- 44
- Points
- 15
- Location
- North Lincolnshire
- Driving
- MG4 XPOWER
OK, so here's the scenario: I'm on the 'Octopus Go' tariff, (which gives cheaper rate electricity between 0030 and 0430) and I have a waEV EV1 charger (waEV-charge EV1 | waEV-charge | EV Charging Solutions for Housebuilders, Developers, Landlords & Homeowners). The charger has a 'smart charge' setting whereby you nominate your tariff, and the charger knows when to charge. Plug the car in, and the blue light goes green in a few seconds, but charging only happens when it's cheap. This works well 90% of the time, but in around 10% of attempts, I wake up in the morning and nothing has happened. I have woken up in the night and checked it on the MG App to be told 'Not charging'. Clicking on 'Start Charging' starts it OK, and charging is stopped as expected at 0430.
I contacted waEV, who checked their logs, and was told the car didn't respond on those occasions, as if it were in some kind of sleep mode. To counter this, for a few weeks, I would unlock and lock the car using the remote at around 1100. If this helped at all, it wasn't perfect. I've since given up and set the car's timer, which (touch wood) seems to be working OK. Though it does mean that when I need to charge on, say, a road trip, I'll have to remember to turn off the timer. A minor faff, but sub-optimal.
Question: Has anyone else experienced this? Is there a better solution/work round?
I contacted waEV, who checked their logs, and was told the car didn't respond on those occasions, as if it were in some kind of sleep mode. To counter this, for a few weeks, I would unlock and lock the car using the remote at around 1100. If this helped at all, it wasn't perfect. I've since given up and set the car's timer, which (touch wood) seems to be working OK. Though it does mean that when I need to charge on, say, a road trip, I'll have to remember to turn off the timer. A minor faff, but sub-optimal.
Question: Has anyone else experienced this? Is there a better solution/work round?
