Tessie API integration (Tesla control via Tessie)

Feature requests
1

Tessie API Integration (Tesla control via Tessie)

Hello everyone!

I propose integrating Tessie into Gladys Assistant. Tessie offers a very convenient and intuitive API to control and monitor your Tesla. The app is known for its ease of use, clear documentation, and rich feature set. It’s also a solution I already own, and I know other community members may have purchased the standard or premium subscription (which also provides access to real-time telemetry via WebSocket).

Goal

Enable:

  • Control of main functions (opening, closing, charging, pre-conditioning/starting…) via Tessie from Gladys
  • Reporting of vehicle information (battery, lock status, location…) to the Gladys dashboard
  • Automation of actions in Gladys based on vehicle state, retrieval of telemetry (via WebSocket for users with the appropriate subscription)

Why Tessie?

  • Ease of use: clear documentation, simple Auth API (token generation from the app)
  • Very complete API: almost all native Tesla functions usable via Tessie
  • Real-time telemetry available via WebSocket for premium subscribers
  • The mobile app and web portal are well made and the Tessie user community is active

Technical inspirations

To structure the future plugin, we could draw inspiration from the work already underway for the Tesla Fleet API integration (see this thread) for central command management and data usage, but:

  • Authentication via a simple token generated in the Tessie app, no OAuth2 currently
  • All Tessie API routes will be accessible according to their documentation, as needed for development

Useful links

Thanks in advance to the community! If some of you already use Tessie with Gladys (or via NodeRed/other), your feedback on concrete use cases or integration ideas is greatly appreciated.

Note: AI-boosted feature request!!

2

Progress status :

image
image799×1350 69.1 KB
image
image801×568 23.4 KB

image
image798×700 29.2 KB
image
image795×781 30.9 KB

Data update processing in progress!

PR : [WIP] Tessie-integration by Terdious · Pull Request #2339 · GladysAssistant/Gladys · GitHub

2 Likes
3

image
image591×752 59 KB

2 Likes
4

@pierre-gilles,

Could you, in addition to a route for the Tesla Fleet API, generate a Gladys Plus route for Tessie’s websocket for me? That would allow me to think about a more relevant logic because I’m implementing dynamic polling in Tessie.
Indeed, based on the Tessie app as well as Teslamate to get the info. When driving or charging, we make requests more often than when the vehicle is stopped (60s when stopped vs 5s driving vs 10s charging).

I’d like to see how live telemetry behaves in these scenarios to see if there are needs for additional polling (even though I would only add it in v2).

I don’t remember exactly what you need anymore, maybe nothing ^^ I’m sending you what I have ^^

image
image791×788 38 KB

image
image914×949 88.3 KB

5

If Tessie has WebSockets, you don’t need to go through Gladys Plus, you can do it directly locally because WebSockets are bidirectional ;)\n\nGladys Plus works with WebSockets!

1 Like