Problem with TriggerLinc 2421

[RussD]

Hi, I have a complete home system with 100+ devices and have had no problems until today. This is the first time I am trying to use the 2421. I am using an ISY99i/IR PRO at version 3.2.6.

 

I was able to add the TriggerLinc device using Link Management > New INSTEON Device, then entering the address, name, and selecting "[10.02](2421) TriggerLinc" for device type. I used "Remove existing links" and the device appeared to link OK with no errors. However when I open/close the contact I am seeing no status change. Launching the event viewer and setting the level to "Device communication events", I am seeing no status changes in the event log.

 

Thinking it may be a problem with the device, using a brand new battery I tried another as I purchased (4). The second appeared to link fine also with the communication events showing writing and the ack's back. After the linking was done I again tried opening/closing the contacts with no events shown in the event viewer.

 

Thinking it may be the RF or the device I removed the 2421 from ISY, and manually added the living room light switch directly to the TriggerLinc. I have full control of the light and I can move the TriggerLinc throughout the main floor without problem.

 

This is when I started having bigger problems. Since the TriggerLinc was controlling the light, I attempted to add the device back to the isy99i instead of using "Remove existing links", I choose "add devices found in links and keep existing links". During the linking I could see writes happening to several other devices listed under My lighting. When the linking finished I had new scenes for the Coffee Maker, Dinning Room Light, Master Closet, and changes to KeypadLinc's in the master bedroom. None of these have anything to do with the TriggerLinc and the only device it was linked to was the Living Room.

 

After cleaning up the scenes, I tried adding the TriggerLinc again using "Remove existing links". Still no status updates in the event viewer. I then created a new scene and added the TriggerLinc and a light. The TriggerLinc now controls the light but the scene status is not being updated. It appears I can write to the TriggerLinc and add scene devices for it to control but the PLM is not seeing any of the status updates.

 

One thing I did notice when linking manually, the TriggerLinc status light changes from flashing (linking mode) to off as soon as the device has been added. When linking in the isy99i, the light continues to flash until I push the set button twice to get it back to normal mode. Not sure if this means anything.

 

The TriggerLinc's are showing "5011 REV 1.3" on the address sticker.

 

Thanks for the help.

Russ

[LeeG]

Run Tools | Diagnostics | Show PLM Links Table. When the display is fully populated with PLM link records click Count to get a count of the PLM link records. The Show/Count should be done at least 3 times to see if the Count is consistent. Any Insteon traffic reaching the PLM during the Show process will result in an inaccurate link record display. Post PLM the link record count.

 

The TriggerLinc LED blinking difference between a manual Set button link and ISY linking is normal. The message exchange for a Set button link is different. Unless the device supports Set button multi device linking the LED will stop blinking at the end of the first Set button link.

[RussD]

Ran three times all with the same count 507 / 507 / 507. I am using a 2413S PLM.

 

I also tried Diagnostics > Show Device Links Table on the 2421. Very strange. It is showing all kinds of links today that do not make sense. The device dropped out of linking mode before the complete table could be retrieved. Yesterday when I tried it there were only (3) links. I saved the links table but it will not let me upload it (possible acctack vector). Extension txt was also not allowed when I tried to add the event viewer.

 

Here is some of the xml:

40882482491644850816645887 -40802402411592216416119543 -40722322331539582015593199

40642242251486947615066855 -40562162171434313214540511 -40482082091381678814014167

 

Thanks Russ

[LeeG]

Run Help | About, check Firmware and UI lines both indicate 3.2.6.

 

It gives the appearance of being an I2CS device that was not added under 3.2.6 UI.

 

0FF8 : F8 F9 FA.FB.FC FD FE FF

0FF0 : F0 F1 F2.F3.F4 F5 F6 F7

0FE8 : E8 E9 EA.EB.EC ED EE EF

0FE0 : E0 E1 E2.E3.E4 E5 E6 E7

0FD8 : D8 D9 DA.DB.DC DD DE DF

0FD0 : D0 D1 D2.D3.D4 D5 D6 D7

Device Record Count : 6

[RussD]

Both Firmware and UI look OK.

 

Help > About

Firmware:

Insteon_UD99 v3.2.6 (2012-05-04-00:26:24)

UI:

Insteon_UD99 v3.2.6 (2012-05-04-00:26:24)

 

Thanks Russ

[LeeG]

The TriggerLinc was added to the ISY under 3.2.6? If so ...

 

Delete the TriggerLinc. Run Tools | Diagnostics | Event Viewer with Level 3 selected. Add the TriggerLinc to the ISY and post the event trace.

[LeeG]

