Blackbird Posted January 8, 2016 Posted January 8, 2016 (edited) Below is a log of the events. Can anyone explain why my garage door opened at 2:57am? The scene "All On Off" is to turn off any lights left on at 2:57am. That scene does not include the iolinc for the garage. Scene:All On Off Off 0 Fri 2016/01/08 02:57:00 AM Program Log Overhead garage door-Sensor Status 100% Fri 2016/01/08 02:57:01 AM System Log Overhead garage door-Relay Status 100% Fri 2016/01/08 02:57:01 AM System Log Porch keypad - Garage Door- H Status 100% Fri 2016/01/08 02:57:01 AM System Log Overhead garage door-Relay Status Query Fri 2016/01/08 02:57:16 AM Program Log Overhead garage door-Relay Status 0% Fri 2016/01/08 02:57:16 AM System Log Scene:ISY Status Query Fri 2016/01/08 03:00:01 AM Program Log Overhead garage door-Relay Status 100% Fri 2016/01/08 03:00:05 AM System Log Deck Lights Status 0% Fri 2016/01/08 03:00:08 AM System Log Overhead garage door-Relay Status 0% Fri 2016/01/08 03:00:09 AM System Log Scene:DeckL Off 0 Fri 2016/01/08 03:00:13 AM Program Log Porch Keypad F Deck Lights Status 0% Fri 2016/01/08 03:00:13 AM System Log Edited January 8, 2016 by Blackbird
Teken Posted January 8, 2016 Posted January 8, 2016 Do you have trigger reverse enabled in the I/O Link?
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 No the trigger reverse box is not checked on the options Just momentary B and LED on TX
Teken Posted January 8, 2016 Posted January 8, 2016 how do I check that? Go to the node in the Admin Console and select options. If its checked then yes its enabled if not at least we removed one area from concern.
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 Also my deck light wasn't supposed to turn off until 9:35am What part of the log shows that the door opened?
Teken Posted January 8, 2016 Posted January 8, 2016 No the trigger reverse box is not checked on the options Just momentary B and LED on TX Next step is to do a visual confirmation the wires leading into the various I/O ports are properly seated and no bare wire is present. I've seen lots of installs where the bare wire was too long and some random movement caused the two adjacent wires to connect and initiate a random open / close. Don't rely on simply looking at it plugged in, wiggle the wire and see. If nothing happens unplug it and really look and pull on the wires to make sure all of them are seated and tighten down.
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 I will check for sure but does seem like a coincidence that its at the same time as the all off scene
Teken Posted January 8, 2016 Posted January 8, 2016 I will check for sure but does seem like a coincidence that its at the same time as the all off scene I agree and the next step is to really eye ball to make sure this device is indeed NOT part of this scene at all. Is it fair to say this never happen before and this program has been active for awhile and no previous issues have been seen?
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 It is not part of that scene and I created the scene about a month ago
LeeG Posted January 8, 2016 Posted January 8, 2016 Blackbird The I/O Linc Sensor Status was logged before I/O Linc Relay which suggests something else moved the door. The I/O Linc Sensor is a Controller only node, not changed by an Insteon command.
Teken Posted January 8, 2016 Posted January 8, 2016 I was more curious about why the log shows a query for the GDO I/O Linc: Overhead garage door-Relay Status Query Fri 2016/01/08 02:57:16 AM Program Log
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 (edited) Blackbird The I/O Linc Sensor Status was logged before I/O Linc Relay which suggests something else moved the door. The I/O Linc Sensor is a Controller only node, not changed by an Insteon command. Do you mean something other than insteon or ISY? They are both within the same second Edited January 8, 2016 by Blackbird
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 (edited) This was from the night before and all was fine Bedroom Light Status 0% Thu 2016/01/07 12:46:28 AM System Log Scene:All On Off Off 0 Thu 2016/01/07 02:57:00 AM Program Log Living room above chair light Status 0% Thu 2016/01/07 02:57:00 AM System Log Scene:ISY Status Query Thu 2016/01/07 03:00:00 AM Program Log Edited January 8, 2016 by Blackbird
Teken Posted January 8, 2016 Posted January 8, 2016 Can you offer more back ground as to how your home is set up to use the GDO I/O Link? I see you have a KPL assigned to the unit is this case? Also, can you shed some light as to any programs / scenes have the GDO included.
LeeG Posted January 8, 2016 Posted January 8, 2016 Blackbird Since the I/O Linc Sensor could not be affected by the All On Off Scene directly, I would look at the Log before what is posted in post 1. Also something invoked the All On Off Scene which also adds to the areas to examine. You've indicated the All On Off Scene has no reference to the I/O Linc so something else is communicating with that device Sensor and Relay.
Teken Posted January 8, 2016 Posted January 8, 2016 Are you on Windows 7? Ideals are peaceful - History is violent
Teken Posted January 8, 2016 Posted January 8, 2016 windows 8 Assuming its still present in the search field type in *Snipping Tool*. If its there you can launch it and it will allow you to perform a image capture.
Blackbird Posted January 8, 2016 Author Posted January 8, 2016 I thought there was a different way post your programs
Teken Posted January 8, 2016 Posted January 8, 2016 I thought there was a different way post your programs On the program just right click and select copy to clip board. Then come to this post and right click and paste. I thought you meant an image from your Admin Console
stusviews Posted January 8, 2016 Posted January 8, 2016 The Snipping Tool has been continued through Win 8 and Win 10.
Blackbird Posted January 9, 2016 Author Posted January 9, 2016 (edited) These are the only programs I have for the garage I/o linc Cant remember what this does but one of you recommended it Overhead Garage door relay off - If Status 'Overhead garage door-Relay' is On Then Wait 15 seconds Set 'Overhead garage door-Relay' Query Else - No Actions - (To add one, press 'Action') Pushover notification when door is closed Garage Door Closed - If Status 'Overhead garage door-Sensor' is Off Then Send Notification to 'Pushover' content 'Garage Overhead door closed' Else - No Actions - (To add one, press 'Action') Notification when door is opened Overhead Garage Door Open Notification If Status 'Overhead garage door-Sensor' is On Then Send Notification to 'email' content 'Garage Overhead Door sensor Open' Send Notification to 'Pushover' content 'Garage Overhead Door sensor Open' Else - No Actions - (To add one, press 'Action') This is the scene for the overhead garage door. I used to control the door from the key pad in the house but disabled it a while ago so the keypad would only light up when the door is open This is the all on off scene which I have set to a mini remote and a fast on and of on the kitchen light. This is my program that turns all the lights off at night incase I forgot to do it. This is the program I believe triggered the garage door to open as the door opened at 2:57am All off at night - If Time is 2:57:00AM Then Set Scene 'All On Off' Off Else - No Actions - (To add one, press 'Action') Edited January 9, 2016 by Blackbird
LeeG Posted January 10, 2016 Posted January 10, 2016 Blackbird I have not been able to relate posted Log entries.to the Programs. If this type event happens with any regularity suggest having Event Viewer at LEVEL 3 running for a few minutes before the activity begins so detail information can be collected and posted.
Recommended Posts