Is it possible this is something to do with the API issue some people had last week with 3rd party apps - ie could the app developers have changed something in their software that may be causing this?
As I don 't use those 3rd party apps, am on 36.10 & iOS14 & don't have any problem with the car waking maybe there is a link?
I, too, had wondered if there was a link between this problem and Tesla shutting down access from cloud service providers.
What we know for sure is that Tesla blocked access to the cloud services that were being used by TeslaFi and a few other unofficial apps. We also know that they didn't block access from individuals using software like Teslamate, which they could have done very easily, as every Teslamate connection advertises itself, I believe, so Tesla could have chosen to block every stand alone (i.e. running on a RPi or similar) instance of Teslamate accessing their API had they wished to.
What we don't know is why Tesla decided to do this. Some have speculated that Tesla's services may have been seeing too much traffic, but given that it seems that TeslaFi, and, perhaps others, have switched servers and have been back up and running for a while this doesn't seem that likely. As with Teslamate, TeslaFi and others will advertise themselves to the Tesla servers, so Tesla could block them if it wished. Some have speculated that this was preparatory work prior to the rollout of 2FA. This seems more rumour than fact, as I don't think there's yet been confirmation of the future use of 2FA (although I'd expect Tesla to switch to is before long). Some have speculated that the blocking of cloud service providers was due to a DDoS attack, but if so, then it would have been a pretty amateur one to try and use cloud service providers.
It seems that Tesla software QA isn't exactly wonderful, as it's far from unusual to have software rolled out that is very quickly found to have major flaws. For example, a nav update was rolled out a few weeks ago, tens of thousands of cars downloaded GB of data, only for that update to be rolled back within 24 hours. Software testing is clearly limited, almost to the point of being apparently non-existent at times. For example, the failure within the charging control software that resulted in the car failing to wake up and charge when it received a state change on the Control Pilot, a non-compliance with IEC61851 that meant that several charge point manufacturers had to produce work arounds, using the unofficial API to wake the car.
There is a theme developing here, though, around waking the car and the unofficial use of the API both to overcome Tesla software failings and to get useful data for owners. Might just be coincidence, but it does seem slightly suspicious that waking the car up seems to be at the heart of some issues over the past couple of years.
