MG App not working

[1MGEVUSER]

Has anyone had issues with the app connection to the ZS new facelift?

It has been working ok until today.
I have tried unlocking and locking the care with the remote keyfob but with no difference.

My home "charger" just got swapped from Easee One to Ohme ePod just yesterday and discovered the MG App issue while doing a test charge required for changing the Octopus Go to Intelligent Go.

I cannot view the current data from the MG App, so, I am trying to figure out if this is related to the switchover or if the MG Server is momentarily unavailable. ...or just a coincidence.

 

[JCFlippen]

Availability of the app is sporadic. I find that there is no rhyme or reason for it operating in a haphazard way. It is what it is.

 

[1MGEVUSER]

As I mentioned above, the unlock/lock of the car with the key fob will usually solve the problem with the iSmart app not synching.

I hope it's nothing to do with the new "charger"...

I only wanted to see at what kWh did the test charge operated at and I can only see that in the iSmart, as the ePod does not show that information. I find the Ohme App not as useful as the previous Easee One App.

 

[1MGEVUSER]

I think I may know what is causing the issue with the app not synching.

Maybe to do with the eCall error notification I saw while driving today.
It disappeared off the central display soon after.

I assume that the car uses the internal phone to connect with the MG server before relaying the information to my phone. That's why it cannot also find the GPS I guess.

Is there a way to reset that or do I need to contact my dealer?

 

[Coulomb]

the unlock/lock of the car with the key fob will usually solve the problem with the iSmart app not synching.

That suggests to me that the issue is the relevant computer going to sleep. The circuit that listens for the key fob obviously can't sleep, and it can wake other computers.

There may be plenty of blame left over for the MG servers, but perhaps they're not the main problem.

 

[DB Go Rex]

100% it is the car in the majority of instances.

Unlock\lock or powering the car on and off solves it for me when this happens.

 

[1MGEVUSER]

The same for me usually, but not this time.

 

[steve401]

I find the app stops working every now and again. It usually comes back, but the last time I disconnected the negative battery terminal for a few minutes then when reconnected it seemed to get it working again.....

 

[1MGEVUSER]

I have just been to the MG Dealer and I was asked to book it in as apparently because of the eCall error, it's not likely to resolve the issue by disconnecting the negative terminal from the battery.

Another strange thing is, the iSmart App showed high data stream.

 

[daveosmith]

I have just been to the MG Dealer and I was asked to book it in as apparently because of the eCall error, it's not likely to resolve the issue by disconnecting the negative terminal from the battery.

Another strange thing is, the iSmart App showed high data stream.

Not been able to connect to the car since last night it always stops working when I want it to!! But I do recall an error message about the ecall.

 

[1MGEVUSER]

It would be good to hear from people that have had the eCall error to learn how they resolved/reset it and if the iSmart issue was resolved.

I find it difficult to understand why the iSmart connection has not been resolved after so many reports over many months.

 

[DBedford]

We had the eCall error a week or so ago on our ZS, and it just cleared itself a day later!

 

[1MGEVUSER]

Do you mean, it disappeared from the screen?
Mine disappeared from the screen seconds later.
Not sure it's still in there, in the background. I can't see anywhere to look at any logs.

 

[1MGEVUSER]

Took the car to my nearest dealership and the guy said that it was likely that the Ecall is the reason the app stopped working.

He tried replicating the eCall error by physically shaking the computer that is associated with that feature, mimicking going over potholes and the error reappeared. He is ordering a replacement for it, covered under Motability.

Today driving in the rain, the eCall error and front collision error appeared. I assume that the front collision feature error may be to do with a dirty sensor?? Both errors cleared soon after.