I am having trouble authenticating the plugin. Using my iPad, I accessed the local host URL from my home bridge log and the website appears as expected, but then I am immediately redirected to the App Store listing for the Amazon Alexa app—note that I already have the app installed. If I try from my MacBook, I get a QR code to scan; if I scan it with my phone, the same things happens, it bounces me over to the App Store listing.
Note that I did already set up Amazon with the Google Authenticator app. I also tied two different proxy ports (9000 and 7000) but that change had no effect.
My Alexa app has two hostnames listed:
na-api-Alexa.amazon.com
Alexa.amazon.com
None of those are options in the drop-down, so I selected amazon.com. Since that did not work, I went into the JSON config and tried both of the above options, one at a time—this had no effect.
Logs:
[homebridge-alexa-smarthome] Failed to initialize connection to Alexa. - Please open http://Homebridge.local:7000/ with your browser and login to Amazon. The cookie will be output here after successfull login.
[29/01/2024, 18:03:27]
[homebridge-alexa-smarthome] After initialization - HttpError(Error getting smart home devices. Reason: Cookie invalid, Renew unsuccessful)
Describe Your Problem:
I am having trouble authenticating the plugin. Using my iPad, I accessed the local host URL from my home bridge log and the website appears as expected, but then I am immediately redirected to the App Store listing for the Amazon Alexa app—note that I already have the app installed. If I try from my MacBook, I get a QR code to scan; if I scan it with my phone, the same things happens, it bounces me over to the App Store listing.
Note that I did already set up Amazon with the Google Authenticator app. I also tied two different proxy ports (9000 and 7000) but that change had no effect.
My Alexa app has two hostnames listed:
na-api-Alexa.amazon.com Alexa.amazon.com
None of those are options in the drop-down, so I selected amazon.com. Since that did not work, I went into the JSON config and tried both of the above options, one at a time—this had no effect.
Logs:
Plugin Config:
Screenshots:
N/a
Environment: