It just feels like bad coding to me. They can make their patches cumulative. Think about simple Windows updates, they are cumulative if you have something older that has not been updated for awhile. When I bought my 24 Touring the car had been sitting somewhere for 10 months. I saw somewhere the list of updates they had to do to get it to 2.3.10. (I forget where I saw it though). Furthermore this is not a case of not updating a car for 20 years. It has been relatively recent.
I’m sure making them cumulative is something they’re working on; it’s not trivial, as Windows has to update a single OS on a single CPU on a single motherboard. Lucid has over 70 updateable ECUs, last I checked, and some of them *they* don’t control (it’s vendored) but Lucid still has to be the one to deliver the updates. On Windows, you can download drivers after the fact, right? Can’t do that for a Lucid.
It’s a different problem.
Moreover, no, it wasn’t 20 years, but 20 months is a long long time. Remember that this hasn’t been updated well before 2.1.43, the update we were all talking about.
I’m a bit surprised to see this much back and forth on a topic like this.
In no universe is this situation an agreeable one for a vehicle …
To be ultra super clear: I agree. I think Lucid should fix this, and explain to OP what happened.
But it isn’t pitchfork-worthy either. On average, Lucid tries to do the right thing by customers; let’s give them a chance to look into what happened. Surely they’ve generated that good will, no?
Perhaps not with OP, which I totally get - but certainly with some of the members of this forum.
The most likely options here are:
1) a rogue service manager decided not to cover it, or,
2) something else is going on.
I can pretty much guarantee it isn’t as simple as “you didn’t update your car, sucks to be you.”
Warranty aside, there can be many life situations for owners where a timely software updates may not be possible. Likewise, having a car in a service or sales process it would actually be unlikely that software updates would be performed, critical or not.
Not for 20 months. And if it’s in service, they will update it for you. It is part of what they do with every single service, like a complementary wash or key fob battery replacement.
It sounds like the burden is on the latest buyer. Doesn't feel reasonable IMO.
The burden was on the original owner to install the updates.
The burden on the new buyer is to ensure the vehicle is delivered damage-free and with no issues. If it had a broken muffler, that would’ve been on the buyer too, unless he’d had the original owner fix it.
That’s not new.
What *is* new is that the car said it was up to date (which is confusing UX and not what that message means), and that Lucid does not have an officially published list of software releases, to my knowledge. Thus, even if
@rking0122 had wanted to figure out the right version to update to, he would’ve had to find it on either this forum or a different enthusiast website.
The issue isn’t that the used buyer is a used buyer; it’s that you buy a car as-is, after inspecting it has all the things you think it does and everything is in working order. The definition of “caveat emptor,” unless you’re buying it from a dealership (there are lemon laws at play then, potentially).
But you
can’t do that if you have no way of verifying the car is up to date. The answer should have been to talk to Lucid and confirm it before buying the car, but Lucid doesn’t make that easy.
That’s why I think Lucid should cover it. I don’t think they have the
obligation to, as whatever happened with the original owner and them means they didn’t see each other for at least 20 months, missing at least one annual, because again: they would have updated the software for the original owner if it had gone to a service center.
But because it is
confusing and Lucid does not publicize a list of releases (which I think they should), it is harder than it should be, and so I think it would be right for Lucid to cover it.
But it’s not absurd for them not to.
So the question to me is why a critical software update mentioned here isn't simply pushed without user intervention or consent. Tesla has no problem doing this and it's technically not a problem to recognize if the vehicle charge/state is ready to process the update.
I explained this above. A car being bricked in the morning ie extremely more infuriating than a phone.
I hated that Tesla did this and turned it off.
I turned off automatic updates on Unifi for the same reason; I’ll update it when I can watch it, because all too often it would update automatically and *take down my network*. No thanks; sometimes it did this when I was in Europe and couldn’t fix it. Hard pass.
Did anyone tag
@mcr16.
@rking0122 you should also try reaching out to him directly. I’ve seen he has been able to help resolve service disputes in other cases as well
She/her, fyi.
—
Moreover, none of this has anything to do with the “30 days” language in the warranty, so if anyone wants to discuss that, do it elsewhere please.
In addition, none of this has anything to do with “the update that they told us we must install” aka 2.1.43. This car never got close to there. That is completely unrelated.