Echo Devices (Alexa) as Media Player - Testers Needed

[Steven_Rollason]

I originally had the alexa_media component configured via configuration.yaml, but have now switched over to using the config flow to make configuration easier (less restarts) but I’ve had a couple of issues:

1. I can’t find a way to change the included/excluded devices after the initial configuration without deleting and re-adding the integration. Is this the only way this can be done.
2. If I disable the unwanted entities in Home Assistant instead (from the Integrations or Entities pages) this still leaves the notify services for these. Do you know if these can be disabled in any other way?

[alandtse]

@jolly

how come one is seen as a speaker and the other is not?

That may be a bug and we’d need logs to diagnose why. Is that the only broken functionality?

@Shayne_Bergan

Guard alarm not working in latest Beta 0.103.0b0, let me know if you need logs

Thanks. We have an issue tracking.

@DevScientist

Any ideas?

Is everything working? Has the .pickle file expired requiring a deletion and relogin?

@maurizio53

How to get rid of them?

And more, one doubt. Is still needed the entry regarding alexa media_player inside configuration.yaml or not?

It’s a cosmetic error and not high priority to fix.
No you don’t need configuration.yaml anymore.

@zsmitchell

Is there something that has to be done differently when pushing the (below) script to an ecobee, as opposed to an Echo Dot?

I saw you figured it out but it’s a known issue where non Amazon devices lost Announce. You can only use TTS at this point.

@flippedcracker

I’ve added the integration and logged in with the captcha. Do I need to do something else?

Would need logs to diagnose but something didn’t load properly.

@jriker1

Please tell me I don’t have to reinstall the component.

You have to delete and readd. It won’t impact any scripts/automations though as everything will be readded with existing entity_ids.

@Steven_Rollason

1. I can’t find a way to change the included/excluded devices after the initial configuration without deleting and re-adding the integration. Is this the only way this can be done.
2. If I disable the unwanted entities in Home Assistant instead (from the Integrations or Entities pages) this still leaves the notify services for these. Do you know if these can be disabled in any other way?

1. See answer to jriker above.
2. Notify is weird in HA like device_tracker so I don’t believe it has the disable functionality yet.
   Probably should open a issue with HA to have them figure out how they want to handle it. While we could probably add some functionality to try to remove them if the media player entity is disabled, it seems a bit hackish to rely on components to figure it out.

[zsmitchell]

@alandtse

n and log

Thank you for confirming!

[jriker1 (John)]

@alandtse

You have to delete and readd. It won’t impact any scripts/automations though as everything will be readded with existing entity_ids.

Thanks. What I’ll be interested in is if the below shows or does anything with Media Player:

https://www.motorola.com/us/products/motorola-axh01-wireless-home-telephone-alexa-built

I purchased the four handset version and it’s tied to Amazon but technically you have to push a button down to activate Alexa and do not think each handset gets exposed to Amazon individually.

[wmaker (Tommy Long)]

I just upgraded to 0.103.0. The following shows up in my log:
2019-12-12 12:45:07 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform alexa_media is taking longer than 60 seconds. Startup will proceed without waiting any longer.

As such the alexa_guard entity is not getting created.

I don’t know if related but I also noted the following comment in the blog for version 0.103.0:

0.103: Happy Holidays, Service calls, StarLine, GeoNet NZ and Proxmox

From this release every integration based on alarm_control_panel (like this one) won’t work because they introduced an abstract method supported_features. It’s obviously a breaking change, but it wasn’t listed as such…

[AhmadK (akasma74)]

I’m afraid it’s not related - in my case it was an abstract function added to the base class alarm_control_panel…

[Pirol62 (Jörg Nauen)]

Hi,
I posted this issue before and you reported this as harmless.
But now I have it permanentely

That’s not a normal behavior from my point of view.
Is there anything I should do?

[joe8mofo (Josh)]

Restarted homeassistant on 102.3 and received a new message.
alexa_media_player 2.3.5

2019-12-13 10:34:31 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform alexa_media.alarm_control_panel: Platform not found (cannot import name ‘SUPPORT_ALARM_ARM_AWAY’ from ‘homeassistant.components.alarm_control_panel’ (/usr/src/homeassistant/homeassistant/components/alarm_control_panel/init.py)).
2019-12-13 10:34:31 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.alexa_media

[wmaker (Tommy Long)]

v2.3.5 solved the alexa_guard problem I was having earlier
Thanks!!

[jriker1 (John)]

@joe8mofo

Restarted homeassistant on 102.3 and received a new message.
alexa_media_player 2.3.5

Not the same but I’m getting:

2019-12-13 13:16:09 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform alexa_media is taking longer than 60 seconds. Startup will proceed without waiting any longer.

I’ve always seem complaints in my system about it taking more than 10 seconds like this:

2019-12-13 13:15:19 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Setup of platform alexa_media is taking over 10 seconds.

but this is new.

[alandtse]

Sorry, stay on 2.3.4 if not on HA 103. I thought the minimum HA version check would stop HACS from offering it more broadly.

[jriker1 (John)]

Think my 60 second giving up thing or whatever is gone now. Noticed there was an update from 2.3.4 to 2.3.5. So far not showing after reboot.

[poudenes]

Hello All,

After update to v2.3.5 I get this error when restart HA:

Unable to prepare setup for platform alexa_media.alarm_control_panel: Platform not found (cannot import name 'SUPPORT_ALARM_ARM_AWAY' from 'homeassistant.components.alarm_control_panel' (/usr/src/homeassistant/homeassistant/components/alarm_control_panel/__init__.py)).

[alandtse]

Read two posts above.

[poudenes]

I’m still on 0.102.3 not 0.103.0

[alandtse]

Then don’t use 2.3.5.

[poudenes]

will update HA this weekend

[h4nc]

I’d like to confirm that I got all the new switches and sensors by switching to exclude_devices (from include_devices).

I than had a lot of unnecessary new entities, which I disabled directly in the core.entity_registry file (in the .storage folder). Be careful with this, because messing this file up, will brake your ha instance.
So entities that I want to be disabled got:

"disabled_by": "integration",

instead of

"disabled_by": null,

Restart ha after that.

[alandtse]

@h4nc

I than had a lot of unnecessary new entities, which I disabled directly in the core.entity_registry file (in the .storage folder). Be careful with this, because messing this file up, will brake your ha instance.

There’s a UI under the Integrations section to disable entities. You don’t have to do it manually.

[h4nc]

Thanks. I know, but it takes a lot more time to secant every new entry in the Integrations section and disable every single entry.
For me it’s easier to do it in the entity_registry file.