EV charging at Tesla-session taken over by Rivian

[nellbarr]

I have had this happen 3 times. I start the session, session gets taken over by Rivian app at the higher non-member rate. I have sent info to Rivian. Session was started with the Tesla app, I did not use navigation to reach the charging station. Tesla app gets interrupted and Rivian continues the session at the higher rate.

Anyone else experience this?

Sponsored

 

[zefram47]

Did you plug in before you activated with the Tesla app? My understanding is you need to start the session in the Tesla app and then plug in. If you plugin first, then the Rivian authentication will almost certainly occur before you get things going in the Tesla app. That said, I've only let things go through Rivian.

 

[RivianRiverRat]

Is the Telsa account in your name?
Asking because I can start the session in the Tesla app (like zefram47 states) but it will charge me the non-member price because the account was set up in my wife's name
I tested this when we were charging together at a Tesla Charger. Used her phone to start my Rivian (it showed member discount) and then started her Tesla.

 

[cevans]

I use SuperChargers all the time and have never had this problem. As previously mentioned you must start the session from the Tesla app, be sure you have the correct charger chosen (this has tripped me up when I chose "1C" vs "2C" etc.) and then plug in only after Tesla app instructs you to plug in.

 

[ndmiller]

I use SuperChargers all the time and have never had this problem. As previously mentioned you must start the session from the Tesla app, be sure you have the correct charger chosen (this has tripped me up when I chose "1C" vs "2C" etc.) and then plug in only after Tesla app instructs you to plug in.

+1 on it works as designed and you need to select correct charger in Tesla app.

 

[nellbarr]

Did you plug in before you activated with the Tesla app? My understanding is you need to start the session in the Tesla app and then plug in. If you plugin first, then the Rivian authentication will almost certainly occur before you get things going in the Tesla app. That said, I've only let things go through Rivian.

I started the session with Tesla, I was in the vehicle when it started (same as last time) and the Tesla app stopped but charging continued. I ended the session on Rivian and removed the charger and started the session again with Tesla. This time Tesla finished the session.

So, if that happens-you (hijacked session) need to stop it on the Rivian dashboard and then restart the tesla app session. I was charged $1.40 for 1 minute on Rivian (3 kw It states), then $27.14 for 71.435 KW by Tesla.

This is the 3rd time it’s happened. If Rivian continues the session-it is substantially more.

 

[DeafPug]

I’ve not seen the behavior you mention, but I can definitely see that as happening if there is an error during the charging session and then it recovers by starting a 2nd unrelated charging session. I could definitely see that as being billed through Rivian at the non-member pricing. I can also see how that would be frustrating.

My only suggestion would be to maybe record a session with a video camera to document exactly what is going on. if this is an intermittent issue, that could be difficult to capture it happening. With “video evidence”, that could be sent to Rivian to understand more of what is going on. Note the time when any errors occur.

 

[Riviot]

I started the session with Tesla, I was in the vehicle when it started (same as last time) and the Tesla app stopped but charging continued. I ended the session on Rivian and removed the charger and started the session again with Tesla. This time Tesla finished the session.

So, if that happens-you (hijacked session) need to stop it on the Rivian dashboard and then restart the tesla app session. I was charged $1.40 for 1 minute on Rivian (3 kw It states), then $27.14 for 71.435 KW by Tesla.

This is the 3rd time it’s happened. If Rivian continues the session-it is substantially more.

I’ve not seen the behavior you mention, but I can definitely see that as happening if there is an error during the charging session and then it recovers by starting a 2nd unrelated charging session. I could definitely see that as being billed through Rivian at the non-member pricing. I can also see how that would be frustrating.

My only suggestion would be to maybe record a session with a video camera to document exactly what is going on. if this is an intermittent issue, that could be difficult to capture it happening. With “video evidence”, that could be sent to Rivian to understand more of what is going on. Note the time when any errors occur.

That's odd it allows a new charge session to start without requiring you to unplug from the vehicle first. Both the EVSE and vehicle should require an unplug before starting anything new.

To confirm, you:
1. Started in Tesla app
2. Waited for app to prompt connection
3. Plugged in

Do any other thing and it'll route through the Rivian. Plug in too soon, Rivian takes over. Plug in too late, Rivian takes over.

 

[nellbarr]

That's odd it allows a new charge session to start without requiring you to unplug from the vehicle first. Both the EVSE and vehicle should require an unplug before starting anything new.

To confirm, you:
1. Started in Tesla app
2. Waited for app to prompt connection
3. Plugged in

Do any other thing and it'll route through the Rivian. Plug in too soon, Rivian takes over. Plug in too late, Rivian takes over.

The first time I did not realize what had happened. Second time, called Tesla (not EASY to speak to someone) and they could not even confirm on their end that an active charge at that particular post was in session. Told me to call Rivian. Rivian customer service really did not know why or how and “did I start it on Tesla”? When it happened before I removed the credit card on the Rivian App-could not then charge at Tesla despite having a Tesla account with a different credit card on file. ALSO despite have a preset charger limit-vehicle continued charging until it reached 100% then stopped. Going forward I will stop charge on Rivian and restart tesla-seems to be a connection blip despite having connect + that causes a disconnect (when it should not) with Tesla app and Rivian then takes over.

 

[runwithscissors]

Why can't Rivian figure it out so that plug and charge works with membership pricing? Many of us have memberships and don't want to play the 2 app game to get the discount. I've had it error out too and then start to charge using the higher rate. Had to stop the charge and start all over again with the Tesla app to get the discount.

 

[shandel]

This happened to me on my trip last week. I opened the Tesla app, picked the charing station and the charger "1d". I then plugged in and it charged. I checked my credit card statement and Rivian charged me but Tesla did not.

 

[nellbarr]

Is the Telsa account in your name?
Asking because I can start the session in the Tesla app (like zefram47 states) but it will charge me the non-member price because the account was set up in my wife's name
I tested this when we were charging together at a Tesla Charger. Used her phone to start my Rivian (it showed member discount) and then started her Tesla.

Nope, I am the one and only user of the Tesla app. Session was started and I verified on TESLA, after less than 2 minutes-Tesla app did not show it was active but vehicle was still charging. I stopped the session on the Rivian dashboard, removed charger and started Tesla app again. That time it continued on uninterrupted.

AND, you cannot remove the credit card from the Rivian App in an attempt to avoid this-cannot charge at Tesla even if you have the Tesla app and a different active credit card until you add on a card back on the Rivian.

 

[UnsungZero_OldTimeAdMan]

Have never experienced this. It’s possible a glitch at Tesla’s end prematurely ended the session and caused plug and charge to initiate. Find out if it’s a fluke or repeatable behavior at a different site. If repeatable, contact Rivian support.

 

[mritt]

Had this happen to me this weekend.

Sponsored