Garage door sensor problems

[neromir]

I have an Insteon IOLinc hooked up to my garage door opener that has been hooked up for around a year, and have started having problems with it in the last week or so. I'm not sure if it's a communication problem. Two things have happened: until today, I could always receive garage door opened sensor updates from the IOLinc, but garage door closed messages never got through. If I queried the sensor manually from the ISY admin console/page, it would get the correct closed value.

 

In order to try to fix the issue, I installed a SwitchLinc for the garage lights today, thinking the ISY might be having trouble getting the messages for close. Now it's worse-- I don't get open or close messages from the IOLinc until I manually query it.

 

I have since factory reset the IOLinc, but that doesn't seem to have made a difference. I'm not actually even sure that the problem is communication, or if the IOLinc is going bad.

 

I've logged some of the communication from the event viewer, but I'm having a hard time understanding what I'm looking at. Can anyone shed some light on what I'm seeing here? The garage door sensor's address is 34 8B BF, if that helps.

 

Also, trigger reverse is checked, it's set to momentary C, and I'm using the sensor that came with the garage door kit from Insteon-- I believe it's an NC sensor.

---> Closed garage
Fri 04/08/2016 04:59:16 PM : [INST-SRX    ] 02 50 34.8B.BF 00.00.01 CF 13 00    LTOFFRR(00)
Fri 04/08/2016 04:59:16 PM : [Std-Group   ] 34.8B.BF-->Group=1, Max Hops=3, Hops Left=3
Fri 04/08/2016 04:59:16 PM : [D2D EVENT   ] Event [34 8B BF 1] [DOF] [0] uom=0 prec=-1
Fri 04/08/2016 04:59:16 PM : [  34 8B BF 1]      DOF   0
Fri 04/08/2016 04:59:16 PM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 45 13 01    LTOFFRR(01)
Fri 04/08/2016 04:59:16 PM : [Std-Cleanup ] 34.8B.BF-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
Fri 04/08/2016 04:59:16 PM : [INST-DUP    ] Previous message ignored.
Fri 04/08/2016 04:59:16 PM : [INST-SRX    ] 02 50 34.8B.BF 13.01.01 CF 06 00           (00)
Fri 04/08/2016 04:59:16 PM : [Std-Group   ] 34.8B.BF-->13.01.01, Max Hops=3, Hops Left=3
Fri 04/08/2016 04:59:16 PM : [INST-INFO   ] Previous message ignored.
Fri 04/08/2016 04:59:17 PM : [X10-RX      ] 02 52 FF 80 
Fri 04/08/2016 04:59:17 PM : [         X10]       J/Status Request (10)
Fri 04/08/2016 04:59:17 PM : [X10-RX      ] 02 52 F2 80 
Fri 04/08/2016 04:59:17 PM : [         X10]       J/On (3)

---> Queried sensor from ISY
Fri 04/08/2016 05:00:11 PM : [INST-TX-I1  ] 02 62 34 8B BF 0F 19 01
Fri 04/08/2016 05:00:11 PM : [INST-ACK    ] 02 62 34.8B.BF 0F 19 01 06          LTSREQ (01)
Fri 04/08/2016 05:00:11 PM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 2F 06 01           (01)
Fri 04/08/2016 05:00:11 PM : [Std-Direct Ack] 34.8B.BF-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Fri 04/08/2016 05:00:11 PM : [D2D EVENT   ] Event [34 8B BF 1] [ST] [255] uom=0 prec=-1
Fri 04/08/2016 05:00:11 PM : [  34 8B BF 1]       ST 255
Fri 04/08/2016 05:00:11 PM : [D2D-CMP 000D] STS [34 8B BF 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Fri 04/08/2016 05:00:11 PM : [D2D-CMP 000A] STS [34 8B BF 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Fri 04/08/2016 05:00:11 PM : [D2D-CMP 0009] STS [34 8B BF 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true
Fri 04/08/2016 05:00:11 PM : [D2D-CMP 0004] STS [34 8B BF 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Fri 04/08/2016 05:00:11 PM : [INST-TX-I1  ] 02 62 34 8B BF 0F 19 00
Fri 04/08/2016 05:00:12 PM : [INST-ACK    ] 02 62 34.8B.BF 0F 19 00 06          LTSREQ (LIGHT)
Fri 04/08/2016 05:00:12 PM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 2F 06 00           (00)
Fri 04/08/2016 05:00:12 PM : [Std-Direct Ack] 34.8B.BF-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

---> Opened garage
Fri 04/08/2016 05:01:50 PM : [INST-SRX    ] 02 50 34.8B.BF 00.00.01 CF 11 00    LTONRR (00)
Fri 04/08/2016 05:01:50 PM : [Std-Group   ] 34.8B.BF-->Group=1, Max Hops=3, Hops Left=3
Fri 04/08/2016 05:01:50 PM : [D2D EVENT   ] Event [34 8B BF 1] [DON] [0] uom=0 prec=-1
Fri 04/08/2016 05:01:50 PM : [  34 8B BF 1]      DON   0
Fri 04/08/2016 05:01:50 PM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 45 11 01    LTONRR (01)
Fri 04/08/2016 05:01:50 PM : [Std-Cleanup ] 34.8B.BF-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
Fri 04/08/2016 05:01:50 PM : [INST-DUP    ] Previous message ignored.
Fri 04/08/2016 05:01:50 PM : [INST-SRX    ] 02 50 34.8B.BF 11.01.01 CF 06 00           (00)
Fri 04/08/2016 05:01:50 PM : [Std-Group   ] 34.8B.BF-->11.01.01, Max Hops=3, Hops Left=3
Fri 04/08/2016 05:01:50 PM : [INST-INFO   ] Previous message ignored.
Fri 04/08/2016 05:01:50 PM : [X10-RX      ] 02 52 FF 80 
Fri 04/08/2016 05:01:50 PM : [         X10]       J/Status Request (10)
Fri 04/08/2016 05:01:51 PM : [X10-RX      ] 02 52 F3 80 
Fri 04/08/2016 05:01:51 PM : [         X10]       J/Off (11)

---> Queried sensor
Fri 04/08/2016 05:02:30 PM : [INST-TX-I1  ] 02 62 34 8B BF 0F 19 01
Fri 04/08/2016 05:02:30 PM : [INST-ACK    ] 02 62 34.8B.BF 0F 19 01 06          LTSREQ (01)
Fri 04/08/2016 05:02:30 PM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 2F 06 00           (00)
Fri 04/08/2016 05:02:30 PM : [Std-Direct Ack] 34.8B.BF-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Fri 04/08/2016 05:02:30 PM : [D2D EVENT   ] Event [34 8B BF 1] [ST] [0] uom=0 prec=-1
Fri 04/08/2016 05:02:30 PM : [  34 8B BF 1]       ST   0
Fri 04/08/2016 05:02:30 PM : [D2D-CMP 000D] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Fri 04/08/2016 05:02:30 PM : [D2D-CMP 000A] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Fri 04/08/2016 05:02:30 PM : [D2D-CMP 0009] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false
Fri 04/08/2016 05:02:30 PM : [D2D-CMP 0004] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Fri 04/08/2016 05:02:30 PM : [INST-TX-I1  ] 02 62 34 8B BF 0F 19 00
Fri 04/08/2016 05:02:30 PM : [INST-ACK    ] 02 62 34.8B.BF 0F 19 00 06          LTSREQ (LIGHT)
Fri 04/08/2016 05:02:30 PM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 2F 06 00           (00)
Fri 04/08/2016 05:02:30 PM : [Std-Direct Ack] 34.8B.BF-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

[stusviews]

Communication appears OK. What is the result if you run the Then sections of the programs?

[larryllix]

Do you have CFL bulbs in your garage door operator?

[neromir]

Communication appears OK. What is the result if you run the Then sections of the programs?

 

I'm not sure I follow. Which programs? Just any?

 

Do you have CFL bulbs in your garage door operator?

 

I have one, but I removed it with no change in behavior. I do also have two currently in the garage, connected to the SwitchLinc I just installed, but they were off during most of these test cases here. I also have an incandescent in the other side (two lights on the opener, one on each side) that has been flickering a bit while the garage door is opening or closing. I think I'll try pulling that one out and see if it makes a difference.

[jerlands]

Communication doesn't seem to be an issue (Hops Left=3 in all tests.)

If you have "LED on TX" enabled you should be able to use the garage door opener remote (or fixed control if within range) and observe green LED light flashing when message is sent (you'll need to be close.)

If you use an Insteon device (as in a mini remote) to open it the status message from the sensor won't be discernible from the command except on close.

You could also do this by jumping the sensor terminals (NC contacts are open when magnets are close.)

 

 

Jon...

[neromir]

Got that option turned on, a couple of tests with the button on the wall show that the LED blinks when the magnet on the door moves away from or into range of the sensor. I may have been using the ISY to open and close the garage in the tests above; I can't remember now, so I suppose it may have interfered with seeing the messages.

 

It's getting late here, so I'll fiddle with it some more in the morning via the garage button and see if the event viewer output is any different, or see if I can find a convenient wire to jump/unjump the sensor repeatedly.

 

Thanks for the help so far, all.

[jerlands]

Got that option turned on, a couple of tests with the button on the wall show that the LED blinks when the magnet on the door moves away from or into range of the sensor. I may have been using the ISY to open and close the garage in the tests above; I can't remember now, so I suppose it may have interfered with seeing the messages.

 

It's getting late here, so I'll fiddle with it some more in the morning via the garage button and see if the event viewer output is any different, or see if I can find a convenient wire to jump/unjump the sensor repeatedly.

 

Thanks for the help so far, all.

 

If the sensor status message is being sent then the problem would be PLM link record is missing.  You did factory reset and "Restore Device" so that should have rewritten it but you could try deleting the IOLInc than relink (programs shouldn't get affected but check.)

 

 

Jon...

[stusviews]

I'm not sure I follow. Which programs? Just any? the garage door is opening or closing. I think I'll try pulling that one out and see if it makes a difference.

 

The programs that send a message (i.e., email, text).

[jerlands]

I may have been using the ISY to open and close the garage in the tests above; I can't remember now, so I suppose it may have interfered with seeing the messages.

 

If you're referring to tests posted in message #1 those won't matter.  I'm speaking about testing locally while observing the LED for messages sent by the sensor and how to exclude those from the relay.

 

 

Jon...

[neromir]

The programs that send a message (i.e., email, text).

I have a couple that react to the garage door sensor, one that turns on a light just inside the house if the garage door is opened at night, and one that sends me an email if the garage door is open later at night. Both programs work as expected if the sensor is stuck on the "open" value. i.e. with last week's behavior if I had opened the garage but not manually requeried the sensor after closing it, then once the sun went down the light one come on, and once the time got late enough I would get an email, even though the garage was closed. If I manually re-queried the sensor prior to those times, then the programs' then-clauses didn't run. 

 

You could also do this by jumping the sensor terminals (NC contacts are open when magnets are close.)

 

Jon...

 

Okay, I have the door closed, magnet is right there by the sensor. Jumpering the contacts on the sensor itself seems to be having no effect, which is interesting. Do you know if the IOLinc keeps a constant voltage on one of the wires? I guess I would expect it to, otherwise it wouldn't be able to detect when the sensor changes.

 

Testing the contacts with my multimeter shows no voltage differential between them, but checking for resistance shows a 1 ohm resistance between the contacts. That said, querying the sensor while I have the multimeter attached doesn't show a voltage being applied either, so my budding theory about whatever's applying the constant voltage going bad doesn't seem to be holding water.

 

Deleting and re-adding the IOLinc doesn't seem to have had any effect. Still only catches the update in the ISY if I manually query the sensor.

 

So, there are two LEDs on the IOLinc, there's a green one down where the wires for the sensor and garage opener control go, and there's a white one right next to the set button. On open, I don't see the white one blink (may just not have been in position fast enough), but on close I do see it blink a couple of times (one blink significantly brighter than the others) once the magnet gets right next to the sensor. The green one turns off when the magnet moves away from the sensor (door open), and turns on and stays on when the magnet is close to the sensor (door closed)

 

This is the event viewer traffic from that exchange, which leads me to believe that the messages are being received, if I'm reading this right.

---> Opened garage door via wall button, closed ~30sec or so later
Sat 04/09/2016 09:24:26 AM : [INST-SRX    ] 02 50 34.8B.BF 00.00.01 CF 11 00    LTONRR (00)
Sat 04/09/2016 09:24:26 AM : [Std-Group   ] 34.8B.BF-->Group=1, Max Hops=3, Hops Left=3
Sat 04/09/2016 09:24:26 AM : [D2D EVENT   ] Event [34 8B BF 1] [DON] [0] uom=0 prec=-1
Sat 04/09/2016 09:24:26 AM : [  34 8B BF 1]      DON   0
Sat 04/09/2016 09:24:27 AM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 45 11 01    LTONRR (01)
Sat 04/09/2016 09:24:27 AM : [Std-Cleanup ] 34.8B.BF-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
Sat 04/09/2016 09:24:27 AM : [INST-DUP    ] Previous message ignored.
Sat 04/09/2016 09:24:27 AM : [INST-SRX    ] 02 50 34.8B.BF 11.01.01 CF 06 00           (00)
Sat 04/09/2016 09:24:27 AM : [Std-Group   ] 34.8B.BF-->11.01.01, Max Hops=3, Hops Left=3
Sat 04/09/2016 09:24:27 AM : [INST-INFO   ] Previous message ignored.
Sat 04/09/2016 09:25:02 AM : [INST-SRX    ] 02 50 34.8B.BF 00.00.01 CF 13 00    LTOFFRR(00)
Sat 04/09/2016 09:25:02 AM : [Std-Group   ] 34.8B.BF-->Group=1, Max Hops=3, Hops Left=3
Sat 04/09/2016 09:25:02 AM : [D2D EVENT   ] Event [34 8B BF 1] [DOF] [0] uom=0 prec=-1
Sat 04/09/2016 09:25:02 AM : [  34 8B BF 1]      DOF   0
Sat 04/09/2016 09:25:02 AM : [D2D EVENT   ] Event [34 8B BF 1] [ST] [0] uom=0 prec=-1
Sat 04/09/2016 09:25:02 AM : [  34 8B BF 1]       ST   0
Sat 04/09/2016 09:25:02 AM : [D2D-CMP 000D] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Sat 04/09/2016 09:25:02 AM : [D2D-CMP 000A] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Sat 04/09/2016 09:25:02 AM : [D2D-CMP 0009] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false
Sat 04/09/2016 09:25:02 AM : [D2D-CMP 0004] STS [34 8B BF 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true
Sat 04/09/2016 09:25:02 AM : [INST-SRX    ] 02 50 34.8B.BF 39.00.8F 45 13 01    LTOFFRR(01)
Sat 04/09/2016 09:25:02 AM : [Std-Cleanup ] 34.8B.BF-->ISY/PLM Group=1, Max Hops=1, Hops Left=1
Sat 04/09/2016 09:25:02 AM : [INST-DUP    ] Previous message ignored.
Sat 04/09/2016 09:25:02 AM : [INST-SRX    ] 02 50 34.8B.BF 13.01.01 CF 06 00           (00)
Sat 04/09/2016 09:25:02 AM : [Std-Group   ] 34.8B.BF-->13.01.01, Max Hops=3, Hops Left=3
Sat 04/09/2016 09:25:02 AM : [INST-INFO   ] Previous message ignored.

I'll try getting the multi-meter on it while the garage is open, but I'm going to have to wait until I have a helper for that one.

[jerlands]

In your trace what I notice is that the IOLinc isn't sending a Status (ST) message for ON..

 

Sat 04/09/2016 09:24:26 AM : [ 34 8B BF 1] DON 0

 

but you see it for OFF...

 

Sat 04/09/2016 09:25:02 AM : [ 34 8B BF 1] DOF 0
Sat 04/09/2016 09:25:02 AM : [D2D EVENT ] Event [34 8B BF 1] [ST] [0] uom=0 prec=-1
Sat 04/09/2016 09:25:02 AM : [ 34 8B BF 1] ST 0

 

If you remove the sensor leads from the IOLInc, attach a short piece of wire to one of the terminals then jump out the other you should see a signal sent (this is easiest done off the ceiling and plugged into an extension cord.)

 

At the same time you can test the sensor using conductivity test (resistance) by testing the sensor in the closed position then open it partially (a foot or so) and test the sensor again.  NC contacts will show infinite resistance with garage door closed (display will depend on meter) and low resistance when door is open.

 

I don't know that the problem isn't the sensor rather than the IOLinc and this is what you're testing for.. to ensure the IOLinc is sending status messages on sensor change and that the sensor is working.

 

 

Jon...

[neromir]

Ok, just tested it with a helper. Contacts on the sensor itself read 5v differential and infinite resistance with the door open, contrast that with my previously measured 0v differential and 1 ohm resistance while the door was closed, and I'm wondering if this is not actually an NC sensor, but is instead NO.

 

Additionally, had the helper open and close the garage a couple of times while I could see the IOLinc LED, and I'm seeing the white LED blink with a similar pattern both on open and close, which seems to be indicating that the sensor value changing is being picked up by the IOLinc.

 

Got some people coming over, so won't be able to test the direct jumpering on the IOLinc for a while, but in the meantime, it seems like the sensor probably wouldn't be bad, just judging from the fact that the LEDs on the IOLinc are changing when the sensor state changes. I haven't dealt too much with embedded devices like this, but just trying to logic it out a bit. It seems like if the sensor were bad that I would see either failure of one or both LEDs to indicate changes, or inconsistent behavior on one or both LEDs during/after state changes. Admittedly, I haven't been in a good position to see the white one all the time for judging consistency, but the green one has been very consistent.

 

Thanks again for the help so far. Feel like I'm in a much better position to start understanding what's going on.

[jerlands]

Ok, just tested it with a helper. Contacts on the sensor itself read 5v differential and infinite resistance with the door open, contrast that with my previously measured 0v differential and 1 ohm resistance while the door was closed, and I'm wondering if this is not actually an NC sensor, but is instead NO.

 

Yes, your initial query shows status as On with garage door closed so contact is NO

Fri 04/08/2016 05:00:11 PM : [ 34 8B BF 1] ST 255

 

If all tests prove good I'd delete from ISY, factory reset and relink with device connected to extension cord and plugged into same outlet as PLM.

 

 

Jon...

[larryllix]

Ok, just tested it with a helper. Contacts on the sensor itself read 5v differential and infinite resistance with the door open, contrast that with my previously measured 0v differential and 1 ohm resistance while the door was closed, and I'm wondering if this is not actually an NC sensor, but is instead NO.

 

Additionally, had the helper open and close the garage a couple of times while I could see the IOLinc LED, and I'm seeing the white LED blink with a similar pattern both on open and close, which seems to be indicating that the sensor value changing is being picked up by the IOLinc.

 

Got some people coming over, so won't be able to test the direct jumpering on the IOLinc for a while, but in the meantime, it seems like the sensor probably wouldn't be bad, just judging from the fact that the LEDs on the IOLinc are changing when the sensor state changes. I haven't dealt too much with embedded devices like this, but just trying to logic it out a bit. It seems like if the sensor were bad that I would see either failure of one or both LEDs to indicate changes, or inconsistent behavior on one or both LEDs during/after state changes. Admittedly, I haven't been in a good position to see the white one all the time for judging consistency, but the green one has been very consistent.

 

Thanks again for the help so far. Feel like I'm in a much better position to start understanding what's going on.

From your posts it would seem you have your "Reversed" option turned on incorrectly.

 

Your input should be labelled "garage.door.closed" or equivalent as you contact is N.O. and indicates closed = Insteon Logic 'On' when the garage door is closed.

 

I haven't seenyour programs but you may have been playing off a contact bounce that stopped happenning with the reverse option checked.

 

Mine is also N.O, shows On when GD is closed, and I do not use the "reverse" option as that will cause it to show incorrectly every 3-4:00 am query until operated again. A query reports the status in the non-reversed status.

[neromir]

Well, that seems to have gotten it. I turned off trigger reverse and tried it a few times and the ISY has picked up the change each time.

 

I wonder why it would have stopped working all of a sudden? I didn't change any settings on the IOLinc that I'm aware of. I wonder if perhaps something changed subtly with the timing and if it was, like you said, relying on a transient bounce to trigger, the timing that allowed that isn't happening anymore due to some environmental factor.

 

My programs could have been depending on the bounce-- the ones depending on this sensor look like the below. Then I have others that trigger off the variable setting to do things like turn on the light inside the house.

Garage Door Opened Late - [ID 0004][Parent 0005]

If
        Status  'Garage Door Sensor' is Off
    And From    Sunset 
        To      Sunrise (next day)
 
Then
        $Garage_Door_Open_Late  = 1
 
Else
   - No Actions - (To add one, press 'Action')
 

At any rate, I'm just really glad it's working now. I'd be happy to see any thoughts, theories, or insights into if my theory is right or how I might have otherwise ended up in this state after having it work for a year.

 

Thanks again for everyone's help!

[stusviews]

The nightly query is apt to reverse trigger reverse.

[larryllix]

Well, that seems to have gotten it. I turned off trigger reverse and tried it a few times and the ISY has picked up the change each time.

 

I wonder why it would have stopped working all of a sudden? I didn't change any settings on the IOLinc that I'm aware of. I wonder if perhaps something changed subtly with the timing and if it was, like you said, relying on a transient bounce to trigger, the timing that allowed that isn't happening anymore due to some environmental factor.

 

My programs could have been depending on the bounce-- the ones depending on this sensor look like the below. Then I have others that trigger off the variable setting to do things like turn on the light inside the house.

Garage Door Opened Late - [ID 0004][Parent 0005]

If
        Status  'Garage Door Sensor' is Off
    And From    Sunset 
        To      Sunrise (next day)
 
Then
        $Garage_Door_Open_Late  = 1
 
Else
   - No Actions - (To add one, press 'Action')
 

At any rate, I'm just really glad it's working now. I'd be happy to see any thoughts, theories, or insights into if my theory is right or how I might have otherwise ended up in this state after having it work for a year.

 

Thanks again for everyone's help!

Nice!

 

I would use a Wait 2 seconds before setting your variable.

 

If you did get a signal bounce from wind or static interference etc. it could help ignore it, although using status and a variable, it may not matter depending on your downstream triggered program off the variable state.