Echo Devices (Alexa) as Media Player - Testers Needed

Share your Projects! Custom Integrations
84

@keatontaylor Is it possible to control the volume of my Echo with this addon? Thanks in advance for a reply.

85

I have this installed and can confirm that you can change the volume of your echo

86

@keatontaylor - fantastic work. Really appreciate sharing!

87

@shire210 Great, how did you manage that? I’m just a HA beginner :wink:

88

To adjust the volume? Once you add the component, there is a volume slider that you can adjust:
image

Or you can do it as a script/automation:

    - service: media_player.volume_set
      data:
        entity_id: media_player.office_dot
        volume_level: .6
1 Like
89

Thanks a lot !!!
Now have to find a way to save the previous volume_level before rising volume and restore that level after the message.
I use my echo mainly for background music/radio, so with low volume, and then the volume level of a message is to low.

1 Like
90

Volume is a bit tricky. There needs to be an active queue (playing or not) for the volume controls to work. This is a limitation of the unofficial API that the Alexa website users.

91

Hi @keatontaylor ,

I guess I missed something, but:

# docker pull ketaontaylor/amd64-addon-alexa-api
Using default tag: latest
Error response from daemon: pull access denied for ketaontaylor/amd64-addon-alexa-api, repository does not exist or may require 'docker login'
92

sorry… my bad. Just did a copy/paste and later noticed that keatontaylor was misspelled.

1 Like
94

:sweat_smile: Apparently I seem to misspell my name.

1 Like
95

Just installed your addon, simply awesome! Media Control, Cover display, Volume Control, TTS, all is working great!

96

Any chance to get instructions to use with a docker instance of HA on unraid? I tried to pull the docker image but received error.
root@TornTower:~# sudo docker pull ketaontaylor/amd64-addon-alexa-api
Using default tag: latest
Error response from daemon: pull access denied for ketaontaylor/amd64-addon-alexa-api, repository does not exist or may require ‘docker login’

1 Like
97

@Charles_Brown, there was a typo in the docker pull command. (my name no less)

docker pull keatontaylor/amd64-addon-alexa-api

Follow the rest of the instructions above for the rest.

98

How would i use this within node-red? ive tried a service call node with

Domain: media_player

Service: alexa_tts

Data: {“entity_id”:“media_player.office_dot”,“message”:“Test message”}

I can call the service from within HA and it works fine just dont know how to use it within node red.

2 Likes
99

Thank you. I got the docker image installed. There was a trick to it though, I had to specify the “tag” since there was no “latest” tag available.

keatontaylor/amd64-addon-alexa-api:0.4

I created a config.json file and populated it with my Alexa login info. Then I added alexa.py to my Home Assistant /custom_components/media_player directory.

Thank you. I got the docker image installed. There was a trick to it though, I had to specify the “tag” since there was no “latest” tag available.

keatontaylor/amd64-addon-alexa-api:0.4

I created a config.json file and populated it with my Alexa login info. Then I added alexa.py to my Home Assistant /custom_components/media_player directory.

Ignore the following section. I figured out my mistake, I did not read the first post before adding my media_player definition. I was trying to manually define each echo device.

100

Everything worked just fine until I installed 0.4 and HA 0.73.1. Now it wont find the entity mediaplayer.alexa… Anyone alse who have the same error?

101

You should use the docker IP, not the device IP.

102

It seems that the docker image doesn’t play very well with portainer. If you try to restart it from portainer you got this on the logs:

Fatal server error:
(EE) Server is already active for display 99
    If this server is no longer running, remove /tmp/.X99-lock
    and start again.

any hints?

103

Here is how I have it set up in Unraid. based on your eror message, I think you need to include the tag “:0.4” on the end of the repository name.

IMG_0033
IMG_00332208×1242 145 KB

1 Like
104

@keatontaylor thank you for the component
trying follow the container installation, but getting these errors in the docker log

Mon, 09 Jul 2018 12:40:53 GMT nightmare running
There was an errorInternal endpoint: 
curl -X POST -d "tts=Ask Alexa team for a proper TTS API" -d "deviceSerialNumber=deviceSerialNumber" http://localhost:8091/alexa-ttst request for getDevicesTypeError: 
Cannot read property 'alexaURL' of null
    at Object.getDevices (/workspace/alexa-api.js:180:19)
    at /workspace/index.js:29:13
    at Layer.handle [as handle_request] (/workspace/node_modules/express/lib/router/layer.js:95:5)
    at next (/workspace/node_modules/express/lib/router/route.js:137:13)
    at urlencodedParser (/workspace/node_modules/body-parser/lib/types/urlencoded.js:100:7)
    at Layer.handle [as handle_request] (/workspace/node_modules/express/lib/router/layer.js:95:5)
    at next (/workspace/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/workspace/node_modules/express/lib/router/route.js:112:3)    at Layer.handle [as handle_request] (/workspace/node_modules/express/lib/router/layer.js:95:5)
    at /workspace/node_modules/express/lib/router/index.js:281:22