jgcharlotte

Late to the game here, but very interested.

When the event occurs, she does not need to be queried. There is a different method for notifications, where she has to be queried, and that works very well for that use. It uses Network Resources.

Ok I see it now. It's a separate step in the routine, not a setting in the 'say' part. That works. It would be nice if they would give the option to use that setting for just this routine, so it would return to the previous setting when the routine finishes. Just a check box in the Device Setting step.

Is it only for that announcement or does it change the volume for everything after that? I use notifications for my outside motion sensors since it automatically plays on all Echo's.

Really, I didn't see it. I'll look again, thanks!

I don't suppose there is a way to set the volume when setting up an ISY triggered announcement in Routines? Like maybe embed a volume setting in brackets or something since there does not seem to be a setting in the routine setup to do that. Sometimes we have the volume set very low and an announcement comes through. Can't hear it, then it's gone. It would be nice, too, if you could select more than one echo to play the announcement. I'm going to try adding one in the ISY to see if both will play. Sounds like a good feature request to Amazon!

Hmmm, when I asked her for the status of a certain device, she responded 'that's not supported yet. You can get the current temperature from thermostats, though.

This is so true. Imagine doing all of your scheduling and programming in the cloud. "Oh, gee, a glitch on their server set my furnace to 100 degrees"

It is a pain, and I don't have close to 500! I make the first part of the variable name something constant for the variable use. At least that way they are grouped together when sorted by name. Fortunately, the variable names can be fairly long.

Looks like it went away on it's own last night. With a programmer's help of course.

Building on larryllix response above, what I do is set flags using state variables, then use the flags to trigger certain messages using the motion sensor/routine method.. garage door is open > set state variable 'door open' to 1 garage door is closed > set state variable 'door open' to 0 you always know whether the door is open or closed by the value of 'door open' Then you can compare the verbal command/action taken to the 'door open' flag to see if it is valid and trigger the appropriate message. I think that would work, if I understand what you're trying to do. I do kind of the same thing with a bathroom heater. I have an open/close sensor on the bathroom door. If the door is open, the heater doesn't heat up the bathroom too well (it is upstairs, we usually turn on the heater from downstairs) 'Alexa turn on the bathroom heater' If the door is closed, she replies 'the bathroom heater is on' If the door is open, she replies 'the bathroom heater is on, but the bathroom door is open'. Then somebody needs to run up and close the door. I also set a flag high when either of those 2 messages is played that disables any more until the heater has been turned off and then on again. This prevents messages from being played every time the door is opened while the heater is on. Hope this helps!

I'm using routines (not notifications) in Alexa to announce various things; 'garage door is opening', etc. Was working great. All of a sudden, in addition to the intended message, she is spouting a bunch of other gibberish, sounds like 'Amazon selection blah blah blah, then my message, then the gibberish again. Anyone else having this problem?

But don't they just change numbers? I don't even answer any more unless I know the caller. If it's a client or legit potential client they will leave a message.

Agree and I'm sure that's where I'm headed. I would do it a lot sooner if I know it will fix my DNS issues!

This is great feedback, thanks all for taking the time to respond! My router is a leased router from Spectrum, the account (200/10) is not a business account. It is separate from the modem, not a combo. They said it would be no problem at all to replace it if I decide to do that. Or I can get my own. One reason that I think it may be the router itself is that they replaced one for me a few years ago when I was having trouble getting on certain sites. When they replaced it, he said it was DNS issues. Anecdotal troubleshooting by association I know, but I'm about out of ideas. I have tried the Google DNS addresses 8's and 9's. Same result. I have it hanging in free air now. Seems a bit better, may be coincidence, still getting errors I figure if I just go out and buy my own and have the same problem, I can just return it and re-install the original. Or just keep it since it's probably a better router anyway. Sounds like Asus is the way to go. Thanks again!