Anybody got these errors before?
If sleep is the solution didn’t @borski say it should only take a few minutes to get to that point rather than 15-20 minutes.The X microphone brake reboot is infotainment. This error is not part of the infotainment. I would reboot by letting the car sleep and reset. Lock it and walk away for 15 to 20 minutes keeping the keyfob away from the car. Then come back and see if the error is still there.
Right! Super odd message but lucid service has been helpful so far… in BFE Indiana and they are sending a tow to get it to Goose Island service center.I’ve heard of this, you’ll need to go to service.
Weird error message too. Left stalk is the turn signal…
Maybe they just don’t want people driving without proper turn signals. Safety first!Right! Super odd message but lucid service has been helpful so far… in BFE Indiana and they are sending a tow to get it to Goose Island service center.
I am not convinced that @borski is correct on the two minutes. I would give it some more time.If sleep is the solution didn’t @borski say it should only take a few minutes to get to that point rather than 15-20 minutes.
I was also under the impression that holding for a second bing was a different level of reset.
Still learning new stuff so always up for instruction.
Then prepare yourself for an argument of epic proportionsI am not convinced that @borski is correct
No need. My proof is the API states, which doesn’t have a state deeper than the standard “SLEEP”, which only takes a couple minutes to go into. You can see that with HA.Then prepare yourself for an argument of epic proportions![]()
Put this in your signature, will save timeUnlikely, but possible!
This is also accurate to my understanding in case people were wonderingYes holding the X mic brake for the second chime is a deeper reset but it is still only infotainment.
A quick and painless win.No need. My proof is the API states, which doesn’t have a state deeper than the standard “SLEEP”, which only takes a couple minutes to go into. You can see that with HA.
It is entirely possible there is a “hidden” state that isn’t shown and I’m unaware of. Unlikely, but possible!
I wil say this is the second time (very far apart occurrences) that we have charges on a slow charger and the charger kicked off THEN we got a bunch of errors. Both times ended up clearing themselves though.Well now went back an hour later and all errors cleared. Maybe it was just software?
Yeah, we've been through this. lolNo need. My proof is the API states, which doesn’t have a state deeper than the standard “SLEEP”, which only takes a couple minutes to go into. You can see that with HA.
It is entirely possible there is a “hidden” state that isn’t shown and I’m unaware of. Unlikely, but possible!
Probably a false error but I wouldn't want to take a chance. Glad you're getting it checked out though hope it doesn't take a month for you.Well now went back an hour later and all errors cleared. Maybe it was just software?