TriggerLinc Rev 1.1

[rcolemanca]

Has any one had success adding a TriggerLinc Rev 1.1 to their ISY-99i?

 

I am running version 2.7.15.

 

I get: "failed getting engine version. Reverting to i1" and then "[-200000] Node not added -- failed reading links" when I try to use New Insteon Device and choose a TriggerLinc (2421) as my device type and specify the nn.mm.jj address and a name such as "door".

 

I do not have any older revision TriggerLinc's so I don't know if I am doing something wrong.

 

I do know that they work (i.e. I can manually set them up to turn an Insteon controlled lamp on and off). I have tried wih the TriggerLinc manually linked as well as with it not linked to anything else.

 

Any and all help would be appreciated.

[Brian H]

When you tried to add the TriggerLinc to your ISY99i setup.

Did you hold the linking button for three seconds so it was in the Linking Mode?

As an RF device it is in a low power saving mode and will not respond to the ISY99i if it is in power saving mode.

 

Try it in the Linking Mode if you have not tried it yet.

[LeeG]

I have added a TriggerLinc 1.1 successfully. I specified the TriggerLinc Device Type rather than Auto Discovery. As was mentioned before the TriggerLinc must be in linking mode by pressing Set button before clicking OK on device add.

[rcolemanca]

Brian and Lee;

 

Thank you for responses.

 

I have therefore kept trying. One difference this time is that I have the magnets close to the sensors (i.e. the triggerlinc would be in a closed state) and now i can discover the devices but they show up as V 00 and their status is not getting updated (I am also still getting the "failed getting engine version. Reverting to i1" error messages as the isy is querying everything I own for a couple of minutes).

 

Not surprisingly, I can now use the triggerlincs as conditions in my programs but since they are not being queried the programs don't actually do what they are supposed to.

 

The Triggerlincs still do trigger what I have manually set them to trigger -- so I know they are working.

 

Any more hints?

 

Thank you in advance.

[LeeG]

I don't think it makes any difference but my TriggerLinc was Open when I defined it. Do not use Auto Discovery. That did not work for me. Select the specific TriggerLinc Device Type. When you click on OK a popup should come up with instructions to put the TriggerLinc into linking mode before proceeding. The TriggerLinc does not have the command set to support the I1 engine. The ISY has to use the I2 engine which it did do when I specifically selected the TriggerLinc Device Type and went into linking mode before proceeding. The ISY will not be able to "see" the TriggerLinc state changes because the I1 engine was not able to establish the necessary links. Remove the TriggerLinc device definition and try again with the specific TriggerLinc device type and entering linking mode before. The other possibility is the TriggerLinc is outside the range of one of the Access Points so RF communication is not possible. An Event Log trace level 3 should show successful I2 engine activity. If the ISY switches to I1 when the TriggerLinc device type was selected likely there is an RF communication problem. Try moving the TriggerLinc closer to an Access Point.

[rcolemanca]

Lee;

 

Thank you for the pointers.

 

I have kept at it and I now have two of my four TriggerLinc's working. I still need to unbox the other two.

 

They work in that I can discover them while in the closed state and they report status when in the open state (not the other way around ). And I am now using them in programs.

 

