The newer firmware has an option under advanced which states …
“Some vehicles will shutdown if left in sleep mode (pilot signal enable) and then can not be woken up by timers/PV divert. Changing the pause state to disable should resolve this issue, however this removes the ability for the charger to detect if a vehicle is connected when paused.”
My unit now has to charge two vehicles, an MG5 and a ZE50 Zoe. The Zoe does a 60 mile commute Mon-Fri so is plugged in the same evening and charges fine on a timed charge to match Octopus Go.
Now I have my MG5, that gets used a little during the week, gets plugged in on Sunday and charges on a timed charge fine.
Last week I used the MG5 quite a bit and did a longish journey on Saturday so down to about 27%. Plugged it in on Saturday evening and it charged for four hours overnight but wouldn’t have reached 100%. So I just left it plugged in but it didn’t charge over Sunday night and there’s my problem.
I think both the MG5 and MG ZS don’t implement the charging protocol correctly in that if it charges and then stops, it won’t start again if there’s more than 10 minutes worth of delay.
So my question is will the option to disable pause solve my problem (yes, I’ll try it the next time but …), and what are the side-effects i.e. will it have an impact on the Zoe, will it continue a trickle charge (which I know some other units do to get around this) etc.? Is the ability to detect a vehicle an issue or is it just transparent essentially?