2019 3D+ ambient temperature reading 102F while it's 30F outside

Anyone observe odd ambient temperature readings on 2020.48.12.1?

Yesterday, 30F outside and cloudy, I noticed my 2019 Model 3D+ displaying an ambient temperature reading of 102F: imgur.com

After some time parked with climate running, it climbed to 103F, then went down to 90F. A reboot and power off did not change the reading, so I let the car sleep.

After sleeping for a few hours (still ca. 30F outside), the car showed a much more realistic reading of 42F. However, shortly after I got in, the temperature started climbing, a degree every couple of seconds. After 5 minutes, the car was showing an ambient temperature reading of 85F. I went for a drive at highway speed and it gradually dropped to 38F and then fluctuated between 38 and 40F for the next hour. Will take it for another drive today and see if it recurs.

I realize this is possibly a hardware problem and not necessarily related to the update. However, since my nearest SC is a couple hours away and mobile service doesn't appear as an option for any appointment category at the moment, I wanted to see if this may be affecting other cars. Cursory research pulled up some threads about a blank reading due to rodent damage to the front wiring harness, but nothing on severely inflated readings. The ambient temperature sensor attached to the active grille assembly looks clear of salt and debris, the front wiring harness is plugged in and doesn’t have any signs of damage. The only notable event yesterday was the update to .12.1.

Based on how fast the temperature readings climb when the car is first awoken and climate is enabled and then stabilize, it kinda feels like it’s displaying readings from a different temperature sensor that’s somewhere in the HVAC loop.

Hope this is not what Elon meant by the holiday update being :fire: :fire:

 

That was my first guess too, but there are a few arguments against it:
- There is an actual reading. In cases I've read about where there was damage to the front wiring harness, the reading was displayed as "---"
- As ambient temperature fluctuates, the reading also fluctuates. For example, it was 30F yesterday, and when I woke the car up, it showed 32F. It's 50F today, I just went out and woke the car up, and it is showing 55F. So the sensor is at least functioning, the temperature build up starts after a few minutes.
- No traces of damage on the wiring, no rodent feces on any visible surfaces, etc.

 

Welp, looks like the wrong temperature reading is affecting cabin HVAC - my car is running A/C and blowing freezing air out of the vents while it is 30F outside. Based on the lack of reports on TMC or Reddit, I am guessing a hardware issue with the sensor or the wiring harness is at fault here. I went ahead and scheduled the earliest available appointment for January 19th.

 

Thanks, this is very helpful - the description fits. This is why I did ask for a firmware redeploy in the appointment request. Hopefully someone reads it soon and pushes out the current firmware to me. I do some QA as a part of my job so I trust my hunch when it comes to thinking this is software-related. The sensor functioning is too normal to be a hardware failure.

Edit: no sooner than I posted this, I got an update notification. Reinstalling now, will see if this helps.

 

I *think* redeploying the firmware fixed this. I just went for a 10 minute drive and the ambient temp only climbed by 1 degree. I'll be able to do a better test later today, but - hopefully - this was it. Thanks again, @bbell - I owe you one.

 

Unfortunately, the problem recurred last night. After the car fell asleep, I got in and watched the ambient temperature reading immediately start climbing again, all the way to a balmy 96 degrees after some 3 minutes. It is, of course, not anywhere near 96F in New HYampshire right now. The odd thing was that I then drove to a grocery store 5 minutes away, spent some 30 minutes there with the car parked and awake (sentry running), and when I got back in, the temp was reading 32F and did not climb for the rest of the drive, some 40 minutes.

So, my theory as of last night was that this is somehow related to the car sleeping and leaving the car awake and parked led to a calibration routine running. I say "was", because when I walked out to the car this morning and got it, the reading did not climb at all. So in addition to everything else, the issue is intermittent.

At this point, I am keeping my appointment to rule out an intermittent hardware fault, but I still feel like this is a software (or, possibly, software/hardware) issue caused by an interaction of several conditions that I have not yet narrowed down. While I wait, I will continue observation.

Oh, and here's the issue in action, albeit at the lower end of the temperature range: imgur.com
It was 26F outside when this was taken.

 

Just an update that I’ve since had a few instances of blank readings, the issue comes back on and off. Mobile is coming at the end of the month, no estimate yet so don’t know what their plan is.