But I still get those errors when I add something new to my system (which I do not get if I remove the triggerlinc's). And while it adds 'controls' in for the closed state -- they do not work.

 

So, that all said, I have things working.

 

Thank you for your encouragement.

[ctwilliams]

I am having trouble with this as well. I just received a triggerlinc (also version 1.1) and this is the first one I have have used.

 

The error I am getting is the same as noted above. When it is attempting to program the triggerlinc and remove the links it says in the progress box something to the effect of the I2 commands and not working and switching ti I1. However, it does not give this message every time. It always ends with the device not added failure to remove links message.

 

I have tried with it open and closed.

 

I am picking the triggerlinc as the device and putting it in the linking mode as described (light flashing).

 

If I link it manually without use of the ISY to a light it works fine.

 

Any ideas? THANKS GUYS

 

(In the code below it seems to be working on device 0A.11.F4. No idea what that is, it is not the address of any of my devices. Is that the plm or something?)

 

Sun 07/11/2010 12:16:41 PM : ---- Initializing the linked devices ----

Sun 07/11/2010 12:16:41 PM : ---- All Linked Devices are now initialized ----

Sun 07/11/2010 12:16:41 PM : ---- Add remaining devices ----

Sun 07/11/2010 12:16:41 PM : [  13 E6 47 1] Removing all links

Sun 07/11/2010 12:16:41 PM : [13 E6 47 1  ] Querying engine version

Sun 07/11/2010 12:16:41 PM : [iNST-ACK    ] 02 62 13.E6.47 0F 0D 00 06                 (00)

Sun 07/11/2010 12:16:42 PM : [iNST-SRX    ] 02 50 13.E6.47 12.9D.97 27 0D 01           (01)

Sun 07/11/2010 12:16:42 PM : [standard-Direct Ack][13.E6.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Sun 07/11/2010 12:16:42 PM : [13 E6 47 1  ] Retrieved engine version is i2

Sun 07/11/2010 12:16:42 PM : [13 E6 47 1  ] Calibrating engine version ensuring support for i2

Sun 07/11/2010 12:16:42 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)

Sun 07/11/2010 12:16:51 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)

Sun 07/11/2010 12:17:00 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)

Sun 07/11/2010 12:17:04 PM : [13 E6 47 1  ] i2 data transfer commands do not work. Reverting to i1

Sun 07/11/2010 12:17:04 PM : [13 E6 47 1  ] Using engine version i2

Sun 07/11/2010 12:17:04 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)

Sun 07/11/2010 12:17:13 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)

Sun 07/11/2010 12:17:22 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)

Sun 07/11/2010 12:17:26 PM : [  13 E6 47 1] ** Not added ** Remove Device Links failed

Sun 07/11/2010 12:17:26 PM : ---- All Remaining Device Added ----

Sun 07/11/2010 12:17:26 PM : [A 11 F4 1   ] Using engine version i1 for '0A.11.F4.1'

Sun 07/11/2010 12:17:26 PM : [A 11 F4 1   ] Link    0 : 0FF8 [E201000000000001] Writing [E201000000000001]

Sun 07/11/2010 12:17:26 PM : [iNST-ACK    ] 02 62 0A.11.F4 0F 28 0F 06          SET-MSB(0F)

Sun 07/11/2010 12:17:35 PM : [iNST-ACK    ] 02 62 0A.11.F4 0F 28 0F 06          SET-MSB(0F)

Sun 07/11/2010 12:17:44 PM : [iNST-ACK    ] 02 62 0A.11.F4 0F 28 0F 06          SET-MSB(0F)

Sun 07/11/2010 12:17:48 PM : [A 11 F4 1   ] Link    0 : 0FF8 [E201000000000001] *Failed Writing [E201000000000001]

Sun 07/11/2010 12:17:48 PM : [12 BB A4 1  ] Memory : Write dbAddr=0x0264 [00]

Sun 07/11/2010 12:17:48 PM : [iNST-ACK    ] 02 62 12.BB.A4 1F 2E 00 01 07 00 00 00 00 00 00 00 00 00 00 00 00 06        (00)

Sun 07/11/2010 12:17:57 PM : [iNST-ACK    ] 02 62 12.BB.A4 1F 2E 00 01 07 00 00 00 00 00 00 00 00 00 00 00 00 06        (00)

Sun 07/11/2010 12:18:06 PM : [iNST-ACK    ] 02 62 12.BB.A4 1F 2E 00 01 07 00 00 00 00 00 00 00 00 00 00 00 00 06        (00)

Sun 07/11/2010 12:18:10 PM : [12 BB A4 1  ] Memory : Write dbAddr=0x0264 [00] - Failed

[LeeG]

The following Event Log messages are the ISY attempt to communicate with the TriggerLinc using I2. Three attempts are made; each fails to get a response from the TriggerLinc. Since ISY was able to successfully query the device for the I2 engine support it looks like the RF communication with the TriggerLinc is spotty. Try moving the TriggerLinc closer to an Access Point or temporarily move an Access Point to the ISY if working with the TriggerLinc on the desk. The other possibility is the TriggerLinc timed out of its linking mode but that is approx 4 minutes long and you would see the green LED on the TriggerLinc stop flashing if that happened.

 

