Jump to content

Garagelinc sensor problem


sumguy

Recommended Posts

I am fairly new to ISY and am not sure why I am having this problem. Any assistance would be greatly appreciated.I have a garagelinc kit installed that has been functioning flawlessly for 3+ years. I have an ISY994i PRO on firmware 4.3.6.

 

Recently the sensor status is randomly reporting incorrectly. Doesn't happen often but it did alert me last night at 3AM that my garage door was now open. Didn't notice the alert until around 5:50AM, when I checked my phone. Got my heart rate up a bit until I checked the camera in the garage and saw it was still closed. I refreshed the sensor and then it reported correctly again.

 

This is not happening all of the time. The status has been incorrect maybe 3 or 4 times over the last 3 weeks. This is the first time it happened at night.

 

Below is the log from last night. Does anything seem out of ordinary here? 

 

 

Scene:ISY   Status   Query   Thu 2015/07/16 03:00:00 AM   Program Log

Great Room / Thermostat Humidity   55%   Thu 2015/07/16 03:00:04 AM   System Log

Garage / Garage-Sensor   Status   0%   Thu 2015/07/16 03:00:19 AM   System Log

 

 

Garage / Garage-Sensor   Status   Query   Thu 2015/07/16 05:49:05 AM Web Log

Garage / Garage-Sensor   Status   100%   Thu 2015/07/16 05:49:05 AM System Log

Garage / Garage-Sensor   Status   Query   Thu 2015/07/16 05:49:10 AM Web Log

Garage / Garage-Sensor   Status   100%   Thu 2015/07/16 05:49:10 AM System Log

 

I also ran level 3 event viewer and queried the sensor. 

 

Thu 07/16/2015 10:16:28 AM : [iNST-TX-I1  ] 02 62 20 F7 FE 0F 19 01

Thu 07/16/2015 10:16:28 AM : [iNST-ACK    ] 02 62 20.F7.FE 0F 19 01 06          LTSREQ (01)
Thu 07/16/2015 10:16:28 AM : [iNST-SRX    ] 02 50 20.F7.FE 2F.B8.E4 27 00 01           (01)
Thu 07/16/2015 10:16:28 AM : [std-Direct Ack] 20.F7.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Thu 07/16/2015 10:16:28 AM : [D2D EVENT   ] Event [20 F7 FE 1] [sT] [255] uom=0 prec=-1
Thu 07/16/2015 10:16:28 AM : [  20 F7 FE 1]       ST 255
Thu 07/16/2015 10:16:28 AM : [D2D-CMP 0009] STS [20 F7 FE 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Thu 07/16/2015 10:16:28 AM : [iNST-TX-I1  ] 02 62 20 F7 FE 0F 19 00
Thu 07/16/2015 10:16:28 AM : [iNST-ACK    ] 02 62 20.F7.FE 0F 19 00 06          LTSREQ (LIGHT)
Thu 07/16/2015 10:16:29 AM : [iNST-SRX    ] 02 50 20.F7.FE 2F.B8.E4 27 00 00           (00)
Thu 07/16/2015 10:16:29 AM : [std-Direct Ack] 20.F7.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
 
Any idea what could cause a random false sensor status?
 
Thanks in advance!!
Link to comment

1. Do you have trigger reverse enabled in the I/O Linc?

 

2. What type of sensor do you have? The little small one offered currently by Smarthome or the larger SECO-LARM 226L-3 unit?

 

3. Open and close the GDO five times and watch the status of the *Sensor* does it reflect the correct state? Perform a query and confirm the state of the sensor does not change.

 

Please also review this related thread: http://forum.universal-devices.com/topic/16449-io-status-lost/

Link to comment

1. Trigger reverse is not selected.

2. I have the larger Seco-larm sensor.

3. The state of the sensor was correct each time. 

 

The ISY reports the status of the sensor correct almost every time. The incorrect status has only happened approx 3-4 times all within the last 2-3 weeks.  I have had the device for approx 3 years without any problems prior. The incorrect status doesn't happen when I actually open or close the door. It happens when the door has been idle just like in my logs above. It was the middle of the night and I was asleep. The other times were on the way home from work, I pulled up my garage in Mobilinc to open it and it showed that it was already open when it was physically closed. Each time I confirmed that the ISY had the incorrect status in the logs. Can't figure out what is causing it to randomly and infrequently cause the status to incorrectly change.

Link to comment

Archived

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


×
×
  • Create New...