Skip to content

Releases: timdorr/tesla-api

v3.1.0

30 Jan 17:40
e17a447
Compare
Choose a tag to compare

This release handles the new auth process (see #260). It does not yet handle MFA users.

When upgrading, any previously stored refresh_tokens will no longer function, as they are being generated by a new system. While existing Owner API access_tokens will continue to work until they expire, a full login will be needed to obtain new refresh_tokens.

Changes

  • Update for new authentication process

v3.0.7

12 Nov 15:25
0762cd3
Compare
Choose a tag to compare

This release is sponsored by RedAlert, a smart alerting platform for Tesla vehicles.


Changes

v3.0.6

17 Sep 20:41
4b79d3a
Compare
Choose a tag to compare

This release is sponsored by RedAlert, a smart alerting platform for Tesla vehicles.


Changes

  • Set stream protocol to HTTP 1.1 (#219 by @cyu)

v3.0.5

17 Sep 20:41
0725ccd
Compare
Choose a tag to compare

This release is sponsored by RedAlert, a smart alerting platform for Tesla vehicles.


Changes

v3.0.4

14 Oct 15:55
dfd3bba
Compare
Choose a tag to compare

This release is sponsored by RedAlert, a smart alerting platform for Tesla vehicles.


Changes

  • Fix a bug with streaming telematics.

v3.0.3

11 Oct 16:31
ce97d55
Compare
Choose a tag to compare

Changes

  • Handle streaming errors and timeouts.
  • Drop faye and eventmachine deps in favor of async.

v3.0.2

04 Oct 18:53
e1f025d
Compare
Choose a tag to compare

Changes

  • Add new methods for the V10 update:
    • set_preconditioning_max
    • window_control
    • share (just aliased to navigation_request currently)
    • trigger_homelink
  • Add new methods for media playback controls.
  • Added vehicle_config as a separate method from data.

v3.0.1

26 Sep 19:26
dda4fd7
Compare
Choose a tag to compare

Changes

  • A small fix to the new .vehicle(id) method.

v3.0.0

25 Sep 23:06
26da58a
Compare
Choose a tag to compare

This release is sponsored by RedAlert, a smart alerting platform for Tesla vehicles.


Sorry for the quick major bump again, but this is warranted. The internal HTTP client I was using (HTTParty) was entirely thread-unsafe, so things like Sidekiq jobs or other multi-user systems would be impossible to implement safely.

As a bonus, I've updated the streaming API to use the new WebSocket endpoint. The old HTTP streaming endpoint is completely defunct now.

Changes

  • Replace HTTParty with Faraday. This ensures instances stay separate from each other.
  • Update Vehicle.stream to use the WebSocket endpoint.
  • Add a Client.vehicle(id) endpoint for getting a single vehicle from the API.

v2.0.0

23 Sep 17:47
5b9928e
Compare
Choose a tag to compare

Changes

  • Revamped TeslaApi::Client
    • .new now uses keyword arguments: email:, access_token:, access_token_expires_at:, refresh_token:, client_id:, and client_secret:. Note: access_token_expires_at should be a DateTime.
    • Methods .token=, .expires_in=, .created_at= have been removed. You can set these when creating the client.
    • Added a refresh_access_token method to obtain a new access token using a refresh token. Note: Tesla invalidates the previous refresh token when obtaining the new access token.