New (To us) 2023 Lucid Air - lots of random bugs.. typically?

[PaulPS]

Last month we traded in our Tesla for a 2023 Lucid Air Touring. We bought the used Air directly from Lucid and took delivery in Costa Mesa. We've had a series of odd issues with the car. A mobile tech came out, and said that what he saw couldn't be repaired by him. We have an appointment at Costa Mesa next week. But I wanted to see if others have these issues, and if we should expect them to be fixed, or they are known software 'bugs':

(1) Car doesn’t always preset handles upon approach even with app open, we need to touch the unlock button. Sometimes the fobs work to get handles to present, other times it takes up to a minute for the car to react to a fob. We've replaced both fob batteries with new Duracells and no change.
(2) Profiles and Seats - We have a profile programmed to each fob. Sometimes the car recognizes the fob and will change the profile, sometimes it won't. Sometimes it will set the Fob-profile media but not the seats. Sometimes the opposite. Sometimes a message appears to ask if you want to load the fob's profile.. very inconsistent and frustrating since the two drivers have very different seat settings.
(3) The screen between the seats sometimes does not go on. We have to walk away from the car and re-wake it up for it to work. The mobile tech confirmed the screen needs to be replaced when we bring it in so at least we know that will be replaced.
(4) 50% of the time when we park the car in our garage and walk away, the car does not turn off. We will come back several minutes later and it's still on. The only way to turn it off is to log on to the app and lock it (locking with the fob doesn't turn it off) It rarely happens when we are parked away from the house.
(5) One night we went out to dinner and came back to find the Frunk wide open. Couldn't close it with the app, the button on the dash or the button inside the Frunk...had to manually close it.
(6) The passengers side reading light randomly comes on while driving.
(7) We set up a valet key with a pin to drive. Since doing that (and turning the pin off) when we use one key fob it always asks for a pin to drive.

We are hoping its one 'computer' issue that when replaced these strange issues go away... but realize this is like buying a first generation iPad that always needs rebooting.. will most of these issue go away?

Look forward to others experiences and if Lucid was able to resolve the issues.

 

[segbrk]

(1) Varies unfortunately. My experience isn't as bad as it sounds like yours is. Some people have no issues, some have worse(?)
(2) No idea as I only have the one profile

The rest... not normal at all. Only one person on here has reported their frunk has opened randomly as far as I'm aware. I have never heard of the reading lights coming on randomly. You've got some demons in that car. Hopefully like you said it's one bad computer ruining the bunch.

 

[bmathieu]

(1) Varies unfortunately. My experience isn't as bad as it sounds like yours is. Some people have no issues, some have worse(?)
(2) No idea as I only have the one profile

The rest... not normal at all. Only one person on here has reported their frunk has opened randomly as far as I'm aware. I have never heard of the reading lights coming on randomly. You've got some demons in that car. Hopefully like you said it's one bad computer ruining the bunch.

Agreed 100%. #1 and #2 are normal Lucid behavior (unfortunately). The others are unusual and not frequently reported (if ever, and I have been following the forums closely for six months).

 

[Halodde]

Out of curiosity, how did Lucid even have possession of a used '23 Touring? I don't they had any as test drive cars and they don't take trade-ins AFAIK.

 

[bmathieu]

Out of curiosity, how did Lucid even have possession of a used '23 Touring? I don't they had any as test drive cars and they don't take trade-ins AFAIK.

Not sure but I did my test drives out of Newark HQ in a 2023 GT (to purchase my 2025 GT). So they have them somehow. Perhaps they were employee cars.

 

[PaulPS]

Thanks everyone.. they have 'used' vehicles posted on their website as cars that are available now. This one only had 7000 miles on it and was somewhere in the south. We had to pay to have it shipped to CA. From what I understand they said it was a former rental.. not sure if that means loaner.

 

[segbrk]

Thanks everyone.. they have 'used' vehicles posted on their website as cars that are available now. This one only had 7000 miles on it and was somewhere in the south. We had to pay to have it shipped to CA. From what I understand they said it was a former rental.. not sure if that means loaner.

Could be a loaner maybe? But Enterprise does have Lucids, it could have been one of theirs. Not sure why it would be returned so soon (or at all) in that case, but I have no idea how rental companies operate.

 

[BS8899]

Last month we traded in our Tesla for a 2023 Lucid Air Touring. We bought the used Air directly from Lucid and took delivery in Costa Mesa. We've had a series of odd issues with the car. A mobile tech came out, and said that what he saw couldn't be repaired by him. We have an appointment at Costa Mesa next week. But I wanted to see if others have these issues, and if we should expect them to be fixed, or they are known software 'bugs':

