oberkc

It should work great. The only problem I see is if there are communication problems. If not, it'll work great. Make sure you use "status" for the button you choose.

Not sure what this means. Do you want run THEN (start) or ELSE (stop) in a program? Do you want to initiate a program path that has a wait state (or loop) that you want to later stop? Enable or disable programs as suggested by lilyoyo1? That is how I would do it I tend to pick a couple of the buttons in the scene as the canary. Keep in mind that (with all due respect to Mr Kohanin) I think you will need to use "status" rather than "control" in this case, just in case you use one of the scene buttons that is not specifically called out in your program. Of course, if your program condition includes ALL your buttons in the scene, "control" conditions could work: if ( control buttonA I s on or control buttonb is on or.....rest of buttons ) and ( control buttonA is not off control buttonB is not off or....rest of buttons ) then start program (whatever that means) else stop program (whatever that means)

I am not sure one can make this conclusion. Direct actions on an insteon device can be, I understand, more robust due to repeats and acknowledgements. I don't believe that these exist in scene commands.

The only downside that I would consider is the reliance on the cloud for setup and operation. So long that smartlabs stays in operation you are probably fine, but you need to ask yourself if that consideration is important. Of course, you could consider other options later, if anything happens to smatlabs.

You can safely assume all insteon switches are compatible. Many z-wave switches will be also, if you have the zwave version of the ISY. Cannot say regarding black switches.

If no light, use the on/off switch to control another fixture or light in the room. Lamps? Overhead?

Like kclenden, I took it the other way also. Made no sense to me either. Better to wire the fanlinc to constan power. Use the KPL on/off buttons NOT to control “power to the fan” (direct quote) but use these buttons (rather than pull chains) to control the light

Yes, I believe this is under “power” options. One can modify the power-on and power-off sequences to include additional commands.

I think jec6613 correctly diagnosed the problem. I don’t know that variables are the simple solution, however. What about modifying your original program: - disable it - remove the first condition (if ir006 is pressed) Then, add a second program such as: if if ir006 is pressed then run modified IR 06 program (if path)

I think this is good advice. The only downside to this is that, IIRC, many around here claim that the alarm is a GREAT repeater...a better repeater than other z-wave devices. Even better would be if you have a need or interest in an alarm. Given that I purchased the aeotec alarm, I went ahead and created a simple program to trigger it under certain conditions. It gives my wife some level of comfort when I am gone.

That has been my experience. I understand that z-wave is a mesh system also, thought I also understand it tends to established fixed routes as devices are added. In my case, the additional z-wave devices resulted in a better z-wave network. Another thing is that, apparently, some z-wave devices can use secure communication and some cannot. Also unlike insteon, z-wave repeaters need to be added to the ISY994. It seems many have recommended the Aeotec alarm as a good repeater. I have one, along with the Aeotec repeater, and am happy to recommend them also. Get a couple, install them first, the install the door lock. Sometimes it can be necessary to program the lock while near the ISY, then install it, but I suspect you will be able to make it work. One thing I suspect you will like about the z-wave locks is that, unlike the morninglinc, they report status. Now, when you unlock the door from the keypad or knob, the ISY will know it. Added bonus: you may find some z-wave devices you like that don't have counterparts in the insteon world. Now you will be ready to incorporate them into your house.

As far as I know, the morninglinc is the only insteon lock version available. The practical options remaining are, in my mind, zwave. Perhaps you could use a wifi lock such as a homekit or google lock, but most of those are deadbolts, I think, and would require some special network instructions or nodelincs or polyglot or one of those other systems I know little about. I don't know how far away is your lock from the ISY, but my guess is that the odds are pretty good you can make that work, with one of the z-wave range extenders. Whether or not there is one with knob/handle I don't know.

Check your other topic

Such a program never “checks” status. Instead, the program is triggered when status changes. If the door was always ON, the program would never run.

