The automation below has been working for a while, but stopped working recently. I thought this was related to the AMP authentication issue, but I resolved this and the automation is still not working. The phone is still receiving notifications.
I’m not sure where you got that notify action from but as far as I know that notify isn’t correct. even the AMP documentation doesn’t reference that notify action.
As far as I know there aren’t any notify entities. TBH I can’t remember if that’s the way it used to be or not but if it was it hasn’t been that way for a really long time.
this is how my notification work with my echo dots:
- service: notify.alexa_media
data:
target:
- media_player.livingroom_dot
- media_player.computer_room_dot
- media_player.sunroom_dot
message: "put your text here"
data:
type: tts
First, make sure you know which Alexa integration you are using.
As Finity pointed out, Alexa Media Player provides distinct notification services/actions for each end device and a generic action notify.alexa_media that can target the devices’ media_player entities.
Alexa Devices provides distinct notifyentities that can be targeted by the notify.send_message action.
Second, there have been significant issues with both AMP and AD over the past couple weeks due to Amazon making changes to the API. AMP posted an update a few days ago and seems to be working.
Currently AD is not working for many users. It looks like a fix for AD is already in the dev branch, but we’ll have to wait and see if there’s an update release this week, since it’s beta week.
Thanks, I assumed it was due to the Alexa issues. I’m using AMP and this was working up until my authentication failed again about 10 days ago. Fixing the authentication didn’t solve the problem this time.
I tried the suggestions above, but nothing worked. I was checking my Alexa integrations and it says my Alexa devices have a configuration error. I assume this happened with the last authentication issue. I fixed the authentication issue, as it showed up under repairs, but not the Device configuration error.
I reconfigured the device setup, but the setup issue reappeared as quickly as it disappeared.