Trouble linking TriggerLinc (2421)

[wswartz]

Hello,

 

Recently purchased an ISY-99i and must say I'm lov'in it.

 

I tried to link a new TriggerLinc and can't seem to get it to work. I tried the linking process with various degrees of success/failure. Following the directions, I added the device manually. The instructions said to follow the on screen instructions for when to hit the SET button; I never get any instructions. After a bit, I hit the set button anyway. From the event viewer, I see it try to communicate, but eventually, in most cases, it just fails. I did get it to link once, but the moment I tried to use it in a scene, it gets and error saying it can't communicate and gives a red ! next unit. Tried several times to Write Updates to Device but it never works. Before trying it again, I would set the TL to factory defaults; this doesn't seem to help.

 

I tried doing this in an area where another RF device is working fine (a motion sensor). Also put the TL within 2ft of the dual band PLM with no luck.

 

I was able to manually link this TL to a KPL and that works flawlessly. I could leave it this way as this was my end goal, but it sort of defeats the point of using ISY to manage everything in the network.

 

I'm running v3.1.15. Upgraded to get a new Dual Band KPL to work which wouldn't prior to the upgrade.

 

Thanks.

 

WS

[Michel Kohanim]

Hello wswartz,

 

With TriggerLincs, you have to make sure you have a good battery and that you make sure it's in programming mode: press and hold the set button till it starts blinking.

 

In all cases that I have dealt with, 99% of the time, the problem was the battery.

 

With kind regards,

Michel

[wswartz]

Thanks for the suggestion. Had a brand new battery (measures 1.57v), and as I said, it links up fine directly with the KPL. Once linked manually to my KPL, it's quite reliable and from several areas of my house (including where I'm testing - about 2ft from the PLM).

 

Before attempting to link it to ISY, I unlinked it from my manual KPL link.

 

I replaced the battery (1.61v) and tried to link again with the same (negative) results. First attempt actually linked, and I could even get it to show in the admin console when it was ON vs. OFF. However, I could not add it to a scene as it was not fully initialized and had a red ! next to it. Several attempts to Write Updates to Device failed with error "Cannot communicate with . Please check connections." Not sure this is the case as there is no issue talking to my KPL.

 

On subsequent attempts, I deleted the TL and attempted to do it again. After 4 more tries, I was not able to get it to link. Each time, it failed with the error, "Failed writing the highwater mark [-200000/-1] Node not added - failed removing links (14 89 B1 1) [-200000/-9]". After each attempt, I've done a factory reset on the TL just to be safe.

 

Something else interesting; even with out being linked, I can see events showing up in the Event Viewer whenever I activate the TL so it seems to be broadcasting it's status, and ISY is picking up this status just fine.

 

Again, during this process, ISY never tells me when I should place the TL in Link mode. After selecting Link Management, New INSTEON Device, I fill in the address (read from the sticker and verified from the Event Viewer), Name, and Device Type [10.02] (2421) TriggerLinc. I select "Remove existing devices", but also have tried "Add Devices Found in Links and remove existing links"; both with the same results. After hitting OK, I immediately get a message box saying, "Initializing System", and it seems to be scanning for the TL. I've tried to do noting and see it if finds it, I've also tried hitting the Link button right after I hit OK to add the device; neither seem to matter.

 

Any other thoughts?

 

WS

[LeeG]

Put the TriggerLinc into link mode by holding the TriggerLinc Set button until Green LED is blinking. Then proceed with the New INSTEON Device process. Actually all the fields in New INSTEON Device can be filled in, put the TriggerLinc into linking mode, then click Ok

[wswartz]

Thanks, I haven't tried starting the TL linking BEFORE hitting OK on the ISY setup. But I'm still having the same issue.

 

I got it linked (again), but still getting the communications errors when trying to add it to a scene. Here is a snippet from the Event Log:

 

Thu 12/29/2011 06:00:25 PM : [14 89 B1 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............]

Thu 12/29/2011 06:00:25 PM : [iNST-ACK ] 02 62 14.89.B1 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 00 06 (00)

Thu 12/29/2011 06:00:34 PM : [iNST-ACK ] 02 62 14.89.B1 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 00 06 (00)

Thu 12/29/2011 06:00:42 PM : [iNST-ACK ] 02 62 14.89.B1 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 00 06 (00)

Thu 12/29/2011 06:00:46 PM : [14 89 B1 1 ] Link 3 : 0FE0 [0000000000000000] *Failed Writing [00..............]

 

Activating the TL causes the ISY admin console to detect whether it is on or off. These are the messages I get when I toggle between open and closed:

 

