DaveStLou

I've been using Notify Me for months and suddenly it stopped working. I looked into it and found that I'm getting an error saying my access code is invalid. Since I hadn't made any changes I doubted that but I went back to the original email and double checked it was correct. So i requested a new access code but it's been 24 hours and I've not received a new code. Anyone else experiencing trouble? Is this skill still working?

I'm switching to using the same State Variable. The help doesn't explain the "set to" prompt. Is that the amount that will be added to or subtracted from the variable when called?

Thanks. I hadn't used volume variable before adding AVRemote NodeServer. I made the assumption it worked like Channel Up/Down/Set.

Is there possibly something else going on where it would execute a different program than what was mapped? When I say Volume Up it is adding 20 to the variable instead of running program 0005. When I say Volume Down it's subtracting 20 instead of running program 00E7.

I'm trying to make some changes for an AV device and found that the boxes to put in the variable and program names are not showing up. Anyone else seeing this?

Working great for me. There was a delay of about 90 minutes for the first notifications to come through to my Echo. Since then they arrive almost immediately.

I haven't seen any projected ETA for Amazon to fix the problem so this is the workaround I'm using too.

I have had the same issue with open garage door working for awhile and then suddenly stopped 6-8 weeks ago. You may want to try the new Routines in the Alexa app. I intend to explore them for more complicated set ups but yesterday I was able to set up "Alexa,Open Garage" and "Alexa, Close Garage" as routines pointing to the programs via the portal. It has worked for the last 24 hours so far. YMMV

More fun and mystery. In the portal I changed the spoken word for my garage door program to "Laundry Lights" - changed nothing else. I asked Alexa to open and close Laundry Lights and surprise, it worked. It appears the spoken word is the complication, not the reserved action word "open".

Echo, Dot and Tap are version 588442920 FireTV stick is version 573210720 Dash doesn't display a software versions Alexa app is client version 1.24.2573.0/Bridge Version 2.1.297.0 Reverb app is version 1.2.0

As for them being reserved words, that also has been inconsistent with my experience. Early this year, without me making any program changes, Echo began allowing me to say "open" and "close" garage door. For many months, it worked that way. Then just as suddenly, about a week or so ago, Echo started saying that device does not support that. So if the point is to reserve those words due to some concern about lock security, why the intermittent periods of responding to those words?

Open garage door worked for me from about mid-July until last week. Rather than going back to "Turn on (or off) garage door", I'll have to go back to using an IFTTT applet. "Trigger open (or close) garage door" isn't as good but it is an improvement.

I don't have a Google Home device but I did buy a Pixel XL and have also successfully setup "Open Garage" and "Close Garage" with Google Assistant via IFTTT and ISY portal. I choose to use the portal since it simplifies the Maker request and doesn't require opening up ports at home.

I'm considering a Pixel XL myself. Even though I have multiple Echos, the tie into Google Home is compelling. Here's an article on Google Assistant SDK which is coming in December: http://www.zdnet.com/article/google-plots-embedded-google-assistant-sdk-tools-for-developers/

Michel, I had a similar issue which I posted to a separate thread. My question is where was the notice of the maintenance release posted? Even if a release is not expected to cause problems, if there is a notice we can find out and give feedback if there are issues.

While writing the original post mine came back online. Seems like it's working now.

Anyone else receive unusual errors on the portal this morning? This morning my Amazon Echo complained "that command doesn't work" on my devices. Logging into the ISY Portal I found my ISY is online and through the admin console UDI portal shows online. When I tried to review settings under Amazon Echo after a long pause I got "Devices are not available HTTP error 500" and "Scenes not available". When I went to ISY Web Access on the portal after a long pause I get "error, Loading: /config/". I tried rebooting my ISY994i but no change. Then about 8:20am CT all returned to normal. I don't see any messages about maintenance on the portal.

aceball, You're right. It is a little less awkward. Hilariously, the first time I tried it though, Alexa added "Garage Door" to my shopping list.

Interesting. I added our GDO yesterday and used open/close. I just read your post and tried. Open/close works!!! edit: Maybe 'door' is a problem. I didn't use that word. I was hopeful when I saw your post, stusviews, so I changed the "Spoken" word in ISY portal, removed all discovered devices in Alexa app and re-discovered devices. Unfortunately Alexa's response is the same when I saw "Open garage": "I'm not quite sure how to help you with that." I still seem to be running into what Michel referred to above. My question remains: Why is "open" more insecure than "on"?

Can someone explain to me or point to the rationale for Amazon restricting the use of the word "open"? When the ISY Optimized for Smart Home updated to V2 I lost the capability to simply say "open garage door". Now I have to say "turn on garage door". Why is it safer to turn on a garage door than to open a garage door?