Closed delboy711 closed 2 years ago
I have the same issues. I am still figuring out what's going on.
Tesla changed the id_s values. Just get the new one with a 'vehicles' command and identify a car thanks to the VIN to get the matching id_s.
Le mar. 8 févr. 2022 à 16:08, Martin Schimmel @.***> a écrit :
I have the same issues. I am still figuring out what's going on.
— Reply to this email directly, view it on GitHub https://github.com/onokje/node-red-contrib-tesla/issues/42#issuecomment-1032712406, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADUNWNMO2EA56VMPAGAXKILU2EWYHANCNFSM5N2W55HQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
Easiest way: 1 Redeploy all nodes 2 Open faulty tesla node in editor 3 Reselect your vehicle and click done 4 repeat step 2 und 3 for every other tesla node in your flows 5 Redeploy all nodes
Yes That was it.
Thanks
Nice1 guys.
After working perfectly for months, in the last few days I have been getting "Error response: 404" to 'wake' commands. 'vehicle list' still works.
I assume this is because of a Tesla API change?