Car won’t go into DRIVE !

[borski]

Interesting, but that means you think the car being plugged in means it stays awake differently than when it's not even if it's done charging? I don't think that is true, is it?

I had the almost the exact opposite thought, see my test on page 4: https://lucidowners.com/threads/car-won’t-go-into-drive.12216/post-269002

I tested "plugged in but not idle for long" to see if the problem was related to it sleeping for too long (overnight when plugged in). I debunked that but the test would be completely misguided if the car sleeps differently when plugged in.

That’s a fantastic point, and they are different. There are two SLEEP states: POWER_STATE_SLEEP, and POWER_STATE_SLEEP_CHARGE.

Next test: for someone for whom this happens in a repeatable way - can you check either Home Assistant or testmycode.cc before, during, and after it occurs, and submit the responses? (Or look on your own and check the sleep state - see what it’s in and what it switches to when it wakes up?)

 

[bakerjin]

This issue happens to me whether I wake it up and cool the car remotely (regardless of how long, but usually I only do it 5 minutes before entering the car) or if I just walk up to it normally (since the mobile app often takes too long to bother to wake it up at home). I'm glad that the software team is aware of this problem and I hope they can release a fix soon.

 

[helios4382]

New 2025 Pure owner with 800 miles on the clock, this has happened 3 times since getting the car 1 month ago, after unplugging charge cable in the morning. CS advised me to reboot (hold steering buttons & brake pedal for 20 to 30 sec). This has solved the issue every time but is still annoying!!

 

[knewman]

That’s a fantastic point, and they are different. There are two SLEEP states: POWER_STATE_SLEEP, and POWER_STATE_SLEEP_CHARGE.

Next test: for someone for whom this happens in a repeatable way - can you check either Home Assistant or testmycode.cc before, during, and after it occurs, and submit the responses? (Or look on your own and check the sleep state - see what it’s in and what it switches to when it wakes up?)

Great idea, I keep forgetting to trace it out in the logs. Had it happen to me today when I stopped at a convenience store for a few minutes. No charging.

My HAOS log shows the following:

15:17:13 - Transition from "Drive" to "Accessory" (me parking and getting out of the car)
15:17:27 - Transition from "Accessory" to "Wink" (accessory state for 13.9s)
15:18:37 - Transition from "Wink" to "Sleep" (wink state for 1:09m) - this must have occurred while I was in the store
15:20:07 - Transition from "Sleep" to "Monitor" (sleep state for 1:30m) - not sure what triggers Monitor, my digital wallet shows transaction at 15:20, so I was still in the store when this happened. maybe the car saw my phone wake from the parking lot?
15:20:56 - Transition from "Monitor" to "Accessory" (monitor state for 49s) - this must be me getting into the car. note the car did not respond to handle push, had to unlock via the app
15:21:45 - Transition from "Accessory" to "Dive" (accessory state for 48.9s) - this is me sitting in the car waiting for it to respond to gear selection

Comparing this to a normal interaction (i.e. no delay selecting D) from a stop at the library earlier that same day:

14:59:55 - Transition from "Drive" to "Accessory" - me getting out of the car
15:00:37 - Transition from "Accessory" to "Wink" (accessory state for 41.9s)
15:01:49 - Transition from "Wink" to "Sleep" (wink state for 1:12m) - occur while in the Library
15:12:19 - Transition from "Sleep" to "Drive" (sleep state for 10:29m) - interestingly no accessory state or monitor state. maybe it was too quick for HAOS to log?

ps the home assistant integration ROCKS

 

[knewman]

I should note I have engaged with CS at this point. They've had me try a hard reset - holding down the X button, Mic button and brakes until reset triggers. I've let them know the problem is still happening, waiting for further communication.

 

[borski]

New 2025 Pure owner with 800 miles on the clock, this has happened 3 times since getting the car 1 month ago, after unplugging charge cable in the morning. CS advised me to reboot (hold steering buttons & brake pedal for 20 to 30 sec). This has solved the issue every time but is still annoying!!

That sucks; this is not the typical way OTAs go lol. Please don’t let it tarnish your opinion of the car; I do hope it gets fixed soon.

It sounds very annoying.

 

[knewman]

Just had it happen again, this time after a charge session. HA logs show power state transition was sleep/charge > wink > accessory (delay here) > drive. I was thinking perhaps that "monitor" state was part of the problem but evidently not. I think we're just going to have to wait for Lucid to patch it. Sounds like they're aware of the issue and are testing a patch so hopefully not much longer.

 

[dingo]

Happened to me again in a parking lot. It seems to resolve faster these days at least. Center screen and right screen still work though they’re slow. I don’t know if it’s a fix (probably not) but the last two times when I folded and unfolded the mirrors the car magically dinged and was ready to go.

 

[massducati]

Happened to me again in a parking lot. It seems to resolve faster these days at least. Center screen and right screen still work though they’re slow. I don’t know if it’s a fix (probably not) but the last two times when I folded and unfolded the mirrors the car magically dinged and was ready to go.

I had a period where it seemed as if the issue was resolving more quickly, now it seems to be a coin flip. Extremely frustrating.

Tight parking lot at son’s little league game, requires everyone to file out semi-orderly. Normally not a problem …unless you’re the one in the brand new car that won’t move until IT decides it’s time. Line of parents and kids waiting to get out and get home and all I can do is sit and wait while everyone honks. I’ve started driving our old wrangler for reliability’s sake …and that’s saying something.

