Remove Streaming API as it is currently broken. #45
Conversation
|
The Tesla API is in a really sad state at the moment. Not sure why they're being so anti developer. Maybe better for a GitHub discussion rather than a PR comment, apologies. I think this change is fine but what happens when (if) it eventually works again? I don't know if we should remove code because the upstream isn't working correctly. |
|
If there's someone who wants to consume the streaming bits, they can revert the change that I note in the README, ensure it's working again, and we release that? |
|
Also presumably the streaming API does work - I'm fairly confident that teslamate is using it to record data. |
|
In my eyes the streaming api is pretty valueable - due to all the phantom drain problems when waking up the vehicle. Teslamate is using wss://streaming.vn.teslamotors.com/streaming/ for their streaming ...would like to contribute during work in progress but right now not long enough into golang to do it from scratch completely |
|
@mark-sch The proposal here is not to permanently remove this wrapper, but since it's broken in its current state we temporarily "hide" it by deleting it for now until someone who does use it has time to work on it and we can release a working version. |
|
How about just parking these files in an internal folder and hence making them inaccessible from the outside world? I intend to look into this, but no ETA. |
|
I'd prefer to leave this as is - moving to an internal folder would require modifying the deleted files so that tests keep passing. As it is to get this back to work on in we'll just have to |
|
Just in case it was missed above, an immediate follow up commit will write notes in the README in the root about the lack of the streaming API and pointing at the commit this PR creates. |
Fixes #44.