kaybee335

Understood - thank you.

Can I ask why only the ON button is assigned to the scene and not the OFF button? I assume this is handling the ALL ON key from the KeypadLinc. Why does the ALL OFF case not have to be handled? I don't own any KeypadLincs currently so I can't try this out to see what is going on - just trying to understand. Thanks, Kris

The ISY/Insteon-fu is weak with this one Still getting my head wrapped around devices, scenes and programming the ISY (which is a subject unto itself - simple things are really simple, complex things on the ISY can sometimes be REALLY complex). I had pretty much come to that conclusion about the Open/Close and had read that portion of the User Manual. That was why the earlier statement about this was more of a rant than a "how do I?". Thanks again for the help, Kris

Thanks Lee. I did not correlate the statement in the user manual saying with the jumper un-installed it triggers one of two scenes as resulting in two different devices appearing in the ISY. As far as series/parallel - I probably wasn't clear on what I was trying to do. I thought I could use both the internal sensor mounted on a door and then run an external sensor line out to a nearby window. The external and internal sensor seem to be wired internally in parallel so, as long as the door remains closed, I will never see a change of state on the external sensor no matter what combination of series/parallel wiring or NO/NC switches I use. I probably don't care if the window is open when the door is wide open as well. What I want to know is if the window is open while the door is closed and it seems there is no way to get there from here. Or I could be all messed up in my understanding again .... Thanks, Kris

I have a number of wireless Open/Close sensors (2843-222) linked in to my ISY. Each sensor shows up as two separate devices, one with the suffix "-Opened" and the other with the suffix "-Closed". The "-Opened" device updates appropriately based on the state of the sensor but the "-Closed" device never gets a state update (as far as my observations go, after linking you will not get a state update until there is a transition - I think this is because it is a battery powered device and it essentially sleeps until it has something to say). What is the "-Closed" device supposed to be showing? I thought it might be showing the state of the external sensor terminals inside the sensor itself but if I jumper those terminals, the external contact closure state is added in parallel to the internal closure state as described in the docs for the sensor. Why something that is most likely going to be used in a security application would do that in parallel rather than series is completely beyond me - I want to know if either sensor is open not if either one is closed (but that is a rant for another time What is the device with the "-Closed" suffix supposed to be showing me? Thanks, Kris

Thanks very much for the prompt response folks!! I am new to the Insteon/ISY world (from X10 and misterhouse) so still trying to understand the various advantages/limitations and (some) quirks of the various types of devices/controllers/etc. The explanation makes perfect sense to me and I know what to watch for in similar situations now. Off to solve it by programming .... redsfancfp - my apologies for jumping in on your question with something unrelated. I hope you find or have found the solution to your issue. Thanks again, Kris

I have a question that I think is related to this. I have a RemoteLinc (6 scenes, separate ON/OFF buttons for each scene) and a RemoteLinc2 (8 scene) in toggle mode where I am trying to use one press to turn on or off the controlled device based on it's current state (ie. go to the opposite). I am trying to get each RemoteLinc to reflect the associated state of the other switch. No matter what I seem to do the state of the two controllers does not seem to track. I have tried the following: - place both RemoteLincs (as controllers) in the same scene with the device being controlled. They show independent states. Try copying Scene attributes - still independent states. - place both RemoteLincs in the same scene (virtual two way, I guess) and have device being controlled in a separate scene. Still no luck with any variation of copying scenes. The reason I think this is related is LeeG's statement "The ISY will automatically cross-link the devices so they are in sync with each other". I am not seeing the state of the on/off RemoteLinc track the state of the toggle RemoteLinc2 or vice versa. One will say OFF while the other will say ON. Neither seem to be linked to the actual state of the device being controlled (an OutletLinc). I am currently running FW 4.0.1 (UI 3.3.9) but this is a problem I have been struggling with through previous FW versions as well. I could solve this programmatically in the toggle switch logic but unless I am totally misunderstanding things here (which is quite likely), I shouldn't have to. Not trying to hi-jack the thread - let me know if you want me to re-post as a separate issue. Thanks, Kris