oberkc

I am curious...what device controls your lights? Inline linc? My temptation would actually be to create two scenes. One soft. One bright. Each scene would have the same responders, but only the single, applicable controller. Set the scene attributes as you describe. Keep your buttons mutually exclusive. Your programs would be nothing more than setting each scene, according to your described conditions. if dusk set scene dim on if motion set scene bright on wait xx minutes set scene dim on You could, of course, do this the brute force method: if dusk set KPLC on set r1 - xx set r2 = xx set r3 = xx etc.... but I think I would try the first option.

I have been experienced mismatches between ISY-displayed status and actual device status. I am told that, under certain circumstances, ISY assumes a status based on commands sent, and does not necessarily rely on a query or response to confirm. Yes, communications sounds to me like a plausible explanation for your issues.

I think I saw something about older switchlinks not able to control all the buttons from ISY. I would have to search the forum to confirm. Regarding the spouse messing with scenes, the options I see all involve some spouse retraining. If you set the local-controlled on level to match that of the scene, then it would be possible to return that light back to the scene level by a single press on. To get to full on, use either two, quick on taps, or press and hold until it reaches the desired level. You have a problem unkown to me. My wife never turns off lights.

I will be interested in this as well. I want to permanently install these types of lights so that I don't have to put christmas decorations up each year (and take them down in the cold).

I was not sure whether you had or had not enabled any of the X-10 addresses. Still, I have heard folks say that they can come from the factory with addresses. If you performed a factory reset before installation, then this is likely not a problem. Under event viewer, I would expect to see an X-10 command, including house code, number, and on/off/dim/bright, etc... It is pretty obvious if it is there. Instructions for removing X-10 addresses are in the instructions for each device. If you don't have them, they are available on-line. In general, put your device into unlinking mode (hold button 10 seconds, then hold again for 10 seconds) then send three consecutive, identical x-10 addresses (it does not matter which).

Is it possible that some of your devices have an X-10 address assigned? I hear they can come from the factory this way. You can watch the event viewer for signs of X-10 activity. If so, follow the intructions for removing X-10 addresses from your affected devices.

Rand, Are you saying that the 2474D and 2475D are different devices, both inline, but with one having limited access to the scene attributes? If so, I would be a bit frustrated with smarthome. If so, then would swapping out the parts from the 2-wire dimmer kit with a "normal" switch and "normal" inline link solve Mr Martin's problems with direct scene control?

if a is turned off or b is turned off or c is turned off ..... Then turn off KPL-A

I understand that the links are stored in the PLM, but program execution requires the ISY.

I did not realize that the ISY configured keypads from 6 to 8 button. Is your old one and new one different button configurations (one and 8 and the other a 6)? If so, have you attempted to manually configure your new one to match the old, then replace?

It appears you have identified a problem with your light fooling your dusk/dawn sensor. When it does, the program conditions change and it stops. I don't yet use insteon motion sensors, but do you have the option to use "control" versus status? I suspect this could cause you problems in this application, as well. I am wondering if first creating a dusk/dawn program with nothing more than: If control "study motion-dusk/dawn" is turned on then else Modify your "study motion" program to read if control "study motion-sensor" is turned on and program "dusk/dawn" is true then set scene "study Lights.Scene" on wait 10 minutes set "study lights/scene" off else This still may suffer the problem with your study lights changing your input conditions before your 10 minutes. I wonder if you will also have to change your battery program condition from status to control.

That is my understanding. Of course, the remote link has to be in linking mode for this to work. Then, to link other devices, use the ISY to create a scene, add to the scene the remote link button you want (as controller), than add any other controllers and responders.

I have a remote link. As near as I can tell, the all on and all off affect the devices that are linked to the remote. I don't think there is any programming. Whatever six devices you have linked to the remote will go on and off at the press of the "all" buttons. The dim and bright affect the most recently controlled device. Turn on device 1, the dim/bright controls device 1 until you turn on/off another device. I hope this helps.

