I have setup the Tesla binding, and it’s working - mostly.
I have found that after a few hours there is a lot of this in the events.log:
2017-05-01 11:06:34.835 [hingStatusInfoChangedEvent] - 'tesla:models:1' changed from ONLINE to OFFLINE 2017-05-01 11:06:50.089 [hingStatusInfoChangedEvent] - 'tesla:models:1' changed from OFFLINE to ONLINE
A in the openhab.log:
2017-05-01 11:06:34.833 [ERROR] [b.binding.tesla.handler.TeslaHandler] - Event Stream : An exception occurred while establishing the event stream for the vehicle: 'java.net.SocketTimeoutException: Read timed out' 2017-05-01 11:06:34.834 [WARN ] [b.binding.tesla.handler.TeslaHandler] - Event Stream : Resetting the vehicle connection because of a failing event stream
I have plenty of bandwidth and there are no congestion issues on my link generally. My suspicion is something at api.tesla.com is getting upset with the number and frequency of requests (when things are working, there appear to be a lot of requests - ie: several per second, even when parked). This has been an issue for some time and I have only just got around to looking at it closely. (My goal is to start/stop the car charging based on power usage in the house and the output of my solar system I’m about to get installed.)
I’m on the release version of OH2, on a Debian system (there was not any beta version - I think - and not game to try the snapshots)
I’m not a programmer, but know my way around a Linux system and good with networking, so happy to provide any data you may need to help debug.
The solution may also be to have some sort of config option for the max requests per second (I see there is a throttler class in the code, but not across Java enough to figure out how it works from my quick look).