Rivian dual-motor vehicles equipped are experiencing a major software bug that displays incorrect battery charge levels, leaving drivers stranded when their vehicles run out of power despite showing remaining range.
The issue affects the battery management system’s state-of-charge display, causing it to show higher remaining battery capacity than actually available, according to reports from multiple owners on social media.
As of press time, the exact number of vehicles affected is still unknown.
One driver was stranded on the roadside with over 20% state of charge displayed before the vehicle completely lost power, according to X user ‘RivianTrackr.’
“I just had a friend with over 20% SOC run dead on the side of the road because the R1S was showing more charge than there was,” the user wrote on Saturday.
The stranded driver waited four hours for a tow truck and was taken to a DC fast charging station, but both a Level 2 charger and the fast charger had faults.
“This is the type of s— that makes people angry. No communication on this type of issue that should be a recall,” the X user posted adding that the owner now “wants to get rid” of the vehicle.
The company has not issued a formal recall, safety notice, or public statement regarding the battery gauge malfunction and it remains unclear whether Rivian proactively contacted all potentially affected owners.
Multiple other Rivian owners responding to the post reported receiving calls from the EV maker regarding the issue.
Several owners reported that Rivian deployed a software update to address the issue. “Sent you a DM the other day about the call I got regarding it!” one user posted.
Another stated that he received a software update on Friday to fix it.
“I created service ticket after what happened to me last Tuesday at Wawa early in the morning. Rivian contacted me next day. Told me update coming to fix this. You then posted it. Installed yesterday,” the user wrote.
‘RivianTrackr’ later confirmed through owner reports that Rivian identified the problem as a software bug rather than a battery chemistry issue.
“No it’s a software issue per Rivian,” the account posted in response to questions about whether the LFP battery chemistry was responsible.
