oberkc

OK. So...everything is working like you hoped, but you just wanted a better understanding of the event log?

I have found nothing that I can do manually that I cannot do with the ISY, but many things with the ISY that I cannot do manually. I have also found no limitations that the ISY imparts upon devices. I may have misunderstood your problem, but I also have some 6-button dimming keypads, programmed through the ISY. I can still dim the hardwired light. Press and hold. Am I missing something here?

I would watch the event viewer while you press your remote buttons to make sure that the event is recieved and is consistent with the "if" condition of your program.

It sounds like your program executed exactly as intended. Is this correct? I assume you refer to the status as indicated by the admin panel? My guess is that, since motion sensors do not listen for insteon signals, nor respond to them, that the ISY does not recieve an acknowledgement back, so it assumes that is remains on. I am not sure that this will create a problem for you besides being a nuissance when you open the admin panel.

Yeah, I miss MSDOS. Yes, I agree, there is some level of learning curve with this little black box. Still, I would not like to go back to running through the house pushing buttons. And the programs (if, then, else) is something that cannot be done without a device like this or some other automation software.

I have never been able to get this to work. I am not sure that this helps, but one thing you can do through a program is adjust the on levels and ramp rates for devices within scenes. Perhaps this offers some options to accomplish your goals.

I suspect this has something to do with your keypad being non-dimmer. Is this a possibility? I have a scene not unlike yours and notice the same thing. When the main scene is selected, all devices show up. Even ramp rates and on levels, even though ramp rates and on levels are not adjustable with relay keypads. Then when you choose one of the controller devices (keypad C, in your case, all devices that are not dimmer go away). Since on levels and ramp rates are not adjustable on relays, I guess the question is not why they don't show up, but why they do when the scene is selected. I also recall certain issues with controlling the load button with another button on the same keypad, but I think this had to do with the mutual exclusion option. If your keypad is a dimming version, we will have to dig a little deeper. Perhaps the forum's smart people have some other ideas.

Out of curiosity, are the other keys lit while in the off condition? My experience is that non-toggle off buttons will be dim, based on the setting of the entire keypad. I recall, too, that earlier models of keypads have differing capabilities with regards to backlighting and ISY access to this feature.

How did you program the A button? Through the ISY or at the keypad? Remember, or be advised, that these devices, including the ISY, allows one to set different on levels, depending on how a scene is activiated. One could set it up to turn on at 50% if activated by the ISY/PLM and 100% if activated by the keypad. To check, open the scene where you can see the included devices. Click on the scene folder. I assume you see the on level for light B at 50%. Now click on keypad A (within the scene). What is the on level for light B now show? Does it show 100%. If so, change it to 50%. I think, too, there is an option to copy setting from scene. If not, we will have to find another solution.

Yes, I agree with MarkJames. Unless you see signs of problems, not to worry. Still, it would be interesting to know what this is, and why it happens. I have recently heard that access points also have insteon addresses. I wonder if these sometimes show up in the device' links database.

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