do you have another alexa device nearby?
just an example:
i got a echo flex in room A, and an echo dot in room B.
normally i could speak to the flex and she did what i wanted.
but its summer, so the door between room A and B is now always opened.
when i stay close to the flex in room A, room B hears me and responds.
it also seems that a further away 3th gen responds faster then a closer 2th gen device.
Hi,
I would like to have the possibility to enable/disable wake up alarm with a switch.
And also have a list of those so to delete or edit when needed.
Any idea if custom command can help and if so anyone that already did ?
Thx,
Simone
Hi, @chemelli you can do that with Helpers, basically variables that you can put in your dashboard and toogle or change the variable.
Go into Configuration - Helpers
There you can create a new one, could be a switch, a number, a text, list, etc.
After creating the helper, just add it to your automation as a condition to be on and whatever rule you already have.
After that just add the switch to the dashboard.
Hope it helps, have a great day
Hey all,
Not sure if anyone has covered this here, but if Im playing a skill (like brown noise) the device shows the state as standby.
Can anyone confirm this is normal? That it just wont show the state if it’s a skill?
Thanks
Hi, @chemelli you can do that with Helpers, basically variables that you can put in your dashboard and toogle or change the variable.
Hi @heartbox, what I miss is the command to execute the operation 
How can I enable or disable a wake up call ?
How can I change the time of the wake up call ?
How can I change the schedule of the wake up call ?
Thx,
Simone
Why don’t u simply use the alexa app or speech? I think these functions are not used every day.
So is it worth to develop scripts for that? What is the use case?
Why don’t u simply use the alexa app or speech? I think these functions are not used every day.
So is it worth to develop scripts for that? What is the use case?
Basically for 2 reasons:
Simone
Hmm, ok. Basically I would say: everything you talk to alexa in order to initiate a command can be used with custom commands but you have to find out the whole sentence with all parameters to be changed. Quite difficult. The second thing is: You may change the parameters with every new commant. For this, you need some input_selects or input_dateTime in order to build your command with templating.
But first I would try to find the right sentence(syntax) to change you time or frequence of the alarm.
But first I would try to find the right sentence(syntax) to change you time or frequence of the alarm.
Agree, so we are now back to the initial question: how to proceed to get those ?
Simone
To make the alarm play something in alexa you need to use services inside HA,
check Developer tools - Services and then all the services of media_player
There is another device in the area and it’s an Ecobee with Alexa, but it’s the family rom device that comes back with “Hmmm. I’m not sure about that”. Would assume if it was conflicting with another device I would hear the other device respond.
If I say the same thing but not 100% like “Alexa, light to 99%” it works fine. Seems to be something with 100%. Light in the master bedroom doesn’t have this issue.
but it explains the stuff in the history saying: this isnt ment for this device.
I don’t get it, what in what I wrote would make you think that? If I speak to the Family Room Alexa and say to turn on the light 99% and it does it, and I say to turn the light on to 100% and it is confused, what am I missing?
you said that in your logs you got things like:
Audio was not intended for this device
Audio could not be understood
when you start a foot away from it.
so allthough it doesnt explain the different behaviour by different commands, it explains the log entries.
and it really gives me the feeling that it has to do with different devices listening.
Wondering if anyone can help me here.
I have this amazing integration and I love it!
However.
Recently a lot of my local Royal Phillips Electronics lights have been unresponsive when using Alexa.
I feel as though there might be a limit on the number of amazon-echo-device-nodes you can have.
Is this the case? If so does anyone know that limit and is there some sort of work around?
I’ve not been terribly descriptive because I can’t find the docs anymore for what I implemented. So here is a screenshot of part of my node-red flow to give a bit more context:
btw, I did read this entire thread and the wiki about groups, but if I missed the answer to this question, please direct me. I just installed this for the first time today, and I haven’t had any success with creating groups. All I wanted to do was create a tts door chime for all my echo devices to announce when the door is opened. I will think of many other great things to do with this, no doubt, so far, I can’t figure group tts announcements.
BTW, I work for Amazon customer service phone support for Alexa and Echo, full time, 40 hours a week. My setup before installing the integration is one echo show 5 and two 3rd gen echo dots setup as a stereo pair with my fire tv 4k. it all works fine and I really like the stereo pair home theater setup.
I was only able to get announcements working on the echo show. the echo dots just don’t respond at all and the speaker groups setup in amazon show up in my call service dev tools, but the dots and groups just ignore me.
The dots should work with tts, but for the stereo group you might use type: announce instead of tts.
This works for me on my stereo group:
service: notify.alexa_media_officestereo
data:
data:
type: announce
message: Say something
update: after removing the stereo pair in Alexa app and re-pairing for home theater stereo pair, the echo dots are finally working individually, and I have no idea why that would help, but it made all the difference.
One good suggestion about groups, because, trust me, speaker groups are buggy at best, just on the amazon side, is to go to alexa.amazon.com to verify and even make changes to groups and then check in the app. In my experience it is often different there compared to the alexa app, and that was the case for me when troubleshooting this integration. I have been restarting HA after any changes to speaker groups on the Alexa app.
I have found that with the echo show, it works for announcements with either the announce or the tts data type, so that was helpful to learn about that data type. the difference being that beep before the announcement, which I really like.
I can send announcements to each of my echos individually now, but no progress on groups, even with many, many attempts at different groups configurations. when I send an announcement to my “all echos” group, the echo show plays the announcement and the dots ignore it, even without a stereo pair now.
asking alexa to play music on the “all echos” group works fine so the group is valid and recognized by HA.
You have to distinct between stereo groups and normal groups. On normal groups neither work (for me), not tts nore announcing and not playing music.
On a stereo group announcing is working, playing music only when I address one member of the stereo group.
Check out this for Alexa Groups
mine is similar now, I can announce from call service to either my stereo pair or the echo show but if attempting to announce to “all echos” group, it only plays on the echo. when trying to send announcement from alexa app to all echos group, it didn’t play on dots so I discovered something very embarrassing to admit… I had communications turned off on the echos so I couldn’t do announcements to the echo stereo pair even from the alexa app 
ok, fixed that, restarted HA, but no joy for group announcements 
I finally found a working solution that I was afraid to try, but works ok. In the automation to announce when the door is opened, I just added a second action. one for the echo show, and one for the stereo pair. Done! hopefully my experience and many mistakes will help someone else. This is a perfectly acceptable workaround for my goal to have announcements from HA play on all echos 
The sync is a little annoying, but not too bad.