I am trying to control the volume by
alexa_remote_control.sh -d MyAlexadevice -e vol:10

But volume stays unchanged

I executed some commands. Output:

root@SmartHomeV2:/var/homebridge/devices/sprachausgabe# ./alexa_remote_control.sh -e automation:'aufwachen'

setting default device to:
MatteosZimmer
sending cmd:automation:aufwachen to dev:MatteosZimmer type:++++++++++++++++ serial:++++++++++++++ customerid:++++++++++++++++
<
But alexa doesnt do anything. The config file seems correct.

I got everything setup and can get all my devices but none of the command will work (no sound)

anyone any idea, just spend the last 3 hours on this haha :P

Hallo.
Ich habe ein Problem mit dem Script beim ausführen von Routinen.
Wenn ich mehr als 20 Routinen in der Alexa-App (ganz einfach und nur mit einem einfachen Wort gekennzeichnet) anlege, werden die neuen Routinen als nicht vorhanden ausgegeben.
ERROR: no such utterance 'Fenster' in Alexa routines
Alles was über den älteren vorhanden Routinen angelegt wird, wird nicht ausgeführt, bzw. wird zwar ausgeführt, aber dafür eine ältere nicht mehr. Ist das Script irgendwie auf ein Limit gesetzt, oder wie bekomme ich es hin das dass Script nach neuen Routinen sucht und diese auch ausführt, mit dazu nimmt?

Hi.
I have a problem with the script when executing routines. If I create more than 20 routines in the Alexa app (quite simply and with just a single word), the routines will be displayed as missing.
ERROR: No search utterance 'window' in Alexa routines
Everything that is created over the older existing routines, is not executed, or is executed, but no longer an older one. Is the script somehow set to a limit, or how can I get it that script searches for new routines and executes them, takes with it?

I downloaded the github, changed the items in alexa_remote_control.sh to USA values. But when I run "sudo ./alexa_remote_control.sh -a" I get the error below.

cookie expired, logging in again...
log in failed, aborting

And if I run without sudo it cannot delete the cookie. Any ideas what I need to change? Many thanks!

Looks like it doesn't work with the new Echo Dot 3rd Gen.?

I've both a 3rd Gen. and 2ng Gen. dot at home, both apparently configured same way.

Same speak command works on 2nd Gen, it doesn't on 3rd Gen.

Hi, i am facing issue with echo dot 3rd Gen. Script does not work. Making some troubleshooting i've noticed that there is an "500 SERVER INTERNAL ERROR" response.
Below a snippet of error code:

* Hostname was NOT found in DNS cache

