I checked the access token data and it should be valid for 8h.
But that’s only the access/Bearer token.
Any further request will automatically refresh the access token after a http 401 response using the stored refresh token.
I have no idea why in your case the refresh token is invalid.
It looks as if your refresh token (stored in car device data) is somehow cleared or gets invalid caused by other reasons. Normally this happens if you remove the Homey app from your Tesla account or if you change the passoword of your Tesla account.
Do you think it could be something to do with the fact we have 2 cars, and we are both owners on our own cars so when I connect I don’t have “owner” on the other car? I’m not sure that would be the reason because it seems to add fine, and the token kicks me off my own car as well. Neither of us remove the app or change the password
@Peter85 FYI and test
Perhaps you are starting flow actions parallel instead of sequential (for one car). That could cause parallel requests. The change should fix this - if that was the reason.
Brilliant thanks for this I’ll give it a try! We only usually execute for one car at a time, e.g. preheat, keep doors unlocked, open boot, turn house heating off etc.
Hi, just thought I’d touch base and say that error hasn’t happened since which is good, but I have had some odd random behaviour, such as having to run automations twice for it to work, and this morning I got MESSAGE_FAULT_ERROR_INVALID_SIGNATURE which I’ve never seen before, but I ran it again and it was successful
Going to keep testing it over the next few days thanks for your help!
Invalid signature for commands is often caused by a long delay while sending the command - the signature has only some seconds lifetime.
If “auto wake up” is set for car device, a wake up command is sent first. The following can be processed then.
I can imagine that the car is not reachable in time (while Tesla server tries to send tje command to the car). I have seen such send issues if the car is at the end of Wifi range and is switching between Wifi and LTE.
Hi Ronny, since a few days, the value for estimated battery range is zero. When checking the graphs, I see that the range was not updated for a few days before it was set to 0. The optimal battery range value is still updating though. Is this a known issue?
Hi, I’m not using telemetry but the fleetapi. It is only this one value that is not updating. Other values do update: see screenshot: 10 hours versus 8 days
If I remembet right, the car is registered in a region (North America, Europe, CN). The user account must also be registered in this region.
Do you have a leased car or a car imported from another region?
We also had similar cases where the account was created in another region. But I don’t know if this still works. It’s a bit tinkering with browser console
yeah, I did some research on it before posting. I was wondering if anyone had a quick and easy way, or a script already knocked up that will register account in both regions.
To answer the question, mine is a leased Tesla through Octopus. I am UK based.
My account must be EU based, while the car is probably registered on a business account based in NA. (whoever Octopus use for their tesla management Id guess)
I will see if I can get some time to knock up a quick script to try and do this. Need to find the fleet API docs first I guess. Probably in the dev account ive just registered for
