OTA Update 2.6.0

What charger? And when is your schedule set to and when did you plug it in?

Asking because my scheduled charging used to do this but hasn’t in years (and works on 2.6) which is why I’m curious to see if we can find a root cause.

This only started on 2.6?
Lucid Home Charger. Plugged in when my wife got home at about 7p. Set to start at midnight. Has had issues before not being reliable in the past (see the scheduled charging unreliable thread as it is not just me) but has worked consistently for a while. This was the first scheduled charge after the update. It was scheduled, but never woke the car up and charged.
 
Two issues since the 2.6 update. First, the car keeps going offline and always offline when away from the home wifi.

The second issue is the scheduled charging which failed last night. It only started charging when my wife woke up the car to leave for work this morning. This has been a major issue for me. It is like rolling the dice. Sometimes it works sometimes it doesn’t. I would like the to charge overnight when I plug it in. Everytime. My cheap Leaf does this 100%. Why can’t Lucid do something so simple as decent scheduled charging. It almost makes me want to get rid of the Lucid.
Are you maybe stopping the charge when you first plug it in? I’ve never been able to have the car restart charging on the schedule automatically if I stopped it manually until the next time I wake up the car.
 
Are you maybe stopping the charge when you first plug it in? I’ve never been able to have the car restart charging on the schedule automatically if I stopped it manually until the next time I wake up the car.
Nope. The car is set for scheduled. Plug in and the app says charging scheduled. Actually, the car will always start charging if you wake it up within the 12h scheduled charging window (which I wish Lucid would fix with a true start / stop window, that you can set differently for weekdays and weekends like my Leaf, but I digress). For example, this morning I noticed that I only pulled 7 kW of power overnight which was the Leaf on the ChargePoint charger. Strange, since the Lucid was also scheduled. Opened up the Lucid app. The car had not charged, but started charging when I woke it up since it was in the 12h window. I stopped it because it was no longer off peak. When my wife went out with the key, the car started charging again. Bottom line, the car will always start charging if within the 12h scheduled charging window, whether or not you stopped it or if it had reached the limit. If it had reached the limit, it turns on charging and then stops shortly after because the limit had again been reached.

I believe this is a glitch with 2.6 as the car goes offline when not on the home wifi. The car “forgets” to wake at the scheduled charging time.

As for scheduled charging unreliable, I can move to the other thread to answer your questions.
 
I always have to unlock the car to unplug the handle, but once unlocked, I can pull the handle out any time regardless of charge level.
Could it be that you were just waiting for the car to unlock in those 15-30 seconds?
The situation I describe is 1) Charge to 80% completed 2) Later that day go to car and unlock 3) Car boots up and starts to charge; unable to pull out handle 4) 15-30 seconds later, car realizes charge is/was complete and I'm then able to disconnect.

It seems like it was charging to exactly 80%, then when it boots it may be at 79.9% and tries to start charging again. Now what I'm seeing is when I unlock, the car won't try to initiate a charge and I'm able to pull out handle immediately. I'm wondering if the 80% charge target now stops at something north of 80%, where before it stopped immediately at 80%.
 
Lucid Home Charger. Plugged in when my wife got home at about 7p. Set to start at midnight. Has had issues before not being reliable in the past (see the scheduled charging unreliable thread as it is not just me) but has worked consistently for a while. This was the first scheduled charge after the update. It was scheduled, but never woke the car up and charged.
Yup, okay, that’s weird. I have mine set to start at 9:01pm and it used to fail at starting to charge but hasn’t in ages. I wonder if it’s because it’s set to midnight? Maybe try setting it to 11:59pm. That would be dumb, but I’m curious.

Or it’s a bug in 2.6. Also very possible.
 
I scheduled to charge at 12:03 am and the scheduled charging work's fine for me. Sometimes I use the charger that came with the car or Lucid LCHS.
 
I know that the road rash warnings were tweaked in this release but my car has suddenly showing a road rash alert not available even though I have not been in a low light, rain, or other situation that might interfere with the optics. It was working after the update but then stopped. I have tried a logo reset and that didnt help? Any insights?
 
The situation I describe is 1) Charge to 80% completed 2) Later that day go to car and unlock 3) Car boots up and starts to charge; unable to pull out handle 4) 15-30 seconds later, car realizes charge is/was complete and I'm then able to disconnect.

It seems like it was charging to exactly 80%, then when it boots it may be at 79.9% and tries to start charging again. Now what I'm seeing is when I unlock, the car won't try to initiate a charge and I'm able to pull out handle immediately. I'm wondering if the 80% charge target now stops at something north of 80%, where before it stopped immediately at 80%.


When you charge the car overnight, it stops charging when it hits the charge limit you set. However, if you don't drive the car after it reaches the limit, the charge level will dissipate over time (an hour) and it will top up to the charge level. If you happen to enter the car when it's topping up you will not be able to unplug. You will get notifications of these events: end of charge, start of charge, end of charge.
 
