DaveStLou

I tend to use a similar model to @paulbates. I use ISY scenes and programs the most since I prefer to have the predictable portions of my home automation done by ISY program if at all possible (e.g. turn off lights in occupied rooms after a period of time). My wife and I use Alexa for spontaneous, on-the-fly changes in what's on or off. Since I often incorporate the Harmony polyglot, it also helps to have ISY aware of what is going on as much as possible so I can act on it with other programs. Simply said, is use ISY for everything I can and only use Alexa scenes if there's no other way to do it within ISY.

I was confused by the wording. It's working as designed.

You're right. It's missing for me as well. I tried unlinking and linking again but no change. I'm also receiving and error in the portal "Devices are not available HTTP error 500"

It was removed in the last Portal update.

Mine first just showed the node server, I restarted the node server and it added the camera nodes automatically.

You can do by setting a variable to the percentage. Something like this: Set i.Bat.PorchSensor - [ID 0177][Parent 009A] If 'Front / PorchSensor2-Motion' Battery Level >= 0% Then $i.Bat.PorchSensor = 'Front / PorchSensor2-Motion' Battery Level % Else - No Actions - (To add one, press 'Action') Then using User Variables as explained in the Substitution Variables wiki you can put them in an email. I have been less than successful in getting the 2844-222 in particular to reliably report battery and temperature to my ISY at all but it works for my Z-Wave Motion Sensors.

Learning Python is on my post-retirement bucket list which a couple of years off.

I'm am interested in this as well. I have to reinstall Polyglot on my RPi for at least the second time.

I agree with @paulbates that best is subjective. In my case, I switched to an Insteon thermostat years ago and have been very happy with it. If you're used to working Insteon devices, it's a breeze to set up and work with programming on the ISY. It's also relatively easy to integrate with Alexa through the UDI portal.

The error was invalid access code even from the test link in the original email when I received the access code. I did disable and re-enable the skill but forgot to relaunch. I've done that now so I'll look for the access code email again.

Sent

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/