You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
I have “serious” UniFi WiFi and there is no question that the M3 completely disconnects from WiFi when asleep. It is also possible, however, that in the complete absence of mobile signal the car decides to keep the WiFi connected instead (which would explain @Glan gluaisne scenario). However, it doesn’t explain how it could be limited to the U.K. only, whereas an SMS issue would.
I still tend to believe it is SMS or nothing, and that @Glan gluaisne car is secretly able to receive these messages in spite of living at the bottom of a very deep well, I mean valley.
Thanks, that is very helpful.Greetings for Spain.
I want you to know that we are suffering this same problem here. It affects many cars with MCU2, mine included (M3 LR AWD).
Also, I have *exactly* the same symptoms you described since last Wednesday. On late Friday, 2020.36.11 was aggresively pushed to many cars here, including mine. Once the installation finished, my car stayed awake during more than one hour, which is definitely an anomalous behaviour. Since then, the phantom drain has been increased. I think that this happens because my car awakes (by itself) more frequently, and stays awake longer. I have no third party parts, TeslaFi, etc. accessing my car.
and that @Glan gluaisne car is secretly able to receive these messages in spite of living at the bottom of a very deep well, I mean valley.
yes it is for sure, connection may be
WiFi LTE BT radios all powered off in deep sleep. Only remaining radio is gsm. Sms is anywhere from 140-250 bytes, nothing, even for an old network. They’re getting through.
I looked at the router's low-level logs and I can see the DHCP request coming in when the car wakes, so I'll pretty sure it's not connected when it's sleeping.Whether or not the car appears on the list of connected clients on the router seems to be random, from what I've seen. 90% of the time our router doesn't report the car as a connected client, but neither does it report our Roberts internet radio as connected either (in fact it never seems to report that as being connected). I've sat looking at the router "connected clients" page, trying to work out what's connected, and often things that are on all the time (like the RPi running Teslamate, or my Android tablet) don't show on the list. I've never worked out why this is, but it's an annoying feature when setting up something like a new RPi, and not being able to easily see what IP address it's acquired via DHCP. Angry IP scanner seems to work a little better than our Asus router at finding connected devices, but even that sometimes takes several scans to find some devices. It's one reason that all the stuff I've made that connects to the network, plus our network printer and my NAS, are configured with fixed IP addresses. At least that way I can quickly SSH into the things I need to access without messing about trying to find out if their IP has changed since last time.
Yes it will work because it uses Bluetooth to wake the car but it will only work within Bluetooth range.My work around to wake the car up without going out to it is to use the Phone app to unlock and then lock the car. This seems to work even when the app is in its endless waking up state. Within a few seconds of doing this the app connects with the car as normal.
Could an sms be sent as a belt and braces in case there is no data connection as a backup which then prompts the car to connect WiFi if available. I agree it is unlikely to be the primary method?Sorry, that's not true. The keys wouldn't work if Bluetooth was off, and GSM won't be a separate 'radio', it's all part of the same modem component. It seems highly unlikely that SMS is any part of this, and I see no evidence to suggest it is. No way your car would wake in a few seconds in the app if that relying on a SMS message.
Lots of places don't have mobile coverage, as pointed out by Glan SMS specifically doesn't work where he lives yet the car wakes up.
The car simply maintains a data connection, like your phone does. Perhaps it drops wifi if there is a decent signal.
Could an sms be sent as a belt and braces in case there is no data connection as a backup which then prompts the car to connect WiFi if available. I agree it is unlikely to be the primary method?
yes it is for sure, connection may be
WiFi LTE BT radios all powered off in deep sleep. Only remaining radio is gsm. Sms is anywhere from 140-250 bytes, nothing, even for an old network. They’re getting through.
Perhaps not directly related to your problem.... but I've recently had my Tesla app fail to connect to the car, consistently. What had changed in my situation was I recently installed a VPN on my phone (that is hosted by MS servers) and apparently Tesla recently has decided to not allow connections from certain servers, including MS.
Turned off my VPN and voila remote connection from the app works again.
The problem we have here though is not that we can't connect to the Tesla mothership - that works fine. The problem is between the mothership and the car.Perhaps not directly related to your problem.... but I've recently had my Tesla app fail to connect to the car, consistently. What had changed in my situation was I recently installed a VPN on my phone (that is hosted by MS servers) and apparently Tesla recently has decided to not allow connections from certain servers, including MS.
Turned off my VPN and voila remote connection from the app works again.
This is the log I get from Teslafi when I try to do something with the car that requires a wake-up:Tesla blocked access from several cloud services a week or so ago, so it may be they also blocked any VPNs using the same services?
Seems possible, given all the hassle that users of TeslaFi and other similar apps had when this happened.
This is the log I get from Teslafi when I try to do something with the car that requires a wake-up:
View attachment 590314
So, there's no issue with TeslaFi talking to the Tesla server - it's that the car isn't responding to the wake-up request that the Tesla servers indicate was successfully received.
That works if, but only if, your phone is within bluetooth range of your car.I've done this a couple of times to work-around it, seems to work:
- go to app front screen
- hit unlock
- the car wakes up
- hit lock (assuming you wanted to wake it rather than to unlock)