Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain amazon.com does not match reported account domain https://www.amazon.co.uk; functionality is not likely to work, please fix #1129

Closed
danmed opened this issue Jan 24, 2021 · 8 comments
Labels
wontfix This will not be worked on

Comments

@danmed
Copy link

danmed commented Jan 24, 2021

I'm running this as an integration through HACS on HA OS.. .everything seems to be working but this log annoys me...

How do i fix it?

@alandtse
Copy link
Owner

Register devices to your domain properly. I get too many people saying stuff doesn't work because they chose the wrong domain. This is intended to stop that.

@alandtse alandtse added the wontfix This will not be worked on label Jan 24, 2021
@danmed
Copy link
Author

danmed commented Jan 24, 2021 via email

@alandtse
Copy link
Owner

If everything is working, then just ignore the warning. But you should make sure your Amazon account is registered to the domain you're using. If not, you can change it. And that devices are also registered in the right domain.

But again, if it works for you, I wouldn't change anything.

@alandtse alandtse pinned this issue Jan 24, 2021
@michthom
Copy link

michthom commented Feb 1, 2021

[EDIT - I'm an idiot - looks like I missed the option to set the Amazon region when configuring the component - so I'll delete and try again, actually READING the screen and not taking the default region. Sorry for being a dunce, I'm tired.]

Original post left as a warning for others....

"I apologise if I'm necroposting, but I've also run into this issue (in a fresh install of alexa_media_player 3.6.3) and my amazon.co.uk account shows my country/region set correctly to "United Kingdom" and I can see all my devices both in Amazon's "Devices" tab and also in the HA media_player list now, but I can't communicate with them, getting the same error as the OP above. In my logs I can see:

2021-02-01 00:00:33 DEBUG (MainThread) [alexapy.alexalogin] Login created for my_email - amazon.com

Does this mean that I somehow messed up the app setup on the Amazon site? The documentation links to the amazon.com domain to generate the 2FA key. but I thought I should log in to the UK site instead (https://www.amazon.co.uk/a/settings/approval), which is where I got my built-in 2FA key, which successfully worked when configuring the custom component? But that doesn't seem to have configured the media_player for my region.

I didn't see any instructions in the installation guide on how to set a non-US region, but if they exist please point me to them?"

@michthom
Copy link

michthom commented Feb 1, 2021

Yup - I was a buffoon (and @danmed you may have done what I did also). When adding the integration into HA, you need to change amazon.com if that's not your region to amazon.co.uk or whatever. I completely missed that step, but after removing and reinstating the component, it all works just fine.

@garethcheyne
Copy link

Just want to add comment to this, and believe that making the changes solved all my problem.

Preamble, originally when I got my first echo, years ago AU/NZ was not a region, and there for set up in US. Following @alandtse instruction above, I changes my region, de-register all my devices, and then re-registered them again. Now everything is working as expected.

After first install I managed to send a few tts commands, and work, and then it just all turned to crap. I also noticed in my network I was getting flood traffic out of my echo devices to the point that my firewall start dropping the packets. Since I have done the above, and reset it all back up, iIno longer have this issue, I can send tts, media_play commands etc, and my Echo stay online.

@alandtse Amazing, this is working wonders, and be good in the future to send media_play commands, to a echo smart group. This is really going to help with my new home that we are building, and having Home Assistant, and Echo drive everything.
5* addon.

@adwoodworth
Copy link

I'll just add that it is a little bit awkward for people who move devices around countries and have multiple accounts. Seems like the error handling or logging should consider this. I can't just unregister and reregister devices on a frequent basis. Everything seems to work OK, but the entry in the log persists.

@alandtse
Copy link
Owner

Thanks. Given this misconfiguration is the cause for a lot of broken functionality, it'd be hard to remove it. There's no way to know it's someone with the special use case of moving countries. Just ignore it if you're in that special case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

5 participants