Hi,

I installed the free version awhile ago and couldn't get any data to populate. I can honk the horn and probably other functions like that. The test connection completes with success. The controller shows connected but initially showed 99 after restart. The only error I see is:

Gary's Tesla ERROR failed to connect to streaming server - {"response":null,"error":"Unauthorized missing scopes vehicle_location for vehicle data access","error_description":"","txid":"84c02aab24c0da620bd754c1e1242213"}

Not sure what I need to do in order to correct that.

Current Version: 0.2.14 / Free [Production]

Any suggestion apricated.

Thanks

Tesla 2023 model S with latest software.

Edited Thursday at 06:37 PM3 days by garybixler

I assume you have Location_EN set to True in the config

The only think I can think of is to remove the access in the Tesla APP and the reinstall the node and try again to go through the authentication process. The token may not have been updated and old setting may remain

It is difficult to debug - especially since I do not own a tesla :-(

So far no luck. Maybe someone with a Tesla could verify what the key should look like associated with the eisy. Mine looks like this: my.isy.io with unknown key underneath. Also no edit capabilites.

Thanks

I found the problem with location and now the NS starts up with no error messages, but still can't get data from the car. Reinstalled, re-authenticated and re-started with no success. Tried many times.

I included a debug log.

TeslaEV.txt

Edited Thursday at 09:57 PM3 days by garybixler

The car is reported offline - It needs to be on-line for the initial sync - Data may start flowing later as sync is obtained, but I cannot say for sure

There is also an overload reported with result 429 - It may be the ISY server limiting the number of calls (you may have triggered it trying to get the node working)- I would stop the node for a while and try again in 24 hours

Just out of curiosity - what was the issue with location?

BTW - Can you try to reinstall - I found a minor logic bug, (but I do not think it is the cause of your issue)

I did not issue a new version, as I want to make sure it runs (which is difficult to test without a car)

Thanks @Panda88

I tried all of the above a couple of times but still can't get any data from the car. I re-installed while the car was charging so it definitely was awake when I did the re-install and authentication. I have allowed all access to the iox third party app on my Tesla web site. At one last attempt I will delete everything from the car and web site and give it one more try. Will let you know what happens.

Thanks

@Panda88 ,

The location issue was that I didn't have that checked off on the 3rd party app at the Telsa web page.

@Panda88

Unfortunately no success after deleting everything and starting from scratch. I assume after the NS is installed I should have received recent data while the car is awake. It had been awake for about 2 hours while charging but nothing was received. I see that there is a limit for wakeups and commands per day but does that affect data being received from the car as data changes like charging or tempature info?

I don't see how I can get this to work but thanks for you help.

Gary

Can you send me a log - I really wonder if the issue resides in the ISY server that forwards the data

I woke the car with the app but nothing happened till I did a 'test connection'. The previous connection connection was 'failed'. It looked like it should have loaded some data. I attached the debug log for that session.

TeslaEV.txt

It seems there is still an issue with the setup 0 see message from API below

2026-08-07 17:10:53.666 Command udi_interface DEBUG TeslaOauth:_callApi: request response: <Response [500]>, 500, {"response":null,"error":"vehicle rejected request: your public key has not been paired with the vehicle","error_description":""}

Guess there is one more step missing

I did do a fix for the error in line 131 (but did not update version yet)

Edited Saturday at 10:55 AM1 day by Panda88

I re-did the pairing and it seemed to go OK. I don't see the vehicle rejected request in the latest log I attached. I was able to do a honk horn that worked but still can't seem to get any data while the car is not sleeping even though the cabin temperature would be changing.

Thanks

TeslaEV.txt

There is not enough info in the log - the key is to see if the car syncs to the streaming interface

I have checked everything but I don't know how to see if the car syncs to the streaming interface. I assume that if I can do a horn honk that there is a connection to the car. Perhaps they broke something in version

2026.20.6.11, fsd v14.3.6

I think I'll give up for now as the free trial is expiring and I have made no progress.

Thanks for all your help. I'll try again at a later date.

Thanks Gary

you can check log for keyword synched

once synched data os supposed to start flowing

On this latest log I did see " udi_interface DEBUG TeslaAPIOauth:teslaEV_streaming_synched:"

TeslaEV.txt

can you send me whole log from start - need to make sure there are no errors in the data we subscribe to - if ok, then it is likely in the ISY server not passing the data

The trial version ran out so I purchased the NS. I included the log from install. I see several synched references but no data is loaded like climate info.

Thanks

TeslaEV.txt

I contacted the owner of the UDI server to ask what he sees

one dumb question - you are in the US - correct?

and you ran the webhook test again to see it pass?

Edited 9 hours ago9 hr by Panda88

Yes, in the US and each time I run the Stream test "Test Connection" it passes.