All,
Sometime in the last several months I started noticing that my app was having trouble connecting to Sansa, my Model 3. Its basically never an issue when I'm away from home, but its almost impossible for me to get the app to connect to the car when I'm on my wifi. It also seems like the app has a hard time connecting to the car when the car is on wifi as well.
Adding to those issues, I'm on my second software download in a row where the download is stuck at 50-51%. The first time it happened I tried pretty much all of the troubleshooting steps below before creating a service request with Tesla. They ended up clearing the download cache on the car and a day or so later it received and successfully downloaded the update. However, today I'm in the same boat, the car downloaded to 50% and has stayed there for over 24 hours, despite being on wifi.
I get the impression that there is something funky going on with my wifi network, as it seems to be the constant in the issues I'm having. Here are the following toubleshooting steps I've taken:
car:
-disconnect and reconnect to wifi (including forgetting the network and readding)
-Moving the car closer to try and get a better signal
-did a soft reset by holding both steering wheel buttons until the computer rebooted
-Powered off the vehicle, waiting a couple minutes before pressing the brake to turn the vehicle back on
-connected the car to my hotspot's wifi network (after the download was already stuck - no improvement)
home network:
-Rebooted the router
-Bought a wifi extender and placed it pretty close to the driveway (increased average signal from 1 bar to 2 bars)
-Reset the wifi extender
-Disabled DNS filtering on the PiHole (see below)
Here's where the plot thickens. Being an IT guy, like many IT guys, I decided to make my network a bit more complicated. I installed a PiHole DNS filter which I've configured to act as my DHCP server as well as send all DNS traffic through cloudflare (1.1.1.1, 1.0.0.1). I've done a couple of security changes as well, like using DNSSEC. I'm not actually positive that this is the culprit, as I've checked the logs, and I see no blocking of any tesla related DNS request, nor do I see any blocked traffic when I look at all of the requests coming from the car of the DNS logs.
Saying all that, I will admit that I haven't tried removing the PiHole from the network all together, but as I noted, I did disable the DNS filtering, which made no difference. I suspect it is possible that DNSSEC is causing an issue, but the logs show no problems. I will also point out that I don't think the range extender as actually required. I had previously downloaded updates on my network before with just the router, but I find my phone sometimes loses wifi in my driveway, so it was really more of shoring things up than finding actual issues with connection previously.
Geez, I'm long winded. I have a couple of troubleshooting steps I need to try (mainly, try removing the PiHole from the DNS loop altogether) to see if my DNS server is causing the issue. However, I wanted to ask you guys if you've had any similar experiences and know of some other possible solutions. Also, I just found @Seth2020 's The definitive guide to RESET on Tesla Model 3 so I'm looking through that to consider next steps as well.
Thanks!
Sometime in the last several months I started noticing that my app was having trouble connecting to Sansa, my Model 3. Its basically never an issue when I'm away from home, but its almost impossible for me to get the app to connect to the car when I'm on my wifi. It also seems like the app has a hard time connecting to the car when the car is on wifi as well.
Adding to those issues, I'm on my second software download in a row where the download is stuck at 50-51%. The first time it happened I tried pretty much all of the troubleshooting steps below before creating a service request with Tesla. They ended up clearing the download cache on the car and a day or so later it received and successfully downloaded the update. However, today I'm in the same boat, the car downloaded to 50% and has stayed there for over 24 hours, despite being on wifi.
I get the impression that there is something funky going on with my wifi network, as it seems to be the constant in the issues I'm having. Here are the following toubleshooting steps I've taken:
car:
-disconnect and reconnect to wifi (including forgetting the network and readding)
-Moving the car closer to try and get a better signal
-did a soft reset by holding both steering wheel buttons until the computer rebooted
-Powered off the vehicle, waiting a couple minutes before pressing the brake to turn the vehicle back on
-connected the car to my hotspot's wifi network (after the download was already stuck - no improvement)
home network:
-Rebooted the router
-Bought a wifi extender and placed it pretty close to the driveway (increased average signal from 1 bar to 2 bars)
-Reset the wifi extender
-Disabled DNS filtering on the PiHole (see below)
Here's where the plot thickens. Being an IT guy, like many IT guys, I decided to make my network a bit more complicated. I installed a PiHole DNS filter which I've configured to act as my DHCP server as well as send all DNS traffic through cloudflare (1.1.1.1, 1.0.0.1). I've done a couple of security changes as well, like using DNSSEC. I'm not actually positive that this is the culprit, as I've checked the logs, and I see no blocking of any tesla related DNS request, nor do I see any blocked traffic when I look at all of the requests coming from the car of the DNS logs.
Saying all that, I will admit that I haven't tried removing the PiHole from the network all together, but as I noted, I did disable the DNS filtering, which made no difference. I suspect it is possible that DNSSEC is causing an issue, but the logs show no problems. I will also point out that I don't think the range extender as actually required. I had previously downloaded updates on my network before with just the router, but I find my phone sometimes loses wifi in my driveway, so it was really more of shoring things up than finding actual issues with connection previously.
Geez, I'm long winded. I have a couple of troubleshooting steps I need to try (mainly, try removing the PiHole from the DNS loop altogether) to see if my DNS server is causing the issue. However, I wanted to ask you guys if you've had any similar experiences and know of some other possible solutions. Also, I just found @Seth2020 's The definitive guide to RESET on Tesla Model 3 so I'm looking through that to consider next steps as well.
Thanks!
Last edited:
