matapan Posted March 6, 2012 Posted March 6, 2012 I installed my first Triggerlinc in my network today. Two nodes appear in the Admin Console device tree when a Triggerlinc is added. Curiously, only the Open node seems to track state information for the device. The Closed node remains blank regardless of the device state. There is a passing reference to this behavior in this discussion here: viewtopic.php?f=25&t=7932&p=60477&hilit=triggerlinc+triggerlinc+node#p60477 Apparently, the jumper setting affects when the open and closed nodes are updated, using something called Group 1 and Group 2 commands. Trying this setting out, I noticed that removing the number to update both the Open and Closed nodes appears to be hardly useful. Only an On state is reported when the device is toggled, and the state information is persistent - when the device is not ON, the node state is not cleared. This results in the node state recorded for both nodes being ON all the time. On the face of it, this appears to be totally useless. What is the intended use for this setting, when the jumper is removed from the Triggerlinc? If you simply want to track states from a sensor attached, does one simply use the jumpered setting and the Open node for state information? I think this is the case, but before I make that assumption here, I thought I'd ask the question on this forum. The blurb about the Triggerlinc behavior and the jumper setting in the side discussion referenced is useful info. Can we add this to the appropriate Wiki page referencing the Triggerlinc?
LeeG Posted March 6, 2012 Posted March 6, 2012 “What is the intended use for this setting, when the jumper is removed from the Triggerlinc?†From the TriggerLinc User Guide…. This mode is ideal when you need more flexibility: - For rooms where you want the lights left on after the door is closed – simply don’t Link any Responders to Scene 2 in this case - Turning lights on at full-bright when a door is opened and dim when the door is closed - Activating two independent scenes when a door/window is opened as opposed to closed “ If you simply want to track states from a sensor attached, does one simply use the jumpered setting and the Open node for state information?†Yes. “On the face of it, this appears to be totally useless.†Some Insteon devices have features that are useful where no automation is in use.
matapan Posted March 6, 2012 Author Posted March 6, 2012 Then the issue lies with how IOLinc's scene activation is reported in the Admin Console: - If I understand IOLinc's documentation correctly with respect to the multi-scene mode feature, when the contact is open, then one of the scenes is activated. When the contact is closed, the other scene is activated. Presumably, when one scene is activated, the other is not. - Only an ON state exists in the Admin Console when the IOLinc is set up to use multi-scene mode. There is no blank state or OFF state. Once the ON state is reported in the Admin Console, it persists, until such time that the ISY is restarted. Is this really the intended behavior? - If the first assumption regarding exclusive node states is correct, then the Admin Console would presumably report an ON for one node and a BLANK or OFF state for the other. Neither node would ever have the same state. So, the problem is really about how to get the Admin Console to correctly show which scene was activated in multi scene mode.
LeeG Posted March 6, 2012 Posted March 6, 2012 As the TriggerLinc is a Controller Only device the Admin Console reports the last command received from either node. This is true for all Controller Only devices, not just the TriggerLinc. With the TriggerLinc jumper removed the TriggerLinc sends On commands ONLY, to one node or the other depending on whether the magnetic switch goes to Open or Closed. With the jumper removed no Off commands are sent so the Admin Console will not show an Off status.
Recommended Posts