Communication module inop

Sounds like there will be resolution soon.

 

I just pushed it. Got Toyota voice said it was trying to connect. Then said unable to connect. Different from the communications module inoperable message before. Ten minutes later Toyota Connect called my mobile to ask if all was ok. They received the signal they said. I told them I was testing it and they said to complete activation I need to drive it for 15 minutes, two times, then push button again to confirm it works. I will try that tomorrow. This is slightly ridiculous...

 

The "SiriusXM" caller ID name may be a red herring. Safety Connect has nothing to do with satellite radio, although it is possible that Safety Connect is using a response center operated by SiriusXM, resulting in that caller ID name. Or the caller ID name info could just plain be wrong. If you are using a landline or your cellular provider's Caller Name ID service, then the Caller ID name info comes databases run by the phone providers. If you are using some other caller ID name app, then the app is consulting some random database for number to name lookup, which may or may not be up to date. Since it is trivial to set the caller ID number delivered with a call to anything you want, it should always be taken with a grain of salt

 

Sounds like the built in cell phone is functional again, so the telematics work (the Advanced Entune apps). But there are still some details related to connecting to the operator that are still not quite there yet. But this IS progress. When the SOS button was pressed, it clearly was able to communicate with the automated part of the process and trigger the backup phone call,which is what happens if the operator cannot contact the user over the voice link.

 

It has to to with the account setup for the built-in cell phone. Why only certain accounts? Who knows.

 

So I followed the direction of the operator from Saturday night. I drove it twice, fifteen minutes each, then pressed the SOS button - same message "unable to connect". And this time I didn't get a call back - maybe because I resumed driving and was doing so for another hour. Not sure.

 

The adventure continues.

 

Thanks crewdog. This clarifies why people are seeing "SiriusXM CVSI" on their caller ID. Note that this means that Toyota is internally using a service from the SiriusXM company as part of their Safety Connect feature; it has nothing to do with satellite radio service in the car, even though the Advanced does happen to have a Sirius/XM radio.

 

This might be a really significant piece of information.

The people who handle customer service for the original Sirius/XM radio accounts all seem to be located off-shore somewhere AND always seem to screw something up when I have to deal with them.

Today I tried to switch my account from one car to another.
Everything they told me on the phone sounded right......and she read it back to me.....TWICE.
Then I got the confirmation email........and it was WRONG and not what she had told me.

It's been like that for YEARS and I absolutely HATE dealing with them, even for the smallest thing.
If the same people are running the CVSI branch of the company, I really feel sorry for you.

 

Looks like normal service is starting to return. As soon as I started the car tonight I got the "communication module is connected" voice notification and the green status light came back on. Held down the SOS button to make a test call and the call center agent said the connection was good and he was able to verify the current location of my car.

I was able to get the Prime apps to start updating again by first setting my Service Level in the Entune app to "None" and saving. Then I reselected the service level I wanted, entered the contract ID, and pressed save again. For now I can only force the Charge Management status to update but I'm hoping the location and eco dashboard reinitialize when I drive to work tomorrow morning. Didn't try remote climate yet. Hope we all get full resolution soon!

 

I also verified that the operator callback to my car after pressing the SOS button worked correctly.

 

I have the same problem. Mine stopped working April 16 or 17 of 2018. They have been working on it since then. About a year ago they had to replace my telematics module but that tests OK now. After replacing they module it did not work properly for several months. They tried to blame my phone claiming it was not compatible but since no email was sent they finally agreed it was broken. Seems there are several computers where the EIN and VIN need to be linked (like 7) and there is no automated process to do that except when the car is built. Now it sounds like the set our systems to expire in a year instead if 3 years. With all the time the system has not been working they should extend our contracts a year at no cost.