upstatemike said:
Thanks. I had it explained to me so I think I understand it now. You don't really link a switch, you link a load to a button. Could be a button on another switch or the button of a keypad. If you want three switches to be slaves to a fourth "master" switch, the load of each slave gets linked to the button of the master.
For a virtual 3-way circuit the load for each switch must be linked to the button of the other. That way pushing either switch will control both loads. (As far as I know the load of a switch is always controlled locally by it's own button... unlike UPB where that does not have to be the case) The status LEDs are considered part of the load so even if one of the switches is only used as a transmitter with no lights attached, you still have to link its load (the LEDs) back to the button on the other switch so that all the LEDs stay in synch.
The LED on a keypad button is also considered a load from a linking perspective. If you link a keypad button to the load of a switch, the keypad will turn on the switch but if you want the LED on the keypad to go on when the switch is activated locally you also have to link the keypad button's LED (its load) to the button of the switch.
This is kind of a different way of looking at it so someone let me know if I'm still off-base.
Hey Mike,
You're absolutely correct! The LEDs on the INSTEON SwitchLinc are in a sense "physically" connected to their SwitchLinc load output. If the load is ON, the LED will reflect it. There is (currently) no way to have the LEDs NOT reflect the current state of its load output, unless of course you were not using it to physically control a load, but rather as a controller (virtual 3-way) for another SwitchLinc. If you were using a SwitchLinc (A) to control another (B ), basically using it (A) as a controller, you must link it (A) to the other (B ).
This is great if you want to control 'B' from location 'A' but what happens in the following example:
After linking A to control B you turn on "B" by pressing "ON" from 'A'.
Now you goto "B" and you turn it (B ) "OFF" from 'B'.
Well if you've only linked 'A' to control 'B' you'll notice that the LEDs on 'A' (the controller) will still be illuminated, showing (or indicating) that the load (physically controlled by B ) is still ON.
But we know it's OFF because we just turned it OFF @ location B. However, in order for location 'A' (the controller) to "know" that you've turned OFF B, you need to "cross-link" B to control A. So basically you link A to B then "crosslink" B to A.
Crosslink = A to B, then B to A
The same is true for controlling a SwitchLinc (or any device) from a button on a KeypadLinc. Since the buttons KeypadLinc have LEDs for each button (acting as little indicators) it's important to "crosslink" the keys with the SwitchLinc (or other INSTEON devices) being controlled by that key. This will ensure that the LEDs on the KeypadLinc will always reflect the true state (On/Off) of the device(s) it’s controlling.
I hope this helps clear up some confusion. If not, let me know. I have lots of personal experience with linking and cross linking.
Regards,
Mike Fernandez - Dr. Buddha