Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streaming API #137

Open
jkropp opened this issue Mar 12, 2019 · 7 comments
Open

Streaming API #137

jkropp opened this issue Mar 12, 2019 · 7 comments

Comments

@jkropp
Copy link

jkropp commented Mar 12, 2019

Streaming API not working, html bad request error.

@bendinwire
Copy link

Seeing the same thing.

@TheSpaceCowboy
Copy link

I'm not sure if this is what you are getting, but this began about 6 days ago or so. The 502 contines without end. Cut & paste from streaming startup:
timestamp: 1552955768856 }
18 Mar 20:37:07 - getting charge state Aux data
18 Mar 20:37:07 - getting climate state Aux data
18 Mar 20:38:07 - getting charge state Aux data
18 Mar 20:38:07 - getting climate state Aux data
18 Mar 20:38:13 - Polling again because poll returned HTTP error:Error: ESOCKETTIMEDOUT
18 Mar 20:38:23 - Bad timestamp ()
18 Mar 20:38:23 - Unexpected problem with request:
Response status code = 502 Error code = null
Polling again in 10 seconds...

@wumpus
Copy link

wumpus commented Mar 19, 2019

There's probably an error message in the thing that starts with "<html>\n" ... which, btw, is visible in the github email and not above because you didn't quote the <html>

@TheSpaceCowboy
Copy link

True, there was an html in the bad timestamp message, but it disappeared in the cut and paste. The error message was the 502 error.

@wumpus
Copy link

wumpus commented Mar 20, 2019

Well, if the error message wasn't informative, then perhaps it's worth watching with the Tesla app at the same time you're making this call. If the app continues working, then perhaps you've triggered some kind of defense, or, the Tesla app isn't using that interface the same way these days.

@MichaelSinz
Copy link

I had this start on March 7th. I have not yet discovered the real cause but I have been streaming my telemetry for well over a year (including needing updates a few times) but this time I can't seem to find the problem. I still can control the car (including turning on the climate system in the morning)

@MichaelSinz
Copy link

PS - the error returned is:

<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants