Closed alandtse closed 4 years ago
This may be related to the number of devices that have the OTP suppressed reaching a limit of 50 and no devices being allowed to be added. I was able to get past this after reseting the list of devices in the Amazon security page.
Edit: I ran into it again while retesting so it may not be related to the number of devices. However, reseting the devices suppressed bypassed the error.
I've got the same error here.
It started appearing last night. It might have been a change from Amazon's end...
I've also been able to get past this by entering the OTP code immediately after the password.
E.g., if my password is password
and the otp is 123456
.
Enter password123456
in the password field.
Alan, thanks for fixing this. I enabled 2fa on amazon's user account page, selected suppress OTP for my browser and used google authenticator for creating the 2fa codes. I then entered the google OTP code immediately after the password and the connection took. I can only imagine the complexity under the hood to get the handshakes working correctly......
@BuxtonCalvin Thanks for the kind words. It's a moving target and at some point I think Amazon will be able to lock us out. When this hit yesterday I thought we might be at that point but at least some people had said they had solved some of these issues by adding the OTP manually so that gave us a path forward.
Describe the bug Attempting to log in results in Amazon rejecting the login with "There was a problem\n Enter a valid email or mobile number\n"
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen. Continuation of login.
Screenshots If applicable, add screenshots to help explain your problem.
System details
const.py
or HA startup): 2.10.4pip show alexapy
or HA startup): 1.13.0Logs Please provide logs. We'll be most likely asking for them anyway.
Additional context It appears Amazon may have changed their login system as there is now an encrypted password field generated via JavaScript.