Car locked with child inside and would not unlock

It's an $80k+ car. Most software programmers (who live in the hyper-expensive Bay Area) can't afford to spend that much on a vehicle. Even with an employee discount.
I think Lucid will save a lot of money if they give all their software programmers cars for free. The software will become much more useful and many of the bugs will be fixed really quickly if you have to use the software you develop.

Not sure if you recall the quality of Microsoft Teams (Skype for Business or whatever it was called) before the pandemic struck and the Microsoft employees were forced to use it for their day-to-day communications.
 
I think Lucid will save a lot of money if they give all their software programmers cars for free. The software will become much more useful and many of the bugs will be fixed really quickly if you have to use the software you develop.
I don't know if it is still true....Lucid gave Lucid company cars to their Mobile Tech. That way, they don't show up at the customer's house in a Honda, or worse yet, in a Tesla!

Also, the mobile techs become much more in-tune with what the customer was talking about.

I remember an incident about 2 years ago a mobile tech (from Millbrae) came to my Marin County home to do regular maintenance. I told him to look into why my valet key cards don't work. He could figure it out during his visit. To his credit, after he got back to the service center, he met his supervisor and his colleagues. they concluded the B-pillar sensor was bad. The mobile tech came back a couple of days later, replaced my sensor, and it worked!
 
I don't know if it is still true....Lucid gave Lucid company cars to their Mobile Tech. That way, they don't show up at the customer's house in a Honda, or worse yet, in a Tesla!

Also, the mobile techs become much more in-tune with what the customer was talking about.

I remember an incident about 2 years ago a mobile tech (from Millbrae) came to my Marin County home to do regular maintenance. I told him to look into why my valet key cards don't work. He could figure it out during his visit. To his credit, after he got back to the service center, he met his supervisor and his colleagues. they concluded the B-pillar sensor was bad. The mobile tech came back a couple of days later, replaced my sensor, and it worked!
I meant: "He COULDN'T figure it out during his visit. "
 
Quick update on this: I honestly didn’t expect this to get as much attention as it did, but after I shared the details with @marqie, someone from Lucid reached out directly. They were very attentive to my concerns and thoughtful about the situation. Most importantly, they acknowledged that this is a real issue and confirmed that they’re actively working on it.

They’ll be taking my car in for service so they can repro better. Hoping this is a small step toward getting these issues fully resolved once and for all. I definitely feel like they care, which is really important to me.
Still, I’m wondering what the fix is. The phone lock/unlock is the number 1 nagging issue with the Air, which is obviously well known. Are they saying it’s an issue with detecting weight on the seat and that a human may be inside?
 
Engineering hat on

Honestly, the biggest issue here seems to be the car making hard yes/no decisions in situations that really need more context-aware behavior.

Right now the logic may effectively be:
- phone RSSI drops / credential moves away = auto-lock

But real-world behavior around a vehicle is more nuanced than that. A parent walking around the car to grab a child can temporarily look identical to “owner walked away.”

The access system should be looking at multiple signals together before deciding the interaction is over:
- how recently the drive ended,
- recent rear door activity,
- whether the phone is still moving around the car,
- cabin activity,
- repeated unlock attempts,
etc.

Instead of immediately auto-locking, the car should probably stay in an “active interaction” state for a short grace period when things are ambiguous.

I also can’t help but wonder if the whole lights/handles/choreography sequence is making the system more fragile than it needs to be. It feels like too many things have to happen perfectly in sync:
- wake states,
- credential auth,
- handle presentation,
- latch authorization,
- lighting animations,
etc.

That’s a lot of moving pieces for something that fundamentally should just prioritize:
“always let the authorized user back into the car safely.”

In edge cases like this, the system should bias toward accessibility and safety instead of aggressively committing to an auto-lock state off a single signal transition.
 
Engineering hat on

Honestly, the biggest issue here seems to be the car making hard yes/no decisions in situations that really need more context-aware behavior.

Right now the logic may effectively be:
- phone RSSI drops / credential moves away = auto-lock

But real-world behavior around a vehicle is more nuanced than that. A parent walking around the car to grab a child can temporarily look identical to “owner walked away.”

The access system should be looking at multiple signals together before deciding the interaction is over:
- how recently the drive ended,
- recent rear door activity,
- whether the phone is still moving around the car,
- cabin activity,
- repeated unlock attempts,
etc.

Instead of immediately auto-locking, the car should probably stay in an “active interaction” state for a short grace period when things are ambiguous.

