is there a quick way to announce to all echos? instead of listing each one in a json list. i don’t see anything about it in the docs.
What is the correct way to add this to HA? I see there is different solutions.
This is a snippet from my configuration.yaml
group:
house_talk:
name: house_talk
view: no
entities:
- media_player.kitchen_echo
- media_player.livingroom_echo_dot
- media_player.bedroom_echo_dot
- media_player.bathroom_echo_dot
- media_player.guestroom_echo_dot
- media_player.richard_s_tablet
- media_player.sandy_s_tablet
1.3.0 is out.
This version support Guard Mode settings along with various bug fixes. We finally removed the media_player.alexa_tts service. Use the notify component instead.
We’ve swapped to supporting HACS since custom_updater is deprecated. This release should work for custom_updater, but I didn’t test it nor do I intend to fix any issues on it.
For those on hassio, you may have to restart 2-3 times before HA will load the dependencies. It doesn’t look like something we can control.
Features:
- Add Alexa Guard mode support as an alarm_control_panel. Use ARM_AWAY to enable. (resolves #186)
- Add HACS support. We will deprecate custom_updater shortly; please migrate. Thanks @xatr0z(resolves #201)
Fixes:
- Remove async references (resolves #171)
- Fix bug where announce did not work for multiple accounts (resolves #210)
- Add further existing entity checks (resolves #180)
- Add additional websocket reconnect logic (resolves #181)
As always, please use the the Wiki and FAQ if you need instructions or have questions. Also, please help in documenting features in the wiki since this thread is basically unsearchable now. We also use GitHub for bug reports/feature requests .
1 Like
Currently this is only available in the US right?
Yes, but it should only create the alarm_control_panel if it discovers the Alexa guard entity in your devices. Of course, I don’t have a non-US account so it’s possible Amazon has enabled the entity in the device list so we may try to load it even if it’s not functional.
Alarm panel is working perfectly… Good man
Just updated to v1.3.0, no issues so far, thanks for the continued work on this component. 
Updated to v1.3.0. Good
You can add it here https://github.com/home-assistant/custom-components-wheels that way the wheels for the dependencies are pre buildt 
I’ve switched to the newest release using HACS and adding the repo manually in settings.
Everything seems to be working as far as the media players getting recognized (i’m not at home to test that they actually say anything, tho) but I’m getting the following error in the log:
2019-06-23 09:59:32 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Error while setting up platform alexa_media
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/alexa_media/alarm_control_panel.py", line 34, in setup_platform
hass) \
File "/config/custom_components/alexa_media/alarm_control_panel.py", line 73, in __init__
['LambdaBridge_AAA/OnGuardSmartHomeBridgeService']
KeyError: 'LambdaBridge_AAA/OnGuardSmartHomeBridgeService'
I’ve restarted three times waiting 5 to 10 minutes between restarts and the error keeps returning.
I’m running non-hassio HA in Docker.
1 Like
I have followed the same installation and have exactly the same error in the log, all notifys and media players work OK though. On Hassio and in UK
- Add HACS support.
With which path is your plugin entered under HACS. With ‘keatontaylor / alexa_media_player’ it does not work. Latest version 1.3.0 is installed.
Same problem here, but in hassio.
Thanks PR submitted. Also, I noticed you’re a mod, any way you can update the first post in this thread with an update at the top to go to the Wiki for the install instructions and latest info? The existing links are broken and people regularly come in and we have to redirect them.
Fix should be here. Need someone to test and confirm before I push out.
Instructions here.
1 Like
I just tried it…I think.
I wasn’t sure exactly how to do it so I made an educated guess.
I copied my existing directory and renamed my existing directory to aleaxa_media.old. I then copied the alarm_control_panel.py and media_player.py files from the dev branch (most recently changed files?) into the current directory. Saved them and restarted. Same error.
If that wasn’t the correct procedure let me know and I can try again.
Just installed 1.3.0 (using Custom Updater). Had the same issue where everything works as before but now getting the “LambdaBridge_AAA/OnGuardSmartHomeBridgeService” error. As I was typing up this message, I enabled Alexa Guard in my Alexa app and restarted HA, and now the error is gone!!.
Alexa Guard - For those like me that didn’t know anything about this, Alexa can be configured (via the Alexa App) to detect smoke detectors/CO detectors blaring out as well as glass breakage (and can act upon it too). You can subsequently turn this detection on and off with your App of course using Home or Away button, but you can now also turn this on and off from this wonderful code!!
Use the services: alarm_control_panel.alarm_arm_away or alarm_control_panel.alarm_arm_home.
You should see a new entity “alarm_control_panel.alexa_guard_xxxx” from which these services are used for.
OK, I checked the changes and the commit changes weren’t in the code so now I think I figured out how to really use the commits, but I may have done it the hard way.
I copied over only the changed portions of the files and pasted the changes into the alarm_control_panel.py file.
I restarted and the error is gone.