GlowingHair

@mapeter I think all you have to do is follow the switch instructions to associate the switches directly with each other, no PLM or hub necessary.

Cool! It's been working for me now, too. (Didn't chime in before - seemed like enough you had it managed. Thanks)

@smokegrub 90% of the time, my finder is blank when starting. I hit refresh and it populates. Have you tried that? Also, I have saved the configuration so it can be loaded if necessary. If I recall, I've only had to do that 3-4 times.

My routines are triggering, but about 1-3 minutes after they should. Luckily, for me at least, they aren't for anything critical, just convenient.

@Techman Perfect! Thank you so much. Definitely going to bookmark this. Edited to add: I still wasn't satisfied, so did a little more searching, and what I found is to use http://ip.addr.of.isy/rest/nodes/ (thanks, @MrBill), and I added the specific address to that to return the specific device's properties. This is what I recall using before, but had forgotten.

@Techman Thanks, but I already know how to do that. What I need to know is how to list the properties so I know which property to assign to the variable. Of the three I listed in the original post, only two do I know off the top of my head (or by referring to existing NR); the third I found in my search of the forum, so could use that for my immediate need. However, I would like to be able to list all the available properties so it is easier to find what I need to use. Make sense?

I thought I had run across a way to list z-wave device node properties, like CLITEMP (temperature), CLIHUM (humidity), BATLVL (battery level), etc. Is there some command that can be issued in a browser to list he properties (that's what I seem to recall seeing, though I can't remember the details)? I tried several searches and couldn't find what I was looking for, although I did find the correct property in another post by accident so I could get my network resource working. Any help would be greatly appreciated. Thank you.

A New Day for Insteon! — Insteon

Why not write a program to execute shortly after the ISY restarts to disable the problem programs? No harm/no foul if they are already disabled. That's assuming the ISY also loses power.