I also can’t help but wonder if the whole lights/handles/choreography sequence is making the system more fragile than it needs to be. It feels like too many things have to happen perfectly in sync:
- wake states,
- credential auth,
- handle presentation,
- latch authorization,
- lighting animations,
etc.

That’s a lot of moving pieces for something that fundamentally should just prioritize:
“always let the authorized user back into the car safely.”

In edge cases like this, the system should bias toward accessibility and safety instead of aggressively committing to an auto-lock state off a single signal transition.
Looks like you are a perfect potential employee of Lucid! Go for it! 😊
 
I also think UWB won’t fully fix the problem.

UWB wil improve the proximity detection and accuracy, but the issue still seems to be how the software handles edge cases and ambiguous situations. That’s probably what they can optimize for.
 
I can't say I have had any vehicle with PAAK that I didn't have to do this on occasion.

- 2021 Tesla Model 3 Performance
- 2022 Rivian R1T Adventure Quad Motor
- 2025 Kia EV6 GT-Line AWD

(and now my Lucid)
For my BMW iX with PaaK, I occasionally need to wake up my phone to unlock. It doesn’t bother me much but it does happen.
 
I agree with all the points you made. Yes, some problems might be hard to reproduce. That doesn't mean these are entirely random. Perhaps some of these problems (let's say locking/unlocking as an example) result from events prior. Perhaps a register was corrupted or not flushed properly, perhaps there was a race condition that was not anticipated in the architecture, etc..

While I think each of the SW developers validate their own codes but is/was there an overall architect/integrator that has the responsibility of exercising the final integrated system in its entirety. Even if you did all of that, you might still be missing something.

Yes, not every owner encounters the door lock/unlock problem. But I was surprised by @Bobby's passionate post regarding his frustration with the locking/unlocking in his Air, to the extent that it could modulate his decision whether to buy another Lucid ever again!

So, why don't we recruit @Bobby, have Lucid instrument his Air. Data-log all the relevant data/signals for the next 30-60 days. Perhaps we can all learn something.
They know I'm willing.
 
They know I'm willing.
You are the man!

You are credible. You do what's right!

With respect to the door locking/unlocking problem, I am totally with you. That said, sometimes, intermittent problems are hard to diagnosis. If we can data-log from a credible source and analyze the events recorded, perhaps we can find a clue to this "mystery".

You have the credibility and knowledge to help Lucid make progress on these gremlins.

I hope Lucid take us upon this!
 
Yeah, the car locking your kid in is just a small inconvenience.

Think of the stock price people, stop talking about locking kids in!
Kids = short 🤣
 
You are asking the right question. Some of these intermittent problems don't show up persistently. If the SW team (or, for that matter, the Service Center team) are not truly embedded in and intimately familiar with the vehicle, they won't see the kind of problems that an owner would.

I actually posed your exact question to several Lucid SW engineers. While it is a small sample and my survey was not "scientific", this small group of Lucid SW engineers don't own and drive Lucid vehicles every single day.
Next flyover video should be of the AMP-1's employee parking lot 🙂
 
You are the man!

You are credible. You do what's right!

With respect to the door locking/unlocking problem, I am totally with you. That said, sometimes, intermittent problems are hard to diagnosis. If we can data-log from a credible source and analyze the events recorded, perhaps we can find a clue to this "mystery".

You have the credibility and knowledge to help Lucid make progress on these gremlins.

I hope Lucid take us upon this!
@marqie, Can you help action this? I think @Bobby would be a great candidate to gather the data. I can volunteer as well. But i don't accumulate as much mileage as you might think because I split my time driving my Lucid and my Rivian. My 2022 AGT "only" has 20,000 miles on it.
 
I’ve defended Lucid for a long time. This is actually my second Lucid Air in 3 years, and I’ve tried to be patient with all the software glitches, key issues, random bugs, and “it’ll get fixed in an update” stuff.

But yesterday honestly was the worst for me.

I was driving home with my 1.5-year-old in the back seat. He had finally fallen asleep listening to his favorite lullaby through CarPlay. Right before we got home, CarPlay randomly disconnected out of nowhere and stopped playing. Would not connect back at all. He’s a super light sleeper, so he immediately woke up crying.

I pulled into the driveway, opened the driver door, and walked around to get him out of his car seat.

And the car locked itself.

Wouldn’t open. Wouldn’t respond. Just completely locked with my baby inside crying.

I can’t even explain the panic of standing outside your own car, trying everything, while your kid is locked inside screaming.

Eventually it opened, but that moment completely broke my trust in this car.

I can deal with little tech annoyances. I can deal with bugs here and there. But basic reliability and safety issues like this? On a car that’s been out for years? Unacceptable.