If the Event Log indicates ISY reverting to I1 it is all over. The TriggerLinc does not have the command set to support I1. The ISY only reverts to I1 when the attempts to communicate using I2 fail. I2 communication can be more of a problem than I1 as not all of the Insteon devices in the field repeat I2 messages. That could be why the SD I1 message to query the type of engine in the TriggerLinc works but the I2 commands do not. I keep an Access Point plugged into the PLM location so that I2 commands immediately go out on RF without the need for any Insteon device to repeat the I2 messages to get to an Access Point. I have mainly older Insteon devices installed and adding an Access Point to the circuit where my controllers are located that use I2 greatly improved my I2 message reliability.

 

Sun 07/11/2010 12:16:42 PM : [13 E6 47 1 ] Calibrating engine version ensuring support for i2

Sun 07/11/2010 12:16:42 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Sun 07/11/2010 12:16:51 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Sun 07/11/2010 12:17:00 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

Sun 07/11/2010 12:17:04 PM : [13 E6 47 1 ] i2 data transfer commands do not work. Reverting to i1

[Michel Kohanim]

Hello ctwilliams,

 

Please try using Add New INSTEON Device instead of Start Linking.

 

With kind regards,

Michel

[ctwilliams]

The following Event Log messages are the ISY attempt to communicate with the TriggerLinc using I2. Three attempts are made; each fails to get a response from the TriggerLinc. Since ISY was able to successfully query the device for the I2 engine support it looks like the RF communication with the TriggerLinc is spotty. Try moving the TriggerLinc closer to an Access Point or temporarily move an Access Point to the ISY if working with the TriggerLinc on the desk. The other possibility is the TriggerLinc timed out of its linking mode but that is approx 4 minutes long and you would see the green LED on the TriggerLinc stop flashing if that happened.

 

 

That makes sense. The triggerlinc is about 15 feet away from the access point and when linked to a switch without going through the ISY is working flawlessly.

 

I will keep working on it....

 

Thanks for the info...

[ctwilliams]

Hello ctwilliams,

 

Please try using Add New INSTEON Device instead of Start Linking.

 

With kind regards,

Michel

 

Hey Michel....

 

I am using the Add New Insteon Device and selecting the Triggerlinc (last choice in my drop down box)... The log I posted above is the result of using the add new insteon device...

 

CT

[LeeG]

15' should be fine. The problem is likely unreliable I2 Extended message communication. Temporarily move an Access Point to where the ISY PLM is located so that the TriggerLinc will have direct RF Access Point communication with the PLM. Once the TriggerLinc is successfully added and the links established, SD message communication is used to signal the TriggerLinc state change which is likely more reliable than the I2 ED message in your installation as all the Insteon devices repeat SD messages. Extended message reliability is becoming less a problem as more and more newer Insteon devices are installed which do repeat I2 ED messages. Sometimes moving one of the Access Points closer to the ISY PLM will help but you have to be careful not to lose the 120v leg coupling. As I mentioned before I like to keep an Access Point (beyond the ones used to couple) at the PLM site just to insure better ED message reliability. The other approach is to use a Dual Band PLM on the ISY so that RF communication is immediately available at the ISY PLM. This requires the use of an external power supply as the Dual Band PLM (2413S) does not provide the power to the ISY as the standard PLM (2412S) does.

 

When I2 ED messages are working you will see a response from the TriggerLinc to the ED command rather than the message being retried 3 times at approx 9 second intervals. Once an ED response is received the ISY will use ED commands to complete the TriggerLinc device add process.

[ctwilliams]

I have an access point plugged into the PLM itself and that is about 15 feet and one floor away from the triggerlinc. The other access point is right outside the room about 15 feet away from the triggerlinc....

 

You gotta love insteon...

[IndyMike]

Hello ctwilliams,

 

