I have several TriggerLinc's in my home which for the most part work very well. However, once in a while they will not trigger correctly. This doesn't just happen with 1 particular TriggerLinc but all of them. Most of them are paired to Insteon dimmer switches, like in closet doors, pantry, etc. Sometimes the light will trigger when I open the door and not trigger when I close it and visa versa. The contacts are in the correct position and the batteries are new. Has anyone else noticed this? Is it a bug or a hardware defect?

 

Thanks!

Chuck

Hi Chuck,

 

TriggerLincs are battery operated/RF devices so I am sure you already know that you must have a good access point very near to them.

 

With kind regards,

Michel

Thanks for the reply Michel,

 

Yes, I have an access point in every room of my house. Again, for the most part my TriggerLinc's work very well with the exception of approximately 1 out of 50 times not triggering correctly. Perhaps this is just an instance of a wireless command sent from the TriggerLinc that never made it back to the Insteon switch?

 

Chuck

Hi Chuck,

 

Yes, it could be. Another question: when the devices are NOT triggered, does ISY still see the status change for the TriggerLincs or is it that neither ISY sees the status change nor are the devices triggered?

 

With kind regards,

Michel

That's a great question Michel. The next time it happens, I'll go into my ISY and check the status for that particular TriggerLinc.

Hi Chuck,

 

Yes, it could be. Another question: when the devices are NOT triggered, does ISY still see the status change for the TriggerLincs or is it that neither ISY sees the status change nor are the devices triggered?

 

With kind regards,

Michel

 

This happened again today where I opened a door with a TriggerLinc linked to an Insteon Dimmer, and the light never triggered. I immediately checked my ISY and sure enough the TriggerLinc showed as open which tells me that the signal never made it to the Insteon dimmer or the dimmer never responded. Fortunately this doesn't happen often, however it would still be nice to understand why this is happening in the first place...

Hi Chuck,

 

So, the path to the switch is broken while the path to ISY is not.

 

Do you have any Thermostats or SWL v35?

 

With kind regards,

Michel

Yes, I have an Insteon All-In-One thermostat (2491T).

Hi Chuck,

 

Can you tell me the firmware version for your thermostat?

 

With kind regards,

Michel

Does the firmware proceed the model of the thermostat in the ISY devices? If so, it appears to be 14.94.56.

 

Chuck

The device firmware level is on the second line of the device detail in the right pane. v.xx

Thank you. V.95.

Hi Chuck,

 

I think the problem is the TriggerLinc itself.

 

With kind regards,

Michel

I would agree with that assumption if it weren't happening to just one of my TriggerLinc's. I've seen this happen with all of my TriggerLinc's. Again it's rare (maybe 1 out of 100) times or so...

Hi Chuck,

 

Then, we will have to look at all your RF devices. What type of Access Points do you have? Are they old or new?

 

With kind regards,

Michel

All of my access points were purchased approximately six months ago (v.40).

Hi Chuck,

 

If you look at your logs (for which there should be an entry for the event generated by TriggerLinc) for when this happens, do you see a lot of activity - especially activation of scenes - at around the same time?

 

With kind regards,

Michel

I've checked my log files and it's very difficult to nail down the exact instance of when the TriggerLinc didn't trip the Insteon light. That said, I did check other instances and didn't notice a lot of activity at that time. The next time this happens I'm going to note the exact time so I can check it in the log file.

Thanks Chuck.

 

The reason is that if there's a lot of traffic, then it's possible that a signal can be missed.

 

With kind regards,

Michel

I see. Well, I guess I'll just wait until the issue occurs again, then make a note of the time and check the log files.

 

I appreciate all of your help!

Chuck