Open danielbrunt57 opened 1 month ago
Hi @danielbrunt57, thank you very much for your input! This part of the code sits here: https://github.com/Apollon77/alexa-remote
The maintainer @Apollon77 would surely appreciate a PR.
As per alexapy/const.py, see PR 246 for 4 additional domain lookups: 'amazon.ca','amazon.com.mx': host 'bob-dispatch-prod-na.amazon.com' 'amazon.com.in','amazon.co.nz': host 'bob-dispatch-prod-fe.amazon.com'
released in 7.0.5
I am new to node-red-contrib-alexa-remote2 as of yesterday but have been a long time user of the Alexa Media Player in HA and have been doing lots of debugging in it and
alexapy
which proved invaluable in figuring out what to set the "Push Dispatch Host" to despite the severe lack of user documentation on what that entry can be set to. My Echo devices are registered to my account inamazon.ca
but that domain resulted in HTTP2 connecting by default tobob-dispatch-prod-eu.amazon.com
. When I usedamazon.com
then HTTP2Push connected to the correct gateway (bob-dispatch-prod-na.amazon.com
) but then I had zero devices. Before I delved inside the code, I tried entering thealexapy
gatewayalexa.na.gateway.devices.a2z.com
and Push then worked. That alias is the same IP as thebob-dispatch-prod-na.amazon.com
alias.I therefore recommend that the
/alexa-remote2/alexa-http2push.js
should be amended as follows foramazon.ca
:I'd also recommend that the
Alexa Account configuration node
help info include thePush Dispatch Host
field and the three possible settings for that field:bob-dispatch-prod-eu.amazon.com
,bob-dispatch-prod-na.amazon.com' and 'bob-dispatch-prod-fe.amazon.com
.