Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Cabin Overheat Protection A/C not working for 2 months

This site may earn commission on affiliate links.
I have observed that for the last two months my cabin overheat protection is not working properly in A/C mode. Frequently I walk up to the vehicle it is hot and the fan is not running. When I open the app to check it is 125-137 F, sometimes opening the app is enough to get the overheat system to turn on and cool down to 105 F.

I have observed this with the following software versions:
2020.16.2.1
2020.12.11.11
2020.12.5

Is anyone else seeing this bug? I reported it using "bug report" but there is no way to know if Tesla knows or will fix it.
 
  • Like
Reactions: fiatlux
One "feature" of the COP that somewhat annoys me is the 12 hour limit. So if I park my car at 6pm, by the next morning it has stopped, so I have to manually precool the car if I don't want to enter a super toasty car the next morning. I would prefer an 18 hour limit.

I understand the reasoning to turn it off automatically, since leaving the car for days would add quite a bit of battery drain, although perhaps an option for unlimited would be nice for those that know what they are doing.
 
Mine is working fine. I did notice that when my last update happened the AC protection setting was changed to “OFF” and I had to turn it back on, but other than that it has been working. I usually listen as I approach my parked car to see that I can hear it running.
 
One "feature" of the COP that somewhat annoys me is the 12 hour limit. So if I park my car at 6pm, by the next morning it has stopped, so I have to manually precool the car if I don't want to enter a super toasty car the next morning. I would prefer an 18 hour limit.

I understand the reasoning to turn it off automatically, since leaving the car for days would add quite a bit of battery drain, although perhaps an option for unlimited would be nice for those that know what they are doing.

They need to change the 12hour timer from the next 12 hours to the next 12 hours of actual use. Easy fix for them, and the way it should have been from the start. Must be chaos in their software groups.