After I added the client id/secret I was asked to sign in. After that it failed with that message.
It’s possible it’s related to MFA because next time when I did it it asked for MFA code there instead.
Thanks for the hint. I think I found the bug. The oAuth instance is initialized at start of repair view - before the app credentials are set. That’s why it doesn’t work the first time, but the second time.
1 Like
Test version 2.0.1:
- device repair with new client_id should be fixed now.
6 Likes
Great work @RonnyW! My Model 3 and Model Y is now back in Homey.
Both came back online after “repair” on one of the cars.
Please keep an eye on your app usage with two cars assigned.
You can still adjust the data reading interval to keep below your limit.
Currently it seems that Tesla is not blocking the app completely when the limit is reached. They try to convince you to add a subscription. But take this as a chance to use a poll interval that fits into your 10$ limit.
And then it would be nice if you can share your experience for others to get a good balance for data readings and commands (like done for the rate limit last year).
2 Likes
Hi @RonnyW, thanks a lot for the update and the clear instructions!
I followed the instructions, repaired my existing device and my Model 3 came back in Homey.
Reading of the car’s data is working fine but the sending of a command results in the error message “Signed message error: MESSAGEFAULT_ERROR_INSUFFICIENT_PRIVILEGES”.
I did the registration of the Homey app in the car and this resulted in a new key being added (second one):
Any ideas what I did wrong?
Another question: what is your recommendation for setting the online and offline polling interval?
Not all commands are working yet.
You can keep both intervals at the same value. The app checks first is the car is online and only in this case, a data reading is done.
You have to try out your best aproach. The latest rate limit was daily. Now the limit is monthly. So perhaps a short interval is possible now if the usage levels out over the days if there are days with less usage.
I would start with 2min and check after some days in developer account if it’s ok.
OK, thanks. I assumed that all commands that were previously working, would automatically be working again. I tested with trying to open the trunk. I’ll wait for more news on the command but am already very happy with the progress sofar!
Unfortunately not.
The last app version was using the Teals ProxyServer that managed the command signing/encryption. Now the app has to do it itself. The current state is where I stopped last year as setting up a cloud proxy server was easier 
But hey, we are back in the Tesla game. We just need to catch up a bit 
5 Likes
Where can I find the new test version? Infortunately I removed the old app from my Homey.
1 Like
Sorry, forgot the link. I will add it o the previous posts.
But you already got it. The app is currently hidden in the store. I think I can give the live version to review tomorrow if there are no big issues.
Data reading was the priority for now.
1 Like
Can I also install and test de Battery, Climate, Media and Location device? I have an issue with the battery device, the amp change is not correct when I try to change it with a Homey flow.
You don’t need to change the dependent devices. Only a repair for car device is needed.
If the flow doesn’t work, then it’s one of the not working commands. I have to check one by one.
PS: I added a list of commands to 2nd post
Got it up and running again as well. Great work. Thanks!
1 Like
New test version 2.0.1:
- added commands: start/stop charging & set charging ampere
Now the most wanted commands should work 
2 Likes
@RonnyW hello, thanks for your effort. The app receives the car status, however the commands do not arrive to the car. I receive timeout message after 10000 ms.
I assume you are using a not yet implemented command. If you have the “retry commands” setting activated in car device, the mobile app will show this timeout message.
You can see the API error in car device settings.
The commands will be added one after another. Please be patient
1 Like
Yes @RonnyW. Your are right. I was attempting to use command bot yet available. The other work perfectly. Thanks
Awesome, works fine again. Well done for making the switch so quickly. Set polling both online and offline to 1 hour, let’s see if that is usable with the api limits. Thanks!