An additional possibility. If the ISY is accessed locally and remotely both environments need to be checked for the correct UI level (Help | About) It is possible to have one environment running 3.2.6 Admin Console and the other still invoking say 3.1.17 Admin Console if the Java cache was not cleared or the wrong URL is being used to invoke the Admin Console.

[RussD]

Here is the event log when I added the TriggerLinc. Still not seeing any events after linking when I open/close contacts.

 

When I connected remotely today it was an RDP session to this computer. Checked Help > About again. Both at 3.2.6.

Thanks Russ

 

Mon 06/11/2012 06:03:20 PM : ---- Initializing the linked devices ----

Mon 06/11/2012 06:03:20 PM : ---- All Linked Devices are now initialized ----

Mon 06/11/2012 06:03:20 PM : ---- Add remaining devices ----

Mon 06/11/2012 06:03:20 PM : [iNST-TX-I1  ] 02 62 14 8E 08 0F 0D 00

Mon 06/11/2012 06:03:21 PM : [iNST-ACK    ] 02 62 14.8E.08 0F 0D 00 06                 (00)

Mon 06/11/2012 06:03:21 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 0D 01           (01)

Mon 06/11/2012 06:03:21 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 06:03:21 PM : [14 8E 8 0   ] Calibrating engine version

Mon 06/11/2012 06:03:21 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2

Mon 06/11/2012 06:03:21 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06        (00)

Mon 06/11/2012 06:03:22 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 2F 00           (00)

Mon 06/11/2012 06:03:22 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 06:03:22 PM : [iNST-ERX    ] 02 51 14 8E 08 19 6F 2B 11 2F 00 00 01 0F FF 01 E2 01 19 6F 2B FF 1F 01 C2 

Mon 06/11/2012 06:03:22 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 06/11/2012 06:03:22 PM : [   14 8E 8 1] Adding device to ISY t=10.02.0000

Mon 06/11/2012 06:03:22 PM : [14 8E 8 1   ] Start : Adding device to ISY

Mon 06/11/2012 06:03:22 PM : [14 8E 8 1   ] Finish : Adding device to ISY was Successful

Mon 06/11/2012 06:03:22 PM : [14 8E 8 1   ] Link    0 : 0FF8 [E201196F2BFF1F01] Saving  [E201196F2BFF1F01]

Mon 06/11/2012 06:03:22 PM : [14 8E 8 2   ] Start : Adding device to ISY

Mon 06/11/2012 06:03:22 PM : [14 8E 8 2   ] Finish : Adding device to ISY was Successful

Mon 06/11/2012 06:03:22 PM : [14 8E 8 2   ] Link    1 : 0FF0 [E202196F2BFF1F02] Saving  [E202196F2BFF1F02]

Mon 06/11/2012 06:03:22 PM : [14 8E 8 1   ] Device added to ISY

Mon 06/11/2012 06:03:23 PM : ---- All Remaining Device Added ----

Mon 06/11/2012 06:03:23 PM : [All         ] Writing 16 bytes to devices

Mon 06/11/2012 06:03:23 PM : [14 8E 8 1   ] Link    0 : 0FF8 [E201196F2BFF1F01] Writing [E201196F2BFF1F01]

Mon 06/11/2012 06:03:23 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 02 0F FF 08 E2 01 19 6F 2B FF 1F 01 04

Mon 06/11/2012 06:03:23 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 02 0F FF 08 E2 01 19 6F 2B FF 1F 01 04 06        (00)

Mon 06/11/2012 06:03:24 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 2F 00           (00)

Mon 06/11/2012 06:03:24 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 06:03:24 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 14 8E 08 10 02 00 06 

Mon 06/11/2012 06:03:24 PM : [PLM         ] Group   1 : Writing Responder Link matching [14 8E 8 1   ] Link    0 : 0FF8 [E201196F2BFF1F01]

Mon 06/11/2012 06:03:24 PM : [14 8E 8 1   ] Link    1 : 0FF0 [E202196F2BFF1F02] Writing [E202196F2BFF1F02]

Mon 06/11/2012 06:03:24 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 02 0F F7 08 E2 02 19 6F 2B FF 1F 02 0A

Mon 06/11/2012 06:03:24 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 02 0F F7 08 E2 02 19 6F 2B FF 1F 02 0A 06        (00)

Mon 06/11/2012 06:03:25 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 2F 00           (00)

Mon 06/11/2012 06:03:25 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 06:03:25 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 14 8E 08 10 02 00 06 

Mon 06/11/2012 06:03:25 PM : [PLM         ] Group   2 : Writing Responder Link matching [14 8E 8 1   ] Link    1 : 0FF0 [E202196F2BFF1F02]

