Echo Devices (Alexa) as Media Player - Testers Needed

I’m having trouble setting up the integration, I installed it through HACs and it appeared in my integration page. Everything seems to work up until I need to get a otp, I’ve tried all of the options and I never get a text or push notification. If I need to attach any logs please let me know. Thanks!

Hello, this integration has recognized my Alexa devices, also the groups. Is it possible to create an automation and as an entity a group? For example, when you open a sensor, the group of all the Alexas in my house will sound.
Thank you

Hi @PlayedIn,

Very nice setup! My wife wants your concept for the wall tablet. I’ve taken your code and set everything up.
I struggle with the card that executes the script. It’s functional but it displays the default ‘ execute’ command.

I noticed you have replaced the ‘ execute’ command with an icon. That’s what i’m after as well. I’ve tried implementing a tap action to call the script.turn_on service but i can’t figure it out.

Could you please tell me how to do it or share your code?

1 Like

For each of your scripts, add an entry in customize.yaml. The can_cancel: true portion is the important part. The can_cancel property exchanges the text ‘Execute’ with a toggle that allows the script to be canceled. For example:

script.radio538:
  friendly_name: Start Playing
  icon: mdi:play
  can_cancel: true

1 Like

Ah, it is in fact a toggle. I guess your background fooled me as on the screenshot it looked like a button to me instead of a slider. Thx for the quick reply!

1 Like

Yeah, if you wanted to use an icon instead of a toggle, I would use the custom: button-card. The button-card can execute a script. You could use a horizontal-stack card to create a card that contains the button-card, text-element card, and/or entities-card which looks exactly like that whole row in that conditional card except instead of the toggle you would have the button-card. That button-card can do and look like pretty much anything.

Here’s an example of a button to execute a script:

              - type: "custom:button-card"
                style: |
                  ha-card {
                  background-image: url("/local/cardbackK.png");
                  background-repeat: no-repeat;
                  background-color: rgba(50,50,50,0.3);
                  background-size: 100% 0px;
                  border-radius: 20px;
                  border: solid 1px rgba(100,100,100,0.3);
                  box-shadow: 3px 3px rgba(0,0,0,0.4);
                     }
                entity: script.cc_on
                name: " "
                icon: mdi:closed-caption
                color: rgb(255,20,147)
                action: toggle                        

2 Likes

Thanks for the help. Only thing i would change is this:

Action: toggle

Into:

Tap_action:
  action: toggle

This way the card acts like a button (instead of bringing up the info popup where you have to execute the script).

After updating to 0.109.1 I had to reinstall this and add the integration again. I have my echo media_players back, but the sensor.next_timers are all not there. Any ideas how I could get them back?

My alexa integration stopped work since 4/27. this is what I found in the log:

ERROR (MainThread) [homeassistant.setup] Setup failed for alexa_media: Unable to import component

I’ve tried uninstall it from HACS, but not able to remove it from the integration page, after I click delete icon and confirm, the integration is still here.

Please help how can I solve this?
HA version is 0.104.3

If the integration complains it cannot load, then there’s no way it’s removing from the integration page will work. That page requires the integration to remove everything.

Reinstall from HACS as the error you’re seeing indicates the files are not available.

Are you excluding devices? Are you connected to the right domain? There’s a bunch of possible reasons but it’s hard to figure it out without more info on your setup or logs.

@alandtse thank you very much for the continous improvement of this component.

can you please provide an example of how to use the “queue_delay” command?
as we’re already using “delay” or similar, we want to avoid adding additional delays, if there’s a default 1.5 second

I’m not excluding any devices. When I set up the integration the ‘exclude’ field is empty. I am connected to the correct domain (.co.uk). I’ve looked in my logs but can’t see anything about the missing sensors.

I previously had custom_components.alexa_media: debug on, but couldn’t see anything regarding the sensors. As I said ealier, the media_players are there and working normally.

I’m enabling debuggging again and will post a complete log here, thanks!

It’s not a command. It’s an option. Essentially, certain commands (e.g., notifications, volume) can be queued where they wait for the next command before issuing. This introduces a delay. Before 2.6, it was set at a default of 1.5 seconds of waiting for the next command before issuing. Now you can tweak that value.

It’ll be in the startup logs. It probably makes sense to message me on discord or DM me so your logs aren’t public.

Thanks @alandtse, DMed you.

Thank you alandtse!

Yes I did try uninstall/reinstall and also downgraded to 2.4.14 without error but the media_player.xxx always showing unavailable in state page.
I also tried to completely uninstall it. In HACS page I can uninstall it, but in the integration page, I am not able to delete it.

After enable log, there is exception in the log, detail posted here https://pastebin.com/e4Bn4guT , the last few lines are:

File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/config/custom_components/alexa_media/__init__.py", line 34, in <module>
    from homeassistant.helpers.update_coordinator import DataUpdateCoordinator, UpdateFailed
ModuleNotFoundError: No module named 'homeassistant.helpers.update_coordinator'

Is there any dependency on which version of HA? currently I am on 0.104.3

@alandtse thank you for yoru response. Correct “option”, my mistake.

Yes, you need HA 106 for any version about 2.5.13. HACS should have prevented you from installing assuming you’re on the latest version of HACS.

1 Like

I usually keep HACS and integrations are up to date from time to time, but not HA docker itself, afraid of breaking changes :sweat:

I just upgraded HA to latest, reinstalled alexa and works fine now.

Thank you!

Thanks Thomas. After your conversation with niconath I tried your solution. It works great except for the Multiroom speakers. Did you get this working?

  - service: media_player.play_media
    data_template:
      entity_id: >
        {%- if states('input_select.media_player') in ['Overal', 'Beneden'] -%}
          media_player.alexa_kitchen_2
        {%- elif states('input_select.media_player') in ['Keuken'] -%}
          media_player.alexa_kitchen_1
        {%- elif states('input_select.media_player') in ['Woonkamer'] -%}
          media_player.alexa_livingroom_1
        {%- elif states('input_select.media_player') in ['Badkamer'] -%}
          media_player.alexa_bathroom
        {%- elif states('input_select.media_player') in ['Mobiele'] -%}
          media_player.alexa_mobile
        {%- else -%}
          script.empty
        {%- endif %}
      media_content_id: >
        {%- if states('input_select.media_player') in ['Overal'] -%}
          {{ states('input_select.radio_station') }} on the Alexa Everywhere group
        {%- elif states('input_select.media_player') in ['Beneden'] -%}
          {{ states('input_select.radio_station') }} on the Alexa Downstairs group
        {%- else -%}
          {{ states('input_select.radio_station') }}
        {%- endif %}
      media_content_type: TUNEIN