search

onokje / node-red-contrib-tesla

Node red nodes to control Tesla vehicles and devices
MIT License
21 stars 11 forks source link

Getting 404 errors after Node Red restarts #48

Open mattenz opened 2 years ago

mattenz commented 2 years ago

I'm finding that if Node Red has been restarted, any request to the car comes back with a 404 response. The way around this is to go into each flow, open each Tesla node to repopulate the car and then redeploy each flow and then everything works fine again. Probably not as big a deal to those running Node Red on its own but if you're running it within Home Assistant, restarts aren't that uncommon.

cramlr commented 2 years ago

I’ve had the same problem and found the same solution. It seems like the Auth key for the car gets corrupted on load

GaPhi commented 2 years ago

Key is updated in config node but can only be saved with 'deploy' action in the auth.json file. On restart, the key restored is then a previous one that is not valid anymore. That is the explanation.

I have not found another idea than using a specific file to save the refreshed key yet. If anyone has a better idea... The problem exists for several node kinds.

Le sam. 19 mars 2022 à 01:40, marc rueter @.***> a écrit :

I’ve had the same problem and found the same solution. It seems like the Auth key for the car gets corrupted on load

— Reply to this email directly, view it on GitHub https://github.com/onokje/node-red-contrib-tesla/issues/48#issuecomment-1072905209, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADUNWNL2B7NJPV6TFVFIOX3VAUPBNANCNFSM5RDD3KRQ . 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: @.***>