Trying 52.94.218.248...
Connected to alexa.amazon.it (52.94.218.248) port 443 (#0)
successfully set certificate verify locations:
CAfile: none
CApath: /etc/ssl/certs
SSLv3, TLS handshake, Client hello (1):
} [data not shown]
SSLv3, TLS handshake, Server hello (2):
{ [data not shown]
SSLv3, TLS handshake, CERT (11):
{ [data not shown]
SSLv3, TLS handshake, Server key exchange (12):
{ [data not shown]
SSLv3, TLS handshake, Server finished (14):
{ [data not shown]
SSLv3, TLS handshake, Client key exchange (16):
} [data not shown]
SSLv3, TLS change cipher, Client hello (1):
} [data not shown]
SSLv3, TLS handshake, Finished (20):
} [data not shown]
SSLv3, TLS change cipher, Client hello (1):
{ [data not shown]
SSLv3, TLS handshake, Finished (20):
{ [data not shown]
SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
Server certificate:
   subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=layla.amazon.com
   start date: 2018-11-24 00:00:00 GMT
   expire date: 2019-11-09 12:00:00 GMT
   subjectAltName: alexa.amazon.it matched
   issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
   SSL certificate verify ok.
GET /api/bootstrap?version=0 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:1.0) bash-script/1.0
Host: alexa.amazon.it
Accept: /
Accept-Encoding: deflate, gzip
Cookie: XXXXXX
XXXXXXXXXXXXX
DNT: 1
Connection: keep-alive

< HTTP/1.1 200 OK

Server Server is not blacklisted
< Server: Server
< Date: Tue, 09 Apr 2019 14:52:27 GMT
< Content-Type: application/json
< Content-Length: 138
< Connection: keep-alive
< x-amzn-RequestId: 176f282a-5ad7-11e9-a044-457dd0bd7343
< x-amzn-alt-domain: https://alexa.amazon.com/logout
< Content-Encoding: deflate
< x-amz-rid: B4M8T559VF5SB2PB77CC
< Vary: Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
<
{ [data not shown]
Connection #0 to host alexa.amazon.it left intact
setting default device to:
Echo Dot SALA
sending cmd:speak:Ciao to dev:Echo Dot SALA type:XXXXXX serial:YYYYYY customerid:ZZZZZZZ
Hostname was NOT found in DNS cache
Trying 52.94.218.248...
Connected to alexa.amazon.it (52.94.218.248) port 443 (#0)
successfully set certificate verify locations:
CAfile: none
CApath: /etc/ssl/certs
SSLv3, TLS handshake, Client hello (1):
SSLv3, TLS handshake, Server hello (2):
SSLv3, TLS handshake, CERT (11):
SSLv3, TLS handshake, Server key exchange (12):
SSLv3, TLS handshake, Server finished (14):
SSLv3, TLS handshake, Client key exchange (16):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
Server certificate:
   subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=layla.amazon.com
   start date: 2018-11-24 00:00:00 GMT
   expire date: 2019-11-09 12:00:00 GMT
   subjectAltName: alexa.amazon.it matched
   issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
   SSL certificate verify ok.
POST /api/behaviors/preview HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:1.0) bash-script/1.0
Host: alexa.amazon.it
Accept: /
Accept-Encoding: deflate, gzip
Cookie: XXXXX
XXXXXXXXXXXX
DNT: 1
Connection: keep-alive
Content-Type: application/json; charset=UTF-8
Referer: https://alexa.amazon.com/spa/index.html
Origin: https://alexa.amazon.com
Content-Length: 414

upload completely sent off: 414 out of 414 bytes
< HTTP/1.1 500 Internal Server Error
Server Server is not blacklisted
< Server: Server
< Date: Tue, 09 Apr 2019 14:52:27 GMT
< Content-Length: 8
< Connection: keep-alive
< x-amzn-RequestId: 17d3b663-5ad7-11e9-8ae0-9159098154f7
< Access-Control-Allow-Origin: https://alexa.amazon.com
< Content-Encoding: deflate
< Vary: Origin,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Access-Control-Expose-Headers: x-amzn-dat-gui-client-upgrade,X-Amzn-Error,loginUrl,X-Amzn-RequestId,x-amzn-alt-domain,Date,Location
< Access-Control-Allow-Credentials: true
< x-amz-rid: 2DTVRM9J7XZKVMW2FWVH
<
Connection #0 to host alexa.amazon.it left intact

Hello to all,
Alexa is available in Italy from 30/10/2018 and I'm using an echo dot v3 with italian language.

I'm trying to use alexa-remote-control with the TTS function.
My setup is for Italian WebSite :
LANGUAGE="it-IT"
AMAZON='amazon.it'
ALEXA='alexa.amazon.it'

If I send the command : -e speak:"che tempo farà domani" Alexa don't do TTS using this phrase, but read the phrase as a command , and then tell me the forecast (che tempo farà domani --> What's the weather like tomorrow ?)

Please note : if I set up the echo with English language, the TTS function works fine.

How to solve this issue ? It is an Alexa related problem, or the problem is with alexa-remote-control?

Thanks in advance

Hello your script is very very good !

can y add volume set up for option -e speak:'YOUR TEXT' ?

thank'youuuuu

Hi Thorsten!

I am an Austrian developer of the LoxBerry-Core developer team (https://github.com/mschlenstedt/Loxberry).

One of our plugin authors has integrated your script into a LoxBerry plugin, including patching your script to customize the settings via a Webinterface.
Unfortunately he discontinued updating his plugin, as for him it was too effortful to integrate new versions of your script with patching again.

To keep it short:
Would it be possible to get all of the configuration settings, integrated in the script, out to a configuration file.
I have seen that you already use jq, therefore a json config would be helpful (could directly managed from within the webbrowser).

Maybe, for compatibility, it could be done in a way, that if an external config is available, or if a special parameter with a config file is given, this overwrites the script-internal settings.

If you consider this proposal, I may get the plugin developer to continue support, or otherwise, I would redesign the plugin myself.

Thanks and cu,
Christian

TLDR Summary:
Would you like to collaborate in documenting the Alexa API?
e.g., Known Endpoints

Details:
I am a contributor to a home-assistant custom component that was developed based on this script. While we are not at feature parity with this script yet, I have started looking at features this script does not have yet, which means reviewing the Alexa API.

I searched but I couldn't tell if you already had a page documenting the API as you discovered it, but I thought it may be worth sharing what I've started and invite you to help build that (or some other Wiki).

We currently have a fully open GitHub Wiki and I'm posting info there such as:

• Known Endpoints
• Instructions to our users how to document additional functionality

Not all the Wiki topics will be relevant to your audience, but perhaps we can set up a developer section we can cross reference. Perhaps we can build something like this.
Tesla Unofficial API reference

It may also be a place we can share stuff we figure out like last_alexa disambiguation #38, or some of the bugs we've found in music playing.

.

Hello!
Now we can configure own texts in routines which alexa will say...
It would be a great feature, when we now can start a routine with your script!

Greethings
Carsten

its possible run Speak command to rescan Bluetooth device
"looking for new devices"
("suche neue Geräte" in german)

I can get -lastalexa to work, but fails to speak, or run routines on 4 2nd gen echo dots and 1 echo plus, It doesn't work but there's no error. Here is the output for an automation (routine) that opens a garage door:

core-ssh:/config/alexa# bash alexa_remote_control.sh -e automation:'Open Door'
setting default device to:
Laundry Room
sending cmd:automation:Open Door to dev:Laundry Room type:A3S5BH2HU6VAYF serial:G090L91182330V20 customerid:A17XZBYWJG1SFN
Running routine: Open Door
HTTP/1.1 0 x-amzn-RequestId: 29ef6941-f371-11e8-8b75-e72497d798ce
Access-Control-Allow-Origin: https://alexa.amazon.com
Content-Encoding: deflate
Vary: Origin
Access-Control-Expose-Headers: x-amzn-dat-gui-client-upgrade,X-Amzn-Error,loginUrl,X-Amzn-RequestId,x-amzn-alt-domain,Date,Location
Access-Control-Allow-Credentials: true
Date: Thu, 29 Nov 2018 00:53:19 GMT
Connection: close

Here is the output for trying to speak:

core-ssh:/config/alexa# bash alexa_remote_control.sh -d 'Jeffs Dot' -e speak:'test'                             sending cmd:speak:test to dev:Jeffs Dot type:A3S5BH2HU6VAYF serial:G090L90965222ET4 customerid:A17XZBYWJG1SFN
Sequence command: Alexa.Speak
HTTP/1.1 0 x-amzn-RequestId: 645201df-f371-11e8-bb41-53424d01fabd
Access-Control-Allow-Origin: https://alexa.amazon.com
Content-Encoding: deflate
Vary: Origin
Access-Control-Expose-Headers: x-amzn-dat-gui-client-upgrade,X-Amzn-Error,loginUrl,X-Amzn-RequestId,x-amzn-alt-domain,Date,Location
Access-Control-Allow-Credentials: true
Date: Thu, 29 Nov 2018 00:54:57 GMT
Connection: close

I am new to alexa-remote-control.sh so perhaps its something I'm doing something wrong?

Here is output from successful -lastalexa query:

core-ssh:/config/alexa# bash alexa_remote_control.sh -lastalexa
Bathroom
core-ssh:/config/alexa#

I'm in the US:

LANGUAGE="en-US"

AMAZON='amazon.com'

ALEXA='pitangui.amazon.com'

Currently the script fails with sed: illegal option -- r.
macOS uses BSD tools, hence the options are somewhat different.

So, I've been using this script for about a week now and it's been absolutely amazing. It's been incredibly fun and helpful, and I can't wait to see what I'll do next with it.

That's where this issue comes in: I was wondering if there's currently any capability that supports accessing the "alexa show 5" video webcam. I know you're able to use the drop in feature but I'd love to know if there's a more functional version implemented in this script.

If not, are you aware if it's a possible feature to be implemented later down the road?

Thanks, - Joshua.

I'm not sure how you're reverse engineering these requests, but I'd love to see spotify added :)

First of all thanks!
The script works like a charm.

I would like to send multipe speak commands and get them enqueued so they are all played (every single one).
The behaviuor now is that a new tts command interrupts the one already beeing played.
I tried to include the parameter "playBehavior":"ENQUEUE" in the command (I saw it in the custom skill response api). But no luck, same behaviour.

Does anyone know if it is possible?

Thanks!

Hi there I have been having a play with the script and different settings, here is a list of my changes and the outcomes.

I can login successfully with the following:

| LANGUAGE | AMAZON | COMMENT |
|===============================================================|
| de-DE | amazon.de | ERROR possibly get a capcha login screen.
| de-DE | amazon.com.au | Cookie expired,,, Login failed Aborting.
| en-GB | amazon.co.uk | ERROR possibly get a capcha login screen.
| en-US | amazon.com | ERROR possibly get a capcha login screen.
| en-NZ | amazon.com.au | Cookie expired,,, Login failed Aborting.
| en-NZ | amazon.de | Cookie expired,,, Login failed Aborting.
| en-AU | amazon.com.au | Cookie expired,,, Login failed Aborting.
| en-AU | amazon.de | ERROR possibly get a capcha login screen.
|_______________________________________________________________________________________________________|

Whenever I try to connect to com.au I always get the same error shown in detail below. I do NOT get the capcha error unless I am redirecting to a non native site.

./alexa_remote_control.sh
cookie does not exist. logging in ...
cookie expired, logging in again ...
log in failed, aborting

in order to get past the Capcha ERROR, I can disable javascript and clear the cache on a browser, heade to the http URL of the remote regional site and login it will ask for a capcha and once that is successfully completed I am redirected to the native site (com.au) where I can then enter my username password combination and get logginged into the web app.
Once I have done this is a rerun the script I see this message.

./alexa_remote_control.sh
cookie does not exist. logging in ...
device list does not exist. downloading ...
no alexa command received

I however have had no luck when setting the AMAZON variable to amazon.com.au; I think there is some issue with the script in the redirect case that is preventing it functioning.

Regards

Paul

Can you please support Alexa.Music.PlaySearchPhrase? I found it on https://github.com/keatontaylor/alexa_media_player (where I also found the other commands I recently implemented).
I do not have the required shell scripting capabilities otherwise I would also have implemented it.

The thing is: if you are an Amazon Music Unlimited subscriber as I am you can simply play any song which is available within that subscription. However, these songs are neither imported nor purchased so I cannot use any of the existing methods implemented.

Hi,
Is it possible to add tracks to a queue and not to play them straight away when I call "https://alexa.amazon.it/api/cloudplayer/queue-and-play" ?

I can't find a way to get the items added to my shopping list

which is the command?

Thanks

Hi,

I have 7 echo dots around the house and trying to get them to say something, but I get a few (it varies from 2 to 5), then I get a message of ‘Rate Exceeded’ and the script stops. any view on why this is?

Hello,
Tank you for your script it work perfectly on echo dot 3.
A simply question, it's possible to have the "loop" command?
I have tried to add line in the script remote_control_plain but no work with an error :
In the script :
shuffle)
COMMAND='{"type":"ShuffleCommand","shuffle":"true"}'
;;
loop)
COMMAND='{"type":"LoopCommand","loop":"true"}'
;;
In console :
~ $ sudo /home/pi/domoticz/alexa_remote_control_plain.sh -d "Martial - Echo Dot" -s d4aa4219-78e2-49d9-8f55-e6d686c30a77:1 -e loop
sending cmd:{"type":"LoopCommand","loop":"true"} to dev:Martial_-_Echo_Dot type:A36DOYMUN6DTXA serial:G090U60788740S7B customerid:A2LFOBGMAQ91H0
{"message":"Invalid command specified"}

Tank you

Hat Amazon evtl etwas beim anmelden verändert?
Ich bekomme immer und immer wieder Captcha-Abfrage beim anmelden mit Chrome ohne Java. Sitze jetzt schon eine Woche und gebe haufenweise Captcha-abfragen ein und warte ohne das Script aktiv zulassen . Leider meldet sich das Script nicht mehr bei Amazon an.
Bekomme immer wieder folgende Fehlermeldung Amazon Login was unsuccessful. Possibly you
get a captcha login screen.
Try logging in to https://alexa.amazon.de 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)

To avoid issues with captcha, try using Multi-Factor Authentication.
To do so, first set up Two-Step Verification on your Amazon account, then
configure this script (or the environment) with your MFA secret.
Support for Multi-Factor Authentication requires 'oathtool' to be installed.

MFA habe ich nicht aktiv.
/tmp/.alexa.login wird nicht erstellt bzw. nicht auffindbar

Has Amazon possibly changed something when you log in?
I get captcha query again and again when logging in with Chrome without Java. Sit a week now and give tons of captcha queries and wait without the script to allow active. Unfortunately, the script no longer logs on to Amazon.
Always get the following error message 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 you have all Related links deleted and Javascript disabled!

(For more information have a look at /tmp/.alexa.login)

To avoid issues with captcha, try using Multi-Factor Authentication.
To do so, first set up Two-Step Verification on your Amazon account, then
configure this script (or the environment) with your MFA secret.
Support for Multi-Factor Authentication requires 'oathtool' to be installed.

I do not have MFA active.
/tmp/.alexa.login is not created or can not be found

These commands should also be supported:

• goodnight
• joke
• calendartoday
• calendartomorrow
• calendarnext

Everything was working well, but since some times, the script was not working.
I had a look and sens it fail because cookie expired and a captcha was required. So I made an update of the cookie and the error has gone... but commands seems to have no effect: my device have no reaction.

I have the following feedback in the console:

sending cmd:speak:test test test to dev:Echo Salon type:*************
serial:********************** customerid:*********************
Sequence command: Alexa.Speak
HTTP/1.1 0 x-amzn-RequestId: f6ddf25f-2d68-11e9-bfd6-a39ce45b897c
Access-Control-Allow-Origin: https://alexa.amazon.fr
Content-Encoding: deflate
Vary: Origin
Access-Control-Expose-Headers: x-amzn-dat-gui-client-upgrade,X-Amzn-Error,loginUrl,X-Amzn-RequestId,x-amzn-alt-domain,Date,Location
Access-Control-Allow-Credentials: true
Date: Sun, 10 Feb 2019 19:20:45 GMT
Connection: close

Do you see something I don't ?

Is there a way play audio on Alexa pyhsical device by using alexa-remote-control ?

Is there any way you can retrieve your shopping list using the script?
The data is there at https://alexa.amazon.co.uk/spa/index.html#lists/namedLists
I've tried tinkering with the script but can't find a way to GET anything. Think it's possible?

Hi.

Would be nice to be able to set the device's volume not only to play or say something, e.g. at night, set volume of all devices to 30%, and at morning set them at 80%.

Is it possible to do it now? I have been trying with no success.

Thanks! Good job!

hi - using it on raspberry 👍

it works for three times and then this message appears:

sending cmd:{"type":"PlayCommand"} to dev:Echobad type:A3Sxxxx2HxxYF serial:G0xxxxxxx1860WED
{"message":"No routes found","userFacingMessage":null}

command was: "alexa_remote_control_plain.sh -d Echobad -e play"
on the alexa-amazon-website : the Echobad Device is showing that it is not connected - after 5 minutes it works again (sometimes) and I can also use your script ! the script is doing something strange with the echo.dot device

any ideas

Seems to have recently stopped working for me. Can't even get the list of my devices. Suspect amazon have changed something?

Hi,
I actually don't use the script, but help maintain a python version for Home Assistant that was based off this script.

While implementing lastAlexa functionality for ourselves, we ran into an issue where if a user had multiple Alexa devices that heard the event, it's possible that relying on the last activity record wouldn't work because it the activityStatus was a DISCARDED_NON_DEVICE_DIRECTED_INTENT instead of a SUCCESS. This apparently happens if multiple devices have to decide which one needs to respond to the same command. I coded a solution that pulls 10 records from the API and does a for loop until it find a success. I thought I'd report it to you since you would have the same bug we ran into. While I'd normally provide a pull request, I've been too lazy to set up the script to test and debug it but hopefully I've provided enough info so you can implement a fix easily.

When I run the script I receive the following login error:

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)