Mon 06/11/2012 06:03:25 PM : [14 8E 8 1   ] Link    2 : 0FE8 [0000000000000000] Writing [00..............]

Mon 06/11/2012 06:03:25 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9

Mon 06/11/2012 06:03:25 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06        (00)

Mon 06/11/2012 06:03:26 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 2F 00           (00)

Mon 06/11/2012 06:03:26 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 06:03:26 PM : [14 8E 8 1   ] Link    3 : 0FE0 : Writing High Water Byte

Mon 06/11/2012 06:03:26 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA

Mon 06/11/2012 06:03:26 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06        (00)

Mon 06/11/2012 06:03:26 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 23 2F 00           (00)

Mon 06/11/2012 06:03:26 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

Mon 06/11/2012 06:03:27 PM : [iNST-ERX    ] 02 51 14 8E 08 19 6F 2B 11 2F 00 00 01 0F E7 01 00 02 19 3E C9 FF 1F 02 DA 

Mon 06/11/2012 06:03:27 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 06/11/2012 06:03:27 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA

Mon 06/11/2012 06:03:27 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06        (00)

Mon 06/11/2012 06:03:27 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 2F 00           (00)

Mon 06/11/2012 06:03:27 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 06:03:28 PM : [iNST-ERX    ] 02 51 14 8E 08 19 6F 2B 12 2F 00 00 01 0F E7 01 00 02 19 3E C9 FF 1F 02 DA 

Mon 06/11/2012 06:03:28 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=2, Hops Left=0

Mon 06/11/2012 06:03:28 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 02 0F E7 08 00 02 19 3E C9 FF 1F 02 8F

Mon 06/11/2012 06:03:28 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 02 0F E7 08 00 02 19 3E C9 FF 1F 02 8F 06        (00)

Mon 06/11/2012 06:03:29 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 23 2F 00           (00)

Mon 06/11/2012 06:03:29 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

[LeeG]

It is not an I2CS device which makes the Show Device Links Table results very odd. Was the TriggerLinc in linking mode (green LED blinking from Set button press) when the Show Device Links Table was run?

 

Does the Green LED blink as the magnet is moved to and away from the TriggerLinc?

[LeeG]

Looking at the Hop counts communication with the TriggerLinc is poor. For test purposes move the TriggerLinc closer to a Dual Band device to see if state changes are registered

[RussD]

Tried moving TriggerLinc around the house (everyroom has a dual band wall switch). No events recorded.

 

When I was in the same room as the ISY & PLM, whenever I moved the magnet and the green light on the TriggerLinc flashed, the Green status light on the PLM flashed also. I moved to another room where I could still see PLM and the status light on the PLM continues to flash whenever I move the magnet. No events were shown however in the event log.

 

I tried another Diagnostic > Read Devices Links Table. This time it looks similar to yesterday's

<?xml version="1.0"?>
-Device Links Table : DoorSW-Opened / 14 8E 8 1--40882261166685916719617 -40802262166685916719618 -40720000

 

Here is the event viewer for the latest diagnostic read.

Mon 06/11/2012 07:37:25 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2

Mon 06/11/2012 07:37:25 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06        (00)

Mon 06/11/2012 07:37:25 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 27 2F 00           (00)

Mon 06/11/2012 07:37:25 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 06/11/2012 07:37:25 PM : [iNST-ERX    ] 02 51 14 8E 08 19 6F 2B 11 2F 00 00 01 0F FF 01 E2 01 19 6F 2B FF 1F 01 C2 

Mon 06/11/2012 07:37:25 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 06/11/2012 07:37:25 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA

Mon 06/11/2012 07:37:25 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 CA 06        (00)

Mon 06/11/2012 07:37:26 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 23 2F 00           (00)

Mon 06/11/2012 07:37:26 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

Mon 06/11/2012 07:37:26 PM : [iNST-ERX    ] 02 51 14 8E 08 19 6F 2B 11 2F 00 00 01 0F F7 01 E2 02 19 6F 2B FF 1F 02 CA 

Mon 06/11/2012 07:37:26 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 06/11/2012 07:37:26 PM : [iNST-TX-I2  ] 02 62 14 8E 08 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2

Mon 06/11/2012 07:37:26 PM : [iNST-ACK    ] 02 62 14.8E.08 1F 2F 00 00 00 0F EF 01 00 00 00 00 00 00 00 00 D2 06        (00)

Mon 06/11/2012 07:37:27 PM : [iNST-SRX    ] 02 50 14.8E.08 19.6F.2B 23 2F 00           (00)

Mon 06/11/2012 07:37:27 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

Mon 06/11/2012 07:37:27 PM : [iNST-ERX    ] 02 51 14 8E 08 19 6F 2B 11 2F 00 00 01 0F EF 01 00 00 00 00 00 00 00 00 D2 

