walkman9999 Posted October 2, 2014 Posted October 2, 2014 Sorry for ambiguous title, not sure what the actual problem is. The motion sensor occasionally reports as "on" in the ISY console regardless of its actual status. I can place it right next to a dual-band receiver (to account for possible RF distance issues), put it in a drawer (to account for spurious motion detection), and even take the battery out (for who knows why) but ISY still reports as "on". When this problem isn't happening, ISY reports the detector as off. This happens about once every two weeks Notes: I have on/off checked in "options" so that off command is sent when timeout value expires. When I check status from ISY (after pressing "set" button), it reads the motion detector fine. I've changed batteries. Any troubleshooting tips?
larryllix Posted October 2, 2014 Posted October 2, 2014 I assume we are discussing the Insteon 2842-222 model. Many of us use the MS units with the 'Off' disabled as it makes it easier to manage time-offs in ISY through decision making logic. This may be set that way in your unit but I can't explain the "off" if you have ever seen one. There is a jumper that sets this preference and if the rightmost jumper is on the two p[ins then the software in ISY options at the bottom of the device page sets that option in software. Note the Linking mode must be set on the MS first. The downside is the MS will never indicate "Off" in the ISY and "status" based logic cannot be used. A peel at your Events in level 3 may be usefull to observe the consistency of how many "hops left" are involved in it's communications. This may give an indication of flakey communications with the PLM.
walkman9999 Posted October 2, 2014 Author Posted October 2, 2014 HI larryllix, Thank you. I will enable the level3 debug and set the unit to 'off' disabled. My program logic doesn't use the 'off' command anyway - I'm using the "control" function to trigger the program. Will report back.
walkman9999 Posted October 3, 2014 Author Posted October 3, 2014 The motion detector is working again, but I am still trying to figure out if the communication between the motion senso and the nearest dual-band device is the cause of the problem. I was able to capture the attached debug when the program was triggered. Wondering if anyone can look at it and assess the communication on the network? The motion detector is 2D.64.89. The program that gets triggered: door-programs.txt The log file: ISY-Events-Log.v4.1.2__Fri 2014.10.03 12.21.03.txt Thanks! ISY-Events-Log.v4.1.2__Fri 2014.10.03 12.21.03.txt door-programs.txt
LeeG Posted October 3, 2014 Posted October 3, 2014 The motion sensor comm is at the furtherest edge of success. The Hops Left=0 is as bad as it gets and still function. No room for any interference. Would like to see Hops Left=2, Hops Left=1 is fine if it generally stays at 1. Fri 10/03/2014 12:16:36 : [iNST-SRX ] 02 50 2D.64.89 00.00.01 C3 11 01 LTONRR (01) Fri 10/03/2014 12:16:36 : [std-Group ] 2D.64.89-->Group=1, Max Hops=3, Hops Left=0 Fri 10/03/2014 12:16:36 : [iNST-ACK ] 02 62 1B.5D.49 0F 11 FF 06 LTONRR (FF) Fri 10/03/2014 12:16:36 : [iNST-SRX ] 02 50 1B.5D.49 28.CB.F2 2B 11 FF LTONRR (FF) Fri 10/03/2014 12:16:36 : [std-Direct Ack] 1B.5D.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
walkman9999 Posted October 3, 2014 Author Posted October 3, 2014 Is there a way to tweak it to try more times? I am pretty sure the RF distance is an issue, but that is where the door is so not sure what else I can do? Open to suggestions, but I realize there may not be a way around my problem. Thanks LeeG
LeeG Posted October 3, 2014 Posted October 3, 2014 Hops processing is built into the devices. No options. Could try adding a Dual Band device that is on the same 120v leg as the PLM if there is a circuit nearby.
Recommended Posts