Let me start by saying that this should not happen (but), you may be getting partial cancellation of the signals from your two accesspoints. Please try removing the accesspoint that is not on the PLM.

 

If this does not work, try moving your triggerlinc to the PLM/accesspoint combo. After the initial programing is completed, the triggerlinc should revert to I1 protocol and you will hopefully be OK.

 

IM

[ctwilliams]

I tried the single access point from 15' away and then tried the single access point 1' away and neither worked.

 

I will call smarthome tomorrow and see what they think. Maybe I received a bad unit?

 

Thanks for all of the troubleshooting help!

 

CT

[Michel Kohanim]

Hi CT,

 

First of all, I think LeeG is 100% right on the money.

 

Please do ensure that you have an Access Point and not SignaLincs. SignaLincs do let let i2 messages to go through.

 

Since your system keeps saying "reverting to i1", therefore it means that ISY cannot communicate with your TriggerLinc. So, Access Points are the first possible cause.

 

Secondly, I have experienced the same issue with low battery. What I suggest is getting a new battery, and make sure that the LED blinks when you press and hold the set button.

 

Only after these fail do I think you should get a replacement TL.

 

With kind regards,

Michel

[ctwilliams]

Just to catchup...I do have accesspoints for sure and the battery is good and I tried another just in case....

 

I called smarthome today and they said they have had issues from some customers with the ISY not being able to discover wireless devices. They believe it is a bug in the ISY. I have no idea so I am staying out of that portion of it.

 

They have found that for most people if you add the device (they specifically mentioned motion detectors, thermostats, and the triggerlincs) as a REMOTELINC that it will add to the ISY. They then have you right click on it and remove it. Finally you add it as normal (in my case as a triggerlinc) and it often will add at that point. I have no idea why.

 

So I tried it. I watched the event viewer as it did so and it started the same with the no acknowledgement from the device of the I2 commands. It then gives the switching to I1 statement and from there it seems to work fine (the triggerlinc sends the acknowledgement of the command) and adds it in to the ISY (as a remotelinc so it does not work).

 

I then removed it from the ISY and tried to add it the normal way, but in my case it did not work.

 

They believe that because the triggerlinc is able to link manually to a switch and that is fine that there is nothing wrong with the unit. However, they were more than happy to switch it out and try a new one.

 

Any thoughts on the adding it as a remotelinc idea?

[LeeG]

I have no idea why someone would think that sequence would work. Once the I2 2F ALDB commands fail to get a response three times and ISY switches back to using the old I1 technique for accessing a link database it is all over. The TriggerLinc (and Motion Sensor) did not implement the Set MSB/Peek/Poke commands that are used by the ISY I1 engine. Those commands have been depreciated so it was legal for those commands not to be implemented and I suspect they were trying to keep the firmware size as small as possible to keep the memory size as small as possible because it is battery powered. That is only a guess on my part. The TriggerLinc cannot send the Group message when motion is sensed because the necessary link records could not be written.

 

The fact that the TriggerLinc can link to a switch using the Set button method does indicate the TriggerLinc is working. I never thought the TriggerLinc was failing. However, the TriggerLinc communicating with a different device does not mean that the I2 2F ALDB command from the ISY/PLM is reaching the TriggerLinc or that any response from the TriggerLinc is making it back to the ISY/PLM as the devices are on different locations on the powerline.

 

What revision is the PLM? About how old is it? Do you have any other RF only devices, like a Motion Sensor.

 

I hate to ask this but can you Remove the TriggerLinc and add it back using New Insteon Device run with the Event Log level 3 trace active. I would like to look at the exact structure of the I2 2F ALDB command being issued. I’ll Remove and readd the TriggerLinc here and compare the Event Log entries generated here against what you are seeing. Rather than post an Event Log file you can send the saved Event Log file to lwgwork@embarqmail.com.

 

EDIT: this is the operative part of my Event Log showing how the TriggerLinc should respond....

 

Mon 07/12/2010 08:43:21 PM : [11 B8 2D 1 ] Querying engine version

 

Mon 07/12/2010 08:43:21 PM : [iNST-ACK ] 02 62 11.B8.2D 0F 0D 00 06 (00)

 

