LeeG

I am not aware of TriggerLinc operational/functional differences based on which version is being used. File | Restore Modem (PLM) to rebuild the PLM link database

Is the Admin Console showing state changes of other devices? The link records in the TriggerLinc are what are expected assuming the PLM address is 1B.FD.15. Run Tools | Diagnostics | PLM Info/Status to verify the PLM address matches that in the TriggerLinc records. The last thing would be a Restore Modem (PLM) to insure the Responder link records for the TriggerLinc exist. Regarding the last post, the TriggerLincs were added to the new ISY as new devices? This is not a situation where an old ISY backup was installed on a new ISY and PLM? There is no means of checking RF levels

The TriggerLinc is a Controller Only device. Current State will be blank until the ISY receives a command from the TriggerLinc. I would try an Access Point plugged into the same outlet as the ISY PLM with the TriggerLinc close to the Access Point. Insteon RF communication is automatic and autonomous. There is nothing the ISY can do for or against RF communication. The link records in the TriggerLinc can be verified with a Show Device Links Table. Are other RF devices working?

What ISY firmware is being used? Try a new battery and moving the TriggerLinc closer to a Dual Band device EDIT: if there is an External connection the magnet will not register a change in state

Check the Last Run Time column for the Off Program. Does the Last Run Time reflect the expected time? EDIT: if the Last Run Time does not reflect when the KPL button was turned Off then the Program if section and the Folder If section (if Program is in a Folder) are the areas to look at. If the Last Run Time does match when the KPL button was turned Off then the comm is in question. The test earlier in the day verified the link records are correct but does not mean much relative to comm. What appliances/devices are On or Off, what lighting is On or Off, all can affect comm so something that worked in the afternoon comm wise does not mean it will work later in the day with a different pattern of devices and lighting. Insteon Direct device commands are ACKed and have multiple retry attempts. An ISY Scene has a single Insteon message that has no retry capability so comm. must be reliable for a Scene to work

The If Control in the previous version was probably a race condition between the Folder Condition going False and the Program Off actually getting triggered. I think that same race condition exists, perhaps even more exposed now. I would move the Off Program outside of any Folder. I see no use for the Off Program being in a Folder.

Refer to any Insteon wired device User Guide. http://www.smarthome.com/manuals/2477d.pdf

The 2412 PLM (NO LONGER BEING SOLD) provides 12V DC The 2413 PLM provides no power The ISY spec indicates 5-30V DC

The Then clause is driven by the X10 D4/On The Else clause is driven by the X10 D4/Off

In earlier posts there is an 'off' and 'turn off' Program that use If control. In the last post and I think in an earlier post an 'off' Folder using If Control is mentioned. It is not likely a Folder condition using If Control is working as you expect. A Folder using If Status KPL button On will change from True to False to True based on the state of the KPL button. A Folder using If Control KPL button is switched On will NOT toggle True to False to True as the KPL button changes state. Look at Programs | Summary, watch the Folder status for a Folder using If Status versus a Folder using If Control. They operate very differently because there is no False side of an If Control xxx is switched On or If Control xxx is switched Off. A Folder condition is a gate for the Programs in the Folder. The Folder condition allows the Programs under it to trigger (Folder condition True) or not trigger (Folder condition False). The Folder condition is not meant to trigger Programs under it.

Use Common and NC to connect to the TriggerLinc. When the external connection is shorted the TriggerLinc is Off. Open the external connection the TriggerLinc reports On.

This Program will perform the cycles described. If Time is 1:00:00AM Then Set 'EZFlora' On Wait 30 minutes Set 'EZFlora' Off Wait 5 minutes Set 'EZFlora / EZFlora - 2' On Wait 30 minutes Set 'EZFlora / EZFlora - 2' Off Wait 5 minutes Set 'EZFlora / EZFlora - 3' On Wait 30 minutes Set 'EZFlora / EZFlora - 3' Off Wait 5 minutes Set 'EZFlora / EZFlora - 4' On Wait 30 minutes Set 'EZFlora / EZFlora - 4' Off Else - No Actions - (To add one, press 'Action') I have read where it is not good to water in the middle of the night as the dampness can cause fungus. Don't know if that is true. I start my cycles around 6 AM for whatever that is worth.

A Controller can affect a Scene and drive a Program. A Responder reacts to a Scene and can be controlled by a Program. Basically a Controller is sending commands to a Responder, a Responder is receiving commands from a Controller. Define one ISY Scene. Add the outside devices as Responders. Add the KeypadLinc buttons as Controllers. When the Scene definition is complete, any of the KeypadLinc buttons defined as a Controller can turn the outside lights On or Off. The other KeypadLinc buttons will turn the button LED On/Off as all the KeypadLinc buttons are cross-linked.

The most common garage door control is a single NO button connected to two wires. Pressing the manual button shorts the two wires together. The I/O Linc Relay is simulating a manual button press, shorting the two wires together. With a three button controller using 2 wires it is no longer a simple short the 2 wires together to accomplish three different functions. The momentary timeout value can be played with to see if a value can be found that is reliably interpreted as move the door by the door opener. The absolute way to insure reliable operation is to connect the I/O Linc Relay wires across the Controller button that causes door movement.

The momentary mode timeout value display is not correct. This is expected to the fixed in the next beta drop. What was it set to originally? The momentary timeout value may be having a problem moving the door and not interfering with the multiple button controller. The only programmatic moving of the garage door occurs at Sunset -30 using the posted Program?

Button A has two responders: 1C.CC.50 1D.9B.E1 Button B has two responders: 1C.02.91 1D.9B.E1 Button D has one responder: 1A.B1.E4 The remaining buttons have no responders beyond the PLM for state change awareness as all the buttons have The Restore Device took 20 seconds from first command to last ACK. The RF comm. is consistent in this event trace. For the RemoteLinc2 to have timed out of the 4 minute awake time in earlier attempts I would expect the RF comm. was compromised by something. Distance from Dual Band device, orientation to Dual Band device, something causing RF interference such as a baby monitor.

Sent a PM with my email address

Is this a RemoteLinc or RemoteLinc2? Resetting the RemoteLinc effectively leaves half links in whatever devices were linked to the RemoteLinc. The half links can allow the responders to react even though the RemoteLinc is missing the other half of the link. Not a good situation as the Scene protocol messages between the RemoteLinc and the responders is compromised. Run Tools | Diagnostics | Event Viewer with Level 3 selected. Put the RemoteLinc into linking mode. If a RemoteLinc press the Dim/Bright buttons together until LED blinks. If RemoteLinc2 use its Set button. Then do a Restore Device on the RemoteLinc Primary node. Start the Restore as soon as possible after putting the RemoteLinc into linking mode to take advantage of as much of the 4 minute wake time. The RemoteLinc should stay awake past the 4 minutes if receiving commands. However, if the RF comm to the RemoteLinc is marginal it may not be seeing all the commands. Post the event log.

Latch mode is an I/O Linc Relay option. In Latch mode the relay does not turn Off automatically. An explicit Off command has to be sent to turn the Relay Off. What is the momentary timeout value? With the opener light coming On the opener got a simulated button press but did not move. What type of door controller is being used? Simple push button or multi button controller. When the Light turns On but the door does not move is that the Program running that is in this post or some other means of directing the door to move.

The last link record, which happens to be for the ISY Scene in question, has been marked deleted. 0FE8 : 22 11 19.84.F0 FF 1F 01 The 22 is the Flag byte which indicates the link record has been logically deleted. Try a Restore Device for the LampLinc and run another Show Device Links Table. The 22 should become A2. If the Restore Device does not resolve the problem, remove the LampLinc from the Scene and add it back.

The results of turning the SwitchLinc On/Off directly will not affect any devices that may be linked with the SwitchLinc. That is the way Insteon works. To have both the SwitchLinc and KeypadLinc react together with the Admin Console or with an ISY Program the Scene name has to be turned On/Off. Functionally that is what happens when the SwitchLinc paddle or KeypadLinc button is pressed. The Scene is turned On/Off. Insteon devices do not have the functional capability to send Insteon Direct device control commands. When a paddle/button is pressed a Scene is always controlled. Only HA applications through a PLM have the ability to send Insteon Direct device control commands which operate only on the device being controlled, not any linked devices. Setting beep duration sounds the beeper in the device. Most devices have not implemented variable beep control so changing the duration of the beep request does not change the length of the beep.

Device 18.9D.AC specifically NAKed the Scene request. If these are LampLincs were obtained after March 2012 they are I2CS devices which have requirements not seen in other devices. Right click the LampLinc node, select Diagnostics | Show Device Links Table followed by Compare button click when Show display completes. Are the link records correct? Can the LampLinc be controlled On/Off through the Admin Console. The LampLinc that does not work is I2CS. Is the ISY and the Admin Console at 3.2.6 which is required for I2CS support?

Michel Did you notice all the addresses started with FF. That seems unusual for some many different Insteon addresses.

The Relay status has no relevance. For a garage application the I/O Linc Relay is in momentary mode. The Relay is On for a few seconds to initiate door movement, then turned Off automatically by the momentary mode timeout. The Relay is a Responder Only so it does not report back that it has been turned Off automatically. For the Relay to show Off something has sent an Off command to the Relay. It makes no difference to the operation of the I/O Linc Relay as it is physically Off anyway but look for something in a Program that is issuing an Off command. Or a Scene is sending an Off command which can turn the Relay On for a few seconds depending on which momentary mode is defined. See the I/O Linc User Guide for the characteristics of the three momentary modes. The various command responses are associated with Scene On/Off only. An Insteon Direct command always turns the Relay On and an Off command always turns the Relay Off (normally a no-op as the Relay is normally Off).

Right click the Scene name, select Diagnostics | Scene Test. Is the test successful? The ISY Scene does not have automatic retries associated with Insteon Direct commands so a Scene may have issues if the powerline is marginal to those locations. The Scene Test will verify the necessary link records are present. Responders is fine.