-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to get token - HTTP Error 500/401 #10
Comments
Me too, same problem |
Same issue here. Tried with automatic restart of the docker container, but that didn't help. I really need to re-deploy to get it working again. |
I am facing the 401 too at the moment. Credentials should be correct... I'm not aware that I have changed anything... BUT: |
Normally the 401 shouldn't be a problem. It means the session to skoda connect and thus the token is expired. A reconnect is initialized in this situation. The 401 shouldn't be displayed in the node red debug log. I will fix this soon. Please check the output of the skoda get node by adding a debug node |
hm... I just had a nother try. I've replaced the get node with a new one - put my login data into it and tried it again. It seems to work, at least - it did not show any 401 error, but it was not able to fetch some data - and only showed "requesting data" - without any further change. Is there a limit on how often the API should be called? |
Till now I have not encountered any limits. I'm requesting the API every 2 minutes! |
Hi :) at the moment, there's not much in the log:
Before renewing the node, it was showing the 401 directly on the node itself. I've checked the credentials and logged in into the app without any issues. |
Are you using the newest version of the node and have you selected the enyaq in the configuration of the node? |
I have selected the Enyaq. Yes. |
Does anyone else get one of these error messages sometimes? I'm not sure if it's a problem with the plugin or from the Skoda API. 401 is clear, but the credentials are correct and the app (incl. logout & login) works. After re-deploy of the flow, it works sometimes for a while.
The text was updated successfully, but these errors were encountered: