search

586837r / node-red-contrib-alexa-remote2

MIT License
88 stars 71 forks source link

Login expires almost daily. #211

Open bvandenbon opened 2 years ago

bvandenbon commented 2 years ago

It worked fine for me the first months. Now since about a month or 2 maybe 3, I need to login again every time to make it work.

So, each time it tells me to open my webbrowser and login on the alexa portal. Then it works fine for that day, maybe 2 days, and then again the same problem.

To solve it, I tried to play with the expiration date, because it's actually set to "1 day". If I change that to any other value, login doesn't even work.

These are my current settings. (I live in central Europe, Belgium)

image

Has anything changed recently ? Are other people having similar issues ? Just really wondering what's going on. Because signing in again every day isn't really how I planned to use Node-red.

alexruffell commented 2 years ago

This is an old issue, but I figured I'd comment on a few things I noticed.

1) The file path where you same the login info (whatever it is) seems to be incorrect. I saved it to /config/node-red/amazon.txt 2) The server you are using, I believe, is for the USA. I don't know which server you should be using but the documentation shows one for the UK and one for Germany. The one in the UK, if you want english, might be the one to try.

image

Anyhow, my 'login' appears to be expiring randomly as well. I have to go into node-red and trigger a refresh. It works for a while, and dies again. No idea why. Set up as is, it used to work without issues, then it started having issues a month or 2 ago.

NandishKoppad09 commented 8 months ago

What information should be incorporated into the file path within the Alexa routine node when automating the login process using an HTTP request node? The difficulty lies in the need to redeploy and perform a new login to the Alexa account by opening a new browser after restarting Node-RED.

alexruffell commented 8 months ago

You just specify a valid path and the node will save the cookie into that file when it logs in. I believe it is explained in the documentation for that node if you want more details. In other words, as far as I can remember, you do not need to add anything to the file as the node takes care of that.