I’ll add a “me too” to getting the OTP SMS messages from Amazon. Started in the last few days.
I’m on HA 2025.2.5 and AMP 5.6.0
the integration seems to be fully working and I also just ignore the SMS.
me too.
started a weak or so back.
seems that the “remember this device” on amazon isnt sticking anymore.
i get asked for OTP when i go onto the website also on some devices.
OK. I’m dumb.
My AMP integration works perfectly fine with the exception of the occasional OTP SMS.
Can anyone give a procedure to switch AMP to the built-in authenticator app without needing to nuke my entire working integration?
I already have the google authenticator app working with my Amazon account but I think that the authenticator app that the instructions say to set up is completely different than that. Is that correct?
I really hate the idea of ruining a perfectly working integration just to stop the occasional OTP but if that’s the way it needs to be going forward then I might as well do it now.
I’m just hoping that starting over from scratch is not the only way to make the switch.
FYI;
If you are having issues with OTP/2FA, check that your password does not contain a question mark (?).
I let my browser to auto generate a new password on my Amazon account, and then this plug-in was not able to login. I was stuck in a loop with text code OTP.
So no one has reconfigured their AMP integration from the old OTP auth to the new built-in auth that is willing to share how they did it?
It’s been a while, but I believe I followed this part
1 Like
Do I need to remove/reinstall the integration or is there a way to do it with just a re-configuration?
I saw that but I couldn’t see a way to do it from an already installed integration.
Thanks for the reply, BTW.
I’m sorry, I can’t remember clearly since I did this a couple of years ago. I don’t believe I had to reinstall though - reconfigure should be enough.
1 Like
With Alexa Guard now dead, does anyone know if this add-on supports changing the ‘mode’ in Alexa for home/away? I had some automations which would enable (or disable) routines in Alexa if guard was set to home or away… seems there is now a ‘mode’ feature in Alexa that does this same thing. Guard still shows up as an entity, but it always shows ‘away’ and I can’t change it anymore (which makes sense since Amazon killed Guard…)
Same question here
I’m using this integration via Nabu Casa - it seems the “next alarm” information is intermittent. Any ideas why?
HI, it seems, that amazon doesn’t update the last_called attribute. I have 8 echos and can call alexa from where ever, always the one in the livingroom is true. Is there an alternate meanwhile for the need to catch the media_player which is called?
And by the way: it seems, that it is quite calm around AMP. Will there be an alternate integration or is one in preparation?
Maybe the Alexa Devices integration will eventually expose the last_called attribute along other multimedia features.
More sensors are coming to the 2025.7 release.
2 Likes
Just installed 2025.7.0b3
I see a bunch of new sensors on my Echo Dot 3 for instance, most of them unavailable though.
(same on an Echot Dot 4 with clock)
Nothing media related on the horizon yet (apart from the speak/announce)
I restarted my HA this morning (a few times now) and all my AMP entities are unavailable.
anyone else here seeing this?
I did see in another thread that others are experiencing the same but I figured I’d post here in the official thread as well since no one has reported it here yet.
It seems that Amazon is performing maintenance on the servers. This error is also appearing on Alexa devices.
so if you still had a working AMP or AD dont you dare restart you home assistant or integration or you will be unable get a token
2 Likes
well that sucks.
hopefully it’ll come back soon? Any idea if it will fix itself after the service is restored (and another restart) or will we need to nuke our AMP integration and start over from scratch?
not sure i guess it will solve by itself , but if amazon decide to change the api for the new Alexa+ maybe this will break all the integration that use it (hope this not the case)
1 Like
It appears to have screwed the official HA integration as well.
Doh, Just noticed the above issue was for the official HA integration!
I nuked my AMP and tried starting over. No luck, Amazon is not sending me any of my echos, firesticks or firetv’s.