oberkc

If you already have an IRLinc, this seriously limits the value of the IR capability of the ISY. Still, much depends on where you intend to locate your ISY and what you intend to do with it. There is no integration of video with the ISY. However, there are apps for use on tablets and phones that interface with ISY as well as show video. Personally, I have not seen much value in integration of video and lighting control. At some level, perhaps it would be nice to take advantage of motion sensing that is part of the IP cameras. I suspect this could be done if you wanted to get into the network module and REST interface. I have not.

I have never used houselinc, but my perception is that the conditional logic in the ISY is a bit more powerful and flexible. ISY also includes ability to manage links and scenes and provide remote access to your system (i understand that this capability resides not in the houselinc, but in the smartlinc). Additionally, I suspect the ISY provides greater integration with other stuff, like weatherbug, security, many internet-enabled devices such as audio and video equipment. Some ISY models include IR capability. By the time you purchase a smartlinc AND houselinc, the price difference becomes inconsequential, if there is one.

Or, depending on your needs, you may use a "not on" (less than full) status, or "not off" (more than zero) That type of status is perfect for dimmer use in many cases.

What is you purose with the condition "and status..." By the way, I think removing that condition may solve your problem.

Yes, but this would most easily be accomplished by using a program to trigger motion lights, rather than a scene.

I am sure it COULD be, but not whether this i conclusive evidence.

This surprises me from one who likes to tinker such as you.

The nature of your solution will depend on a couple of factors. If kpl1 is off and you invoke scene2, do you not want kpl1 to come on? Does it matter? If kpl1 is on and you invoke scene2, do youwant kpl1 to stay on? Does it matter? Are any of the togglelincs dimmers?

I suspect that I am not alone in that setting these types of things up for internet connection is something that I do so infrequently that I never get knowledgeable enough to offer any advice. When I need to do it, I figure it out as best I can, get frustrated, read a lot of web pages and user manuals, and, eventually, get lucky. Three months later, I have forgotten just about everything.

I notice a couple of things wrong. First, I don't see anything that tells it to go off at 830. Second, I don't think you are turning it on. Rather, I think you are simply changing the level it will go WHEN (if) you decide to turn it on. Since you did not anwer my two questions from an earlier post, I will make some assumptions and offer suggested alternatives. In the admin console, select the scene. Change the "on" levels to all devices to 50%. Change your program to be more like: If From Sunset To 8:30:00PM (same day) Then Set Scene 'Under Cabinet' on Else Set Scene 'Under Cabinet' off

In other words, from mobilinc, turn on/off the scene rather than turning on/off a switch within the scene.

Could be several things, but it may be best to start with an actual copy of your program. Do you have other times or cases where you want a program to turn on the lights at some level other than 50%? If you select the scene from your device listing, what are the "on" levels for the various devices within the scene?

I continue to have memories of some of my older switches that require a power cycle before accepting such settings. Unfortunately, I find myself more frequently remembering things that did not happen. I have not memorized version numbers, but how old is your v27? Hopefully, someone can confirm whether this is a concern or not.

Yes, it CAN (I suspect, never had it happen). So CAN the thermostat. In my experience, having the ISY crash is, simply, not a concern.

The method suggested by vyrolan used variables. Yes, I understand these need to be set up in the variables tab. Unfortunately, I am not a user of variables and cannot offer any hands-on advice.

mine gets out of sync with the computer, also, but this is because the computer fails to sync for some reason. In case it was not clear earlier, I don't see the value in putting this program (turn outletlinc off when KPL on) in your folder. Perhaps this is why it did not work for you earlier?

I am not sure if it would run if you put the program in a folder that requires the KPL to be on in order to be enabled. If you turn the KPL on, this would enable the folder, but would it trigger any programs included in that folder? Why not leave it out of the folder? Regardless, it is easy enough to try out either option and figure out which one works best for you.

I don't know why you could not have two programs: if control KPL is switched on then turn off outletlinc else if from time xx:xx to time yy:yy then turn on outletlinc else turn off outletlinc Understand that if you happen to press your KPL button AFTER time xx:xx, it will stay off until the next day.

LeeG, Thanks for the explanation. I was not sure whether changing a responder level required any updates to the controller. I now understand that it does not.

Given your program, this could also be caused by the configuration of the motion sensor. I believe thay can be set to send only "on" commands. If yours is set this way, your program would not turn the lights off (except at sunrise). I am also assuming your elk zone is not in a constand "violated" state.

I believe motion sensors can be set only to on (100%) or off. This is not as I understand it. I understand that it is the responder level that controls response to a motion sensor (or any other controller). There may be a couple of things going on here. First, I wonder (not sure) if one can change attributes of a scene containing a motion sensor. Since motion sensors are battery-operated, they cannot be re-programmed without first putting into linking mode (or within a few minutes of sending a status change). Second (more likely), responder levels can vary based upon which controller is initiating the scene. For example, a "scene on" level can be different if initiated by the ISY versus the motion sensor. Is it possible that you are reducing the master scene levels while leaving the response to a motion sensor at 100%?

Functionally, it should. The difference with scenes is that you may notice a bit quicker response. Otherwise, there is no functional difference that I can see. One nice thing about scenes, however, is that they will continue to work even should something happen to the PLM or ISY.

I believe ANY change in status will trigger an evaluation. The path it takes from there depends on the results of the evaluation. If 'kitchen_oh' is a dimmer, then "on" means full 100%. Anything less will result in a "false" indication, running the "then" path.

Given that I do not think your program is at fault, I would look at other things. -it appears that you manually typed your program into the forum, correct? Make sure there are not any subtle differences (am/pm errors, for example) -check to see if the scene is working. From the ISY control panel, manually turn the scene on. Did it work? -Like LeeG suggests, check program last run time. Is it running at the times you expect? It is possible to disable programs or to include them in folders that are, themselves, disabled. Otherwise, this is pretty simple and not much can go wrong, short of device failure or communication issue.

If Status 'Kitchen_oh' is On Then Wait 2 seconds Set Scene 'Media_Keypad_D' On Set Scene 'Garage_Keypad_D' On Set Scene 'Frontdoor_Keypad_D' On Else Wait 2 seconds Set Scene 'Media_Keypad_D' Off Set Scene 'Garage_Keypad_D' Off Set Scene 'Frontdoor_Keypad_D' Off This looks to me like you are trying to use a program where a scene would be a better solution. Why not get rid of this program and make 'kitchen-oh' controller of the other three scenes?