Software Update 2023.42.0 is out (⚠️ UPDATE: OTA fix rolling out today 11/15/23)

[Swezey]

As a 10-year SWE myself; this was avoidable. This should have been pushed to a small in-house fleet of vehicles where all params were 1:1 except for being grouped as the initial launch phase.

Not to mention the internal testing phases before getting to that point.

It happened, it shouldn't have happened. Hopefully, they will take the necessary steps to avoid this in the future.

But I sure as shit won't be jumping to updating day-1 of any new updates any time soon until one of you fine people do it first haha.

Sponsored

 

[Kenmecca]

One does wonder if hackers could get into Riv servers and brick all our trucks

 

[kanundrum]

One does wonder if hackers could get into Riv servers and brick all our trucks

I warned them that one time!

 

[Dark-Fx]

As a 10-year SWE myself; this was avoidable. This should have been pushed to a small in-house fleet of vehicles where all params were 1:1 except for being grouped as the initial launch phase.

Not to mention the internal testing phases before getting to that point.

It happened, it shouldn't have happened. Hopefully, they will take the necessary steps to avoid this in the future.

But I sure as shit won't be jumping to updating day-1 of any new updates any time soon until one of you fine people do it first haha.

Internal testing vehicles are probably allowed to run unauthorized software.

 

[kanundrum]

Least I can still do my home Depot run

 

[Mathme]

I'll start with a "this should never have happened" and Rivian should have had better safeguards in place to prevent this.

Now there are two important things to note moving forward:

1. How does Rivian get in front of this and address it? Any crisis intervention specialist will tell you the key is communication both during and following the event. Rivian knows which vins are affected and they need to start communicating with those owners as a priority.
2. We as owners need some sort of communication as a debrief stating what happened, what Rivian learned from incident, and how they will change the process moving forward so things like this don't happen again.

 

[Dark-Fx]

Least I can still do my home Depot run

Impressive that you knew how to get there.

 

[COdogman]

I credit cohesive oversight when things go smoothly.

As a 10-year SWE myself; this was avoidable. This should have been pushed to a small in-house fleet of vehicles where all params were 1:1 except for being grouped as the initial launch phase.

Not to mention the internal testing phases before getting to that point.

It happened, it shouldn't have happened. Hopefully, they will take the necessary steps to avoid this in the future.

But I sure as shit won't be jumping to updating day-1 of any new updates any time soon until one of you fine people do it first haha.

I do know for a fact Rivian does put upcoming software into in-house and employee vehicles before release to the rest of us. I don't know for how long or any other details about it.

 

[COdogman]

Least I can still do my home Depot run

That's called branding.

 

[jeeden]

One does wonder if hackers could get into Riv servers and brick all our trucks

Well that has been debated for some time about all "smart" cars. Don't confused development with cybersecurity. I actually talked online with their cyber office at one point when I was considering a job move and they seemed to have some rep so I'm confident. Remember, this issue is technically BECAUSE the software stack is secure. If the vehicle didn't care about certs, it would be working fine.

After reading the discussion about how much connectivity the vehicle still has, I am much more hopeful they will be able to sort out the issue with another OTA than I was going to sleep last night.

The lack of information/movement on the issue from Rivian is probably making us all assume the worst, but remember the best thing to do in situations like this is to STOP, and assess what happened, what is the proposed solution, what could go wrong with that, and work the problem. Just dumping the correct certs in and pushing back out as fast as possible is asking to make the situation worse. I would note that NOBODY is getting an update now including the people who don't have failed updates. Of course, Rivian could put the correct certs in and push it to them at least, but I'm sure they are doing a full assessment of the situation for all owners and then act.

Other than comms (I agree they should have an official email out to people since not everyone is here, on Facebook, in the Reddit forums, etc), In this type of situation you want to be a stone-cold card counter and I think they are doing that.

We could be dealing with this a week from now, but we could very well be sitting here tomorrow after they push the full OTA back to everyone tonight and be talking about how we were worried we needed to go to a SC, stock price impacts, and impacts on the Georgia plant production with giggles.

 

[SDH]

Updating too. Glad to get it updated before I drop it off for maintenance on Wednesday

Oh dear ... at least it's going to the SC anyway !

 

[SDH]

One does wonder if hackers could get into Riv servers and brick all our trucks

I'm sure the Russians and Chinese have already thought of that.

Who here wants to slam ICE cars now?

 

[Zoidz]

Needs more lint !! (inside joke for some of us old software devs.)

I am kinda suprised each system doesn't have its own recovery partition (for lack of a better term) that allows a safe mode reboot, where updates could be safely reapplied. Further, I guess I would have also expected somewhere in the truck would be a USB port for hail-mary rebooting of recovery software, in the event of an OTA or signal/reception hard failure.

But what do I know... I've only been coding for a half-century.


p.s. I didn't apply the update. Been around the block long enough to know how that sometimes unfolds.

p.p.s. Sympathy to all who did apply the update and now have a less-than-perfect Rivian experience. This stuff happens, and it'll get fixed.

Just a "me too" post. In the 80s I decided I don't have time to "beta test" firmware updates. I always wait a week or two before I apply any updates to any of my stuff. The only exception to that is high risk, internet facing Zero Day vulnerabilities. I will bite the bullet on those.

And yes, I'm disappointed that there is no roll back capability if an update fails.

 

[Killer95Stang]

I do know for a fact Rivian does put upcoming software into in-house and employee vehicles before release to the rest of us. I don't know for how long or any other details about it.

Yes they do. For the previous halloween update, it was released a month prior to the official release to my neighbors personally owned R1T. .42 update has been running on his tester and personal R1Ts for a week.

 

[DuoRivians]

Yes they do. For the previous halloween update, it was released a month prior to my neighbors personally owned R1T. .42 update has been running on his tester and personal R1Ts for a week.

I think the issue is that the production build was signed with a beta internal test certificate.

So, the beta works perfectly on internal Rivian cars, because the key is appropriate

But, Rivian forgot to replace the certificate with production key, so it failed on our vehicles

Sponsored