-
Notifications
You must be signed in to change notification settings - Fork 16
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
Notifications on Amazon Echos does not work #1
Comments
Can you please post the complete yaml config of the card as well as check in the developer tools if a notify service with that exact name exists? |
This is the yaml of my card: type: 'custom:notify-card' The service notify.alexa_media_bad is existing in my dev tools list. |
Unfortunately I don't have an Alexa, so I cannot reproduce this issue. Could you try to send a notification through the developer tools and post the yaml of the successful service call? |
This is a valid service yaml of an Alexa notification:
You can also replace the "announce" in data with "tts", then the intro sound will not play before the notification. |
I have now included support for additional data. You should be able to update the card via HACS and try this config:
Please report back if it works. |
Unfortunately it does not work.
By trying to send a notification, an error message appears: This is the error message from the logs:
|
That's very strange. I still don't understand completely what my card is doing differently. One last thing you could do for me to help me is to use the Developer Tools to subscribe to the |
Now it's working! |
When I select the service alexa_media_XXX and want to send a notification, following error message appears:
TypeError: 'NoneType' object is not subscriptable
The text was updated successfully, but these errors were encountered: