Jump to content

Insteon I/OLinc activated by itself


pyrorobert

Recommended Posts

Hello All,

     So this early morning, my I/OLinc that controls the garage door activated by itself and opened the door. Once that happened, my security system activated and sent us into Protection mode! I swept the home to verify that no one was trying to break in, then locked everything back up and rearmed the security system. I looked at my log and it showed that the I/OLinc turned on, but it doesn't show by whom. Does anyone have any ideas or any reason that this would have happened. I have had my system up and running for about 2 years now and this has never happened before. It really put my wife in a panic mode, good thing I was home when it happened. 

Please share your ideas or insight:

 

Here is my log from this morning:

2 Door Garage Door Open                 On                  100               Tue 2014/10/28 02:09:18 AM            Web       Log

2 Door Garage Door Open               Status               100%            Tue 2014/10/28 02:09:19 AM          System    Log

2 Door Garage Status                      Status               100%            Tue 2014/10/28 02:09:20 AM         System     Log

Backyard Light / Garage Door - C    Status               100%            Tue 2014/10/28 02:09:20 AM         System     Log

Garage Front Lights                           On                                       Tue 2014/10/28 02:10:00 AM         Program   Log

Living Room Lamp                             On                                       Tue 2014/10/28 02:10:00 AM         Program   Log

Dining Room                                      On                                       Tue 2014/10/28 02:10:00 AM         Program   Log

Garage Front Lights                         Status               100%           Tue 2014/10/28 02:10:00 AM          System     Log

Living Room Lamp                           Status               100%           Tue 2014/10/28 02:10:01 AM          System     Log

Dining Room                                    Status                100%          Tue 2014/10/28 02:10:01 AM          System     Log

2 Door Garage Status                      Status               Query          Tue 2014/10/28 02:11:39 AM            Web       Log

 

 

 

Thanks,

 

Robert

Link to comment

I don't think the garage door moved as a result of the I/O Linc Relay.   There should have been a Log entry that reflected a Relay command.

 

Scene:SceneIOLincRelay On Tue 2014/10/28 02:39:19 PM Web Log
IOLinc I2CS-Relay Status 100% Tue 2014/10/28 02:39:19 PM System Log

Scene:SceneIOLincRelay On Tue 2014/10/28 02:43:05 PM Web Log

 

oberkc view that it was triggered by RF unrelated to the I/O Linc is supported by the Log which shows the Sensor changing state when the door moved but no Relay activity. 

Link to comment

I offered the RF theory as one plausible explanation (I have no actual evidence to support the theory)...mainly to consider the possibility that, sometimes, things happen for reasons beyond the control of insteon or the ISY. My experience is that if something happens because of the presence of the ISY, there is evidence in the log. If no log evidence exists, most likely the problem is elsewhere.

Link to comment

Check your wiring, especially where you may have disturbed connections wiring your IOLinc. It is very doubtful that stray RF emissions could activate a garage door opener with the rolling security code features used these days. I have owned garage door openers for over 28 years and never experienced one open by itself. We have left them open by mistake a few times though. Early electronics failure maybe? Time will demonstrate that one.

 

As stated  above it is doubtful it came from your ISY. I would be eyeballing the wiring around the terminals with a strong light for stray strands of copper or connections that are loose and moved. The IOLinc has some quite small terminations to watch out for.

 

Another definite possibility is your close jamming detection. These can be current or mechanical detection methods, adjustable by the user, need to be checked every few years, and with some wind or door movement trigger the door to reverse it's perceived closing direction, depending on internal logic. Check for a spider making a winter's nest in your beam units or lens..

Link to comment

Check the wiring between the IOLink and the Opener as well as between the manual button and the opener.  I had one door that was acting up on humid days.  Turned out a staple had worked it way through the insulation and was shorting the wires simulating a button press under the right conditions.

 

-Xathros

Link to comment