I upgraded my 2025 Air Pure to the 2.6 release without issue a few days ago. I've experienced zero issues so far. One curious behavior since the upgrade is that my Android phone (Pixel 7A) sends me a notification that Android Auto is available each time I get in the car. Sadly there is no indication on the Air Pure display or menus that Android Auto is available, so no joy there. I'm guessing that some part of the Android Auto initial handshake interface between the car and the phone has made its way into the release.
 
I know that the road rash warnings were tweaked in this release but my car has suddenly showing a road rash alert not available even though I have not been in a low light, rain, or other situation that might interfere with the optics. It was working after the update but then stopped. I have tried a logo reset and that didnt help? Any insights?
Same here. Permanent notification that curb rash is not available (which I can’t turn off). Plus cameras are now a mess, climate settings don’t maintain previous settings, car defaults to in-house navigation upon every new drive, and Drive Assist that only shows the car straddling two lanes and not in a lane hence it’s now useless. Another update, and two steps back.
 
Same here. Permanent notification that curb rash is not available (which I can’t turn off). Plus cameras are now a mess, climate settings don’t maintain previous settings, car defaults to in-house navigation upon every new drive, and Drive Assist that only shows the car straddling two lanes and not in a lane hence it’s now useless. Another update, and two steps back.
Same for me on Rash not available.
In addition, my heated steering wheel fails to heat nor will indicator stay lit in 1 out of 4 drives. Logo reset and Bobby reset do not correct. Only correction seems to be when it sleeps overnight. (Been very chilly here, and I have Raynauds Syndrome)
 
Same here. Permanent notification that curb rash is not available (which I can’t turn off). Plus cameras are now a mess, climate settings don’t maintain previous settings, car defaults to in-house navigation upon every new drive, and Drive Assist that only shows the car straddling two lanes and not in a lane hence it’s now useless. Another update, and two steps back.

For those of us who long ago migrated from Tesla - this is very Tesla-like. With every update, it’s one wave forward, three waves back.
Or, Lucid/Tesla fix something only to break something else. It’s just the way it goes with these EV manufacturer software updates.
 
Anyone else having issues with the heated steering wheel since 2.6 update? Mine won’t stay on anymore. If I click on the button, it goes on and then immediately turns off. Software reset did not fix it.
For those having this issue, I found on a reddit thread that you can get the heated wheel to stay on by rapidly, repeatedly tapping the button for a few seconds. Stupid thing to have to do, but it works. The issue that remains is that the wheel heater doesn't come on when you try to heat your car with the phone app to be warmed when you get in. My seat heat doesn't turn on remotely, either, but that at least works reliably from the car's screen.
 
I experienced a weird issue with 2.6.0 this morning. The middle and left screens in the cockpit were black and the car didn’t start when pressing the brake pedal.
Logo reset didn’t fix it, but the Mic+X+Brake reset fixed it. I’ve never had anything like this happen to me over my 10+ months of owning it and driving it on a daily basis, but I’m glad I know all kinds of resets to quickly fix it myself.

View attachment 26525
Same thing. I walked away and came back 10 minutes later and it was ok.
 
So, is the consensus that an owners are now facing issues with Drive Assist either pulling to left or right post 2.6 ? Like me ?

PS, I have a minute video but due to attachment being large, I cropped the video
 

Attachments

  • IMG_6890.mov
    12.9 MB
So, is the consensus that an owners are now facing issues with Drive Assist either pulling to left or right post 2.6 ? Like me ?

PS, I have a minute video but due to attachment being large, I cropped the video
Apparently, some. Mine is fine. I imagine it is a minority, but I don’t have data or stats, so that’s just a guess.
 
It seems like it was charging to exactly 80%, then when it boots it may be at 79.9% and tries to start charging again. Now what I'm seeing is when I unlock, the car won't try to initiate a charge and I'm able to pull out handle immediately. I'm wondering if the 80% charge target now stops at something north of 80%, where before it stopped immediately at 80%.
Can you pull the handle out at any time by pressing the latch button on the handle? I'm wondering if the root of your comment is based in the charge restarting (which is perfectly normal depending on conditions), vs not being able to unplug the handle by pushing the latch button.
 
So, is the consensus that an owners are now facing issues with Drive Assist either pulling to left or right post 2.6 ? Like me ?

PS, I have a minute video but due to attachment being large, I cropped the video
Yeah add me to that list. CS had me do the buttons/brake reset and one I hadn’t heard of. Get out of the car. Lock it. Get back in, place in drive and then immediately place in park and then walk away without disturbing the car. Assured me this was different than a tradition power cycle as it triggered the car to reset differently.

Still persistent pulling issue. Service scheduled.

I want to highlight that CS promptly responded to my text message within minutes. They remained responsive even after I was working and could only respond intermittently. They also provided me with a step-by-step guide to help me try to resolve the issue on my own. Before they scheduled a service at the end the call text.
 
Have you tried a reset? I always recommend a logo reset after any update.
Thanks, I tried that, to no avail. I called Lucid to complain. The agent had me jump through a bunch of hoops that I had already traversed. When they failed, she informed me that, oh yeah, we’re having trouble with 2.6. They actually stopped the rollout of 2.6, and apparently are working diligently to fix it.
 
Back
Top