oberkc

Only one scene is needed, should you choose to take my earlier advice.

I cannot imagine why not. Sounds like a simple program... If Status can lights not 100% Then Turn off led light Else Turn on led light You would need to take the led our of the scene, also

AnthemAVM, I am not sure whether you ever received feedback regarding your specific questuob about your program. In my mind, I would change it in two ways. First, disable the second program. Second, I would eliminate the second condition of the second program. I also assume your motion sensor is configured to send both ON and OFF commands

Nickp, I really appreciate the fact that you are trying to figure out WHAT you want to do before figuring out HOW to do it. I think this is a critical step often missed, especially critical as things get more complicated. Some alternatives for your consideration: FASTON (double-tap) could turn on lights and disable motion program FASTOFF could turn off lights and enable motion program A program triggered each morning which re-enables the motion program, in case it was forgotten from the prior night's activities Use the beep function to confirm disabled motion programs or Tapping ON when the lights are already on could disable the motion program, or extend the timer perior Tapping OFF when the lights are already off could re-enable motion

I would actually do this with a single scene. How many dimmers do you have? Is each of the 18 lights connected to a dimmer? Assuming I understand what you want to happen.... -first configure buttons A-D as non-toggle-ON. -create a single scene with Main and A-D buttons as controllers and the dimmer(s) as responder. -for each of the five controllers in the scene, set the dimmer ON levels (full, 50%, etc...) you want to associate to that particular controller button. - for each of the five controllers in the scene, set the ON level of the other four buttons at zero. Understand that, for the main button, one (either ON or OFF) will be lit always. WDoes it make sense for the OFF button to be lit when one of your A-D buttons is on, or does it make more sense for the ON button.to be lit? Give it a shot!

My impressions, for what it is worth, is that there are very few controllers that control "everything". Furthermore, the ability to control some of those things will depend greatly on the amount of work you are willing and able to devote to this. It will also depend on access to some cloud services. I am mostly familiar with insteon, though I use some z-wave, some hue, sonos, and some LED strip lights I purchased from home depot (IR controlled). Since you want to control some insteon devices, this already limits your options to the ISY, hub, vera, homeseer, things like that. Smart things will not control insteon, to my knowledge. Smart things MAY talk to the insteon hub, but I seriously doubt that this option would have the conditional logic you appear to seek. Furthermore, your intentions with conditional logic tends to eliminate some of the typical controllers you might find at home depot or lowes or best buy. My best guess, without doing a lot of research, is that the ISY is likely one of the few that can talk to most of those devices, but for many the support is not native, and that there is not a small amount of programming and configuring and experimenting and other hardware gateways that will be needed. Unfortunately, it seems you have already purchased these devices, so the next point is moot (but I will say it anyhow). If I were starting fresh, I would start with the controller. I would pick a controller based upon its power with logical conditions and flexibility and the variety of devices with which it can speak, and with consideration of whether I am willing to rely on cloud services for core functionality. Once picked, I would then limit my specific devices to those that are compatible with my chosen controller. My choice, based on that approach, would be the ISY-994.

I am not sure that variables offer any efficiencies here, and possibly even increasing the number of programs required. It seems to me that it will take multiple programs with, or without, variables. Without thinking too hard, I suspect you are stuck with DxC programs, where D = number of doors, and C = number of codes. One thing that I have not experimented much, however, is with is customized notifications. I understand that you can use variables to customize your notification where it is potentially possible to have a single program for each door, something like: if door is unlocked then send notifications Where the notification would be different, depending on which code is used to unlock the door. You would not have to create separate notifications for each code. Perhaps this gives you an idea where to look? Edit: Looking a little further, check out the wiki "substitution variables": http://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables&redirect=no Look into user variables. I suspect that if you could use a variable value associated for each lock code, then use that variable to customize a notification, rather than create multiple notifications.

I agree. I don't think it is a program problem. For some reason, I expect the ISY is not seeing an accurate status of all your devices. When you find the KPL is not OFF when you expect, I would go into the admin console and see if the ISY thinks one of your trigger devices is ON when, in fact, it is OFF.

I have never seen a problem with that approach. Yes, maybe you are sending out an occasional unnecessary OFF command, but is there really any harm in this? In exchange, you get improved simplicity and reliability. I use this method every day, and it is well worth the trade, in my estimation. Still, I, too, am curious about your original programs. Were this me, I would be watching the kitchen dim program to make sure it is TRUE and FALSE when you expect. I missed where you described the devices that are in scene "kitchen dim", so I can only assume there could be something in there that may be triggering some of your programs unexpectedly.

I do not see a way for your (or stusviews) program to execute the ELSE path. The program is triggered only by the OFF/LOCKED commands and, once triggered, will always evaluate TRUE. Perhaps I miss something here. I would expect you may need a couple of extra conditions in your program: If Control 'KPL Buttons / Becca KPL.B' is switched Off Or Control 'KPL Buttons / Michael KPL.B' is switched Off Or Control 'Front Door' is switched Key/Manually Locked ​ or Control 'KPL Buttons / Becca KPL.B' is not switched On Or Control 'KPL Buttons / Michael KPL.B' is not switched On Or Control 'Front Door' is not switched Key/Manually Unlocked Then Set 'Front Door' Lock Set Scene 'Front Door Deadbolt' Off Else Set 'Front Door' Unlock Set Scene 'Front Door Deadbolt' On

I note that both programs are triggered by, among other things, a common condition "control kitchen sink off". I do wonder if we have some loops going on here, but my best guess is that this is NOT a programming issue. Run your first program normally (tapping on necessary switches). Once run, execute the second program from the admin panel by "run>>then path". Do your lights turn off as expected, or do some stay on?

Certainly, there have been questions in the past from folks wanting to do this, so it seems certain that some do use the remotelinc as a garage remote. Equally certain is that range will depend on local conditions such as distance to nearest dual-band insteon device and material (brick, walls, boxes, etc...) between remotelinc and nearest device. I do not believe that there is any need for the ISY to "recognize" the presence of a device. I think it simply waits for a signal and, when it is present, the ISY reacts.

Different than what? Setting lights to come on at specific times are straightforward. Do you want them to come on at a certain time, or do you want to enable the motion trigger during certain times? If time is x then set device/scene on else nothing Are these the same or different lights than referenced in the first bullet? If you want different lights to come on with motion always, then I like to configure the motion sensor to send ON commands only, and use a scene with motion sensor as controller and lights as responders. To this, add a program: if control motion sensor is switched on then wait 3 minutes set scene off else nothing If you ever want to constrain operation of the motion sensor by other factors such as time, darkness, whatever, then you must use a program and NOT a scene. Program, above, would accomplish. Are these the same lights as triggered by motion, I assume? Are these the same lights as triggered by motion (include the switch as controller in the same scene)? Same lights as on the timer (create a scene with switch as controller and lights as responder)? suggesting same lights triggered by motion. If so, ammend program above as: if control motion sensor is switched on or control switch is switched on then wait 3 minutes set scene off else nothing would do so if controller in a scene Above suggestions would work whether gone for seconds or for days. Clearly, I am a little uncertain as to which lights are which, whether they are the same in all cases or different and my recommendations might change if I misunderstand what you are trying to accomplish. My suggestion is to start with a more limited set of requirements (such as coming on at certain time of day and working with switches) and see if you can get that working. If so, move to motion.

Yes, if you intend to use motion sensors in scenes to turn on/off other devices, then on and off both need to be enabled. Scenes also tend to be a little quicker responding and work even if the ISY fails. Als, you can use a combination (scenes to turn on, programs to turn off) if that suits your needs. I have found that, for me, I want to apply more contraints on motion sensors than available internally (such as the ability to override) so I tend to use programs.

Either option seems viable. The question that goes through my min is whic option introduces the least delay between motion and response. I suspect that might be option A. Consider, however, option C. What about creating four program folders, each enabled by one of the time ranges. In each folder, add a program: if motion sensed, turn light on, wait x, turn light off. The only uncertainty I have are whether the program wait would be interrupted if the folder is disabled during a wait state.

Yes, this strikes me as a comm problem. Watch the ISY status of a given device and see if it changes as you toggle it on/off. If not, I suspect you have the answer to your question.

Most troubleshooting, it seems, is trial-and-error. I tend to think this is still a possible explanation. In addition, it is very simple to test. Unplug the pinball machine, and plug in a simple incandescent lamp of some sort (or even leave it without anything plugged in). Does this solve the problem? Sometimes the best method is to eliminate the easy things first.

What teken said. Make sure the top is part of NO scene, or NO program, and it should stay in whatever state you want it.

I still cannot help but wonder if we are missing something, but I am out of ideas. It does seem unfortunate that this folder condition does not seem to work.

Yes, that I noticed, and saw those notes in the initial post. It was NOT a problem with grayed-out test button. In fact, the test appeared to work (as indicated by a little pop-up box yielding some results), but the hue light did not respond initially.

"Test" button was NOT grayed out. Pressing it, I originally thought, did not produce any change to the hue device. But, second time a charm. Subsequent devices work just fine from the test button. It is possible that the first now works, but I have not gone back to check. At this point, I would consider the instructions fine as is.

Never figured it out. When I added my second hue light, the test worked fine, as expected. I have no explanation regarding the first attempt, other than incompetence of some sort on my part.

To emphasize and repeat the others, I believe you will find the ISY-994 compatible with ANY insteon switch. I might watch out for very early versions of a few switches, but more for hardware reliability concerns rather than compatibility. At this point, I doubt that anyone would be selling as new any devices this old, however.

I fell prey, also, to the /1234 issue. When I read that, I took it as "optional" whether or not one left it in. For me, it was not optional. For me, also, running the "test" from the network resources did not actually result in the hue lights turning on or off (which I expected to happen). It was not until I actually put them into a program did they work. It took me a little while to discover this. When the "test" did not turn on the lights, I assumed it was some error in the resource, so I continued to look for errors, and re-ran some of the debugging steps instead. When those did not solve the problem, only then did I take the next steps of creating the program and discovered the resource was, in fact, fine (lights turned on!). Perhaps that could be clarified as to what to expect, or not to expect, from running the test step from the network resources page. Otherwise, all worked as well-described in the original post.

DualBandAid I just wanted to say thanks for the time you took to write this up. I have been interested in using some color in my lighting, and the hue strips seem to catch my eye, but I am not interested in anything that cannot be controlled by my ISY-994.. I cannot imagine how long it would have taken me to figure this out, and would not even have tried by myself. But...your instructions gave me enough hope that this would not have been the equivalent of a masters thesis for me that I gave it a shot. Now, I have some hue strip lighting that is triggered by my -994 and I am happy! I doubt that I will use hue for anything but a few color shots, so I will stay with the network resource. Polyglot is too funny a name for me to have to explain to others how it all works, so I will stay away from that for now.