1.9.2 of the app, 2022.8.10.16 (MCU1) in the car.
Seem to have happened at the same time as the app was updated to 1.9.2
Hello.
i cant get this flow too work. I want my Phillips hue bulps to change color when my battery on my Tesla is under 40%. And stay red until I but the charger into my tesla then the bulps goes back to its original colour.
Same problem. Model S 2017 MCU2 v. 2023.26.12, App: 4.27.3-2081-cff349f576
Hi, I havenāt been able to get the location based flow cards to work. Tried out Is at Home, Is at location. But itās always false even though the car really is at these locations.
Is it possible somehow to check GPS coordinates, where the app thinks the car is at?
Tesla changed the API:
1 Like
Hi everyone 
A short update aboute the appā¦
- Tesla deprecated the old Owner-API. That means the current app will stop working from 2024.
- Tesla is using the Feet-API now.
- The Fleet-API will be adjusted to use only signed commands. Itās not sure how this can be implemented into the app without a proxy server between Homey and Tesla API. All commands are affected. Readonly access is still available via REST service.
Pre-2021 Model S/X are excluded from these changes.
So perhaps there are diffent API endpoint needed for different cars.
Thatās a challenge without a clear target.
Nevertheless I took over the app from @balmli (thanks for his work :-))
The first plan was to replace the current app with a new one. But itās not sure if this will be a good way. If there are different capabilities or flows, it can brak your flows. So a new app and a parallel usage could allow a migration of your flows.
Currently the oAuth process and reading of the car data is possible. Itās not sure if and how sending commands will work. So it can be that only a readonly access is possible (including wake up) for an indefinite period of time. Logging car data and location should be possible.
There will be a rate limit for API access:
| Subscription plan | Discovery Tier |
|---|---|
| Device data limits | 1 API request / car / 5 min And 1M API requests / day. |
| Commands limits | 50 API requests / car / day And 500k API requests / day. |
So letās see how Tesla will move forward.
Iāll give you an update if there are news about a new app.
The old app is no longer maintained.
2 Likes
Thanks @RonnyW and happy to help if I can. Iāve currently moved to using the app on Home Assistant and mapping the functions across using the HA community app. I expect they will have the same issues! Same for TeslaMate but thereās is just streaming data so might not be affected. Expect it had to happen at some point.
Beta tester are welcome
I would expect, that the old streaming API also stops work because itās authenticated with the token (generatey by 3th party apps).
The Fleet telemetry API needs an own server to stream data. Thatās only a use case for companies with their own environment and cloud hosting for apps (so perhaps something vor Evee or other apps cased on cloud storage. For TeslaMate you would need an owh developer account to register your server.
So far some technical details ā¦
The new app will be primary a solution for getting base car data (polled in intervals) and sending commands (not sure if and how it will work from 2024).
Other functionality from the old app will be dropped (charge plans, data streaming). So itās a way back to the roots.
@GRat: Is the Homey app not working at all or only parts like location?
I would like to take part, how?
1 Like
Do you know if the new api supports callbacks? Would be awesome if the api could make a http request to homey reporting its position when the shift changes to P.
No, itās only polling. The car doesnāt report such things automatically.
Iām experimenting with online and offline intervals to increase data readings if the car is online.
But it seems that Tesla has not activated the rate limits yet. The annoumced limit is 1 call every 5min. Thatās far from realtime 
1 Like
I think the app should be published in the store first.
For beta tests and parallel usage, this would be a new app (no over-install). Thatās the easiest way.
Iāll give you an update if itās ready.
1 Like
The rate limit looks to be activated for me now. Two days in a row with stopped charge plan, due to exceeding the rate limit.
Model X - 2019.
I get disconnects. I still run it and use for some tasks but, for example, unlocking the charger port I now use a specific button create through HA as itās more reliable.
On the changes by Tesla, just seen this: https://x.com/teslascope/status/1738083967545561377?s=46
So fingers crossed, that might be good news!
1 Like
I donāt use the current app and donāt have a X account, so I canāt check both
Did you get timeouts? Or a specific error message?
Hello everyone.
Current state on the API and app changesā¦
The Owner API seems still be working. But itās not sure how long. So if the app doesnāt work in 2024, please be patient and wait for the new app.
The new app is in work.
But Tesla also changes the FleetAPI that is used for the new app. Currently, commands are possible. But fo new cars and perhaps from 2024 this wonāt work anymore. A new way to send commands (encrypted and signed) is needed. Iām in contact with other developers using this API, but we all donāt know how to implement this in JavaScript. I hope we will find a solution soon.
Here is a short preview of the new app:
- The car device and āsubdevicesā for specific functionality:
- The car:
Edit: We have enough testers now.
I can invite upto 5 beta testers in the Homey Slack channel. If you can spare some time and want to test and help with reporting issues and feedback, you can answer here and post your Slack user. The first 5 posts win
I will create a new thread when the app is onlineā¦
This is the quote from Teslascope on X:
ā We have some reassuring news: Vehicle owners will be pleased to know that Tesla has acknowledged the importance of supporting small developers and self-hosted projects like Teslamate.
While everything is still underway internally, more information will be published in Q1 2024.ā
So hopefully that will help with any future development.
Iām also registered als āprivate projectā at Tesla. Thatās not the problem. If Tesla stops the unencrypted command endpoints, there is currently only one possible way to use a proxy server between. To use these endpoint in Homey, it needs an adaption from GoLang to JavaScript. And without a documentation how encryption is done and how the data structured, itās a long way with trial and error.
Perhaps business cases with their own servers and cloud infrastructure can implement it this way. But not as unpaid leisure developer