I wanted this car to succeed so badly because when it works, it’s incredible. But after yesterday, I honestly don’t know how I’m supposed to trust it anymore. This company has lost sight of basic things in the push to just sell more cars

Done with this car but still hoping they somehow make it through

2023 Lucid Air Touring
2025 Lucid Air Pure
Do not panic. If the key is inside. All you need to do is tp press the handles in and it will pop out. It happened to me also. I thought i locked myself out.
 
When i press lock unlock, it wont respond. Go closer to the car -> Dance for a tune -> and the key will work 😁. This is a hit and miss too 🙂.
You dont need to dance. There is a way to approach the vehicle that ot can detect the keys right away. I have a key fob and i really wish i can make a video on how to make the Lucid Air open keyless. I have only been using the key fob as it is thin enough to live in my wallet. Prob half a second delay if i approach it wrong. But if i had it right. It will open before i reach the door.
 
Engineering hat on

Honestly, the biggest issue here seems to be the car making hard yes/no decisions in situations that really need more context-aware behavior.

Right now the logic may effectively be:
- phone RSSI drops / credential moves away = auto-lock

But real-world behavior around a vehicle is more nuanced than that. A parent walking around the car to grab a child can temporarily look identical to “owner walked away.”

The access system should be looking at multiple signals together before deciding the interaction is over:
- how recently the drive ended,
- recent rear door activity,
- whether the phone is still moving around the car,
- cabin activity,
- repeated unlock attempts,
etc.

Instead of immediately auto-locking, the car should probably stay in an “active interaction” state for a short grace period when things are ambiguous.

I also can’t help but wonder if the whole lights/handles/choreography sequence is making the system more fragile than it needs to be. It feels like too many things have to happen perfectly in sync:
- wake states,
- credential auth,
- handle presentation,
- latch authorization,
- lighting animations,
etc.

That’s a lot of moving pieces for something that fundamentally should just prioritize:
“always let the authorized user back into the car safely.”

In edge cases like this, the system should bias toward accessibility and safety instead of aggressively committing to an auto-lock state off a single signal transition.
I agree with you about a grace period. There's no reason the car should ever lock a few seconds after it detected a valid user's phone, or if a fob double click just happened. Or if you just stopped driving and opened and closed the driver's door, even. There's almost no scenario when the user would want an immediate auto-lock at that point. Let 20 seconds go by before you even consider triggering an auto-lock in those cases.

As far as the system biasing toward access in all cases, I don't know. Unauthorized access is a big deal for an expensive car. You don't want an easy vector for thieves to get inside the car when they shouldn't. If the car has been locked for several hours, and you are trying to open it, I don't have a problem in that case with waiting until you are VERY sure an authorized key is present before opening. Although, from a safety perspective, needing to get into the car quickly if you are being chased is a thing.

Tough call.

Either way, the grace period is an excellent idea. That would be on the top of my list if I were the team working on this.
 
Do not panic. If the key is inside. All you need to do is tp press the handles in and it will pop out. It happened to me also. I thought i locked myself out.
Do you think they never thought to press the handle during this issue?
 
Do you think they never thought to press the handle during this issue?
There are a lot of very knowledgeable owners here and clearly you are one.

But I am guessing some newer owners may not be aware the door handles have inward movement to perform a wakeup, which is all he was saying.
 
There are a lot of very knowledgeable owners here and clearly you are one.

But I am guessing some newer owners may not be aware the door handles have inward movement to perform a wakeup, which is all he was saying.

Yes, @Leftlane. Even I didn't know about the pushing the handles thing until a few months into ownership. And I'm a total nerd for this car.

It's generally good practice here on the forum to double check for understanding (without being condescending of course) before assuming the car is at fault.

The car is very often at fault, to be clear. But user error is also a thing. And most are happy to learn something new when it's pointed out to them politely. Especially if it saves them a trip to service.

I detected no snark in @iceRN09's post. They were just trying to be informative about something they themselves had not known at first.
 
Yes, @Leftlane. Even I didn't know about the pushing the handles thing until a few months into ownership. And I'm a total nerd for this car.

It's generally good practice here on the forum to double check for understanding (without being condescending of course) before assuming the car is at fault.

The car is very often at fault, to be clear. But user error is also a thing. And most are happy to learn something new when it's pointed out to them politely. Especially if it saves them a trip to service.

I detected no snark in @iceRN09's post. They were just trying to be informative about something they themselves had not known at first.
A delay would be helpful. Here's my post from 3 years ago with suggestions to improve the Mobile Key experience with some software functions. Proximity stuff has been implemented; would be nice to have the rest.

 
Back
Top