green1
Active Member
Thanks for the explanation. Makes a lot more sense now. Still a bit odd that there was one error on the drive one way, and a few hours later a different (but possibly related) error for the drive home.Actually, that's what I was suggesting. The "too many streaming requests" means that TeslaMS made a request to Tesla's servers, and the long poll returned too quickly. When you make the request to the streaming server, it's supposed to be a long poll for ~2 minutes. When the request returns, TeslaMS starts a new one. If the streaming server returns too quickly on a repeated basis, TeslaMS stops sending requests so that it isn't pounding Tesla's servers.
It could be that the car wasn't connected to Tesla's servers and is unavailable - I've seen that happen; it could also be because of some type of outage on Tesla's servers. Either way, there wasn't a connection there.
I don't think it's anything to worry about. I have the occasional holes in my data too.
I'm also still debating the sleep mode, as I drive the car relatively infrequently (I don't commute), I really like the idea of saving anything I can on the vampire draw (which can easily use more power per week than actual driving!!) but at the same time, I really like my data, and missing some while I wait for the car is annoying. I'm also not certain how much I'm actually "saving" in sleep mode, seems to me that I lose about 10-12km/24 hours with sleep mode on, running a constant 75-90w draw is an awful lot for a powered down device!