Actually it's good to see Tesla participation here. But this outage for me could not happen at a worse time for me. Spent an hour on hold with customer support to learn they didn't have a clue. You guys should talk to them. And put a status on your web site too - those are both easy, cheap, and painless. And would go a long way with your very frustrated customers right now.
Dan Kim here with Tesla. We’re aware the Tesla app is down for some customers and we’re working to restore functionality ASAP!
Thanks, Dan. It's good to know someone from Tesla monitors these forums and that the issue is being worked on.
Is there any particular reason the app has to connect back to Tesla's servers instead of connecting directly to the car with Bluetooth?
Security is one. If your phone gets stolen, Tesla can invalidate your API keys and passwords centrally from the server side, disabling any app access.
I'm pretty sure the Model 3 will unlock when the owner's phone is nearby, and the connection is through Bluetooth. If that's an acceptable level of security, then I don't see the problem with connecting directly from the app with the S and X.
This would suck...anyone know if app is down model 3 users who relies on it would not get into their car?
Glad it's not just me. I unfortunately tried uninstalling/reinstalling the app on my phone, so now I can't log-in.
Good thing the model 3 has a backup keycard.
I went to check the status of my Tesla via the smartphone App. I got a message that says "Check internet connection."
I'm on wi-fi, so that should be good. All other phone apps that access the internet via wi-fi are working fine.
I logged off the app and tried to log back on. Now I get
Check internet connection" and an OK button, after about 1/2 second. I restarted the phone and still have the problem.
Any ideas as to what's going on? Which internet connection? The phone's (which is fine), the car's, or what?
Bluetooth is short range. Unless you're within Bluetooth's range, you need a server side solution anyway. So you have to engineer this twice, implement it twice, add new features on it twice, test it twice for every change, for the low number of times that there's an actual outage. And you have to prioritize that against all of your other important work that needs resources.
Software development involves tradeoffs and you have to make calls about how much you're going to do. Had to make a lot of similar calls doing software engineering over 20 years.