Jump to content

TirggerLinc Troubles


Recommended Posts

I recently acquired 2 #2141 Rev 1.2 triggerlics and I can't get ether of them to link to the ISY. The error I get is:

Failed writing the highwater mark

[-200000/-1]

Node not added- failed removing links

(14 40 4A 1)

[-200000/-9]

 

I've tried "removing links", not removing links, selecting Auto Discover, selecting TriggerLinc. I've tried linking with the TL 3 feet from the AP. I moved the AP and plugged it into the PLM. Nothing seems to be working. Any other thoughts?

 

LeeG suggested the following:

 

Yes. I just deleted and added a TriggerLinc under 2.8.16.

 

Be sure Link Management | Advanced Options | Automatic is selected. The Device Type should be specified as [10.02] TriggerLinc. Be sure the TriggerLinc is in linking mode using Set button before using New INSTEON Device.

 

If this does not work invoke Tools | Diagnostics | Event Viewer with Device Communications Events selected and post the trace produced during the add.

Link to comment
Share on other sites

OK.. Followed all of LeeG's recommendations. I still can't link the new devices. So, I removed an original TriggerLinc that had been working for some time now and I can't add that one in either. I tried power cycling the PLM (and hence the ISY). When I press the set button on any of the devices the LED on the AP responds in kind. Here's the Event Viewer with DCE:

 

Wed 03/02/2011 07:39:19 PM : ---- Initializing the linked devices ----

 

Wed 03/02/2011 07:39:19 PM : ---- All Linked Devices are now initialized ----

 

Wed 03/02/2011 07:39:19 PM : ---- Add remaining devices ----

 

Wed 03/02/2011 07:39:19 PM : [ 14 40 4A 1] Removing all links

 

Wed 03/02/2011 07:39:19 PM : [14 40 4A 1 ] Querying engine version

 

Wed 03/02/2011 07:39:19 PM : [iNST-ACK ] 02 62 14.40.4A 0F 0D 00 06 (00)

 

Wed 03/02/2011 07:39:20 PM : [iNST-SRX ] 02 50 14.40.4A 0C.A5.8E 23 0D 01 (01)

 

Wed 03/02/2011 07:39:20 PM : [standard-Direct Ack][14.40.4A-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Wed 03/02/2011 07:39:20 PM : [14 40 4A 1 ] Retrieved engine version is i2

 

Wed 03/02/2011 07:39:20 PM : [14 40 4A 1 ] Calibrating engine version ensuring support for i2

 

Wed 03/02/2011 07:39:20 PM : [iNST-ACK ] 02 62 14.40.4A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 03/02/2011 07:39:22 PM : [iNST-SRX ] 02 50 14.40.4A 0C.A5.8E 27 2F 00 (00)

 

Wed 03/02/2011 07:39:22 PM : [standard-Direct Ack][14.40.4A-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Wed 03/02/2011 07:39:23 PM : [iNST-ERX ] 02 51 14 40 4A 0C A5 8E 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00

 

Wed 03/02/2011 07:39:23 PM : [Extended-Direct][14.40.4A-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Wed 03/02/2011 07:39:23 PM : [14 40 4A 1 ] Using engine version i2

 

Wed 03/02/2011 07:39:23 PM : [iNST-ACK ] 02 62 14.40.4A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 03/02/2011 07:39:23 PM : [iNST-SRX ] 02 50 14.40.4A 0C.A5.8E 27 2F 00 (00)

 

Wed 03/02/2011 07:39:23 PM : [standard-Direct Ack][14.40.4A-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Wed 03/02/2011 07:39:32 PM : [iNST-ACK ] 02 62 14.40.4A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 03/02/2011 07:39:33 PM : [iNST-SRX ] 02 50 14.40.4A 0C.A5.8E 23 2F 00 (00)

 

Wed 03/02/2011 07:39:33 PM : [standard-Direct Ack][14.40.4A-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Wed 03/02/2011 07:39:42 PM : [iNST-ACK ] 02 62 14.40.4A 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00)

 

Wed 03/02/2011 07:39:43 PM : [iNST-SRX ] 02 50 14.40.4A 0C.A5.8E 27 2F 00 (00)

 

Wed 03/02/2011 07:39:43 PM : [standard-Direct Ack][14.40.4A-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Wed 03/02/2011 07:39:47 PM : [ 14 40 4A 1] ** Not added ** Remove Device Links failed

 

Wed 03/02/2011 07:39:47 PM : ---- All Remaining Device Added ----

 

Wed 03/02/2011 07:39:47 PM : [All ] Writing 0 bytes to devices

Link to comment
Share on other sites

Sorry for any delay. I was not hooked to this particular topic.

 

The Standard length message is coming back so there is basic RF communication to/from the TriggerLinc but for some reason the Extended length messages are not being received by the PLM. In the trace, after receiving an 0250 (SD message), there is a 9 second delay before the ISY issues another command. This is the ISY waiting for the expected Extended length message which is not received.

 

With this occurring on multiple TriggerLincs and the ISY and PLM having been power cycled, I would unplug the Access Points (or whatever Dual Band devices are being used) for a full minute.

 

Do you have Venstar tstat adaptors? If so unplug the tstat adaptor from the tstat.

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

Did anyone find a resolution to this issue? I am having similar problems with both TriggerLinc and Motion Sensors. Need to get this resolved quickly as I'm going on vacation in 2 weeks.

 

I reset my PLM and ISY99. I unplugged all my Access Points (4). I removed a TriggerLinc and was able to relink it to ISY but I get no status on the Door-Opened device. TriggerLink has new battery and green light is working fine. I have 12 motion sensors and 4 triggerlinks and none of them are working. They have been working well for over a year but just stopped working about a week ago. I haven't changed anything on my ISY which would have caused this to stop working.

 

I'm running 2.8.16 with an ISY99i/IR.

 

Any help GREATLY appreciated.

Link to comment
Share on other sites

Do you have any tstat adaptors? If so unplug the dongle(s).

 

With 16 devices not working there is an RF issue somewhere. It is odd that the TriggerLinc added okay since that requires RF communication. Would have thought there would have been problems adding the TriggerLinc when no other Motion Sensor or Triggerlinc is working.

 

Was the location of the TriggerLinc changed between adding it back to the ISY and when it will not signal a state change?

 

Are the wired devices indicating state changes?

Link to comment
Share on other sites

Not using Tstat adapters. Using Z-Wave thermostats.

All of my wired sensors are working.

 

So I ran some more tests and discovered something very strange. I tried deleting a current motion sensor and re-adding it. This time ISY wouldn’t even let me re-add it. So then I added a NEW motion sensor that had never been added to ISY. To my surprise it added the motion sensor correctly and was accurately reflecting device states. To make matters even stranger, now ALL my triggerlincs and motion sensors reflect the correct state when they are activated. I cannot explain this but am guessing it has something to do with my link tables.

Link to comment
Share on other sites

  • 2 months later...

Similar issues here! So frustrating...overnight 3 motion sensors went down. Called Smarthome, they said that the Rev1 MS had issues and they would recommend switching to TriggerLincs...done it and NOW I cannot even pick it up on the ISY.

 

Any suggestions?

Link to comment
Share on other sites

Hello lapolonyc,

 

Are you having issues linking your TriggerLinc to ISY?

 

Please note that TriggerLincs use very low power and thus you have to make sure you have a good battery and that you are near an Access Point.

 

Also, there has been many reports of older thermostat dongles causing network jam.

 

If all else fails, please do not hesitate to contact our tech support and schedule a remote session assistance.

 

With kind regards,

Michel

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...