Closed:

Thu 12/29/2011 06:09:23 PM : [iNST-SRX ] 02 50 14.89.B1 00.00.01 C7 13 01 LTOFFRR(01)

Thu 12/29/2011 06:09:23 PM : [ 14 89 B1 1] DOF 1

Thu 12/29/2011 06:09:23 PM : [ 1B 56 1 6] ST 0

Thu 12/29/2011 06:09:23 PM : [ 14 89 B1 1] ST 0

Thu 12/29/2011 06:09:23 PM : [iNST-SRX ] 02 50 14.89.B1 00.00.01 C7 13 01 LTOFFRR(01)

Thu 12/29/2011 06:09:23 PM : [iNST-SRX ] 02 50 14.89.B1 00.00.01 C7 13 01 LTOFFRR(01): Process Message: failed

Thu 12/29/2011 06:09:24 PM : [iNST-SRX ] 02 50 14.89.B1 19.74.C6 46 13 01 LTOFFRR(01)

 

Open:

Thu 12/29/2011 06:09:36 PM : [iNST-SRX ] 02 50 14.89.B1 00.00.01 C7 11 01 LTONRR (01)

Thu 12/29/2011 06:09:36 PM : [ 14 89 B1 1] DON 1

Thu 12/29/2011 06:09:36 PM : [ 1B 56 1 6] ST 255

Thu 12/29/2011 06:09:36 PM : [ 14 89 B1 1] ST 255

Thu 12/29/2011 06:09:37 PM : [iNST-SRX ] 02 50 14.89.B1 19.74.C6 47 11 01 LTONRR (01)

 

Testing performed right next to a dual band PLM.

 

WS

[LeeG]

Is the TriggerLinc in linking mode before the Scene changes are made?

 

EDIT: The blue trace entries indicate the device is not responding to the commands the ISY is issuing. This is what a trace looks like if the device is not in linking mode.

 

EDIT2: running 3.1.16 a popup is displayed regarding establishing linking mode when the Device Type TriggerLinc type is selected.

[wswartz]

OK, this is darn weird. I got it working; here's what I did:

 

1. Manually setup up the TL under Link Management, New INSTEON Device per documentation (didn't hit OK yet).

2. Put the TL in linking mode.

3. Hit OK on the New INSTEON Device screen.

4. Let it discover the device, rename it and add it to the proper folder. The TL was still in linking mode so I turned that off.

5. Added the TL to a scene with a KPL. Got a communications error (red ! next to device). Strangely enough, the link to the KPL worked (didn't notice that before)

6. Right clicked on the TL and selected Diagnostics, Show Device Links Table.

7. At this point I got the dialog box I'd expect to get after my step 3 above, that is, a box telling me to put the TL in linking mode. Put it in linking mode.

8. Green arrows saying, "Writing", appeared next to the TL's. Soon after that, all the errors went away.

9. Everything is working as expected.

 

Just for fun, I deleted the device, factory reset the TL, then ran through these steps once again. Did it the same way a second time.

 

Thanks for all the responses.

 

WS

[LeeG]

The KeypadLinc does not sleep so the link records to the KPL will be written. All battery powered devices turn the RF circuitry Off to save battery life. Once Off it is impossible for the RF device to receive any command. It is always best to put the RF device into linking mode before the ISY attempts to write to it. Waiting until the commands are in progress before establishing linking mode could produce unexpected results. If that step is forgotten let the ISY realize no communication is possible marking the node with a red ! or Green Icon indicating pending updates. At that point put the device into linking mode and click the Write Updates To Device option to initiate the update process..

[wswartz]

OK, understand now how it works. Need linking mode not only for initialization, but also for updates.

 

BTW, I just upgraded to v3.1.16, deleted all the TL config and reset it to factory defaults. Unlike your 'EDIT2" above, I still didn't get a dialog box asking me to put the TL in linking mode. I then proceeded to run through my steps 1-4 which worked. At step 5, I put the TL back into linking mode and proceeded to add it to the scene which also worked. No need for steps 6-8.

 

Thanks for all the assistance!

 

WS

[LeeG]

Check Help | About and be sure the Firmware and UI lines both say 3.1.16. If not then clear the Java cache and be sure the URL being used invokes the 3.1.16 Admin Console.

[wswartz]

Confirmed. I'm at v3.1.16.

 

WS

[LeeG]

If both the Firmware and UI lines indicate 3.1.16 I don't know why you do not see the popup. Maybe Java level. What OS and browser is being used?