Mon 07/12/2010 08:43:21 PM : [iNST-SRX ] 02 50 11.B8.2D 12.9F.E4 27 0D 01 (01)

 

Mon 07/12/2010 08:43:21 PM : [standard-Direct Ack][11.B8.2D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Mon 07/12/2010 08:43:21 PM : [11 B8 2D 1 ] Retrieved engine version is i2

 

Mon 07/12/2010 08:43:21 PM : [11 B8 2D 1 ] Calibrating engine version ensuring support for i2

 

Mon 07/12/2010 08:43:22 PM : [iNST-ACK ] 02 62 11.B8.2D 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Mon 07/12/2010 08:43:22 PM : [iNST-SRX ] 02 50 11.B8.2D 12.9F.E4 27 2F 00 (00)

 

Mon 07/12/2010 08:43:22 PM : [standard-Direct Ack][11.B8.2D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Mon 07/12/2010 08:43:22 PM : [iNST-ERX ] 02 51 11 B8 2D 12 9F E4 11 2F 00 00 01 0F FF 01 62 01 12 9F E4 FF 1F 01 00

 

Mon 07/12/2010 08:43:22 PM : [Extended-Direct][11.B8.2D-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Mon 07/12/2010 08:43:22 PM : [11 B8 2D 1 ] Using engine version i2

[Michel Kohanim]

LeeG,

 

Thank YOU! Couldn't have said it any better myself !

 

With kind regards,

Michel

[ctwilliams]

LeeG...thanks for all of the troubleshooting help. This is what I get from the event viewer.....

 

 

Wed 07/14/2010 10:31:23 PM : [iNST-SRX    ] 02 50 13.E6.47 00.00.01 C3 13 01    LTOFFRR(01)

Wed 07/14/2010 10:31:23 PM : [standard-Group][13.E6.47-->Group=1] Max Hops=3, Hops Left=0

Wed 07/14/2010 10:31:23 PM : [iNST-SRX    ] 02 50 13.E6.47 00.00.01 C3 13 01    LTOFFRR(01):  Process Message: failed

Wed 07/14/2010 10:31:23 PM : [standard-Group][13.E6.47-->Group=1] Max Hops=3, Hops Left=0

Wed 07/14/2010 10:31:23 PM : [iNST-SRX    ] 02 50 13.E6.47 00.00.01 C3 13 01    LTOFFRR(01)

Wed 07/14/2010 10:31:23 PM : [standard-Group][13.E6.47-->Group=1] Max Hops=3, Hops Left=0

Wed 07/14/2010 10:31:23 PM : [iNST-SRX    ] 02 50 13.E6.47 00.00.01 C3 13 01    LTOFFRR(01):  Process Message: failed

Wed 07/14/2010 10:31:23 PM : [standard-Group][13.E6.47-->Group=1] Max Hops=3, Hops Left=0

Wed 07/14/2010 10:31:35 PM : ---- Initializing the linked devices ----

Wed 07/14/2010 10:31:35 PM : ---- All Linked Devices are now initialized ----

Wed 07/14/2010 10:31:35 PM : ---- Add remaining devices ----

Wed 07/14/2010 10:31:35 PM : [  13 E6 47 1] Removing all links

Wed 07/14/2010 10:31:35 PM : [13 E6 47 1  ] Querying engine version

Wed 07/14/2010 10:31:35 PM : [iNST-ACK    ] 02 62 13.E6.47 0F 0D 00 06                 (00)

Wed 07/14/2010 10:31:44 PM : [iNST-ACK    ] 02 62 13.E6.47 0F 0D 00 06                 (00)

Wed 07/14/2010 10:31:53 PM : [iNST-ACK    ] 02 62 13.E6.47 0F 0D 00 06                 (00)

Wed 07/14/2010 10:31:53 PM : [iNST-SRX    ] 02 50 13.E6.47 12.9D.97 23 0D 01           (01)

Wed 07/14/2010 10:31:53 PM : [standard-Direct Ack][13.E6.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

Wed 07/14/2010 10:31:53 PM : [13 E6 47 1  ] Retrieved engine version is i2

Wed 07/14/2010 10:31:53 PM : [13 E6 47 1  ] Calibrating engine version ensuring support for i2

Wed 07/14/2010 10:31:53 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)

Wed 07/14/2010 10:32:02 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)

Wed 07/14/2010 10:32:11 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (00)

Wed 07/14/2010 10:32:15 PM : [13 E6 47 1  ] i2 data transfer commands do not work. Reverting to i1

Wed 07/14/2010 10:32:15 PM : [13 E6 47 1  ] Using engine version i2

Wed 07/14/2010 10:32:15 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)

Wed 07/14/2010 10:32:24 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)