My wiring to the IOLinc is an 18g solid wire, nothing that would have frayed across the contacts and it all looks fine. My Garage Door opener is a new Genie that I purchased less than a year ago, and I haven't had any issues with it. Before we went to sleep, I know we armed the security system and was ready when it was armed. I definitely don't believe it could be any humidity as I live in the Los Angeles area. It's pretty dry right now. My security system points to the garage are wireless ones, but don't believe they are even close to being near in frequency. 

 

Thanks,

 

Robert

Link to comment

There's a lot of concurrent activity in your log. Are these programmed or linked devices. If so, what are the details of the programs.scenes? Which are controllers/triggers? Which are responders only? I also don't see anything involving an alarm in the log.

Link to comment

I don't think the garage door moved as a result of the I/O Linc Relay.   There should have been a Log entry that reflected a Relay command.

 

Scene:SceneIOLincRelay On Tue 2014/10/28 02:39:19 PM Web Log
IOLinc I2CS-Relay Status 100% Tue 2014/10/28 02:39:19 PM System Log

Scene:SceneIOLincRelay On Tue 2014/10/28 02:43:05 PM Web Log

 

oberkc view that it was triggered by RF unrelated to the I/O Linc is supported by the Log which shows the Sensor changing state when the door moved but no Relay activity. 

 

The first line of my log shown was the relay on command:

 

"2 Door Garage Door Open                 On                  100               Tue 2014/10/28 02:09:18 AM            Web       Log"

 

Somehow it did come from the ISY, so I would assume.

 

Thanks,

 

Robert

Link to comment

Most of the items shown are part of the programs that were created. Usually the alarm system once activated, will activate all the lights in the house. The ones listed are lights that turn on when arriving home and the garage door is opened plus the disarming of the security system. I did disarm the system before it went into full alarm to not scare the kids out of bed.

  The one listed "Backyard Light / Garage Door - C    Status " is from my Keypadlinc in the kitchen by the back door to show status of the Garage door if it is open or not.

I hope this helps to clarify.

 

Thanks,

Robert

Link to comment

I am, by no means, fully knowledgeable about these logs, or your device naming conventions. What I can tell you, however, is that the relay will not transmit status...only the sensor does. I expect that your log was showing a change in sensor status.

 

Based upon the name alone, do you believe this log is showing a relay command?

Link to comment
It is very doubtful that stray RF emissions could activate a garage door opener with the rolling security code features used these days.

 

There was a lot of news traffic many years ago about some military operations on the same frequencies as many garage doors of the day.  I assume you are correct that later doors are less immune to any interference that may have existed.  Unfortunately, I am unaware of the age of pyrorobert's opener.

 

Or it certainly could have been other causes.

Link to comment

I am, by no means, fully knowledgeable about these logs, or your device naming conventions. What I can tell you, however, is that the relay will not transmit status...only the sensor does. I expect that your log was showing a change in sensor status.

 

Based upon the name alone, do you believe this log is showing a relay command?

This one is the relay module  "2 Door Garage Door Open"

and this one is the sensor status  "2 Door Garage Status"

If you see the log, it does show the status came in right after it opened the door.

 

Thanks,

Link to comment

I pulled this from the events log that was saved in Notepad, I will annotate what each is:

 

 
Tue 10/28/2014 02:09:03 AM : [  24 2C B0 2]       ST 255       IOLinc status
Tue 10/28/2014 02:09:04 AM : [  24 2C B0 1]      DON   0       IOLinc Relay on
Tue 10/28/2014 02:09:04 AM : [  24 2C B0 1]       ST 255       IOLinc Status
Tue 10/28/2014 02:09:04 AM : [  2B 98 C9 3]       ST 255       KeypadLinc showing status
Tue 10/28/2014 02:09:05 AM : [VAR  2    6 ]       1                  DSC showing open status of garage door
Tue 10/28/2014 02:09:05 AM : [VAR  2   13 ]       1                 DSC Entry delay activated
Tue 10/28/2014 02:09:09 AM : [VAR  2   17 ]       1                 DSC heartbeat
Tue 10/28/2014 02:09:39 AM : [VAR  2   17 ]       -1                DSC heartbeat
Tue 10/28/2014 02:09:44 AM : [VAR  2   16 ]       1                 DSC disarmed
Tue 10/28/2014 02:09:44 AM : [VAR  2   15 ]       0                 DSC no longer showing armed-stay
Tue 10/28/2014 02:09:44 AM : [   2A 69 7 1]       ST 255        Front of garage lights on
Tue 10/28/2014 02:09:44 AM : [VAR  2   13 ]       0                 DSC Garage door closed
Tue 10/28/2014 02:09:45 AM : [  22 B7 7C 1]       ST 255       Living Room light on
Tue 10/28/2014 02:09:45 AM : [  29 E7 53 1]       ST 255       Dining Room light on 
 
