Panda88

I think they found the issue - can you try again

can you send a log thanks

UDI is looking at the issue and may have a fix. Can you try again

one dumb question - you are in the US - correct? and you ran the webhook test again to see it pass?

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

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

you can check log for keyword synched once synched data os supposed to start flowing

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

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)

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

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)

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?

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 :-(

If you can control the valve in the app it should be ok to register (start the node) - you can also try to contact yosmart (service@yosmart.com) to see if there is a newer firmware - I know they are working on addressing the deep sleep issue - do you see an option in the app to select mode There is nothing obvious in the log - a few devices report offline (0201) but it does not look like overload on during start up - they should come eventually as code will keep trying to poll devices that have not already reported data - no errors reported in what you send

you need to make sure the Flowsmart is online when you start the node. it goes into a deep sleep mode where you cannot communicate with it. Try to press the set-button before starting the node