Andyw2100
Well-Known Member
See my somewhat related post here. This happened to me just today. (Well, yesterday now.)
Did your Tesla iPhone App refuse to connect this morning? - Page 3
The symptoms and cure are identical.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
VisibleTesla
- Thread starter jpasqua
- Start date
-
- Tags
- Model S User Interface
See my somewhat related post here. This happened to me just today. (Well, yesterday now.)
Did your Tesla iPhone App refuse to connect this morning? - Page 3
The symptoms and cure are identical.
MikeBur
ManualPilot
i too have seen this previously, when we were originally giving Joe feedback and Joe mentioned that the traffic for VT was now reduced significantly. Perhaps TM is throttling upload, though not sure why as VT uploads less than running phone apps. I found this worst when running a vt and iPhone app simultaneously.
btw: remember that disclaimer on startup re. You may lose connectivity. ;-)
Last edited:
Andyw2100
Well-Known Member
From reading breser's post, and from reading others' posts elsewhere, it sounds like this has nothing whatsoever to do with throttling. If it were a throttling issue, a simple reboot would not resolve the issue. I think breser is exactly correct: as I understand it, and in layman's terms, there is some sort of intermittent bug that prevents the connection to the servers when connected through wifi. Based on reports in other threads, I'd say this has absolutely nothing to do with VT.
breser
AutoPilot Nostradamus
I'm pretty sure that Tesla is aware of this bug too. I sent them a bug report about this and detailed all the things I did to diagnose this and explained that ultimately it was resolved by the touch screen reboot. Tesla responded with a very canned response telling me to reboot the touch screen and a picture showing how to do it.
The important bit of there email is this sentence
Based on this and the behavior I saw I'm pretty sure that the problem is that the routing table was busted for the wifi network interface and so traffic was probably not being sent properly. I've seen this with computers from time to time. So it's not terribly surprising to me.
I'm positive this has nothing to do with throttling because VisibleTesla and the apps will immediately start working if you disable the wifi. And then immediately stop working when you enable it again. On top of that I've observed that no traffic to/from Tesla was actually occurring in this state. If there was throttling I'd expect the car to still be able to connect to Tesla and communicate with them. They have complete control over what the car does and I don't see any reason for them to mess with that behavior. But the car was unable to talk to Tesla. If nothing else this same issue presents a problem for Tesla in being able to reach the car for their own diagnostic reasons.
If you're curious about how the network communications work and want some details then keep reading...
For the most part all communications with the car have to be initiated by the car. The reason for this is that the car may be behind a network that has a NAT or firewall that prevents connections from being made to it. This is a pretty standard behavior these days for a network to disallow connections that aren't specifically configured to be allowed to go to various devices. But outbound connections are typically not limited.
So whenever the car is on and running it connects to Tesla and has a VPN to them. Over this VPN then Tesla can initiate connections to the car. Basically the inbound communications are tunneled over an originally outbound communication channel. If the car can't open that communication channel then Tesla can't reach the car.
I'm not entirely clear how the car is woken when it's asleep. I haven't looked into how that works too much but my guess would be every so often the car wakes up, connects into Tesla and sends a message basically asking "Should I wake up?" Tesla then says yes and then the car wakes up and brings up the VPN to allow the app and everything works from there.
- - - Updated - - -
Another bit of proof it's not related to VisibleTesla. Everything was working fine last night with the Android App when I went to bed. Got up this morning and it's back to doing it again. Realized that VisibleTesla wasn't running since yesterday sometime because my desktop had crashed. I know it was crashed when I came home but I didn't think about it. So between me restarting the touch screen and it breaking again this morning, VisibleTesla wasn't being used at all. Restarting the touch screen resolved the problem again. Tesla has some sort of bug.
MikeBur
ManualPilot
Thanks. Sounds definitely more like this. I stand corrected, looks like it's NOT throttling per se.
how are you doing your network analysis Breser?
breser
AutoPilot Nostradamus
Honestly not sure why you'd want to do that. I'd assume that if you extracted the APK you could get Tesla's Android App running on a Kindle Fire (don't think it has access to Google's Play Store). Sure there's some functionality that VisibleTesla has but I'm assuming you mostly want it on a Fire for remote controls.
- - - Updated - - -
My firewall is a Linux box. So I'm just running tcpdump on it and filtering based on IP. I haven't done too much digging into the traffic to/from Tesla but from what I understood it's just an encrypted VPN so not much point in bothering.
MikeBur
ManualPilot
Thanks, was thinking of putting dd-wrt on my linksys router, though unsure of additional value for this.
Your comment on VPN is interesting. Anyone know what flavor / key type is being used?
breser
AutoPilot Nostradamus
From what other people have said in the past I believe it's OpenVPN that they're using. But I haven't personally poked at the VPN network traffic to figure out what it is. I'm not overly interested in poking at it as long as it works.
MikeBur
ManualPilot
Thanks. I'm less interested in any kind of reverse-engineering, more that I'd like to know which modules are updated. This will give significant hints at which systems are being modified. I'd much prefer a change list, though that appears to be a pipe dream...
Andyw2100
Well-Known Member
What version of VT are you trying to use? Are you aware of the issue with the server change, etc.? Read back a few posts--probably just a page or two--for someone with a similar question that I answered with references to the posts that gave the details you may need as well.
Edit: Here are the links for you, from my other post. (Was in a rush earlier, and didn't have time to look for the post.):
Last edited:
breser
AutoPilot Nostradamus
Well I don't think the app is really built to run on Android. I'm guessing you either don't have or don't want to use a PC (Windows, Mac or Linux) at home to run VisibleTesla?
Andyw2100
Well-Known Member
Scroll back a few pages and read some posts about issues involving the mobile app that have nothing to do with VT. breser wound up determining with a pretty high level of confidence. There are also some other threads about the mobile app issues.
JOH
Member
I downloaded VT onto a MAC and it seems to be mostly working for me. The only thing I notice is that it's not capturing any Trip Data. It is catering data for graphing, energy usage, speed, etc. Would the missing trip data be related to the new server issue previously noted?
The old version stopped working a few months ago. I launched it to see if it worked before I downloaded the latest version and it seems to be working again. Guess I'll stick with the old version for now. Great to have it back.
Similar threads
