Echo Devices (Alexa) as Media Player - Testers Needed

Share your Projects! Custom Integrations
5634

The below works, but how to delete it?
Currently its nowhere to be found on the Show or app, yet it is in the random slideshow…

  - service: media_player.play_media
    data:
      media_content_type: image/png
      media_content_id: https://home-assistant.io/images/cast/splash.png
    target:
      entity_id: media_player.echo_show_5_2nd_gen
5635
5636

oh shite, I read that undo twice, well before I got it working, doh. cheers

5637

I have 3 Ring lights connected to my Echo 4.

(I don’t know what the official name of the product is but it’s the Echo with the built in Ring Lighting Bridge).

Anyway 2 of the 3 were discovered easily by this integration. The 3rd one is the Ring Transformer. The only thing I can think that is different is that the Transformer showed up in the Alexa app as a switch while the other two showed up as lights.

But the other two actually are more complicated as they have motion detection and dimming capabilities. The transformer is just straight on/off.

I’m wondering if I can provide any logs or help at all with testing to get this device discovered by the integration.

Thanks.

5638

Hi all,

Is anyone having an issue where the last_called attribute is not populating/updating?

It was working fine, but now it’s stopped working (I’m not sure why).The attribute just states “null”.

There are no errors in my HA logfile.

Thanks,

J.

5639
5640

In addition to what Didgeridrew wrote: Read the GitHub Thread.
last_called state attributes showing as null; api/activities returned 404:Not Found:text/html · Issue #2089 · custom-components/alexa_media_player (github.com)
There have been some possible workarounds posted, which may help to improve the situation

5641

A fix that is working for me was posted 3 hours ago on a fork of the alexa_media_player repo on GitHub. At the time of this post one has to manually replace the alexaapi.py file with a revised version. The function of the alexa_media.update_last_called and notify.alexa_media_last_called services is restored by this fix.

5642

I am currently experiencing a problem where I keep getting served the Amazon captcha in a loop and cannot progress from that.
The configuration runs normally up to the point the external website is opened, then the captcha page is shown and after entering the correct code and clicking “Continue” a different code is shown, and this repeats again for each attempt. I tried it with several different browsers, and both with the local and the duckdns url as the “Home Assistant-URL”.
Any idea what else I could try?

1 Like
5643

Need some help over here. I made the mistake of fixing what wasn’t broken.
I’ve used this integration for a many months now just fine. and I always had an error telling me the domain didn’t match the one from the account. but everything worked so…
yesterday I had the genius idea of finally correcting that. and I did. and now I only get the 1 (one) entity created for my echo devices.
before this I had multiple sensors created by device. and while I won’t miss most of them. I definitely want the temperature sensor one back.
and yes. I do have the " allow devices connected via echo" ticked. and the warning I was getting in the logs is as expected gone.
anyone got any idea of what could be going on?
thanks.

5644

I don’t have the answer but if you’re stuck, maybe you can restore a backup to go back to your former working settings.

5645

Just figured it out…
After a couple reinstalls and fewer hairs on my head, turns out the “include devices” slot does exactly that and no sensors other than the actual media players are created. I thought that would exclude “this device” and “multiroom” but still create the associated sensors to the ones I included. It does not.
just left that blank and got the whole party again. I guess I’ll just disable the extra ones directly from Home assistant.

5646

Cool!
Just out of curiosity: when you say “I do have the " allow devices connected via echo” ticked." => where is that?
Can you share a screenshot please?

5647

Same issue. I’m trying to reconfigure, and it is stuck on the Amazon captcha. Anyone find a fix?

5648

Same for me. Tried a few things but no luck

5649

Actually nermind. Got it to work by doing this on my phone instead.

5650

Found a workaround detailed here Experiencing endless Amazon-Captchas while trying to install integration · Issue #2103 · custom-components/alexa_media_player · GitHub

You just mash the shit out of it until it works.

5651

I noticed that alexa censors out all curse words in tts messages with bleeps. If you want to get her to fˈʌkɪŋ curse. do this international phonetic alphabet trick.

Copy the ipa text to the ph tag below and have fun

oh <phoneme alphabet='ipa' ph='ʃˈɪt'></phoneme> I know how to curse now
3 Likes
5652

I know that this issue has been raised before and I wanted to confirm that specifying “type: announce” will not work with ecobee thermostats. I have an ecobee 4 thermostat and “type: tts” works, but “type: announce” doesn’t. Communications is enabled and Do Not Disturb is turned off in the Alexa app for the thermostat and announcements work to the thermostat when I send them from the Alexa app. Does “type: announce” work through an ecobee thermostat for anyone else?

I can use tts, but the announcement is nice because it plays the chime before, which gets people’s attention.

5653

Check out the ChimeTTS custom component in HACS, I think you’ll find that it will do as you wish.

1 Like