Alexa Announce Feature - Text to Speach via Alexa now a possability?

Feature Requests
70

Having great fun with this, Alexa is spouting all sorts of rubbish at every opportunity. Missus didn’t appreciate Alexa’s personal greeting and turning on TuneIn Radio automatically when she got up this morning though as I ‘forgot’ to warn her :scream:

1 Like
71

lol.
i also had great fun.
letting alexa speak on the fly just what i type.
a friend of us was here and he did ask my wife how it was possible that alexa knows he was there and why she was talking about soccer with him.
my wife kept herself dumb, and i was trying not to laugh, ended up going to the toilet to tell him stuff.

2 Likes
72

Weird. Got the wrapper working from the command line, but calling it from within home assistant yields an error in the log. Do you spot any problem in the notifier like this:

 - name: 'Notify all dots'
   platform: command_line
   command: "/srv/docker/hass-config/ha-alexa-tts/alexa_wrapper.sh -d 'ALL'"
73

Very nice. Thank you very much.

How to slow down the speech. When Alexa speaks very very fast o.O’

74

that isnt possible (yet) with this feature

1 Like
75

Yay, finally cracked a long time goal of getting Alexa to read out the temperature from my Broadlink RMPro…

lounge_temp:
  alias: Lounge temp
  sequence:
  - service: notify.lounge_dot
    data_template:
      message: "The temperature is {{states('sensor.broadlink_sensor_temperature')|replace('.', ' point ') }} degrees"

Until I added the ‘replace’ bit she kept saying “two hundred and thirty one degrees” instead of “twenty three point one degrees”, thanks to an old post by @cederlof for a clue to the answer.

1 Like
76

Ok for those running the script in HA docker, you can still use the full “alexa_remote_control.sh” as opposed to the plain by simply calling the alexa_wrapper.sh from the operating system instead of the HA container.
This is what I did:
I run Ubuntu 18.04 LTS
install jq - sudo apt-get install jq
Run the notify command by ssh(ing) into the OS:
this is mine:

- platform: command_line 
  name: 'Office Echo Dot'
  command: ssh -l hass 192.168.1.XXX "~/docker/homeassistant/assistant_components/alexa_notify/alexa_wrapper.sh -d 'Office Echo Dot'"

Note: I placed the scripts in a folder called “alexa_notify”. You can put them wherever. They must be together and the notify path has to point to the corresponding folder.

I ended up doing this, because the “remote_plain” would only activate 1 of my echos, no matter which one I selected.

1 Like
77

This is good. Earlier I always use | round(0)

78

Does anyone have the script working with Australian Alexa? I keep getting the CAPTCHA for the login and copying over cookies does not help either.

LANGUAGE="en-AU"
#LANGUAGE="en-US"

AMAZON='amazon.com.au'
#AMAZON='amazon.com'

#ALEXA='layla.amazon.de'
ALEXA='alexa.amazon.com.au'
79

did you change add your email and password to the script?

80

hey guys

when I try to run: ./alexa_remote_control.sh -a

I get the following error: -bash: ./alexa_remote_control.sh: Permission denied

Anyone can help please?

81

youre file has the wrong filerights.
the user that you use to start the file has other permissions then the one you used to save it.

82

I get the same error as you now. Do I have to create a separate folder called tmp?

83

/tmp folder should already be there in the root directory.

84

did you chmod +x the scripts?

1 Like
85

Hi all,
I am having the same login issue others are having (cookies and captcha).
I have HA running on an old Ubuntu Linux machine, but I use Chrome on Windows
(and the cookie extension) to download the cookies.txt file and ssh/samba between windows and Ubuntu.
When I run ./alexa_remote_control.sh -a I now get a “cookie expired” and the login fails again.

I’ve double-checked the script and it has the correct email and password that I use
to log into Amazon Alexa.

I’m running the script https://github.com/walthowd/ha-alexa-tts/blob/master/alexa_remote_control.sh
which appears to have U.S. settings (which is where I am from).

Any suggestions? (are cookies tied to the machine?)

86

I had quite a few issues getting mine going… they pretty much all seemed to be resolved by making homeassistant the owner of all the referenced files… I used Firefox on my Ubuntu machine with the cookies.txt extension and saved that as .alexa.cookie and also didn’t realize it but once it works the Alexa.login file turns into an html file which you can click in and login directly to amazon there… all was good at that point… so to answer your question I would suggest you do the cookies.txt thing directly on your homeassistant machine as the cookie is going to have OS and machine identifiers that may not transfer properly…

87

Solved!!! Alexa Announce Feature - Text to Speach via Alexa now a possability?
Running Firefox and its cookie extension on the same machine as HA solved this problem.

Thanks,

1 Like
88

the cookie file in tmp folder keep deleting itself automatically. It there a way to keep the cookie permanent? Or read the cookie from somewhere else that will not delete.

1 Like
89

I have the same issue as you @Sunonline. Did you find a solution? I am running my HA on raspberry pi.