(1) Car doesn’t always preset handles upon approach even with app open, we need to touch the unlock button. Sometimes the fobs work to get handles to present, other times it takes up to a minute for the car to react to a fob. We've replaced both fob batteries with new Duracells and no change.
(2) Profiles and Seats - We have a profile programmed to each fob. Sometimes the car recognizes the fob and will change the profile, sometimes it won't. Sometimes it will set the Fob-profile media but not the seats. Sometimes the opposite. Sometimes a message appears to ask if you want to load the fob's profile.. very inconsistent and frustrating since the two drivers have very different seat settings.
(3) The screen between the seats sometimes does not go on. We have to walk away from the car and re-wake it up for it to work. The mobile tech confirmed the screen needs to be replaced when we bring it in so at least we know that will be replaced.
(4) 50% of the time when we park the car in our garage and walk away, the car does not turn off. We will come back several minutes later and it's still on. The only way to turn it off is to log on to the app and lock it (locking with the fob doesn't turn it off) It rarely happens when we are parked away from the house.
(5) One night we went out to dinner and came back to find the Frunk wide open. Couldn't close it with the app, the button on the dash or the button inside the Frunk...had to manually close it.
(6) The passengers side reading light randomly comes on while driving.
(7) We set up a valet key with a pin to drive. Since doing that (and turning the pin off) when we use one key fob it always asks for a pin to drive.

We are hoping its one 'computer' issue that when replaced these strange issues go away... but realize this is like buying a first generation iPad that always needs rebooting.. will most of these issue go away?

Look forward to others experiences and if Lucid was able to resolve the issues.

I've experienced [1], [2], and [3] on a persistent basis. Sometimes, [1] can be problem-free for many months. But often after an OTA, it malfunctions again. As a matter of fact, I just deleted and reinstalled my Mobile Key probably for the 5th or 6th time to overcome the symptoms you reported on [1]. [4]-[7] are not common occurrence for my 2022 AGT.

In short, Lucid has a lot of bugs with its SW. I am not a SW engineer but I oversaw HW/SW/FW development on many products. And it appears Lucid doesn't thoroughly test/ validate their OTAs before they release them. Over time, there are inevitable proliferation of Lucid variants (different trims, different hardware/firmware components, geo-specific variations, etc.). The released OTA might work on some variants but not on others. And Lucid would then scramble and release a multitude of "dot" OTAs to fight the fire. If true, these are self-inflicted wounds. I hope Lucid can get their act together and instill discipline in their SW and OTAs.

 

[Halodde]

Not sure but I did my test drives out of Newark HQ in a 2023 GT (to purchase my 2025 GT). So they have them somehow. Perhaps they were employee cars.

Yes, that's what I meant. I think all test drive cars were GTs and not Tourings.

 

[valentino]

In short, Lucid has a lot of bugs with its SW. I am not a SW engineer but I oversaw HW/SW/FW development on many products. And it appears Lucid doesn't thoroughly test/ validate their OTAs before they release them.

I don't agree with this assessment. Yes there are bugs. But I also categorized most bugs I see as P3 bugs. I have not seen p1 or p2 personally. There was a recent bug that could potentially be p2 but they managed the rollouts so most of us would never have seen it which is why you manage rollouts (notice how people scream how come I didn't get my patch update yet). While I don't know their inner development I do recognize the process and they are following good software development process. One sign of bad dev would be a p1-p3 bug that was fixed and then resurface 2-3 iterations later and repeats itself down the road which is a sign that someone is terrible at branching mgmt. And the staff composition is not sophisticated enough to do validation on branching.

Customers are the absolute worst when it comes to bug expectation. They will say they understand and expect some bugs. But in reality they expect things like text misspelled or incorrect color on the screen. Anything functional they would scream bloody murder and classify it as P3. The only types of bugs they classify as p1 are things like explosions or skynet takes over and steers your car over a cliff. In my 30 years as a software engineer I have never seen a end user who knows how to manage software expectation. I had one group at the depth of defense actually tell me they don't care if the software functions perfectly and safely and no bugs but if the font and color scheme is not their preferred set they will consider the release DOA. We're not even talking about red instead of blue but dark blue VS less dark blue.

 

[Wilber]

Sorry to hear you have having all these problems. Certainly seems to me you are having more problems than most people. Let me suggest that you tell us which software version you are on. For example, i am on 2.6.11.

I am a former Tesla owner and have been driving my 2025 Air Pure RWD (Yep, the 'base' model) for 6 months. I have NOT linked my iphone as a mobile key. I prefer to use the fob. I have noticed that the car doesnt necessarily unlock or present handles when i walk up to it with a key fob. BUT, If i press on the drivers door handle once or twice it wakes up and presents handles. Also, the key fob is different from a Tesla key fob in two ways: 1. It has a longer range than a Tesla key fob, and 2. the key fob battery tends to deplete faster than a Tesla key fob battery. So, for example If i an in the house with a key fob the car in the garage often senses it and tends to keep the car 'on'. Maybe this is why you are finding the car 'on' when you expected it to be off - as described in your item #4. Others in this forum have reported this problem and bought some kind of a box to put the keyfob in at home so it no longer connects to the car. When you leave to drive you take the keyfob out of this box. Instead i usually keep the key fob at the far end of the house and that seems far enough for the car to relax and stay off.

Hope that helps. and Good Luck!

 

[borski]

Your car has a problem; like everyone said, most of the issues you're facing are absolutely not normal.