Bumbershoot

I pressed the "SET" button until it is in linking mode, then queried it from the ISY.

The must have changed the firmware at some point. Mine are battery powered and I have no "as motion sensed" option at all.

It appears that mine are revision 3, so it could be.

I have mine set like the screenshot shows in my laundry room, and it does not shut off the light when the room is occupied, even with a 30 second timeout. I suspect the "Motion | Condition" dropdown menu contains what you need. At least it seems to be working for me... ?

Michel does recommend a heal if communications aren't good. See this post earlier in this thread:

I had to go back to find my own post, but I performed a heal after the upgrade to reestablish the neighbors to my devices. There have been no ill effects that I've noticed, as everything is working just fine here, with no noticable issues at all.

Thanks for this. All I was looking for is a way to get a bit flipped in my ISY so I can manage external lighting, internal notifications, etc. I was able to purchase a Nest Hello for a $30.00 discount which included a free Google Home Mini (which hasn't arrived yet, but I understand will manage some announcements). All good! I've got the Hello installed yesterday, and it appears that you're exactly correct about the "Event - Person" toggling reliably. I'm off to the races with this thing.

Okay, I have the Nest polyglot nodeserver already running and am happy with it. Is the Hello incorporated into that nodeserver (I might have missed something...)?

Any updates on this with the current firmware (5.0.13A)? Thanks.

I don't know much about Z-Wave, but I did an exclude/include on my lock while it was in place, and it included securely. After a network heal, all the neighbors showed up as expected. I don't know what significance the 'association groups' have. Sun 07/15/2018 17:37:31 : [ZW-SHOW ] ---------------------------------------------- Sun 07/15/2018 17:37:31 : [ZW-SHOW ] ZW 002 Schlage Door Lock Sun 07/15/2018 17:37:31 : [ZW-SHOW ] ZW002_1 uid=2 type=4.64.3 mid=59 tid=25409 pid=20548 model=2 Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x22 V1 APPLICATION_STATUS Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x98 V1 SECURITY Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x86 V1 VERSION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Secure Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x5D V2 ANTITHEFT Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x85 V1 ASSOCIATION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x20 V1 BASIC Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x80 V1 BATTERY Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x70 V1 CONFIGURATION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x62 V2 DOOR_LOCK Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x71 V3 NOTIFICATION Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - x63 V1 USER_CODE Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - xEF V0 MARK Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Last working route from ISY to Node 2 - ZW 002 Schlage Door Lock Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Node 13 - Master Fan Switch Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Node 12 - East Auto Door Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Node 2 - ZW 002 Schlage Door Lock has the following neighbors Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 7 - ZW 007 Siren Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 8 - ZW 008 Multilevel Sensor Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 9 - ZW 009 Multilevel Sensor Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 10 - ZW 010 Water Cop Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 11 - West Auto Door Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 12 - East Auto Door Sun 07/15/2018 17:37:31 : [ZW-SHOW ] - Repeater - Node 14 - Office Dimmer Switch Sun 07/15/2018 17:37:31 : [ZW-SHOW ] Sun 07/15/2018 17:37:46 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.05 ASSOCIATION Sun 07/15/2018 17:37:53 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.05 ASSOCIATION Sun 07/15/2018 17:37:53 : [ZW-SHOW ] Node 2 - ZW 002 Schlage Door Lock cannot retrieve association groups Sun 07/15/2018 17:37:53 : [ZW-SHOW ] Sun 07/15/2018 17:37:53 : [ZW-SHOW ] ----------------------------------------------

I just had a chance to install the new board this morning. It took 3 attempts to successfully perform a Z-Wave restore, but all is well now. No discernible differences. Edit: If it's interesting, I excluded and included my Schlage deadbolt while it remained in the door, and it appears to have excluded/included just fine. It has a new Z-Wave number, but it seems to be securely included, and as far as I can tell, it's working entirely as intended. I have several Z-Wave repeaters between it and the ISY.

I did something similar with previous versions of Polyglot and the LiFX nodeserver. It worked, though a bit erratically with a two second wait between color switches. Both Polyglot and the LiFX nodeserver have improved significantly since then, so you might have some succcess with the lighting.

This was in the release announcement for the 5.0.9 build: 0000371 - Full support for Insteon Siren 2868-222

Yep, I left one a while ago! Thanks for the skill, too!

I have one of these, only it's a dimmer (Homeseer WD-WS200+, with the 7 LEDs), and solved what I believe is a similar problem using both variables and by disabling/enabling programs. My problem might be slightly more complicated that yours, in that I have to choose which LED to illuminate on this dimmer. The problem was straightforward except that I have two garage doors that I wanted to monitor the status of using the same LED on the dimmer. This proved to be trickier than I initially thought, and it took nine programs for me to accomplish this (I'm sure there's an easier way, but I got it to work so I've left it alone for now). The solution involved setting variables in programs, then disabling/enabling other programs that would set the same variable to a different value, based on which (or both) garage doors are open or closed. This might be an approach you could use.

