You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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'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.
The text was updated successfully, but these errors were encountered: