wwat Posted January 5, 2015 Posted January 5, 2015 (edited) I have one of the older garage door opener kits and its been working okay up until last few days. Haven't made any electrical changes recently. It`s linked to a keypadlinc button and works intermittently and sometimes not at all, this applies to both open and close operations. If I use the regular garage door opener to operate the door everything appears to get updated status and the keypadlinc light comes on and off correctly. All my other equipment appears to be working fine. Here are the results from the event viewer after pressing the keypadlinc button once where the garage door didn't respond and the keypadlinc light stayed off. Mon 01/05/2015 17:53:25 : [INST-SRX ] 02 50 33.03.0B 00.00.03 CF 11 00 LTONRR (00) Mon 01/05/2015 17:53:25 : [Std-Group ] 33.03.0B-->Group=3, Max Hops=3, Hops Left=3 Mon 01/05/2015 17:53:25 : [D2D EVENT ] Event [33 3 B 3] [DON] [0] uom=0 prec=-1 Mon 01/05/2015 17:53:25 : [ 33 3 B 3] DON 0 Mon 01/05/2015 17:53:25 : [D2D EVENT ] Event [33 3 B 3] [ST] [255] uom=0 prec=-1 Mon 01/05/2015 17:53:25 : [ 33 3 B 3] ST 255 Mon 01/05/2015 17:53:25 : [INST-SRX ] 02 50 33.03.0B 11.00.03 CF 06 00 (00) Mon 01/05/2015 17:53:25 : [Std-Group ] 33.03.0B-->11.00.03, Max Hops=3, Hops Left=3 Mon 01/05/2015 17:53:25 : [INST-INFO ] Previous message ignored. Edited January 5, 2015 by wwat
wwat Posted January 5, 2015 Author Posted January 5, 2015 Is it possible that some problem developed with the iolinc device.
Teken Posted January 5, 2015 Posted January 5, 2015 Is it possible that some problem developed with the iolinc device. Anything is possible you could simply hard reset it and use the restore device afterwards and see.
wwat Posted January 6, 2015 Author Posted January 6, 2015 (edited) I reset and restored the iolinc. It`s about minus 14 Celsius in the garage at the moment so I`m giving up for the evening. Using Mobilinc I was able to listen for the iolinc while activating the door. At times I`d press the button and hear the iolinc but the door didn`t open and other times I wouldn`t hear anything after pressing the button. Yet at other times It would work correctly. Tomorrow I`ll take another look, can anyone recommend and specific test to determine where the problem lies. Thanks. Edited January 6, 2015 by wwat
stusviews Posted January 6, 2015 Posted January 6, 2015 Observe the white LED on the side of the I/O Linc. It should light up full momentarily when a signal is sent to the I/O Linc and then return to dim. The relay should also click.
wwat Posted January 6, 2015 Author Posted January 6, 2015 Hi Stu, Had a chance this morning to observe the little bluish LED next too the SET button. Using Mobilinc I pressed the relay button and the light flashed every time, however the door didn't always respond. At first there was no clicking and the door still operated every second or so presses, then I heard some clicking when pressing the relay button and the door stopped functioning. No matter how many times I pressed the button the door didn't go down, it required me to used the standard garage door controls. This was the same behavior that happened last night. Now it will begin to work again every second or so presses. I'm wonder whether the cold temperatures have caused a problem with the iolinc. The problem started pretty much at the same time that the temps got low.
oberkc Posted January 6, 2015 Posted January 6, 2015 Is there a wall button? Is it the simple door-bell type button? Is that still working well? Have you checked the wires to ensure they are still tight? Have you tried adjusting the relay time-out? Teken may know something that I don't, but the communication looks good to me (three hops remaining).
Teken Posted January 6, 2015 Posted January 6, 2015 It could be the cold or its failing. Since you already did s factory reset I would confirm all the wiring is firm and sound. Don't just look at it pull on the wires to ensure they are tight and inserted. If in doubt remove one wire at a time inspect and insert back. Do the same thing for the GDO side. If you have a small heater try to warm up the unit and report back success / failure. I've had mine in the garage for more than five years and in -45'C weather and has worked like a champ. To be fair to Smartlabs this is well outside the operating range so can't throw stones at them in my case. Sent from my iPhone using Tapatalk
Teken Posted January 6, 2015 Posted January 6, 2015 Is there a wall button? Is it the simple door-bell type button? Is that still working well? Have you checked the wires to ensure they are still tight? Have you tried adjusting the relay time-out? Teken may know something that I don't, but the communication looks good to me (three hops remaining). I only mention the COM's because it did not decrement by 1. He had a initial three and a final three left over. Which in our experience is impossible because that would mean nothing was sent or received, no? Sent from my iPhone using Tapatalk
oberkc Posted January 6, 2015 Posted January 6, 2015 Perhaps you are correct. My knowledge (and interest) is limited to knowing that more hops remaining is better than fewer hops remaining. Having said this, if the initial command was sent, and the device responded with no repeats necessary, would this not constitute zero "hops"?
Teken Posted January 6, 2015 Posted January 6, 2015 (edited) Perhaps you are correct. My knowledge (and interest) is limited to knowing that more hops remaining is better than fewer hops remaining. Having said this, if the initial command was sent, and the device responded with no repeats necessary, would this not constitute zero "hops"? As I understand how it works based on what we know now. A message is sent and it has three tries to do so in an allocated period of time. It must always use up one hop to start and to get to the receiver device. It would thus have only two more tries to retransmit the command. What I have been seeing in the last few months is a change in behavior in how these hops are being reflected to us via the Level 3 reporting page. It could be this is due to a change in ISY firmware or Insteon device hardware (firmware). In the last few months I have seen what appears to be i3CS features and COM attributes being incorporated into various existing and new products. For example we have never seen resume dim, message clean up, repeat hops, variable settings for low battery, variable heart beat, etc. These are features spoken about in other forums and threads so the fact the OP shows three hops left leaves me to believe its either a COM issue. Or the new Level 3 logs are showing us information portrayed in a different manner than we have come to expect, or see. Back on topic to the OP: Since the device doesn't work now simply bring it inside let it warm up and report back operations of the relay when pushed manually and via the ISY. Edited January 6, 2015 by Teken
LeeG Posted January 6, 2015 Posted January 6, 2015 (edited) Hops Left=3 is new with the PLMs that have the firmware change to correct the All On scenario. More information to come on the total effects on Hops Left counts. The fact that the KPL LED did not turn On is odd unless it is set for non-toggle off mode. Edited January 6, 2015 by LeeG
Teken Posted January 6, 2015 Posted January 6, 2015 Hops Left=3 is new with the PLMs that have the firmware change to correct the All On scenario. More information to come on the total effects on Hops Left counts. On a small tangent this is similar to seeing the device communications retries from 0-9. Even though supposedly this has been long part of the protocol there has been very little discussed about this feature and how it ultimately impacts COM's. It also on the surface flies in the face of the max hop of three which is supposed to be the standard. I believe lots of interesting things are going to be seen and shaken out of the tree in 2015. In the big picture based on some discussions I've had with others some great things are coming down the Insteon pipe.
wwat Posted January 6, 2015 Author Posted January 6, 2015 The fact that the KPL LED did not turn On is odd unless it is set for non-toggle off mode. I'm pretty sure its set to Non-Toggle On Mode, as per instructions on wiki. I'm out at the moment, will be back in about an hour or so and will do as Taken suggests, take it inside and warm it up and test.
wwat Posted January 6, 2015 Author Posted January 6, 2015 (edited) I just performed two test, first from a socket inside the house near the PLM, secondly the iolinc plugged into the garage door electrical socket. I shorted the sensor and ground and then turned the relay on and off using the ISY admin console for each test. It appears to be working but I'm not 100% sure of what I'm looking at. I'm now going to wire it back into the garage door and check all the connections. BTW: the garage door works perfectly using the standard garage door remote and wired wall button. Test 1 - iolinc plugged into socket near PLM Tue 01/06/2015 15:12:34 : [INST-SRX ] 02 50 12.F9.DD 00.00.01 CF 13 00 LTOFFRR(00) Tue 01/06/2015 15:12:34 : [Std-Group ] 12.F9.DD-->Group=1, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:12:34 : [D2D EVENT ] Event [12 F9 DD 1] [DOF] [0] uom=0 prec=-1 Tue 01/06/2015 15:12:34 : [ 12 F9 DD 1] DOF 0 Tue 01/06/2015 15:12:34 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 45 13 01 LTOFFRR(01) Tue 01/06/2015 15:12:34 : [Std-Cleanup ] 12.F9.DD-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 01/06/2015 15:12:34 : [INST-DUP ] Previous message ignored. Tue 01/06/2015 15:12:35 : [INST-SRX ] 02 50 12.F9.DD 00.00.01 CF 11 00 LTONRR (00) Tue 01/06/2015 15:12:35 : [Std-Group ] 12.F9.DD-->Group=1, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:12:35 : [D2D EVENT ] Event [12 F9 DD 1] [DON] [0] uom=0 prec=-1 Tue 01/06/2015 15:12:35 : [ 12 F9 DD 1] DON 0 Tue 01/06/2015 15:12:35 : [D2D EVENT ] Event [12 F9 DD 1] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 15:12:35 : [ 12 F9 DD 1] ST 255 Tue 01/06/2015 15:12:35 : [D2D EVENT ] Event [33 3 B 3] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 15:12:35 : [ 33 3 B 3] ST 255 Tue 01/06/2015 15:12:35 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 45 11 01 LTONRR (01) Tue 01/06/2015 15:12:35 : [Std-Cleanup ] 12.F9.DD-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 01/06/2015 15:12:35 : [INST-DUP ] Previous message ignored. Tue 01/06/2015 15:13:22 : [INST-TX-I1 ] 02 62 12 F9 DD 0F 11 02 Tue 01/06/2015 15:13:22 : [INST-ACK ] 02 62 12.F9.DD 0F 11 02 06 LTONRR (02) Tue 01/06/2015 15:13:23 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 2F 11 02 LTONRR (02) Tue 01/06/2015 15:13:23 : [Std-Direct Ack] 12.F9.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:13:23 : [D2D EVENT ] Event [12 F9 DD 2] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 15:13:23 : [ 12 F9 DD 2] ST 255 Tue 01/06/2015 15:13:26 : [INST-TX-I1 ] 02 62 12 F9 DD 0F 13 02 Tue 01/06/2015 15:13:26 : [INST-ACK ] 02 62 12.F9.DD 0F 13 02 06 LTOFFRR(02) Tue 01/06/2015 15:13:26 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 2F 13 02 LTOFFRR(02) Tue 01/06/2015 15:13:26 : [Std-Direct Ack] 12.F9.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:13:26 : [D2D EVENT ] Event [12 F9 DD 2] [ST] [0] uom=0 prec=-1 Tue 01/06/2015 15:13:26 : [ 12 F9 DD 2] ST 0 Test 2 - iolinc plugged into garage door socket Tue 01/06/2015 15:16:42 : [INST-SRX ] 02 50 12.F9.DD 00.00.01 CF 13 00 LTOFFRR(00) Tue 01/06/2015 15:16:42 : [Std-Group ] 12.F9.DD-->Group=1, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:16:42 : [D2D EVENT ] Event [12 F9 DD 1] [DOF] [0] uom=0 prec=-1 Tue 01/06/2015 15:16:42 : [ 12 F9 DD 1] DOF 0 Tue 01/06/2015 15:16:42 : [D2D EVENT ] Event [12 F9 DD 1] [ST] [0] uom=0 prec=-1 Tue 01/06/2015 15:16:42 : [ 12 F9 DD 1] ST 0 Tue 01/06/2015 15:16:42 : [D2D EVENT ] Event [33 3 B 3] [ST] [0] uom=0 prec=-1 Tue 01/06/2015 15:16:42 : [ 33 3 B 3] ST 0 Tue 01/06/2015 15:16:42 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 45 13 01 LTOFFRR(01) Tue 01/06/2015 15:16:42 : [Std-Cleanup ] 12.F9.DD-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 01/06/2015 15:16:42 : [INST-DUP ] Previous message ignored. Tue 01/06/2015 15:16:43 : [INST-SRX ] 02 50 12.F9.DD 00.00.01 CF 11 00 LTONRR (00) Tue 01/06/2015 15:16:43 : [Std-Group ] 12.F9.DD-->Group=1, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:16:43 : [D2D EVENT ] Event [12 F9 DD 1] [DON] [0] uom=0 prec=-1 Tue 01/06/2015 15:16:43 : [ 12 F9 DD 1] DON 0 Tue 01/06/2015 15:16:43 : [D2D EVENT ] Event [12 F9 DD 1] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 15:16:43 : [ 12 F9 DD 1] ST 255 Tue 01/06/2015 15:16:43 : [D2D EVENT ] Event [33 3 B 3] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 15:16:43 : [ 33 3 B 3] ST 255 Tue 01/06/2015 15:16:43 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 45 11 01 LTONRR (01) Tue 01/06/2015 15:16:43 : [Std-Cleanup ] 12.F9.DD-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 01/06/2015 15:16:43 : [INST-DUP ] Previous message ignored. Tue 01/06/2015 15:19:03 : [INST-TX-I1 ] 02 62 12 F9 DD 0F 11 02 Tue 01/06/2015 15:19:03 : [INST-ACK ] 02 62 12.F9.DD 0F 11 02 06 LTONRR (02) Tue 01/06/2015 15:19:03 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 2F 11 02 LTONRR (02) Tue 01/06/2015 15:19:03 : [Std-Direct Ack] 12.F9.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:19:03 : [D2D EVENT ] Event [12 F9 DD 2] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 15:19:03 : [ 12 F9 DD 2] ST 255 Tue 01/06/2015 15:19:07 : [INST-TX-I1 ] 02 62 12 F9 DD 0F 13 02 Tue 01/06/2015 15:19:07 : [INST-ACK ] 02 62 12.F9.DD 0F 13 02 06 LTOFFRR(02) Tue 01/06/2015 15:19:07 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 2F 13 02 LTOFFRR(02) Tue 01/06/2015 15:19:07 : [Std-Direct Ack] 12.F9.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/06/2015 15:19:07 : [D2D EVENT ] Event [12 F9 DD 2] [ST] [0] uom=0 prec=-1 Tue 01/06/2015 15:19:07 : [ 12 F9 DD 2] ST 0 Edited January 6, 2015 by wwat
Teken Posted January 6, 2015 Posted January 6, 2015 Is the device now installed in the garage? If so does it operate fine now?
wwat Posted January 6, 2015 Author Posted January 6, 2015 (edited) Is the device now installed in the garage? If so does it operate fine now? Believe it or not yes, its again working perfectly. I'll have to wait until it's had some time to get really cold again to know for sure but it could have been a wiring issue I guess but all the wires were in place and tight. I just took them out and put them back in a tightened up again. One thing I find confusing is the status of the sensor and door in ISY admin. When the door is closed the sensor says 'off' and the relay says 'On' but my documentation says that these should be the other way around. I physically checked the little green sensor light on the iolinc and its ON so the sensor should be ON in ISY admin shouldn't it? I'm almost sure if I query it using admin it will read ON but I don't want to touch it now that it is working again. Here is the event log for full up and down of garage door using the keypadlinc. Tue 01/06/2015 16:14:50 : [ Time] 16:15:14 1(0) Tue 01/06/2015 16:14:51 : [INST-TX-I1 ] 02 62 0E 9E 81 0F 11 72 Tue 01/06/2015 16:14:51 : [INST-ACK ] 02 62 0E.9E.81 0F 11 72 06 LTONRR (72) Tue 01/06/2015 16:14:51 : [INST-SRX ] 02 50 0E.9E.81 30.6A.B2 2F 11 72 LTONRR (72) Tue 01/06/2015 16:14:51 : [Std-Direct Ack] 0E.9E.81-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:14:51 : [D2D EVENT ] Event [E 9E 81 1] [ST] [114] uom=0 prec=-1 Tue 01/06/2015 16:14:51 : [ E 9E 81 1] ST 114 Tue 01/06/2015 16:14:51 : [D2D-CMP 0003] STS [E 9E 81 1] ST op=1 Event(val=114 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Tue 01/06/2015 16:15:04 : [INST-SRX ] 02 50 33.03.0B 00.00.03 CF 11 00 LTONRR (00) Tue 01/06/2015 16:15:04 : [Std-Group ] 33.03.0B-->Group=3, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:15:04 : [D2D EVENT ] Event [33 3 B 3] [DON] [0] uom=0 prec=-1 Tue 01/06/2015 16:15:04 : [ 33 3 B 3] DON 0 Tue 01/06/2015 16:15:04 : [D2D EVENT ] Event [12 F9 DD 2] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 16:15:04 : [ 12 F9 DD 2] ST 255 Tue 01/06/2015 16:15:04 : [D2D EVENT ] Event [33 3 B 3] [ST] [255] uom=0 prec=-1 Tue 01/06/2015 16:15:04 : [ 33 3 B 3] ST 255 Tue 01/06/2015 16:15:04 : [INST-SRX ] 02 50 33.03.0B 11.00.03 CF 06 00 (00) Tue 01/06/2015 16:15:04 : [Std-Group ] 33.03.0B-->11.00.03, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:15:04 : [INST-INFO ] Previous message ignored. Tue 01/06/2015 16:15:05 : [INST-SRX ] 02 50 12.F9.DD 00.00.01 CF 11 00 LTONRR (00) Tue 01/06/2015 16:15:05 : [Std-Group ] 12.F9.DD-->Group=1, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:15:05 : [D2D EVENT ] Event [12 F9 DD 1] [DON] [0] uom=0 prec=-1 Tue 01/06/2015 16:15:05 : [ 12 F9 DD 1] DON 0 Tue 01/06/2015 16:15:05 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 45 11 01 LTONRR (01) Tue 01/06/2015 16:15:05 : [Std-Cleanup ] 12.F9.DD-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 01/06/2015 16:15:05 : [INST-DUP ] Previous message ignored. Tue 01/06/2015 16:15:30 : [INST-SRX ] 02 50 33.03.0B 00.00.03 CF 11 00 LTONRR (00) Tue 01/06/2015 16:15:30 : [Std-Group ] 33.03.0B-->Group=3, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:15:30 : [D2D EVENT ] Event [33 3 B 3] [DON] [0] uom=0 prec=-1 Tue 01/06/2015 16:15:30 : [ 33 3 B 3] DON 0 Tue 01/06/2015 16:15:30 : [INST-SRX ] 02 50 33.03.0B 11.00.03 CF 06 00 (00) Tue 01/06/2015 16:15:30 : [Std-Group ] 33.03.0B-->11.00.03, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:15:30 : [INST-INFO ] Previous message ignored. Tue 01/06/2015 16:15:43 : [INST-SRX ] 02 50 12.F9.DD 00.00.01 CF 13 00 LTOFFRR(00) Tue 01/06/2015 16:15:43 : [Std-Group ] 12.F9.DD-->Group=1, Max Hops=3, Hops Left=3 Tue 01/06/2015 16:15:43 : [D2D EVENT ] Event [12 F9 DD 1] [DOF] [0] uom=0 prec=-1 Tue 01/06/2015 16:15:43 : [ 12 F9 DD 1] DOF 0 Tue 01/06/2015 16:15:43 : [D2D EVENT ] Event [12 F9 DD 1] [ST] [0] uom=0 prec=-1 Tue 01/06/2015 16:15:43 : [ 12 F9 DD 1] ST 0 Tue 01/06/2015 16:15:43 : [D2D EVENT ] Event [33 3 B 3] [ST] [0] uom=0 prec=-1 Tue 01/06/2015 16:15:43 : [ 33 3 B 3] ST 0 Tue 01/06/2015 16:15:43 : [INST-SRX ] 02 50 12.F9.DD 30.6A.B2 45 13 01 LTOFFRR(01) Tue 01/06/2015 16:15:43 : [Std-Cleanup ] 12.F9.DD-->ISY/PLM Group=1, Max Hops=1, Hops Left=1 Tue 01/06/2015 16:15:43 : [INST-DUP ] Previous message ignored. Edited January 6, 2015 by wwat
Teken Posted January 6, 2015 Posted January 6, 2015 The state of the sensor is dependent upon the type of sensor used and how its wired. The older units came with the super large and (awesome) dual option of either N.C. vs N.O contacts. The newer (cheaper) kit comes with only one option and I believe its N.O?? The relay state does not matter as it changes state quickly and always shows a ON. The only thing that matters is the Sensor state of either ON / OFF. If the (sensor) shows off with the GDO door closed this is the most common and accepted method of use. The reverse is also true when the GDO is open the sensor will show ON. Those who have purchased the newer style either had to live with the backwards sensor state or change out the sensor. Please keep us in the loop when the mercury drops further and how the GDO operates.
wwat Posted January 6, 2015 Author Posted January 6, 2015 Thanks for everyones help with this. Taken, mine is one of the older iolinc's with both the n/c and n/o options. Currently the sensor is connected to the n/o terminal. Just thinking about it wouldn't it be more appropriate if connected to n/c because the door is closed most of the time.
Teken Posted January 6, 2015 Posted January 6, 2015 Thanks for everyones help with this. Taken, mine is one of the older iolinc's with both the n/c and n/o options. Currently the sensor is connected to the n/o terminal. Just thinking about it wouldn't it be more appropriate if connected to n/c because the door is closed most of the time. It really comes down to how you expect it to operate and whether you're happy with its operations. Given, you had this installed for years with out issue in terms of how it reports its door state. You can certainly change it to what ever suites your needs or wants. For me so long as the sensor reflects the GDO in my KPL's, ISY UI, Mobilinc in human form that makes sense. I don't care how its installed as long as it makes sense to the lay person.
wwat Posted January 6, 2015 Author Posted January 6, 2015 (edited) I guess as a lay person it doesn't really make sense to me at the moment because it's hooked up to a n/o terminal. I would have though that the sensor should be on a n/c terminal given that the door and sensor are normally closed. However I'm not going to mess with in right now, come warmer months I may look at it again just to get a fresh understanding about how it all works. I used to know how it all worked but because I rarely have to work with it the knowledge gets lost lol. Thanks. Edited January 6, 2015 by wwat
Teken Posted January 6, 2015 Posted January 6, 2015 I guess as a lay person it doesn't really make sense to me at the moment because it's hooked up to a n/o terminal. I would have though that the sensor should be on a n/c terminal given that the door and sensor are normally closed. However I'm not going to mess with in right now, come warmer months I may look at it again just to get a fresh understanding about how it all works. I used to know how it all worked but because I rarely have to work with it the knowledge gets lost lol. Thanks. LOL . . . Just monitor it and report back any issues. Happy New Years!
stusviews Posted January 6, 2015 Posted January 6, 2015 It really doesn't matter to the operation of the I/O Linc whether you use NO or NC. It may matter to the responder (e.g.,, lit, unlit). Even the state of the responder can be changed by using the reverse trigger option. But, I've heard that the Query All can change that, so it may not be a good idea. Back to the I/O Linc. All my I/O Lincs correctly show the state of both the sensor and relay. For the garage doors, the relay is closed (On) only during the brief time that the relay is activated. Otherwise, the ISY correctly displays the relay as open (Off). And the sensor is lit (On) whenever the garage door is not closed. In particular, the garage door must be fully closed for the sensor to show Off.
wwat Posted January 7, 2015 Author Posted January 7, 2015 Stu, thank you for the clarification. The 'Reverse Trigger' option is active in my current set up and up until now I've had no problem with the 'Query All' program. I'll keep an eye on it though.
Recommended Posts