node-red-contrib-alexa-remote2
node-red-contrib-alexa-remote2 copied to clipboard
586837r
user/pass authentication not working
Hi all, I'm getting authentication errors when trying to use the user/pass options, I've checked the credentials and I know they are correct. Any ideas why it's failing? The cookie method works, however as it expires this method isn't reliable.
Thanks
Same Problem here! Cookie works but usr/pass does not. v10.13.0 I found workarounds with passw and 2 fact auth. To type in the Password like:
_Add the security code to the end of your account password on the device or app you are attempting to register and submit again. For example, if your password is “abcdef” and the security code you receive is “12345”, then enter “abcdef12345” in the password field.
You will then be signed into your Amazon account._
But nothing works... I always get the Message Login unsucessfull, check credentials...
does yours work now? Any Idea?
I have found out how to fix this. I am using NodeRed v0.20.5 with v10. The trick is to use user/pass and you must set the User Agent to: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0' including the quote marks. This fixes the "Error: Amazon-Login-Error: Important Message!: To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below." error message .....
-Hi, with undefined User Agent error: "Error: Login unsuccessfull. Please check credentials." -With UA 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0' "Error: Amazon-Login-Error: Important Message!: To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below." NodeRed v0.19.5 v10.15 Location: Deutschland
strange!... I made sure that cookie is clear and user/pass is filled in. I used the UA above (with the single quote). I now have a separate problem in that the influx node does not like node10.
Maybe try another UA?
Now it works for me! First i thought iam using the wrong quote marks, because in Germany we have " and not the ' But now iam using the UA without any quote marks and it woks!
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
i logged in with firefox at layla.amazon.de and found the UA by pressing F12...
I cant get it to work using the above suggestions.
Service Host: pitangui.amazon.com Page: amazon.com User Agent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0'
Alexa-command: v0.0.6 node-red-contrib-alexa-remote2: v1.1.0
9 Apr 14:08:18 - [info] Node-RED version: v0.20.5 9 Apr 14:08:18 - [info] Node.js version: v10.15.3 9 Apr 14:09:27 - [error] [alexa-remote-init:7479b72d.dd16b8] Error: Login unsuccessfull. Please check credentials.
I opened another bug case. because the User-Agent do not fix the problem on a long-term period. after approx. 14 days same issue appears again. Guess we need finding some settings within Alexa/Web Settings.
-Hi, with undefined User Agent error: "Error: Login unsuccessfull. Please check credentials." -With UA 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0' "Error: Amazon-Login-Error: Important Message!: To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below." NodeRed v0.19.5 v10.15 Location: Deutschland
Some issue... guess if we could "captcha" it would work persistantly
Hi @spants hows you actual config look like? did you change anything on Alexa settings? I believe, if the "relogin" issue could be addressed than with usr/pwd it would work. And as said, I don't like cookie login since it expires.
Just wanted to give feedback: with the last update is one the raspmatic working fine. Proxy ok.. :) Thanks und danke
I'm nearly a little sorry, I found one more issue. if you send "refresh" in msg.payload, the Init node acknowledge the refresh, but after this all other node sending cmds state: "no json". if you restart there node in any way with "node red update", changing anything inside the Init node and change it back, it is working again.
i i have/had the same problem with the refresh. Always after i init via "refresh" i got the "no json" error. After a few month doing nothing to solve that problem, now i had time to play again and tried it with the output-payload of the alexa-Init node: Now i use the output-payload of the alexa-Init-node and send it with a delay-node (delay of 2 days) to the input of the same alexa-init-node. I tried it with a delay of 20s, and it worked, now iam waiting for the future...
i i have/had the same problem with the refresh. Always after i init via "refresh" i got the "no json" error. After a few month doing nothing to solve that problem, now i had time to play again and tried it with the output-payload of the alexa-sequenze node: Now i use the output-payload of the alexa-sequence-node and send it with a delay-node (delay of 2 days) to the input of the same alexa-sequence-node. I tried it with a delay of 20s, and it worked, now iam waiting for the future...
This is a good work-a-round, I've tested it with 20sec delay and yes this solves the issue.
You're right 'refresh' was broken, should work now (v2.3.5)!
Testing was successful, well v2.3.5 has fixed the issue.! TNX
Update today: It stopped working actually again.
- Speak+Volume not working
- lose connectivity, cookie refresh not working and no error message displayed, but neither Tunein, nor speak is working until I start providing the pass/user again (browser)
"Error: Login unsuccessfull. Please check credentials." I am facing this error after following the suggestion.Have tried with alexa remote2 and alexa cakebake. Can any one help? I am trying to implement it in a system where I can not use proxy method
