I have recently experienced the scheduled charging (wall charger) not working on my MG4, after it had been working fine since getting the car last May.
If I set the scheduled charging in the app, or in the car, it seems to switch on ok for perhaps ten minutes then switches itself off again, resulting in no charge, or only a very small charge overnight.
I have been playing with it this morning, and the problem seems to be something to do with the car. If I force the system to charge, it charges ok for about ten minutes, then it switches off again every time. The charger is a Polar 'dumb' charger which charges my wife's Zoe as expected on scheduled, or forced charging. Renault Zoe's are notoriously fickle when it comes to connecting to chargers, so our wall charger must be working absolutely fine for that car to charge.
Coincidently, while out and about yesterday in the MG, I had the red warning light come on for the 12V battery which has never occurred before, and as I was close to the dealer's workshops, I took it straight there and got someone to look at it without switching off the ignition. They agreed there was a problem as the battery voltage was down to 12.05V, but when we switched off and restarted the car, the 12V battery started charging from the drive battery as usual and went up to 12.9V. The car is booked in for a check-up on April 11th with advice to trickle charge the 12V battery for a few hours which I did yesterday.
I am now wondering if the issue with charging and 12V battery problem yesterday are related in some way.
I am going to take the car to a ultra rapid charger this morning to check if the car charges from that ok, because if it doesn't, it will have to go to the dealers site and be left there until they can sort it, because I will run out of charge in the next 60 miles or so.
There is one other factor that I think may possibly be the root cause this charging issue, a few weeks ago in February I had a software update which has addressed all the issues I previously had with the LKA and laggy screen responses etc. I am now wondering if that update has caused this problem!