Echo Devices (Alexa) as Media Player - Testers Needed

ReDaLeRt · January 12, 2020, 3:26pm

Could you check this, please?

https://developer.amazon.com/en-US/docs/alexa/alexa-voice-service/alerts-overview.html#scenario2

Thanks.

alandtse · January 13, 2020, 1:36am

Thanks. The API wasn’t a secret. The issue is how would you interact with it in HA without building a new UI. The work on the component is entirely the HA backend so if the HA frontend doesn’t really support the use case, we don’t spend much effort on it.

javierdeluis · January 13, 2020, 6:51pm

has anyone had the problem where the echo won’t respond to a media_player.media_pause command? I can get it to play a playlist, change the volume, text to speech, but I can’t get it to pause playing reliably. Sometimes it works, sometimes it doesn’t, and I can’t figure out what’s causing it. I’m running the latest version from HACS. Tried re-installing, rebooting, etc.

Harry13 · January 14, 2020, 12:30am

routines are support in Alexa media play check the docs. Just not a routine that requires a device change, alexa say routines works great. Cause you can’t use the media_player stop, I use a routine to tell a joke and play a radio station in the bathroom when someone enters and closes the door and one to stop the audio playing when they leave

Harry13 · January 14, 2020, 12:31am

Yeah well stop doesn’t work either

Harry13 · January 14, 2020, 12:36am

No you can use them you, I already tried some of them that werent listed and they worked.

alandtse · January 14, 2020, 7:50am

As a note, found a bug with the queuing not working across all devices thanks to your logs. Shoudl be fixed in the next release. Also added an additional check in that release to automatically repeat requests so 429 errors should go away in the next release.

Only if supported in the App at this point. If you see the functionality, then we can probably add it at some point.

Is the issue when in a script or automation with multiple commands? Or when using manually? If it’s the former, its probably related to the 429 errors I mentioned above; otherwise to debug further we’d need logs.

AZSupra · January 14, 2020, 5:16pm

Do you have an example of one that worked? I tried a bunch and none worked. For example “train_01”

woody4165 · January 15, 2020, 3:25pm

Hi

I’ve just updated via HACS from 2.4.1 to 2.5.0 and it seems to be ok.

But when I do a Configuration Check I get this error

I’m on Hassio 0.103.6 and I’ve restarted it several times (3-4 times at least) and checked every time with the same result.

Until 2.4.1 all was ok.

I did also pip3 install alexapy with this result (sorry if I put images instead of text, but with the web terminal I haven’t found a way)

What can I check more?

Thanks

jeffkjolley · January 15, 2020, 7:41pm

Hi there-
I’m using HACS and I’m on Home Assistant v103.6. When I upgrade from 2.4.1 to 2.5.0, my Alexa Media integration disappears along with the option to install a new one, and I see the following in the log on restart:

2020-01-15 11:55:37 ERROR (MainThread) [homeassistant.setup] Setup failed for alexa_media: Integration not found.

When I revert back to 2.4.1, the integration comes back and everything works as expected. Any thoughts as to how I could troubleshoot this?

-Jeff

Shayne_Bergan · January 15, 2020, 8:46pm

Also same issue as above I’m on 0.104.0b5.

alandtse · January 16, 2020, 4:53am

Just released 2.5.1 that should resolve. Had a working release and then was dumb about wanting to see cool download counters in HACS. So I made one more edit that broke everything and then went to sleep. Thanks to @ludeeus for solving it for me.

Shayne_Bergan · January 16, 2020, 5:46am

All working with 2.5.1 thanks very much love your work

jeffkjolley · January 16, 2020, 4:05pm

Issue solved! Thank you so much for your work on this project.

wmaker · January 16, 2020, 6:46pm

Perhaps this has been mentioned before, but regarding the last_called attribute;
I have two echos now with this attribute set as true (they do have different timestamps). This use to not be the case, where only one would show as true, but its been a few releases since I tested it.

I do have my echos associated with two Amazon accounts, but they both are and have been set to use the same account ever since I started using this custom component.
I’m running 2.5.1 on 104.0.

alandtse · January 16, 2020, 7:00pm

And only one account is used by the component?

wmaker · January 16, 2020, 7:05pm

Yes, only one account is listed under the component’s configuration:

alexa_media:
  accounts:
    - email: !secret alexa_user
      password: !secret alexa_passwd
      url: amazon.com

terryhonn · January 16, 2020, 8:07pm

I’m seeing this too, running 2.5.1 on Hass.io 0.104.0b5 . I just updated to 2.5.1 this morning, thinking it might have fixed what I was seeing, so I’m pretty sure it was in 2.5.0 as well.

Ash_Wells · January 16, 2020, 8:26pm

Last Alexa only working for me in v2.4.1. Both v2.5.0 and v2.5.1 not working

Harry13 · January 16, 2020, 9:28pm

Great work on Alexa,
Question
why are all the, switches repeats, dnd, shuffle etc unavailable, the only thing avaliable is the media player.
How can i stop them from being created in the first place as i cant workout why i would ever use them. And they just fill up my list of devices in Alexa.
I rather prefer the ability to use the media_player stop service.