Jump to content
Do Not Sell My Personal Information


  • Join Toyota Owners Club

    Join Europe's Largest Toyota Community! It's FREE!

     

     

PHEV - MyT app failed to communicate with car - again.


ernieb
 Share

Recommended Posts

So set the car/charger (granny cable) to charge overnight and this morning the app says that it did not charge, still 47% as it was last night. Refreshed the app, no change. Opened the charge page and did a refresh to ‘wake the car’ no cage but timed out. Eventually got a comment that the app was unable to wake the car. Opened the car doors via the remote and still the same message. When I go to the car and check it charged perfectly fine and shows 100% and 54 miles range on EV.

It’s not a great issue but once again it seems to suggest that the app/ cars ability to talk to the server is compromised. My thoughts are how much more is this likely to happen when there are more users and people using full BEV’s.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites


I haven't had this problem with MyT so far, tho I have only had the car 2 weeks, tho I will say that it is orders of magnitude more compliant/user-friendly and (so far) reliable than the equivalent Nissan one, and they've been doing EVs for over a decade. The chat on those forums implies that their app has always been horrendous, so I would think that perhaps it's a design flaw, rather than a user-load issue, as it's the communication that is the problem you describe, rather than the charging, and I am making an assumption that all car manufacturers in recent years will have an app to communicate with the car in some capacity, or be working on them for newer models? 

 

If its a design flaw, then it can be fixed (assuming the manufacturer is interested in devoting resources to troubleshooting etc) 

Link to comment
Share on other sites

I presume you've set the car to link to your home WiFi when parked up? If not, then the other option is a problem with mobile coverage for the inbuilt sim, or a network issue? 

Link to comment
Share on other sites

I suspect that, once again, there is a bit of a 'spotty' issue with the Toyota servers since they mediate all such communications.

The other day I went to check for a map update (for the wife's car) and it took three or four goes before communication with the server was successful ...

Just a guess ...

Link to comment
Share on other sites

In general it works fine and I see few issues, but as Philip suggests it feels like a server outage/uplink issue rather than software or my settings. It’s still not communicating the full charge status on either my iOS iPad or Android phone.

  • Like 1
Link to comment
Share on other sites


I had a few failed attempts to log in earlier this week which is normally a symptom of issues on the Toyota servers so it wouldn't surprise me.

Link to comment
Share on other sites

35 minutes ago, nlee said:

I had a few failed attempts to log in earlier this week which is normally a symptom of issues on the Toyota servers so it wouldn't surprise me.

Yes I had problems Monday and yesterday...not able to sync with the servers

Link to comment
Share on other sites

I’m still unable to sync the charge data as per image, still shows yesterdays data.

D438B76D-FF33-4DBD-903D-242C700DE402.jpeg

Link to comment
Share on other sites

6 hours ago, ernieb said:

it feels like a server outage/uplink issue rather than software or my settings

Sorry, by design flaw, I mean in a general sense, ie in this case, rather than design a way for the owner to communicate directly with the car, the purpose is also (presumably) to allow the manufacturers to collect all the usage data etc as well, so the setup appears to be:

owner's app sends a request (info/command etc) to the manufacturer server, server communicates with car, car speaks to server, server sends info to app. 

More links in the chain = slower & more vulnerable to failure. Not ideal from a customer priorities perspective, but I suppose unavoidable if one hopes to have better products in the future 🤷‍♂️

  • Like 1
Link to comment
Share on other sites

Almost always the Toyota server and or the car to server connection via GSM. So expect problems in poor GSM reception areas or when Toyota servers are busy or undergoing maintenance.

All this said it is 1000 times better than the Peugeot App on their PHEV. 

Rare that the Must doesn't work in my case. My only gripe is losing trip data. This would benefit from a better implementation.

Link to comment
Share on other sites

So we left yesterday’s location this morning and drove home, 115 miles. I tried the MyT app/sync after I was in the car and in the READY mode, still no indication of charge level, just timed out. We drove home and the trip was recoded accurately.  The MyT app worked perfectly when we got home. So my assumption is a lost of SIM connection except it did record the trip completely.

  • Like 1
Link to comment
Share on other sites

I think it's just having one of it's periodic wobbles again Ernie. Mine is still slow to log in and retrieve any data. Sometimes fails to log in or times out with an error when pulling the data. It's showing my car parked in Shrewsbury at the moment but I can see it on the drive out of my window! Although I can see it charged last night.

It did have the journey cut short again on my journey north last night, as per the other thread but I think this is a different issue that the app team are currently looking into.

Interestingly, although the stats of the last journey cut short, it knows the journey ended at my home address, yet it thinks I'm parked up in Shrewsbury so it really has got its knickers in a twist!

  • Like 2
Link to comment
Share on other sites

Just got the definitive answer from Toyota :

 

I have been advised there is a limitation of the module fitted (which is known as a DCM (Data Communication Module) in our cars. The DCM while having a trip capture a lot of data. Each data is stored as an event and at the end of the trip all events are stitched and sent to us as a trip. The DCM cannot store more than 2000 events. Once it reaches 2000 events, after that only the end location is captured. The events can be anything, like the driver behaviour which is not good for hybrid score, threshold breaches like speed, accelerations and breaks. During longer trips, we usually see this issue.

We have gone through the trip that you have mentioned for 27th October and 4th March. There were total 2000 events captured for both the trips. After that DCM could not load more events. Thus no further locations could be captured and we only got the last location after that.

  • Like 3
Link to comment
Share on other sites

post move to the correct thread 🙂

Edited by philip42h
Link to comment
Share on other sites


I have received an answer regarding the Smart Connect system and the 2000 events limit. 

The Yaris Cross will have a new hardware module however the 2000 event limit  remain 'for exceptionally longer trips'. 

That is exceptional for me but not for everyone. 

Link to comment
Share on other sites

From what has been said already a trip of 3 hours or over could not be called ‘exceptional’, just don’t understand why they can not increase the limit?

Link to comment
Share on other sites

Latest Deals

Toyota Official Store for genuine Toyota parts & accessories

Disclaimer: As the club is an eBay Partner, The club may be compensated if you make a purchase via eBay links

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share







×
×
  • Create New...




Forums


News


Membership


  • Insurance
  • Support