Mon 06/11/2012 07:37:27 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 06/11/2012 07:37:27 PM : [All         ] Writing 0 bytes to devices

[LeeG]

This Show Device Links Table is correct. Also wherever the TriggerLinc was located when this Show was run shows better communication.

 

DoorSW-Opened / 14 8E 8 1

0FF8 : E2 01 19.6F.2B FF 1F 01

0FF0 : E2 02 19.6F.2B FF 1F 02

0FE8 : 00 00 00.00.00 00 00 00

Device Record Count : 3

 

Unless no devices are showing state changes at present because of an issue with AV or router (Current State column blank for all devices) I have no explanation for why state changes are not being seen.

[LeeG]

The last thing I can think to try is File | Restore Modem (PLM). This will rebuild the PLM link database from scratch.

[RussD]

Good News - A rebuild of the PLM caused the TriggerLinc events to start showing up in the event log.

 

The PLM Link count changed from 509 (before) to 473 (after).

 

I am looking at the event log trying to understand what to look for in the poor communication so I can debug the system. Both event logs were showing Next Hops of 0 on a lot of the packets but you mentioned one was better than the other. Is there a certain type of packet I need to watch for? My plan if I understand what to look for, will be to turn off all circuits at the main panel and slowly add them back watching for the poor communication to appear.

 

Thanks again for all your help.

Russ

[LeeG]

It is Max Hops and Hops Left in combination. The first trace entry below indicates Max Hops=3 with Hops Left=0. That is bad. On the outer edge of success.

 

The second trace entry indicates Max Hops=1 with Hops Left=0. This is as good as it gets.

 

Not in every situation but many messages will start with Max Hops=1 which gives the fastest performance if it works. If it does not work the controller device adds 1 and reissues the same message with Max Hops=2. If that fails the same message is retried again with Max Hops=3. Best chance of working but the slowest performance. Performance has to do with how long a responder has to wait before sending an ACK.

 

Mon 06/11/2012 06:03:29 PM : [standard-Direct Ack][14.8E.08-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Mon 06/11/2012 07:37:27 PM : [Extended-Direct][14.8E.08-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Some messages are always sent with Max Hops=3 so that in itself does not indicate a problem. Best situation is Hops Left is 1 less than Max Hops. When the differential between Max Hops and Hops Left jumps around , 1 left, 0 left when Max Hops is 3, things are pushing the outer edge of reliability.

 

EDIT: the total PLM record count going down is not unusual. As devices are added and deleted link records can be marked deleted (which are available for use later). These deleted records are removed when a Restore Modem (PLM) is issued. There must have been some invalid link record in the PLM not allowing it to find the TriggerLinc records on the end. The PLM holds near 1000 link records so it is not near capacity.

[RussD]

Sorry to post back with the problem again.

 

I tried adding the second TriggerLinc and I am experiencing the same problem. Adding the new Device, No events. Without doing anything else, I restore the PLM then I start getting the events.

 

The first one continued to work without problems.

 

I saved the PLM Link Tables before and after each device was added if this helps.

 

Russ

[LeeG]

I suspect the PLM is developing a problem. What is the PLM firmware level? (Tools | Diagnostics | PLM Info).

[LeeG]

From the earlier trace the PLM is told to add the two responder link records for the TriggerLinc.

 

Mon 06/11/2012 06:03:24 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 14 8E 08 10 02 00 06

Mon 06/11/2012 06:03:25 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 14 8E 08 10 02 00 06

 

The 06 on the end of the message indicates the PLM accepted the request. If they did not become active that is a PLM issue.

[RussD]

Tools > PLM Status shows PLM at v98. The sticker on the PLM shows v1.5.

Are these things upgradeable?

 

The problem is now consistent with other devices. Tried to add a Motion 2420M and a LampLinc. Both do not work until I restore the PLM. Strange how the "MNG-LNK-RSP" updates work for a restore and not when adding to the end of the table.

 

I will work on getting a replacement unit as it is still under warranty.

 

Thanks for your help.

Russ

[LeeG]

The PLM is not upgradable.

 

Might try doing a Factory Reset of the PLM only (not the ISY) and do another Restore PLM. Thanks for the additional information about it not being specific to the TriggerLinc. Did not seem the kind of failure that would be device type specific. I think the latest PLM is v.99 so there is a later version available.

 

There is a difference in the order of the link records between adding a new device and doing a Restore. Adding a device puts the new link records at the end of the link database. I’m pretty sure the Restore puts all the responder links first, then the controller links. The PLM should find the link records either way.

[ELA]

I returned my V98 PLM a while back after reading about known firmware issues in this forum.