I have a guess:
I tried today, the „Hello MG“ Commamd only works when the MG is online. So maybe this is the reason that some MGs have no Troubles. If „Hello MG“ is turned on, the Command was sent so the fault Server and the MG got a Bad Response. When it is turned off, the fault Server was not contacted…
 
I have a guess:
I tried today, the „Hello MG“ Commamd only works when the MG is online. So maybe this is the reason that some MGs have no Troubles. If „Hello MG“ is turned on, the Command was sent so the fault Server and the MG got a Bad Response. When it is turned off, the fault Server was not contacted…
I don't think I have hello mg on my SE. At least it never does anything if I say "hello mg" never found a toggle for it either.
 
There still seems to be a lingering belief that this had to do with an update.

I don't think that's right at all. An AWS server went down, meaning that our cars couldn't contact mothership. It would seem that that is enough to cripple them, because they go into some kind of loop or limp mode if they can't communicate with the servers.

That is appalling programming, and that is what needs to be fixed, and the lesson to be learned.

We, as users, also have a lesson to learn, which is that if these symptoms appear, we should simply switch off data.

It is a shame that the early, apparently wrong,diagnosis of a failed OTA is perseverating.
If there was an outage to a major AWS service I suspect there would have been more widespread effects and definitely more publicity. The organisation I work at relies heavily upon AWS and we didn't have any issues over the weekend. Not ruling it out, I'm just leaning more towards an intentional change to some MG API or backend service that broke it. Their developers need to subscribe to the concept of "read only Fridays" - no pushes to prod before a weekend!
 
Support us by becoming a Premium Member

Latest MG EVs video

MG4 EV Refresh + NEW MG4 EV Urban - UK arrival dates, prices, specs (2026)
Subscribe to our YouTube channel
Back
Top Bottom