Crude example working
shell_command:
alexa_speak: “/config/alexa_remote_control.sh -d ‘LR Dot’ -e speak:‘hello’”
2 Likes
What type of Echo device do you have this working with?
Echot Dots and the ist gen Echo
Working now, I deleted all the 'alexa." files in /tmp and ran again 
1 Like
i now got a notify function in appdaemon that speaks over all my echos.
tested it and it works like it should.
@badgerhome thanks for the heads up.
1 Like
Can someone provide a brief list of the steps involved in doing this? I don’t expect a step by step just some bullet points… Thanks
depends on what you want.
you have a script that you can save and you can create an appdaemon app to activate the script.
or an commandline switch to activate it, or any other way you can use in HA to activate a commandline
(search components for command line)
I wanted to just run a commandline script through ha… but apparently i can’t even find the script… i don’t know if things are getting lost in translation from the german links provided… maybe this is just way over my head,…
Nevermind found it… sorry
I downloaded the script and updated the 3 lines LANGUAGE/AMAZON/ALEXA, and ran the script in my PI (hassbian) ssh with option -a but got:
pi@hassbian:/home/homeassistant/.homeassistant/thinker $ sudo sh alexa* -a
cookie does not exist. logging in …
ERROR: Amazon Login was unsuccessful. Possibly you get a captcha login screen.
Try logging in to https://alexa.amazon.com with your browser. In your browser
make sure to have all Amazon related cookies deleted and Javascript disabled!
(For more information have a look at /tmp/.alexa.login)
Am I doing this right? Or am I missing something?
TIA
You also have to enter your login credentials into the script.
1 Like
just to make sure others can find it, this is where the script is:
https://loetzimmer.de/patches/alexa_remote_control.sh
Sorry to ask but I use hassio because I’m not up on this side of things so could you flesh out these commands a bit please?
I’m UK too and I’ve added my details and your settings to the script and put it in /config
When SSH’ed in how do I check if I can resolve DNS, in /etc/resolv.conf it says the nameserver is 127.0.0.1, is this right?
What do I need to enter to do the chmod -x ?
Tried running /config/alexa_remote_control.sh -a and got this…
core-ssh:~# /config/alexa_remote_control.sh -a
cookie does not exist. logging in ...
awk: /tmp/.alexa.cookie: No such file or directory
ERROR: Amazon Login was unsuccessful. Possibly you get a captcha login screen.
Try logging in to https://alexa.amazon.co.uk with your browser. In your browser
make sure to have all Amazon related cookies deleted and Javascript disabled!
(For more information have a look at /tmp/.alexa.login)
Any help appreciated.
Did you read the error message?
Obviously! Don’t know what to do about it though which, oddly enough, is why I asked.
OK try the following command
ping www.google.com . If this replies then you can resolve web pages from Hass.IO . If not amend the the nameserver to your router IP address . This will be the default gateway of your network.
If you cannot resolve the webpages you will not be able to login. Also confirm you have added the username and password in the script.
1 Like
Bingo! Just needed the router address adding.
Thanks Simon 
this explains how you can add alexa as a home assistant notify service:
works pretty well.
3 Likes
What happens if your playing music through an Alexa device and a tts notification comes through? Does the music pause to wait for the tts message to be completed or does the tts mix with the music?
The music is muted almost completely for the notification and turned up afterwards.
Just like when you’re asking for the weather while playing music.
Sebastian
That’s what I thought but just making sure. Thanks!