SSML is supported but you need to use announce. It’s not possible with straight TTS.
Is it possible to have some feedback from this component when is it finished saying it’s announcement?
I’m trying to make an automation that turns down my squeezebox media player device just before the Echo device speaks, then turns the volume back up after the Echo has finished speaking.
Right now I’m just turning down the volume for 10 seconds and then back up, but it would be nice if I could turn the volume back up as soon as the Announcement is done.
How about checking the state of media.player.alexa changing from ‘playing’ to ‘paused’.
Hi, thanks for the suggestion. I’ve just tried checking the state during the tts announcements, but all the Echos just stay on ‘standby’ state before, during and after it speaks. 
SSML editors
These has been useful to me, perhaps also to others:
https://www.ssml-editor.com/ (best editor imho)
https://topvoiceapps.com/ssml (has integrated Alexa skill for “live” testing)
SSML documentation
https://developer.amazon.com/docs/custom-skills/speech-synthesis-markup-language-ssml-reference.html
Hi, I got some new Echo Shows and therefore I moved two others. Now I have the Situation, that i.e the entity_id from my Office-echo is still named as media_player.livingroom but the friendly name is Office. That is confusing in developing automations. Is there a way to refresh the entity id’s?
Delete them from the entity registry and they will be readded with the correct name. Or you can manually rename them in the entity registry.
Thank’s. that was the right push.
So easy in the end 
I can confirm that the message is displayed on echo show 5.
Echo-Groups are working as well. As soon as activated in the alexa app, they appear in HA as media_player.
Unfortunately, the synchronization is on the one hand a little bit better compared to tts on several echos but still not perfect.
It seems, that the echos have a different wakeup time. If you start a second announcement right after the first one, the synchronization is nearly perfect.
I can confirm: 0.97.1 and 1.4.1. Everything’s fine.
When starting HA: “No entity id specified for entity This Device shuffle switch”
I don’t have a shuffle switch. So there should be no entity_id.
We have a major release coming up which moves us to async which improves performance and is one of our goals before we try to make this official (if we ever do). If anyone wants to help us test it before we generally release it, please get pull the dev version from alexa_media and alexapy. While it works as well as the existing stable release from my testing, this is for advanced users who are comfortable working without instructions, debugging, and helping track down bugs. Please note, this does not include any new features yet compared to 1.4.1, so it’s really just for testing to make sure the migration to async worked. I may start adding some other features while we’re testing the dev version, so it could get better, but not guaranteeing anything.
1 Like
By the way, I know where this “No entity_id…” message comes from.
When a new echo show5 is connected to the amazon account, obviously 3 switches are created: do not disturb, shuffle and repeat. These switches causes the error because they are not an entity in HA.
I’m having some issues with the media player part after 0.97. Notify function works well.
This works fine.
This does not.
Log: “extra keys not allowed @ data[‘media_content_id’]”
Seems like it could be a node-red issue? Anyone have a node-red example that plays media through an echo?
I fixed it. There is a “media_play” and a “play_media” service. Not sure what the difference is other than one works and one doesnt.
from today echo’s media_player service has disappeared. Has it happened to you too? I didn’t change anything…
File “/config/custom_components/alexa_media/init.py”, line 346, in update_devices
for b_state in bluetooth[‘bluetoothStates’]:
how is it possible to reintegrate the media player alexa if it disappears?
It has stopped working for me since an HA restart also.
Initiating a reintegration can be performed by deleting the alexa_media.[username].pickle in the config directory and bouncing HA.
I just tried this, and got the “Click button to configure” button as expected, however pressing it does nothing except for adding this to the log:
Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/alexa_media/__init__.py", line 123, in setup_platform_callback
login.login(data=callback_data)
File "/usr/local/lib/python3.7/site-packages/alexapy/alexalogin.py", line 238, in login
site = soup.find('form').get('action')
AttributeError: 'NoneType' object has no attribute 'get'
This is a recent bug and we’ll roll out a fix. You won’t be able to do anything until the fix is out.
Enable advanced debugging and view the webpage. The Amazon page doesn’t even have a login form so there is something wrong with the page you’re seeing. Amazon may be forcing you to change your password or enable 2FA or something else.
Thanks for the swift reply.
I enabled advanced debugging and restarted HA and the option to configure has gone and the component is now working again.
I restarted HA several times yesterday in an effort to fix the issue and it made no difference, so it’s possible that this was a transient issue at Amazon’s end.
2.0.0 is out.
This is mainly an architecture revamp. We are now fully async which means all the performance issues like is taking over 10 seconds and other miscellaneous errors should be gone. There were some bug fixes for recently reported issues, but we didn’t add features to try to cut down on potential new bugs.
However, since this was a complete change of the underlying libraries, there could be bugs we missed. Be ready to roll back or wait for the next release if you’re happy with where you are now. If you have HACS, it should be fairly easy to do a rollback.
For those on hassio, you may have to restart 2-3 times before HA will load the dependencies. It doesn’t look like something we can control too well.
Features:
- migrate to async (resolves #282)
Fixes:
As always, please use the the Wiki and FAQ if you need instructions or have questions. Also, please help in documenting features in the wiki since this thread is basically unsearchable now. We also use GitHub for bug reports/feature requests .
1 Like