Wed 07/14/2010 10:32:33 PM : [iNST-ACK    ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)

Wed 07/14/2010 10:32:37 PM : [  13 E6 47 1] ** Not added ** Remove Device Links failed

[LeeG]

If you were in linking mode before starting communication to the TriggerLinc even SD messages is spotty as the SD message to determine if the device indicated I2 support did not respond the first two times attempted.

 

After that the I2 2F ALDB commands did not get a response.

 

What is the PLM revision and how long have you had it.

 

 

Wed 07/14/2010 10:31:35 PM : [13 E6 47 1 ] Querying engine version

 

Wed 07/14/2010 10:31:35 PM : [iNST-ACK ] 02 62 13.E6.47 0F 0D 00 06 (00)

 

Wed 07/14/2010 10:31:44 PM : [iNST-ACK ] 02 62 13.E6.47 0F 0D 00 06 (00)

Wed 07/14/2010 10:31:53 PM : [iNST-ACK ] 02 62 13.E6.47 0F 0D 00 06 (00)

 

Wed 07/14/2010 10:31:53 PM : [iNST-SRX ] 02 50 13.E6.47 12.9D.97 23 0D 01 (01)

 

Wed 07/14/2010 10:31:53 PM : [standard-Direct Ack][13.E6.47-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Wed 07/14/2010 10:31:53 PM : [13 E6 47 1 ] Retrieved engine version is i2

 

Wed 07/14/2010 10:31:53 PM : [13 E6 47 1 ] Calibrating engine version ensuring support for i2

 

Wed 07/14/2010 10:31:53 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 07/14/2010 10:32:02 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 07/14/2010 10:32:11 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 07/14/2010 10:32:15 PM : [13 E6 47 1 ] i2 data transfer commands do not work. Reverting to i1

Wed 07/14/2010 10:32:15 PM : [13 E6 47 1 ] Using engine version i2

 

Wed 07/14/2010 10:32:15 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

 

Wed 07/14/2010 10:32:24 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

 

Wed 07/14/2010 10:32:33 PM : [iNST-ACK ] 02 62 13.E6.47 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (02)

 

Wed 07/14/2010 10:32:37 PM : [ 13 E6 47 1] ** Not added ** Remove Device Links failed

[ctwilliams]

I see what you mean after looking at what you highlighted.

 

The PLM is from 11/09 and reports as v85.

 

Smarthome is sending out another triggerlinc for me to try and I should have it next week.

 

Thanks...CT

[LeeG]

That PLM revision should be fine. I have lost track of all the things you have already tried. If not done up to now try piggy backing an Access Point on the PLM so there is no question about the I2 commands getting to/from RF. If that has already been tried the only thing that seems left is the TriggerLinc itself. There are different commands used between hardware establishing a link with the Set button and what a software/firmware product issues to create links. It seems like a very low possibility but i guess the TriggerLinc could be failing only with the specific 2F ALDB command. This command is not used by the Set button process. Post back when you have tried the new TriggerLinc. Thanks.

[ctwilliams]

Hi again...

 

I received the new triggerlinc today from smarthome and it failed in exactly the same way. The logs look identical from the first one to the second.

 

It must be something in my setup I am assuming but I have no idea what else to try.

 

Ack.

 

CT

[LeeG]

ctwilliams I am afraid I have lost track of all the thing that have been tried. Did you piggy back an Access Point on the PLM and try adding the TriggerLinc while physically near that Access Point.