Car won't sleep

Also cabin is really warm?! It's 60 degrees outside
1000024901.webp
 
Exactly. It feels like the battery is hot, there's heat radiating everywhere in the cabin.
My powerstate indicates:
"powerState": "SLEEP_CHARGE",<br> "cabinState": {<br> "interiorTemp": 26.7000015899539,<br> "exteriorTemp": 25.500000976026058<br> },
 
I'm gonna head home, unplug the car, park on the street and call service
 
My powerstate indicates:
"powerState": "SLEEP_CHARGE",<br> "cabinState": {<br> "interiorTemp": 26.7000015899539,<br> "exteriorTemp": 25.500000976026058<br> },
That’s a normal charging state; it indicates the vehicle is currently charging but nobody is in it. (LIVE_CHARGE would be charging with someone in the vehicle)

So… are you charging? :)
 
Hey @borski do you know what "wink" powerstate means? My car seems to be running the past day too and gone from 54% to 38% over night. It is hot here in Phx though.

1749488196007.webp
 
Maybe this is the kind of issue that Lucid might want to pay attention to. Might be just a small thing, but if an Air catches on fire, it will make the news for sure - not in a good way. @marqie
 
I unplugged my car and can confirm that the phantom loss is suddenly much more than before.

The only change I noticed is that my Android app is now much more responsive. I didn't know the app version had changed.

I unplugged for 10 hours with all doors/trunks/lights/display on/open for an experiment before, and got a phantom loss of 1% (The lights/displays all timed out in about 30 minutes).


This time, for the same 10-hour duration, but now with all doors and accessories off, I experienced a phantom loss of 3%.

I prioritize range over convenience, so I would prefer a slow app response, as before, rather than losing range. I always got very good response from the fob so slow app is not a problem for me.

I don't think there's anything wrong with the car. Someone has been messing around with my Android app.
 
I seem to be losing about 1% an hour. Still in wink state.

1749492197778.webp
 
That’s a normal charging state; it indicates the vehicle is currently charging but nobody is in it. (LIVE_CHARGE would be charging with someone in the vehicle)

So… are you charging? :)
I shouldn't be charging. Am plugged in but hit 81% this morning (dont ask why- the stupid slider on the app limiter is really hard to get to 80%) so shouldn't be charging.
 
After unplugging car
},<br> "powerState": "MONITOR",<br> "cabinState": {<br> "interiorTemp": 25.10000156611204,<br> "exteriorTemp": 23.10000094026327<br> },
 
To test the theory issue is being caused by Android app I turned off my phone about 5 minutes after the last screen shot. The car then showed "powerstate": "SLEEP" and the battery drain has stopped, so it does appear to be an Android App issue with my car and not the car itself. Still curious what the "WINK" powerstate means.

1749495117689.webp
 
To test the theory issue is being caused by Android app I turned off my phone about 5 minutes after the last screen shot. The car then showed "powerstate": "SLEEP" and the battery drain has stopped, so it does appear to be an Android App issue with my car and not the car itself. Still curious what the "WINK" powerstate means.

View attachment 29577
It seems that the app changes the permissions behind the scenes and keeps unrestricted battery access. This causes the app not to go to sleep which in turn pings the car to get the latest battery level info which causes the car to keep awake. Until the fix comes the work around I found was to force stop the app and change battery setting to restricted every time I open the app. Or try not to use the app and use the key fob instead.
 
After unplugging car
},<br> "powerState": "MONITOR",<br> "cabinState": {<br> "interiorTemp": 25.10000156611204,<br> "exteriorTemp": 23.10000094026327<br> },
Can confirm it now shows sleep since unplugging
 
I can confirm that force-stopping the app on Android stopped the drain. The car slept like a baby. I hope reinstalling the app will fix this issue, cause I can't force-stop it every time I use it.
 
This is the 2nd time it happened in a month, the car refuses to sleep. It keeps humming quietly - the sound that it makes after you lock it and walk away. Also, when I open the mobile app it's already connected, usually it takes 5 - 10 seconds.

No, I don't have the phone or key next to it, temperature is around 72F, I don't do anything different. As a result, it drew 9 kw in 24 hours of being parked.

Any ideas?
MY 2023 Touring does exactly the same thing.. The solution to this issue for me has been; every time I get out of the vehicle after parking, I click the key FOB once to lock the car. The car stays asleep until I return to the car with the key FOB in hand.. I sometimes have to double click the FOB to force an unlock... But that works for me and I no longer eat range when i have left the area of the car. Good Luck.
 
MY 2023 Touring does exactly the same thing.. The solution to this issue for me has been; every time I get out of the vehicle after parking, I click the key FOB once to lock the car. The car stays asleep until I return to the car with the key FOB in hand.. I sometimes have to double click the FOB to force an unlock... But that works for me and I no longer eat range when i have left the area of the car. Good Luck.
I never carry the key, just the phone. The problem is with the Android app apparently, for some reason it keeps pinging the car - which it never did before.
 
Hey @borski do you know what "wink" powerstate means? My car seems to be running the past day too and gone from 54% to 38% over night. It is hot here in Phx though.

View attachment 29575
'WINK' means a key of some sort (keyfob, mobile key) was detected, and the vehicle is waking up from 'SLEEP'. It should not stay in 'WINK' for very long, and should switch back to either 'SLEEP' or 'ACCESSORY' within a minute or so. 'ACCESSORY' is the state the vehicle goes into when someone is in the car and everything is ready to go. Then if you go into gear (either 'D' or 'R'), it will switch into 'DRIVE'.

Maybe this is the kind of issue that Lucid might want to pay attention to. Might be just a small thing, but if an Air catches on fire, it will make the news for sure - not in a good way. @marqie
True, but we are far from that, haha. The battery temps have been very reasonable, if a bit higher than normal, and nowhere near 'too high'. Charging on DCFC brings those temps *way* higher, and a fire would mean much, much more failed than just "the car won't sleep."
 
Back
Top