When I try to login to https://alexa.amazon.com with javascript disabled I get a captcha screen. I looked at /tmp/.alexa.login and it shows a captcha request as well.

Any suggestions?

Hello,
Thank you for your job. Just a small info about a failed update from script v0.10b to v.v0.12a
New version returns ERROR : unkown (oups a typo error !) device dev:mydevicename (with mydevicename containing spaces)
Previous version was working with the same "mydevicename"

JC

Good evening everyone,

Did anyone of you manage to run the option alexa_remote_control.sh -s ???

I have searched for all possible trackID imaginable on Amazon Music, I tested all the keys that existed and I do not find how it works.

I arrived there with for example 'Artist' 'Album' but it's not easy to find what to put, I guess with trackID it's easier.
For example: /var/www/html/plugins/script/core/ressources/alexa_remote_control.sh -d "Le salon" -s "Joe Dassin" "Les Champs-Elysées"

If you found where are the trackID, I'm interested with a huge pleasure !!!

iHello,

Tank you for your script, it work perfectly, but i not understand how i use the fonction -w, for play my playlist "Favoris" for example. I can do use the command play, speak, volume but for play a playlist or a track or an album, i don't no.
can someone explain to me?

thank you beforehand

Script recently stopped working for me. I suspected captcha so tried manually logging in with javascript disabled. When it's disabled I can NEVER logon first time. First logon always results in "Enter a valid e-mail or mobile number�" re-entering password second time results in successful login. Similar sort of amazon auth issue reported here speric/kindle-highlights#11

