Alexa text to speech Topic is solved

[salopette]

i nideI need DE Account

[Bradds]

Hi All

For people having cookie/captcha issues on headless systems, you could try https://github.com/jonferreira/node-red ... exa-remote
This node (for node-red) allows you to send speech to alexa and works fine.

To fill in the cookie window in the node config, do the following.

Connect to your alexa web page.
right click somewhere on the page and click inspect.
Click on the network tab.
Press f5
pick one of the name in the list
click on the header tab
scroll down to cookie ( if you do not see it click on another name)
copy all what is in here and paste it in the cookie section of the node-red node.
( note host : alexa.amazon.com (or whatever country link you use) and paste it to ''amazon page '' field of the node-red node

[manutremo]

Hi,

Just installed the script - wow great job. In my case I'm using spanish alexa at alexa.amazon.es. Everything seems to be working fine regarding launching the script, but whatever I ask it to say, alexa always says (in spanish) "Sorry I can't find an answer to your question".

If however I make her speak something like "Alexa connect bluetooth" she will respond as if I had given the order by talking.

In summary she seems to be taking the phrase after the -e speak: command as an order instead of as something she could just convert into speech and repeat.

My settings are:

LANGUAGE='es-ES'
AMAZON='amazon.es'
ALEXA='alexa.amazon.es'

Any idea?

[dadogiobbe]

the same here in italy...it looks like an order...

[johansson]

Great approach, would be perfect for e.g. temperature alerts or so. After a bit of fiddling the login issues were tackled and everything seems to in order, but the sound is missing.

When I do e.g.:

Code: Select all

sudo ./alexa_remote.sh -d Echo -e speak:'Test'

I get as an output:

Code: Select all

sending cmd:speak:Test to dev:ALL type:XXX serial:XXX customerid:
Sequence command: Alexa.Speak
{"message":null}

But no sound from any of my devices! Any ideas and/or advice how to solve this? Same applies to traffic announcements, TuneIn radio and so forth.

[johansson]

Solved. It was a cookie/login/whatever issue anyway: I used an extension called cookies.txt to copy the cookie into /tmp/alexa.cookie and now it's suddenly working.

[darrepac]

Great approach, would be perfect for e.g. temperature alerts or so. After a bit of fiddling the login issues were tackled and everything seems to in order, but the sound is missing.

When I do e.g.:

Code: Select all

sudo ./alexa_remote.sh -d Echo -e speak:'Test'

I get as an output:

Code: Select all

sending cmd:speak:Test to dev:ALL type:XXX serial:XXX customerid:
Sequence command: Alexa.Speak
{"message":null}

But no sound from any of my devices! Any ideas and/or advice how to solve this? Same applies to traffic announcements, TuneIn radio and so forth.

I got the same when I was using a cookie from Chrome, once I used a cookie from Firefox, everything worked!

[satanasinc]

Hi!

It works perfect in Spanish in my raspberry pi.

Thanx for share your workwithus. It’s great!

Greetings from Spain.

[freijn]

I still have the problem that cookies expire after a while ( something like 2 weeks ? )

Anybody found this as well and know a solution?

Very unreliable announcements from Alexa

[EdddieN]

Anyone managed to get all the Alexa devices to speak at once?

From the documentation this should work:

Code: Select all

./alexa_remote_control.sh -d ALL -e speak:'hello'

Also changing the volume before speaking?

[nigels0]

I get them speaking in sequence, but timeout after 3 or 4 of them (I have about 10 devices around). Your options are correct

[EdddieN]

Same line? -d ALL ?

[philchillbill]

In the Alexa app you can setup 'routines' that can be triggered either by a custom voice command or by a smart home event. The result can be another smart home event or it can be a TTS action from Alexa (and these ones don't need cookies). There's an option to have it spoken from any of your echos. Might be worth checking out for people currently trying the Loetzimmer script and struggling.

They only work for devices correctly exposed as being of type CONTACT_SENSOR or MOTION_SENSOR and that proactively report state-changes. HA-Bridge exposes everything as a dimmable light as it fakes Philips Hue, so it won't work with HA-Bridge.

[EdddieN]

Thanks

Yes I got HA working fine. It is more I like to anoche things in all of the Alexa via the TTS. I got it working for individual ones but when I use the -d ALL does not seem to work, however the script runs ok.

[sion]

Just wondering if people have this working reliably?

I worked for me for ages at the start.
Then stopped.
I tryed enabling 2 step, and put the code in the the script for the first go - then took the code out - and this worked for a few days, but stopped again.

I’m going to try and fix the cookie thing, but I don’t have a desktop etc on my pi, so it’s a bit of a job. I have a Mac mini running all the time, so I may have a go on that. But if we are having to redo the cookie every couple of weeks , I may Wait for another solution.

Thanks.

[EdddieN]

It works for me, although a bit slow...
I used the second script and jq

[philchillbill]

Works great for a few days until the cookie expires. PITA to have to renew it manually.


Sent from my iPhone using Tapatalk

[Hesmink]

For anyone who has abandoned this because of the cookie thing: There is now support for 2 factor authentication, supposedly eliminating the re-logging in.
Check https://blog.loetzimmer.de/2017/10/amaz ... -echo.html

You have to enable 2 factor authentication at amazon and add another app that will do the 2 factor stuff on linux for you.

[emme]

I use Alexa-Remote2 node in nodered.
works like a charm!!!!!

[salopette]

I use Alexa-Remote2 node in nodered.
works like a charm!!!!!

How can I install this? Is there a manual for domoticz?