I've got "brief mode" on as well, but I never turned it on. Alexa chimed in after some command and asked if I wanted to have her turn on "brief mode". I said yes, and it's been that way ever since. Never touched an app.

I've tried to design this installation so that if I take my ISY away, the house will still operate as one would expect any house would operate, meaning that the razzle/dazzle is almost entirely controlled by ISY programs. I might turn off the LEDs on the OutletLincs/SwitchLincs and unplug the ISY if showing the house, but otherwise, things should work almost entirely without surprises if no controller/eccentric husband is around to manage it all (this was an early request from the Mrs.). Folks in my neighborhood are warming up to HA (I thank Alexa, iRobot/Roomba, Nest, security systems, home theater, etc. for that). I see a lot of service trucks from local HA vendors/installers sitting in driveways around here, and new construction seems to always include either a Control4 installation or at least a fancy HA controlled media room. At this point, my only concern is the long-term viability of the gear I've installed. I don't expect that people will be interested in the same gear ten years from now, nor will I still be interested in keeping functional, though obsolete Insteon/Z-Wave stuff around. I expect I'll have to do a periodic swap-out of my HA gear to keep it somewhat current -- I see that as a maintenance expense. It's a hobby, after all, and cheaper than a cellar full of fancy wine or a late-life crisis sports car... I think @larryllix is right, it depends somewhat on the neighborhood and the price of the house. And again, times are changin... Somebody's buying all that gear.

Have fun with this. I've found yet another way to surprise the Mrs. with home automation. She appreciates Alexa notifying her when I'm a few blocks away from home.

Nope, you'll need the 5.x.x firmware for node servers. I'd move to 5.0.12 if it were me -- the latest and greatest, you know. Your ISY world can get a LOT bigger when you start looking into Polyglot and Nodelink.

The changes are fairly subtle and a little hard to discern, but can be a bit humorous: {"notification":"The ${sys.node.n001_c230730b1dc55d.name} <prosody pitch=\"+30%\">temperature reached</prosody>${sys.node.n001_c230730b1dc55d.CLISPH} at ${sys.time24}","accessCode":"amzn1.ask.account. This slightly raises the pitch of of the words, "temperature reached". Makes Alexa sound a little kooky, but it subtly gets your attention. Thanks for the link, and I'm glad to see that this works.

After fussing with this Notify ME just a little bit, I've found that Alexa can enunciate specific device states in an intelligible format. Inserting the following into a Notify Me network resource: {"notification":"The ${sys.node.ZW014_1.name} was set to ${sys.node.ZW014_1.ST} at ${sys.time24}","accessCode":"amzn1.ask.account...} produces a notification that sounds like this: "The office dimmer switch was set to 10% at 11:41 and 13 seconds." This means that you can get device status updates using this skill. Unfortunately, you'll have to have a separate NR for each device because you can't use # to reference devices in Network Resources (per the wiki): Instead of specifying a fixed address, the special character # may be used to reference the element in the event that caused the program to run. (Does not work in network resources) Otherwise, a single NR could be used for all devices (I can dream, can't I). Even so, this skill will find some very valid uses in my installation. I'm already using it in conjunction with several devices and node servers: notifying my wife of my imminent arrival home (Occupancy node server on the UDI Portal) of temperature changes (Nest) of doors left open any other thing I can think of I think this skill will prove to be very handy! EDIT: Another example: {"notification":"The ${sys.node.n001_c230730b1dc55d.name} temperature reached ${sys.node.n001_c230730b1dc55d.CLISPH} at ${sys.time24}","accessCode":"amzn1.ask.account... This notification produces: "The family room temperature reached 70 degrees Fahrenheit at 12:02 and three seconds." The address of my Nest (from the Polyglot Nest node server) thermostat is: n001_c230730b1dc55d

This is how I did it in the body of my Network Resource: {"notification":"The back door opened at ${sys.time24}","accessCode":"amzn1...... Works like a charm...

These are only available in the "Then" and "Else" stanzas.

Polyglot can be run on Linux machines with both ARM processors (RPi machines) and Intel processors, as well as on macOS machines with Intel processors. I ran Polyglot on a macOS machine prior to purchasing an RPi. I'm sure that with the source code, it could be compiled/coaxed to run on a Windows machine as well. Here are the precompiled binaries.

I have a Smoke Bridge, and the only programmatic options I see are "Query", "Beep" and "Write Changes" to the Smoke Bridge itself (on any of the nodes). The OneLink detector that the Smoke Bridge listens to isn't visible to the ISY. I have all Kidde interconnected smoke detectors except for one OneLink detector that I use connect to the Smoke Bridge. Any test or alarm on one of the Kidde detectors reaches the Smoke Bridge, which to me indicates that there is some sort of signalling over the wires that you might be able to take advantage of. Maybe an IOLinc inline somewhere? I absolutely have no idea... Were it me, I'd leave the fire system alone and install an Insteon Siren or a Z-Wave Aeotec Siren that I could actuate easily from the ISY.