R1S Not Maintaining Charge While Plugged In

[Electrified Outdoors]

I’ve noticed this on my R1T w/Emporia charger since the last Rivian SW update. Previously, the vehicle would top up throughout the day and maintain within 1% of my set limit.

After the most recent update, the vehicle only charges to the limit when initially plugged in, then proceeds to lose charge without topping up. I haven’t left it for more than 3 days or so since this started, so I’m not sure if it would go on indefinitely or not? I’ve gone out to it 3-5% below my set charge limit in those 3 days.

It would be concerning if I left for very lengthy periods of time if it truly has stopped all topping up. Because there’s not even a “stop charging” or “start charging” button in the app when it’s in this state, it will only charge again after being physically unplugged and re-plugged-in.

Interesting. Seems to be exactly what I am experiencing. Have you contacted Rivian? You might want to contact them to make them aware of the issue.

This is exactly what I see with my R1T (Within 1%).

Sponsored

 

[Electrified Outdoors]

Update. I swapped chargers and it would appear the issue is following the vehicle. I am going to reach out to Rivian again to see what they have to say.

It must only affect certain vehicles because my R1T is on the same software as the R1S. The R1S was built in June 23 so three months after the T.

 

[Electrified Outdoors]

I have noticed this behavior on occasion as well. Perhaps coincidentally, I am also using a TWC that was converted to J1772. I too am charging to 80% and I too have not noticed this issue when charging at 70%. I need to give 85% a try to see if maybe its the fact that its set to a custom rate of 80% and there is something it doesnt like about that. In any event, Im here for the responses.

Any luck when you switch to 85%? I am working with Rivian to troubleshoot this. Its not the chargers and I believe it is an issue with the custom charge limit...at least when its set to 80%. I have another call with them tomorrow. I am going to do exactly what you have and set the S to 85% (pre configured Rivian charge limit) and the T to 80% to see if I can get the problem to switch vehicles.

 

[LevelHeaded]

Any luck when you switch to 85%? I am working with Rivian to troubleshoot this. Its not the chargers and I believe it is an issue with the custom charge limit...at least when its set to 80%. I have another call with them tomorrow. I am going to do exactly what you have and set the S to 85% (pre configured Rivian charge limit) and the T to 80% to see if I can get the problem to switch vehicles.

For my T it is happening on a pre-set limit of 70%

 

[goldburger]

I have this issue and I wonder if it’s not holding a charge because I have it set to charge between 11pm and 6am, so if I don’t unplug until 9am it isn’t charging but also losing 2% in a few hours while the truck is asleep is pretty wild.

 

[Electrified Outdoors]

I have this issue and I wonder if it’s not holding a charge because I have it set to charge between 11pm and 6am, so if I don’t unplug until 9am it isn’t charging but also losing 2% in a few hours while the truck is asleep is pretty wild.

In my case the charging schedule is disabled for both vehicles. If you have that enabled it will prevent the truck from drawing power outside that schedule.

 

[Electrified Outdoors]

For my T it is happening on a pre-set limit of 70%

Do you have a charging schedule setup?

 

[LevelHeaded]

Do you have a charging schedule setup?

No, never have

 

[GrandEnigma]

Any luck when you switch to 85%? I am working with Rivian to troubleshoot this. Its not the chargers and I believe it is an issue with the custom charge limit...at least when its set to 80%. I have another call with them tomorrow. I am going to do exactly what you have and set the S to 85% (pre configured Rivian charge limit) and the T to 80% to see if I can get the problem to switch vehicles.

I am seeing this on 80, 75 and 70%, so preset vs custom doesn’t appear to have any correlation.

 

[Firstlast]

Seeing the same thing on my R1T. That was not the behavior in the past. I was holding hold with Rivian for 40mins before hanging up.

 

[Electrified Outdoors]

I spoke with Rivian again this evening. They are aware of this thread and are looking deeper into the issue.

Does not appear to be related to charging schedules, custom charging limits, or the chargers. Strange thing is my T is working fine. It's the S that has this issue.

 

[elektrode]

+1

Home Rivian charger and R1T no longer maintains the set charging limit once it has reached the max once.

This was at least present on 2023.26.00.

Also the charge curve display in the app has gone wonky and only uses the first 20% of the screen (horizontally) and keeps reusing the last bar for the last measurement. So any charging session only has maybe 5 bars regardless of how long the session is.

Since there is no method for reporting SW bugs, I just post on forums.

 

[elektrode]

It’s doing the same thing in 2023.30.00

Here’s an overnight shot. I never saw 70 be hit. It certainly isn’t topping off like it used to.

 

[RexRemus]

I'm seeing this as well, where I MUST physically unplug the charging cable to get my vehicle to do ANY charging after the first time it hits the charge target.

Meaning - I go out, drive, get home, plugin and vehicle charges to current charge target. AFTER this point, it will never initiate a charge again (battery will slowly drain) regardless of disabling/changing schedule or changing desired state of charge - no "software" mechanism (at least from mobile app) will cause my R1S to start charging again, I must physically go unplug/re-plug the cable for it to top off again.

This kinda needs to get fixed. Is the consensus that this only affects R1Ss? Did the most recent software update change this for anyone? I have not gotten it yet so I can't test.

 

[Electrified Outdoors]

Everyone I created a poll to see how many folks have this issue. If you could cast your vote on the poll so we can get an idea of how many are affected. Especially since it looks like we have at least one owner on .30 software update and it hasn't corrected the issue.

Sponsored