That lucid hasn’t promptly rectified this, or even made a statement/attempted to assuage concerns, is ridiculous.

 

[ColonelBadger]

For me it's when the car goes in to deep sleep, mostly after its been charging overnight.

 

[acsing]

This has been happening to me since the most recent update. I have had to do a logo reset about eight times. It is very annoying. I put in a ticket to customer service and they said they were looking into it.

 

[Kugs10]

That lucid hasn’t promptly rectified this, or even made a statement/attempted to assuage concerns, is ridiculous.

I agree. This is completely unacceptable. This is a core fundamental drivetrain problem that was disabled by a software update. They need to be all over this.

 

[coma24]

I'm a little perplexed as to what is taking so long to identify the core issue given the volume of data out there (presumably), and the fact that it's clearly not isolated to just one or two instances.

 

[Da445]

Between the lousy service response time from Lucid on other recent issues and the pattern of pushing half-baked OTA SW updates that fix one thing, break two others and rarely ever offer new or improved functionality, I'm sorry to say that I'm done with Lucid. The fact that Lucid continues to invest in factory expansions in multiple locations before investing in solving basic and continuing issues with their in-service fleet shows that they're chasing the wrong objective(s). Thank goodness that this was a short-term lease. My Air Touring is dynamically, the best car I've ever owned/leased. From a software/features/service/support perspective, it is the absolute, hands-down worst. That's sad because there is so much potential here and some superb engineering embodied in the car.

So, Lucid, if you're listening (and it's doubtful that you are), please devote some adequate resources to making your customers happy by promptly fixing issues. What you're doing now is exactly the opposite of that.

 

[massducati]

Between the lousy service response time from Lucid on other recent issues and the pattern of pushing half-baked OTA SW updates that fix one thing, break two others and rarely ever offer new or improved functionality, I'm sorry to say that I'm done with Lucid. The fact that Lucid continues to invest in factory expansions in multiple locations before investing in solving basic and continuing issues with their in-service fleet shows that they're chasing the wrong objective(s). Thank goodness that this was a short-term lease. My Air Touring is dynamically, the best car I've ever owned/leased. From a software/features/service/support perspective, it is the absolute, hands-down worst. That's sad because there is so much potential here and some superb engineering embodied in the car.

So, Lucid, if you're listening (and it's doubtful that you are), please devote some adequate resources to making your customers happy by promptly fixing issues. What you're doing now is exactly the opposite of that.

I'm only a month into my lease, but my feelings are trending this way. I'm hopeful to be proven wrong if they can remedy the more serious issue at play here, but the latest update hit within a week of me taking delivery of the car so my experience has been predominantly negative.

 

[borski]

Between the lousy service response time from Lucid on other recent issues and the pattern of pushing half-baked OTA SW updates that fix one thing, break two others and rarely ever offer new or improved functionality, I'm sorry to say that I'm done with Lucid. The fact that Lucid continues to invest in factory expansions in multiple locations before investing in solving basic and continuing issues with their in-service fleet shows that they're chasing the wrong objective(s). Thank goodness that this was a short-term lease. My Air Touring is dynamically, the best car I've ever owned/leased. From a software/features/service/support perspective, it is the absolute, hands-down worst. That's sad because there is so much potential here and some superb engineering embodied in the car.

So, Lucid, if you're listening (and it's doubtful that you are), please devote some adequate resources to making your customers happy by promptly fixing issues. What you're doing now is exactly the opposite of that.

@marqie (who works for Lucid) has already mentioned that they are aware of this issue and actively working on a fix.

I agree it can’t come soon enough, but it isn’t a matter of them not listening.

 

[dingo]

Honestly, I have had nothing but good service experiences, so I probably have more patience than others -- but it does surprise me there hasn't been any sort of official acknowledgement... I get that marqie mentioned the awareness, though honestly I must have missed that post.

 

[borski]

Honestly, I have had nothing but good service experiences, so I probably have more patience than others -- but it does surprise me there hasn't been any sort of official acknowledgement... I get that marqie mentioned the awareness, though honestly I must have missed that post.

Post in thread 'Car won’t go into DRIVE !'
https://lucidowners.com/threads/car-won’t-go-into-drive.12216/post-267899

 

[knewman]

Honestly, I have had nothing but good service experiences, so I probably have more patience than others -- but it does surprise me there hasn't been any sort of official acknowledgement... I get that marqie mentioned the awareness, though honestly I must have missed that post.

I'm in the same boat as you. Communication is difficult for a large organization with many stakeholders. I'm super appreciative of Marqie's (entirely voluntary!) participation in this forum, the presence of a Lucid rep helps to assuage some of the difficulties I've experienced and my feelings on Lucid's commitment to their customers.

That being said, I think Lucid ought to consider establishing a status page like many technology companies have to track ongoing issues. Connected cars are as much of a service as something like Microsoft 365 or GSuite, the communication should be on par with those platforms (not to say they're perfect either).

 

[mikecronis]

I've noticed delayed "Ready" state since the last software update (along with twitchy Adaptive Cruise phantom-braking). Would not go into gear.
Performed my weekly Air-Logo software update and it seems to have fixed the former issue for now.
Not sure why the Adaptive Cruise is now "jerky". Noticed long-distance car images seem to float-around between lanes now on the screen before settling-out; didn't do that before.