FSD attention alert siren won’t stop

[CBMW6674]

Was using FSD earlier today and was looking at my Apple Watch for a second and got a warning alert to pay attention. Well this alert now will not go off and have even tried resetting with the scroll wheels twice and it comes right back on. Have reached out to Tesla and so far all they have said is, that is strange. Anyone have this same issue and was able to reset? The noise is so annoying that it makes the car not drivable.

Sponsored

 

[UberNoob]

What happens when you put it in park and lock the doors. Wait 15-30 seconds and try again ?

 

[CBMW6674]

I’ve got out of the car locked and waited 30 mins and come back to it and it’s still going. It turns off when you lock it and out of it, but once you’re in it and the truck is on, it’s on.

 

[Pops]

I’ve got out of the car locked and waited 30 mins and come back to it and it’s still going. It turns off when you lock it and out of it, but once you’re in it and the truck is on, it’s on.

Are you going to EVER look at your apple watch again while driving? No! See it works as intended.

Try turning off the vehicle in the menu, and coming back later. (Touch Controls > Safety > Power Off)

 

[Gaximus]

Strange I never got that, it just says "Vision attention disable" then I have to go back to tugging on the wheel. I think this is stupid, because if someone looks at the phone, they don't get an alert, it just defaults back to a method that allows you to watch your phone, but keeping tension on the sterring wheel.

 

[bwilliam79]

I had this same thing happen last night. I had FSD set to drive us to CVS and when it reached the destination in the parking lot, the "Take over immediately" warning started blaring and would not stop. I went ahead and parked the truck, thinking it would go away if we got out and ran our errand, but when we got back into the truck it started up again. I then did did a two finger salute reboot, but that did stop it either. After I backed out of the parking spot we were in, I attempted to reenable FSD and that finally made it go away.

I don't know if I could trigger that behavior again if I tried, but it was REALLY annoying. Aside from that, though, FSD on the CT has been pretty awesome so far.

 

[CTofLosGatos]

BTW several of us are facing the similar issue of non-stop alarms (for ~30mins) based on alerts. I think it is a S/W bug that needs to be fixed.

 

[CBMW6674]

I had this same thing happen last night. I had FSD set to drive us to CVS and when it reached the destination in the parking lot, the "Take over immediately" warning started blaring and would not stop. I went ahead and parked the truck, thinking it would go away if we got out and ran our errand, but when we got back into the truck it started up again. I then did did a two finger salute reboot, but that did stop it either. After I backed out of the parking spot we were in, I attempted to reenable FSD and that finally made it go away.

I don't know if I could trigger that behavior again if I tried, but it was REALLY annoying. Aside from that, though, FSD on the CT has been pretty awesome so far.

That worked. Thanks so much for your help.

 

[cofree]

Just drove from TN to CO yesterday/today.

In the middle of KS last night the FSD system froze and gave us the take over immediately alert and was blaring nonstop even though we had control.
After I think the third reboot of the system it stopped making the noise... but kept showing the take over immediately image.
We then tried everything to get rid of the take over immediately image... a few more reboots, into and out of FSD a few times, parked the car, charged it, turned the car off for a few minutes,
nothing helped. While parked it wouldn't even let me get back into TACC as I had to cancel autosteer first!

Then today I was driving with FSD and saw a broom in the road I swerved (i.e. a disengagement by steering wheel instead of hitting the button) and it finally went away... about 400 miles after the issue started.

 

[Oscar]

BTW several of us are facing the similar issue of non-stop alarms (for ~30mins) based on alerts. I think it is a S/W bug that needs to be fixed.

Yes, I strongly believe it is a software bug. It happened twice to me on Wednesday. I rebooted it twice (hold the two scroll balls simultaneously for a while until the screen becomes blank). The alarm gone, but the warning sign still on. Ridiculously, the FSD still worked. After driving for about 10 minutes, the warning sign gone as well.

 

[AIE]

Just drove from TN to CO yesterday/today.

In the middle of KS last night the FSD system froze and gave us the take over immediately alert and was blaring nonstop even though we had control.
After I think the third reboot of the system it stopped making the noise... but kept showing the take over immediately image.
We then tried everything to get rid of the take over immediately image... a few more reboots, into and out of FSD a few times, parked the car, charged it, turned the car off for a few minutes,
nothing helped. While parked it wouldn't even let me get back into TACC as I had to cancel autosteer first!

Then today I was driving with FSD and saw a broom in the road I swerved (i.e. a disengagement by steering wheel instead of hitting the button) and it finally went away... about 400 miles after the issue started.

Listen, same thing happened here but I was fortunate.

Just drove from TN to CO yesterday/today.

In the middle of KS last night the FSD system froze and gave us the take over immediately alert and was blaring nonstop even though we had control.
After I think the third reboot of the system it stopped making the noise... but kept showing the take over immediately image.
We then tried everything to get rid of the take over immediately image... a few more reboots, into and out of FSD a few times, parked the car, charged it, turned the car off for a few minutes,
nothing helped. While parked it wouldn't even let me get back into TACC as I had to cancel autosteer first!

Then today I was driving with FSD and saw a broom in the road I swerved (i.e. a disengagement by steering wheel instead of hitting the button) and it finally went away... about 400 miles after the issue started.

Hey, the same thing happened to me. Let me preface this by saying I had FSD engaged from phoenix to Anaheim, CA the entire time and it worked amazingly well! Less than a handful of interventions.
The following day I engaged FSD once again from Disney down to Irvine spectrum and once we got to the parking lot I wanted to see what would happen if I just left autopilot once the navigation ended. In the parking lot is where this happened to me. I was really freaked out because I needed to drive back to Phoenix the next morning. The alarm was stuck on, the screen looked just like the screen in these photos. I called tesla support and we power cycled and we reset the display. To reset the display go to display and change the language to Español and then change the language back to English. Although this didn't fix my problem it's nice to know about.

After departing Irvine spectrum we were en route to Carlsbad (screen still stuck). This is when I was thinking of ways to fix the issue and noticed that it blind spot sensors were also affected. I thought we'll hell let's see what happens if I try to engage autopilot again while it's fd up. And BOOM! It successfully engaged! I was shocked! A few moments later the screen went back to normal and all the sensors were back online! It was not immediate.

Give it a shot...

 

[REM]

this is a kernel level bug. Have you attempted to perform a shutdown rather than just a MCU reboot?

Sponsored