Do the instructions define a specific connection for line/load? Like you, I would have expected voltage only one place. Are both the same voltage? If you remove the light bulb, does the voltage go away on one conductor?

That is one option. I think harmony has codes for the he ISY also, but I assume that you would have to teach the ISY Oir somehow dowblaod those codes into the ISY. Some harmony remotes have dedicated "smart home" buttons. These buttons, I believe, work independently of an activity. Given this, I suspect it is best to load a dummy device that falls under the smart home category. Otherwise, harmony will only use that device as art of an activity.

The IR capability can be added to an existing ISY.

Yes. I have a backup program that turns lights off at dawn and, among other thngs, resets the motion programs.

My wife is one of those. She claims not to have to turn off lights because they are automated. The problem is also that she gets concerned also when I use geofencing to determine whether she is home (it is creepy, apparently). Between a rock and a hard place.

You do the same thing that I do, except here. Mine revert to "normal" function at dawn.

Glad you figured it out. I could, at best, make educated guesses at many of those settings.

I have always felt that many underestimate the nuances of these types of automation programs. This is definitely a scenario that is worth thinking about in terms of requirements before programming. I agree with you that better understanding of the lights and requirements is needed to provide better answers. The program I proposed, for example, would not halt itself should someone manually toggle the lights while the timer is running (not sure whether this is important or not). I suspect this program will get more complicated still as AnthemAVM thinks further about what he wants to accomplish.

What are "side lights"? Is it the laundry room exterior lights? BBQ lights? Both? Either? What if someone manually turns on the BBQ lights but does not turn on the exterior lights, what do you want to happen: timer or no timer? What do you want to happen if the timer is already in progress, THEN someone manually turns on one or both of the lights? Depending on answer to the questions above, I would probably take a different approach than Larryllix. I would probably keep it two programs: If From 10:01:00PM To Sunrise (next day) And 'SideGate-Opened-Opened' Status is On and ( 'Exterior Lights / Laundry Room Exterior Light' Status is Off Or 'BBQ Island' Status is Off <<<<<<<<<<<<<<<<<this may need changed to AND depending on your answer to my first question ) Then Run Program 'Side Gate On' (then) Else - No Actions - (To add one, press 'Action') If nothing Then Set 'BBQ Island' On Set 'Exterior Lights / Laundry Room Exterior Light' On Wait 5 minutes Set 'Exterior Lights / Laundry Room Exterior Light' Off Set 'BBQ Island' Off Else nothing

Do you know for sure that they actually came on? I understand that there are no programs with this device but, by chance, did any programs run at (or about) 12:09:31AM?

I did not see three motion sensors. Program 3 is not needed. The other programs, as now written (added ELSE statement) will take care of this. Programs one and two should have an additional statement added to the end of each ELSE path: Set Scene 'Flood Lights' Off I will throw out another option: a single program: If ( Control 'Outside / Rear Deck South Side-Senso' is switched On or Control 'Outside / Rear Deck East Side-Senso' is switched On or control third motion sensor is switched on ) And From Sunset To Sunrise (next day) Then Set Scene 'Flood Lights' On Wait 15 minutes Set Scene 'Flood Lights' OffElse Set Scene 'Flood Lights' Off For any program, ask yourself what will force an evaluation of the IF clause. For the ISY, the evaluations are triggered based upon the conditions contained within. In your (and my) specific cases, the programs would be triggered upon the following events: - sunset -sunrise -receipt of ON commands from one of the two motion sensors. Regardless of what triggered the evauation, the entire condition is evaluated. Any time the evaluation is triggered, WAIT and REPEAT would allow the on-going execution to halt and the program restarted, based on the results of the evaluation. At sunset, the entire condition is false (no simultaneous receipt of any ON command) and the else path runs. At sunrise, the entire condition is false, running the else path. Upon receipt of an ON command, condition could be true (if between sunset and sunrise) or false (if after sunrise and before sunset).