Thanks, that is very informative.
I would just send a notification to app rather then psychical device
Already performed the update to 2021.1.4 coming from 2021.1.2
I had to relogin which worked fluently and was the first time after 15 days.
Everythings fine but I’m still on 3.4.8
I thought the latest updates on HA affected HACS and/or this component. Thanks for clarifying it and thank you for all the hard work you have invested on it.
1 Like
great work with these last few updates, they’ve massively increased the time interval between reauths to several weeks. thanks for all you do!
1 Like
I am confused after looking at the wiki, It is possible to control the lights integrated in alexa with this?
Is there a better alternative?
This integration is for using your echo devices as media players to do announcments or actually play media and that functionality to be controlled via an output from HA.
To actually control devices with your voice you need either the Nabu Casa Cloud setup or emulated_hue or via a third party integration such as haaska.
Actually, with custom commands, you can in theory control the lights too since you can type in anything you can say to Alexa. Of course, this is only one way control and you won’t get status updates using this component. The other options provided by @finity give you the status updates.
Might be time to consider a rename?
True, I didn’t think about that.
there is even more.
the custom command can replace almost all others.
like @alandtse in last years i tried to create as much possible options to control alexa.
but the custom command (which i did build in also now (thx alandse) ) makes most other code i use obsolete.
a special command for next, previous, stop, etc. why?
that 1 command can do it all.
I’m having a similar issue:
tts doesn’t work with everywhere, and but does work with individual devices or a list of devices
announce doesn’t work with individual devices or a list of devices, but works with everywhere
announce works with individual device and group for me, I didn’t test a list of devices
How are skill ID’s found? I don’t know what to click on to inspect JSON. I assume this is not limited to my own custom skills, as the wiki shows BBC and NPR.
You can find skill ID’s by inspecting the JSON when navigating to https://alexa.amazon.com and clicking on skills
It seems that notify.alexa_media_everywhere is broken completely now
The Everywhere device is there but you cannot send anything to it.
I tried to uninstall and reinstall the Alexa Media Player but that did not help. It worked a few days ago but now it is broken
Actually.
The notify feature is totally broken and the Alexa Media Player generate 100s of errors in the log. I think the last version is totally broken. So much that I do not even know where to start on a bug report. Am I alone with this?
When I go to Developer Tools and start typing “notify.alexa” I normally get a list of notify_alexa_media_nameofdevice" for each of my Alexa devices.
After a restart of HA 1 one or two are listed. Rest are not there and I get an error when my automations using these are run saying it cannot find the device.
I have tried restarting HA several times. All my devices are listed in the integration. When I try to change the volume I get a Not a number error and the log floods with errors. Something is really broken
Follow up
Two things are broken.
The media_player.everywhere does not work - at all
The notify.alexa_media_devicename does not work for everywhere. It works on other devices - sometimes.
I had to rewrite my scripts to the format - this is the only reliable way at the moment
- service: notify.alexa_media
data_template:
target:
- media_player.echo_living_room
- media_player.echo_hallway
- media_player.echo_bathroom
- media_player.echo_kitchen
data:
type: announce
message: '{{ message }}'
I’d really like to see the ability to be able to disable Alexa from listening to voice commands (the same effect the mute button on the Alexa devices has that lights up the red circle).
This can serve as a security precaution when people outside the home may trigger home automation services using Alexa routines or other connected triggers.
The mute is a hardware button. I’m not aware of any Alexa device that allows you to mute it by software. Probably because if they did you could programmatically unmute it defeating the benefits of a mute.
This is fixed in 3.6.2. In the future, please consider filing an issue with the “100s of errors” so I’m not guessing what is the issue. I got a report on the missing devices so I’m able to try to fix it. The other stuff you mention in the thread may or may not be related but I’m guessing because I don’t have data.
2 Likes
I have been using this integration for a long time and never had an issue, however over the last few days i decided to build a fresh HA instance mainly to clear out all the old items and config that i had gathered over the years and try make a clean build.
All well so far aprt from when i come to add the Alexa Integration.
I go through the motions and then fill in my details at which point it asks to open up a website, it is at this point it all goes wrong.
Can anyone assist ?