Is it possible to modify script to auto retry?

Due to the sed regular expression, full stops are missing out of anything you send to TTS which means whatever Alexa says comes out in one full sentence 😃.

Can be resolved by adding the full stop into the expression (.) like the below.
Doesn't seem to cause any issues when I've tried it and puts in suitable pauses in the TTS.

SEQUENCECMD='Alexa.Speak'
TTS=$(echo ${COMMAND##*:} | sed -r 's/[^-a-zA-Z0-9_,?!\. ]//g')
TTS=",\\\"textToSpeak\\\":\\\"${TTS}\\\""

Could probably do similar for semi-colon ';' but I've not tested this. Before the change the only way to stop her mid flow was to use a hyphen '-'.

Hello. This script usually works well and I use it to make alexa do and say a lot of thing. Now I have this return code 256. What does it mean ?

Hi,
This is such a great little script. Thank you!
I am using it to trigger automations at the moment. I would like to have the ability to trigger individual home automation devices? I couldn't really see anything in Alexa's API, but if you point me in the right direction I can have a go at extending the code :)

Background: I have 4 Amazon Echos in the house. 2 of them were originally activated by me, 2 of them were activated by my wife. All 4 of them are shown in my Amazon account, and my wife's account. When we are at a given device we can say "Alexa, switch accounts". This way my wife can play her music and I can play mine.

Problem: This script will successfully pull all 4 devices and show them, however, I can't control the ones originally activated by my wife. The reason is because this script is making the web request with my wife's deviceOwnerCustomerId (reported by Amazon as the owner), but I'm signed in as myself (a different deviceOwnerCustomerId). If I change the code to always use the deviceOwnerCustomerId of myself (hardcode) the script works fine.

Solution: I believe the fix for this is this component should access https://alexa.amazon.com/api/bootstrap and pull the deviceOwnerCustomerId of the current user. It would only need to do this one time (perhaps after it stores the cookies). It should then use this deviceOwnerCustomerId to make the calls, and not try to make the calls for another user that is not signed in. At the very least, perhaps a config option can be setup so that you can override the deviceOwnerCustomerId for all the calls.

I understand this code was copied from another library - I actually contacted the author of that plugin as well.

This was working fine just now. I was calling it a few times for some test and it just stopped.

I get this from the command line on ALL 4 of my Echo Dots:

parse error: Invalid numeric literal at line 8, column 10
parse error: Invalid numeric literal at line 8, column 10
ERROR: unkown device dev:myechodot

I changed it to use the script alexa_remote_control_plain.sh, and then it worked:

device list does not exist. downloading ...
sending cmd:speak:Hello to dev:myechodot type:...........................

So something to do with the device list, needs re-downloading? How?

Hello,

I have a problem the command -e vol no work on the other hand the order -e speack work
the order -e vol is no longer available?
script version 2019-06-28 alexa_remote_control.sh

sudo ./alexa.sh -d Salon -e vol:50 sending cmd:{"type":"VolumeLevelCommand","volumeLevel":50} to dev:Salon type:XXXXXXX serial:XXXXXXXX customerid:XXXXXXXX {"message":"No routes found","userFacingMessage":null}

I have tried the component and installed it thru HAC and added the info to the config file. Did the restart and the captcha keeps popping up after the restart.

Any suggestion how to fixed it or doing something wrong?

i noticed that amazon did sent me authentication emails with code and suspects was entering the captcha thru home assistant

#alexa_media:

accounts:

- email: !secret amazon_user

password: !secret amazon_password

url: amazon.com

Raspberry pi 3B+
HA image
0.95.4
firefox

Hi - is it possible to read the routine names like e.g. the device list?

I executed some commands. Output:

root@SmartHomeV2:/var/homebridge/devices/sprachausgabe# ./alexa_remote_control.sh -e automation:'aufwachen'

setting default device to:
MatteosZimmer
sending cmd:automation:aufwachen to dev:MatteosZimmer type:++++++++++++++++ serial:++++++++++++++ customerid:++++++++++++++++
<
But alexa doesnt do anything. The config file seems correct.

Hi,
thank you for the nice script, it's working perfectly. Is it possible to get the actual volume from a device back as an info? Perhaps like actual volume is set to level 5 or to 50%.

Is there an automated way to extract the respective cookies from an Alexa account?

It's a bit annoying having to update it every time it breaks.

Thanks,
Peter