oberkc

xothros is, of course, correct. This is one of those details that I continue to forget. In case it is not clear in his updated example, "scene1" would be a newly-created scene with a single responder: KPL1D.

Actually, I think it was Brian H who offered that explanation, but I certainly agree with it. The other point I wanted to make was that using ground as a neutral would not just be a violation of the UL certification basis, but a violation of the NEC (and almost certainly of any local building code).

It is not obvious from me, based on your post, that you have confirmed existing wiring matches the instructions. Does it? It is important to note that the instructions are based on one way to wire a three-way. There are other ways, also. It is more important to understand how your house is wired, so be sure to confirm actual wiring rather than instructions.

The answer to this question could dictate a solution. If it does not matter, simply make KPL1D a responder to scene 2 (which would cause KPL1D to come on and off with scene 2, probably my preference). If you would prefer KPL1D to stay off in response to scene 2, but want KPL1D to turn off when scene 2 goes off, this suggests to me that a scene will not work and that you would need a program, such as: As I see it, KPL1D is an indicator showing that the load on switch 1 is on. I would want KPL1D to come on any time switch 1 goes on, including with scene 2

Unfortunately, I don't have an elk (which is why I did not initially respond). I don't know what triggers elk conditions, nor the difference between "toggled" or not. Obviously, something is triggering these programs (in some cases true, in some false). The only thing I can think to do would be to perform experiments, attempting to duplicate the conditions, and watch the event monitor and program status list for clues as to what is triggering them.

Only if you put something in both "then" and "else" clauses. In some cases, a stream of "on" commands may be a limiting factor. I have not noticed any problems in my setup. But, all other things being equal, I would rather limit a stream of commands, as you suggest.

A great option if you are trying to avoid an ON delay, but still limiting regarding ability to apply conditions for when a device responds motion lighting. If, for example, you wish to have motion work only on weekdays (or only during certain times of the day) for some reason, such an approach falls short. Programs offer greater flexibility for defining conditions necessary to trigger responder devices. Take wswartz question for example. Let's say you want to trigger a light and countdown timer to 50% from motion, but only if the light is not already on (or at a different level). I believe that will be very difficult using a scene relationship between the sensor and light. On the other hand, this is relatively trivial from a programmed response. This is the one that I like, actually. I don't use scenes for motion, at all (can live with the delay). I want to restart the countdown at each sensing of motion, whether every second, or less frequent. The non-sensing mode, I understood, would trigger a built-in timer that would continue uninterrupted (regardless of subsequent motion) and send an off command at the end of the time period (again, regardless of subsequent motion). But, since I don't use it, I may be mistaken.

Of course it could. Programs often fill in the capability gaps. One downside to programs is a slight, but noticable time delay. Below is a general idea (syntax not perfect) of a program that will illuminate a keypad button whenever another switch is anything but completely off: if: status "dimmer" is not off then set "keypad button" on else set "keypad button" off

Thus, the tradeoff. Use scenes when your needs are simple: motion = on always. Use programs when your needs become more sophisticated: motion+time+devicestatus+temperature+date=on else off. The question here is whether the added control of programs is worth the cost in time delay. More my purposes, the silly "sensing" mode works well. I have motion sensors outside. So long as the sensors continue to detect motion, the lights stay on. When the motion sensors stop seeing motion for my defined time period, they go off. I like it.

I have no Elk module, and don't understand elk rules, or elk-based conditions. One thing I do notice, however, is that I see program to send any notifications regarding Kristen. This may explain why "not Kristen". I assume this all has to do with triggers, and when are elk conditions triggered? Any change in output? Upon queries? It seems to me that what is going on here is that these programs are being triggered at times not anticipated.

ngeren If you wish to further experiment, press and hold (either dim or brighten) the master keypad. Set the state in various states of brightness and note whether the linked keypad button consistently goes on or off at a certain dimming level. Like LeeG says, this will not work controlling the device via ISY.

I can't say that I have ever seen a load switch have its led's ramp up slowly but yet have the actual load come on instantly. Other than a defective switch, I don't know why that would happen. I thought we were talking about the ramp rate of a "virtual switch". I understood "virtual switch" as one which does not directly power the load. If true, it is absolutely possible that a virtual switch could have a 2-second ramp rate when the switch controlling the load has zero ramp rate.

Yes. Sometimes it is nice simply to use devices as intended. There can be a lot of freedom when the ability to tinker with devices is taken away...it gives us more time to spend doing more important stuff.

Of course, KPL button backlights are either ON or OFF. They have no way of showing a DIM setting. My experience is that KPL buttons and other insteon ON/OFF indications can show OFF when a linked dimmable controller device goes below half. Is it possible that you are seeing this type of behaviour?

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.