do you have sensors? mine are not showing
so i guess this isnt over, this update was for avoid asking for credential at reboot , so my guess is someone with no APM previews install will no be able to login
ultil a full fix is made , guess amazon change something else
updated to 5.7.3 , but notification still not working (TTS) and I cant control alexa (volume , songs etcā¦) only see the status ā¦
Seems its not over yetā¦
So glad I ditched Alexa when the new integration came out and failed to work. I switched to satellites and elvenlabs. Much better tbh.
I used AMP for years, so sad to see it go 
i also had AMP the only thing that is not working are sensors , tts and volume control work as always
1 Like
Correct, still an issue. The sensors.
for me I see all devices but I cant really control (just doest work) and notifications are not working .
yep, updated to the latest, tts not working, stop/start play not working. I do see the devices now but thatās it.
Is this still broken?
It is unstable when you have polling enabled.
Alexa media player temperature sensor:
If you want to use your Alexa devices only for notifications I advice to use the core integration Alexa Devices. Alexa devices is stable if you turn off polling as well, otherwise it is unstable too.
Alexa devices connectivity unstable if polling enabled:
Today my AMP failed to send notifications. It was fine, just a day or two ago. So I deleted the integration and tried to reinstall. Now my problem is that, when I reiinstall the AMP integration, it doesnāt pickup my devices. I know itās related to the Amazon login, but Iāve tried all different varieties of 2SV, Iāve tried the āsecret keyā, and every other iteration, but still cannot get my devices into AMP. I need my AMP devices to be able to provide notifications, which worked fine for months. Iām working with v5.7.13
I know that this is not a new issue, but if someone can give me a step by step solution as to how to resolve this, it would be much appreciated. Iāve spent hours today, without any luck.
Thanks in advance.
I donāt think itās anything that youāre doing because Iām having the same problems. I thought it was me - Iāve been sitting here trying to get it to work and it just wonāt download any of the devices - just like you said. Now that I know itās not just me, Iāll stop wasting time on it and wait for an update. Itās a bummer.
If you are using AMP mostly for itās tts function then I recommend creating a virtual switch, expose it to Alexa when you create it. Then use it in your automation to turn on as an action. When it turns on you can create an Alexa routine to make it say what you want.
Thanks Syncro. Would it be possible for you to give me some idea on how to accomplish this? Thanks in advance!
Itās pretty simple go to the devices page and at the bottom it say helpers. Create a helper called toggle and name the virtual switch that it creates anything you want. At this point you need to enable Alexa to use it by clicking on the settings icon and turning on enable. Once you do that the Alexa app will notify you of a new device. Them just use it in your home assistant automation as an action to come on instead of the notification from Alexa. You will also need to have the automation wait a few seconds then turn it back off so that it will be ready for the next trigger. Then go to your Alexa routines and make a routine that when the switch goes on then Alexa says whatever you want. If you get stuck chat gpt or Gemini will explain it.
Thanks! Thatās exactly what I did. Chat helped me out. I did have to get a Nabu Casa cloud subscription, because the alternative way was a PITA. Well worth it. Now Iāve got Alexa giving me the announcements that I previously had and no longer rely on the AMP integration.
Glad it worked for you. I didnāt know you needed a nabu casa. Account because I have one so that I have access away from home.
Also donāt forget to have the virtual switch turn off after a short wait period or it will never retrigger the next time it will stay on forever. If only needed for one routine then your done, but if you use it in many routines you should create a routine that turns off.after a short time