Home Charging Error Message

[Frisbee]

Does anyone else have this problem? Over three years I have charged two R1T’s at home with a Wallbox 40 amp charger, 50 amp circuit, R1T’s set at 36 amps to avoid any overheating with no problems whatsoever. With the latest update (2025.18.01), installed yesterday, my charging stops with an error message to unplug and try again. Reducing the charging rate to 34 amps allows me to finish the charging cycle. Has Rivian once again, in an attempt to add new bells and whistles, disrupted something which was working perfectly well?

Sponsored

 

[godfodder0901]

Does anyone else have this problem? Over three years I have charged two R1T’s at home with a Wallbox 40 amp charger, 50 amp circuit, R1T’s set at 36 amps to avoid any overheating with no problems whatsoever. With the latest update (2025.18.01), installed yesterday, my charging stops with an error message to unplug and try again. Reducing the charging rate to 34 amps allows me to finish the charging cycle. Has Rivian once again, in an attempt to add new bells and whistles, disrupted something which was working perfectly well?

Start your troubleshooting at the lowest layer possible, the physical layer. Check the connections and torque of said connections for your charger.

 

[Dark-Fx]

No issues here with my 40A wallbox.

 

[beatle]

Were you ever able to charge at 40A? If you had to charge at 36A to avoid overheating, it sounds like you were already on the edge and now the edge is 34A. Agreed that this sounds like a terminal issue.

It's too bad Rivian still doesn't tell us the volts/amps of the charge session. That would help troubleshoot these kind of issues. If you could see a big drop in voltage and the amps keep up, that indicates resistance somewhere - usually from a bad connection. These can develop and get worse over time as the connections heat cycle.

 

[mikehmb]

FWIW I get the error now every time I plug in, but it self-corrects and charges just fine. Not thrilled about the UI telling me I have a failure, but it hasn't (yet) affected charging on schedule.

 

[jon91581]

I'm getting the same issue on my 2023 R1S. I've tried a soft/hard reset, reset breaker for the charger, changed charging amps and disconnect/close charge door/re-connect procedures without success. Using a Rivian Home Charger.

Update: no issues DC fast charging up to 85% @ EA charger.

 

[mpshizzle]

FWIW I get the error now every time I plug in, but it self-corrects and charges just fine. Not thrilled about the UI telling me I have a failure, but it hasn't (yet) affected charging on schedule.

Do you by chance charge with a Tesla wall connector?

 

[mikehmb]

Do you by chance charge with a Tesla wall connector?

I'm just using the Rivian unit, so nope.

 

[mpshizzle]

I'm just using the Rivian unit, so nope.

Interesting - well here's my hypothesis...

At home I charge with a custom built open EVSE unit and have never seen this error. But I also regularly charge on a Tesla wall connector. When I connect to the Tesla connector it first tries to use some kind of proprietary communication protocol that Rivian obviously does not support. So for a few seconds it will tell me to unplug and try again, and then immediately just start working when the wall connector fails over to j1772.

I have observed that Rivian L2 units also use a proprietary protocol. So I'm wondering if you're having a similar issue to what I'm having with the Tesla wall connector where for some reason the proprietary connection isn't working at first so then it just defaults to j1772. Why it would be failing with a rivian vehicle, I'm not entirely sure but that's my guess

 

[mikehmb]

Interesting - well here's my hypothesis...

At home I charge with a custom built open EVSE unit and have never seen this error. But I also regularly charge on a Tesla wall connector. When I connect to the Tesla connector it first tries to use some kind of proprietary communication protocol that Rivian obviously does not support. So for a few seconds it will tell me to unplug and try again, and then immediately just start working when the wall connector fails over to j1772.

I have observed that Rivian L2 units also use a proprietary protocol. So I'm wondering if you're having a similar issue to what I'm having with the Tesla wall connector where for some reason the proprietary connection isn't working at first so then it just defaults to j1772. Why it would be failing with a rivian vehicle, I'm not entirely sure but that's my guess

That's definitely an interesting theory.

I know my Riv EVSE is on an ancient SW build, so let me check later to see if it has recently updated itself. If it has, then it's entirely likely that it's trying to push via a protocol that the truck doesn't like before failing back to 1772.

It's also possible something changed in the truck's handler and it now is having issues supporting whatever the EVSE is spitting out at handshake (because the EVSE is on such an old build).

Can definitely see this going either way - protocol handling on the truck, or at the EVSE. My money is on the truck because I haven't seen them push a SW update to the EVSE literally ever (despite multiple requests that they do so).

 

[mpshizzle]

That's definitely an interesting theory.

I know my Riv EVSE is on an ancient SW build, so let me check later to see if it has recently updated itself. If it has, then it's entirely likely that it's trying to push via a protocol that the truck doesn't like before failing back to 1772.

It's also possible something changed in the truck's handler and it now is having issues supporting whatever the EVSE is spitting out at handshake (because the EVSE is on such an old build).

Can definitely see this going either way - protocol handling on the truck, or at the EVSE. My money is on the truck because I haven't seen them push a SW update to the EVSE literally ever (despite multiple requests that they do so).

Very interesting, indeed. I you'll have to let us know your findings. @cpucrazy have you ever seen this with your Rivian EVSE?

 

[Frisbee]

Thanks for the suggestion to check the lugs, terminals and connections. They all appear to be securely tight and no evidence of arching or overheating. Because it is not possible to inspect the interior of the Nema receptacle, nor for that matter the Wallbox plug, out of an over abundance of caution, this weekend I am going to replace the receptacle with a Hubble RV rated receptacle and also replace the Wallbox. In the past the Wall Box would charge at 40 amps but always approach the maximum heat limit causing me concern. Hence why I reduced the charging to 36 amps.

 

[cpucrazy]

Very interesting, indeed. I you'll have to let us know your findings. @cpucrazy have you ever seen this with your Rivian EVSE?

I have seen it a couple times. Where it says to unlplug and try again, but only twice over the past 2ish years of having it. And 10/10 times it resolves itself and plugs back in.

Also charging at full 48amps on the 60amp breaker, nothing has changed on the new update.

 

[mikehmb]

Very interesting, indeed. I you'll have to let us know your findings. @cpucrazy have you ever seen this with your Rivian EVSE?

I just checked and the EVSE has indeed updated itself sometime fairly recently. I would need help from someone else with a Rivian EVSE to see which SW they are on to compare revs, but I'm now on 03.04.12, which is certainly different than what it was stuck on for quite some time.

Unfortunately, it does not appear possible to see when the updates were applied. Which is frustrating.

It appears to have changed its name, as well, because the previous name I bestowed upon it was Electron Dispenser (ED for short), and it has renamed itself to "Wall Charger" which I find almost infuriatingly boring and almost hostile.

 

[godfodder0901]

I just checked and the EVSE has indeed updated itself sometime fairly recently. I would need help from someone else with a Rivian EVSE to see which SW they are on to compare revs, but I'm now on 03.04.12, which is certainly different than what it was stuck on for quite some time.

Unfortunately, it does not appear possible to see when the updates were applied. Which is frustrating.

It appears to have changed its name, as well, because the previous name I bestowed upon it was Electron Dispenser (ED for short), and it has renamed itself to "Wall Charger" which I find almost infuriatingly boring and almost hostile.

That version is what I have as well, but it's been out for like a year.

Sponsored