Rear middle seat unbuckled warning when folded down

[allen514]

When the rear seat backs are folded down (or just the larger section), I got this rear middle seat unbuckled warning, is this normal or just another Tesla glitch?

 

[frankvb]

Getting this as well, tap the icon to stop the warning (temporarily) by marking it as a child seat. It's a Tesla glitch indeed... Seems the sensor is way too sensitive.

 

[bbmertz]

Yes, lots of MY owners are experiencing this issue, myself included. Tesla is aware of it but does not yet have a fix, aside from the advice above. Here is one of many threads on this topic: Rear passenger unbuckled alert with seats folded down

 

[allen514]

Thank you all for the reply, glad I'm not the only one with this problem and a fix may include in the future software update.

 

[Snow Drift]

Same here, but I think it's only based on weight.

We hauled a piece of furniture and it set off the sensor. Then this weekend we hauled large decoration boxes (but lighter than furniture) and it didn't go off at all.

 

[GeezerSquid]

I keep the seats folded so my dog can get back there. I simply buckled the seat belt before folding.

 

[mark95476]

I recall having this error and clearing it by marking it as a child seat. I got the 2020.40.3 software and was driving around with my rear seats folded down, but I didn't see this error so it might have been resolved.

Thank you all for the reply, glad I'm not the only one with this problem and a fix may include in the future software update.

 

[Srad600Volt]

Having a similar issue after the latest software update. With child seats in the back (latch anchors, so they don't use seatbelts) my daughters seat keeps blinking the unbuckled warning on/off every few seconds. Mildly annoying...how does one "mark" the seats as child seats? Thx.

 

[allen514]

I recall having this error and clearing it by marking it as a child seat. I got the 2020.40.3 software and was driving around with my rear seats folded down, but I didn't see this error so it might have been resolved.

I tried it this morning too, no more warning after the 2020.40.3 update