non-toggle off, or non-toggle on?

Link Management >> Start Linking Then go to device and put into linking mode. Once done, your device shoult show up in your "My Lighting" list

You make me interested in the weatherbug module. Without any such experience, I am curious about your thoughts on the following: Do you think the light < 1 behaves as a control or a status? If a control, is is possible that it might transition to this light condition before your time window opens? If so, may there be times when your program does not run? Does it really hurt if this executes repeatedly? Once the scene is on, turning it on again won't have any affect, will it?

I think there is an option to copy or replace a device, but I have never had the need and would have to look into this. I would check the wiki or the forum and search. indeed that sounds like a promising option. One other thought I had was purely experimental. I began wondering if your trouble device does not have a fast on option. I thought, perhaps, to temporarily change the program to simple on, and see if it works. This may further substantiate proper communication or narrow the options down a bit if it works.

I understand this to be normal. This is how it works at my house. In many applications, these are clearly devices. If you view them simply as controls, then I can see your point. If you view these buttons as "displays" or status indicators, then the term device might make more sense. Your program is as I would create. And I would expect this to work. The only thing I can think is that your two all on buttons are somehow different buttons than the ones you think they are, but I am guessing you have this set up correctly. I see a lot of traffic about bugs in various types of devices, or in devices that the ISY does not recognize, but this one does not look familiar to me. Perhaps there are others that can dive a little deeper into this possibility and into your log record. Sorry I cannot help much more.

So it appears that your ISY is seeing even the old KPL. The scene test works, which suggests communication is good. Maybe one of the experts at reading these logs can confirm all is well. I may have missed this earlier, but I now notice you have two buttons you want to use to trigger a scene. In your program, do you use two conditions? For example: If control "KPL New Button" is faston or if control "KPL Old Button" is faston Then set scene "all house" on. Are these two buttons used for anything else? What do you want to happen as a result of a single button press? Do you still have either of these two buttons as controllers of a scene or did you eliminate this as a result of the newfound skills of your 2-year-old?

I cannot come up with any theories why you would have a scene coming on at random times. I am assuming you have no motion sensors putting signals on your lines? It seems plausible to me that it may be possible to come up with some experimental scenes to help diagnose the problem. I would normally think this might be some random X-10-, or insteon-like signal causing problems, but you reset your devices, so none with unkown x-10 addresses. I think it unlikely that a neighbor has a device or controller with the same address. It may be possible for technical support at Universal Devices to recognize something in your log that answers your questions.

Blinking, at my house, suggests communication problems. I suggest opening the event viewer and trying your suspect keypad button. See if the event viewer captures the button press correctly. If not, you may have a bad KPL, or you may have some communication issues. Also, try a scene test on your all house scene. Does it indicate any problems?

There are two options. The event viewer needs to be open to see on-going events. There are no stored data here. No need for excel. In addition to the event viewer, there is also a log. From what I can tell, it stores data from the beginning of time. It does not need to be open. It is here that you can see your activity from overnight.

Like Brian H, I am an advocate of putting a filter on the computer if your PLM is plugged in to the same set of outlets. At the suggestion of those much smarter than I, I eventually added a dedicated circuit for my PLM. Right now, my X-10 communication is good.

I do not believe it has to be linked, other than to the ISY/PLM. You did link it to the ISY, did you not? If not, then begin linking with the ISY and then set the KPL button to link status, adding the device to the ISY device list. This is all by memory, but your if condition would be based on a "control" (not status). If control "KPL Button" is faston Then set scene "all house" on. Or something like that. The ISY will, of course, create the correct verbage.

I don't know about the compare function with regards to the PLM, but I believe there is a restore function. I doubt that it would hurt to try it. Good thought. Regarding the log, my experience is that one needs excel to view it. Also, make sure you enable macro's. It is a useful tool.