This shows a little more clarification of what happened. Let me know if this helps
 
Thanks,
 
Robert
Link to comment

It's GremLincs. Most often seen on St. Patric's day, GremLincs also show up around Halloween. They usually travel in groups of two and are commonly known as dual band GemLincs.

Link to comment

Node 2 is the Relay node.   Node 1 is the Sensor node.

 

Tue 10/28/2014 02:09:03 AM : [  24 2C B0 2]       ST 255       IOLinc status
Tue 10/28/2014 02:09:04 AM : [  24 2C B0 1]      DON   0       IOLinc Relay on THIS IS SENSOR, not Relay.
Tue 10/28/2014 02:09:04 AM : [  24 2C B0 1]       ST 255       IOLinc Status
 
Trace of Relay being turned Off/On.  Note the node is 2.
 
Tue 10/28/2014 10:51:57 PM : [iNST-TX-I1  ] 02 62 15 BB 5A 0F 11 02
Tue 10/28/2014 10:51:57 PM : [iNST-ACK    ] 02 62 15.BB.5A 0F 11 02 06          LTONRR (02)
Tue 10/28/2014 10:51:57 PM : [iNST-SRX    ] 02 50 15.BB.5A 22.80.0B 2B 11 02    LTONRR (02)
Tue 10/28/2014 10:51:57 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Tue 10/28/2014 10:55:03 PM : [iNST-TX-I1  ] 02 62 15 BB 5A 0F 13 02
Tue 10/28/2014 10:55:03 PM : [iNST-ACK    ] 02 62 15.BB.5A 0F 13 02 06          LTOFFRR(02)
Tue 10/28/2014 10:55:03 PM : [iNST-SRX    ] 02 50 15.BB.5A 22.80.0B 2B 13 02    LTOFFRR(02)
Tue 10/28/2014 10:55:03 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Tue 10/28/2014 10:55:03 PM : [D2D EVENT   ] Event [15 BB 5A 2] [sT] [0] uom=0 prec=-1
Tue 10/28/2014 10:55:03 PM : [  15 BB 5A 2]       ST   0
Tue 10/28/2014 10:55:18 PM : [iNST-TX-I1  ] 02 62 15 BB 5A 0F 11 02
Tue 10/28/2014 10:55:18 PM : [iNST-ACK    ] 02 62 15.BB.5A 0F 11 02 06          LTONRR (02)
Tue 10/28/2014 10:55:18 PM : [iNST-SRX    ] 02 50 15.BB.5A 22.80.0B 2B 11 02    LTONRR (02)
Tue 10/28/2014 10:55:18 PM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Tue 10/28/2014 10:55:18 PM : [D2D EVENT   ] Event [15 BB 5A 2] [sT] [255] uom=0 prec=-1
Tue 10/28/2014 10:55:18 PM : [  15 BB 5A 2]       ST 255
 
Link to comment

From your original post:

2 Door Garage Door Open                 On                  100               Tue 2014/10/28 02:09:18 AM            Web       Log

The Web at the end indicates to me that this command was issued based on a network request and not as a result of a program or other insteon traffic on the wire.

 

Food for thought...

 

-Xathros

Link to comment

Archived

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


×
×
  • Create New...