Garage Door Opens On Its Own (second time)

[EddieRock]

I have ISY v4.4.6 and it's been running flawlessly! Love it. I've had no issues or questions since March.

 

For the second time, I've been at home and I receive a text that my garage door has opened. I rewind my security camera and lone behold, it opened on it's own. This is the second time this has happened so i now need to know what I should check.

 

I remember reading a while back that someone mentioned that if you have an Insteon motion sensor that is low on battery, it may cause strange things on the network. I have one of those and the batt was low.

 

Garage Door Opener is an Insteon (2450) IOLink v.41

 

Anyone have any ideas?

 

here are the last logs I have. Between 6:40:22 and 6:40:26 something caused the Garage Door to open. I do not have any programs to open or close the door. Just notification programs. 

 

Kitchen Level / Kitchen Motion - Sensor Status 0% Mon 2016/09/12 06:40:21 PM System Log

Scene:Kitchen Level / Kitchen Evening Mode Scene A Fast Off Mon 2016/09/12 06:40:21 PM Program Log

Kitchen Level / Kitchen Can Lights Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Scene:Kitchen Level / Fireplace Lights Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Kitchen Level / Kitchen Sconces Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Kitchen Level / Kitchen Under Cabinet Lights Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Scene:Kitchen Level / All Kitchen Lights Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Kitchen Level / Kitchen Can Lights Status 0% Mon 2016/09/12 06:40:22 PM System Log

Scene:Kitchen Level / Under Cabinet Lights C Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Doors, Garage and Outdoor / Garage Door - Sensor Status 0% Mon 2016/09/12 06:40:26 PM System Log

Bedroom Level / Bedroom Thermostat - Main Humidity 52% Mon 2016/09/12 06:43:38 PM System Log

[stusviews]

I have that occasionally at the 3:00 AM query. I believe it's related to the ALL ON phenomenon which I've also experienced. Sometimes I get a partial ALL ON. OTOH, it could be a low battery.

[paulbates]

Was this initiated by a motion sensor?

 

 

 

Scene:Kitchen Level / Under Cabinet Lights C Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log

 

Its interesting that there was all of the events above exactly at 06:40:22 from the program log. That could potentially to be both a battery panic from a motion sensor and the source of what opened the door.

[EddieRock]

Was this initiated by a motion sensor?

 

 

Its interesting that there was all of the events above exactly at 06:40:22 from the program log. That could potentially to be both a battery panic from a motion sensor and the source of what opened the door.

 

Yes. I have a motion sensor in my kitchen. If there is no motion, it turns off all my scenes and lights in that room. That occurred 4 seconds before my garage door opened. Unsure if it's related. Also, that motion sensor is NOT the one that had the low battery.

 

Ed

[paulbates]

Ed

Gotcha.  All of the programs (the 6 log rows above the red) were sending scene commands at exactly the same time. I think that is related to what's going on.

 

 

Kitchen Level / Kitchen Can Lights Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Scene:Kitchen Level / Fireplace Lights Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Kitchen Level / Kitchen Sconces Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Kitchen Level / Kitchen Under Cabinet Lights Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Scene:Kitchen Level / All Kitchen Lights Scene Fast Off Mon 2016/09/12 06:40:22 PM Program Log

Kitchen Level / Kitchen Can Lights Status 0% Mon 2016/09/12 06:40:22 PM System Log

 

Can you create a new scene with all of those lights in it and use that just to turn them all off with that one scene with one program when the sensor stops sensing motion? 

 

The UDI recommended practice is to put a 2 second 'Wait' gap in programs between the 'If' sensing from a sensor, and commanding the devices to act. 

 

Paul

[EddieRock]

Ed

Gotcha.  All of the programs (the 6 log rows above the red) were sending scene commands at exactly the same time. I think that is related to what's going on.

 

 

Can you create a new scene with all of those lights in it and use that just to turn them all off with that one scene with one program when the sensor stops sensing motion? 

 

The UDI recommended practice is to put a 2 second 'Wait' gap in programs between the 'If' sensing from a sensor, and commanding the devices to act. 

 

Paul

Paul, 

 

Yes, I've set most of my multi then statements with 2 seconds between set lines. Must have missed this one.

 

Interesting is that I haven't changed anything with my ISY since March (I think) and the kitchen motion sensor triggers this program 2-3 times a day without any side effects. I'll add the 2 second wait times.

[paulbates]

Ed

 

These kinds of problems are hard, especially when intermittent.  Let's hope this gets it.

 

Paul

[larryllix]

If the IO/Link is sensitive to X10 commands from a neighbour would they show up in the ISY logs?

 

Was it factory reset before linking to ISY? Do you have any X10 devices?

[MWareman]

 

 

If the IO/Link is sensitive to X10 commands from a neighbour would they show up in the ISY logs?

 

No, it might not. Yet another reason to dislike iolincs connected to garage door openers!

[G W]

I have MyQ and love it. I'll connect it to the ISY but not with an IOLinc. Maybe the Elk.

 

Short and to the point.

Best regards,

Gary Funk

[EddieRock]

Well, at least my system tells me when the door opens. Both times this happened, I had a low battery in a Insteon motion sensor. @larryllix the IOLink was new in the box and I do not have any X-10. My neighbors do not either.

[mwester]

Regrettably, new-in-the-box doesn't mean anything with regard to Insteon settings; it's commonly reported that new Insteon devices show up with all manner of odd (and in some cases impossible-to-reproduce) settings and devices configured.   So the general advice is to factory-reset each device before initial setup.

 

Based on what you've said, I doubt that this is your problem, but a factory reset and a restore of that device certainly wouldn't hurt.

 

(FWIW, I'm in that group of users who've switched to more reliable controls for the GDO -- I use a z-wave door controller instead of the IOLinc.)

[larryllix]

I only use the GD status via IOLink. I didn't see the need to be able to close it for afar, yet.

 

X10 was put into the IO/Linc of the factory QC tested it and can react to noise as it is very insecure.

 

Always factory reset your devices before personal usage!

 

Ignoring warnings given to me, in the past, I have had Insteon devices do things they shouldn't be capable of, before factory resetting them.

[EddieRock]

Regrettably, new-in-the-box doesn't mean anything with regard to Insteon settings; it's commonly reported that new Insteon devices show up with all manner of odd (and in some cases impossible-to-reproduce) settings and devices configured.   So the general advice is to factory-reset each device before initial setup.

 

Based on what you've said, I doubt that this is your problem, but a factory reset and a restore of that device certainly wouldn't hurt.

 

(FWIW, I'm in that group of users who've switched to more reliable controls for the GDO -- I use a z-wave door controller instead of the IOLinc.)

Can you send me a link to the z-wave device  you use?