Insteon motion sensor turning off in 'on only' mode

[wwat]

This sensor (2420M) has been working fine since purchase, yesterday it stopped working so I replaced the battery. After replacement I put it in programming mode and checked the settings, I made a small change to the brightness setting. After waiting for the timeout I triggered the sensor and it turned off which it shouldn't do.

I also noticed that the sensor model was set to 2842-222 which is not something I have ever done. I have two of these 2420M sensors and they have both been set to 2842-222 but the other sensor is actually working.

 

I then removed the sensor and reinstalled with the correct model but this didn't solve the problem.

Not sure where to go from here, any guidence appreciated.

 

ISY 994i/IR Pro

Firmware ver. 3.3.5

[Michel Kohanim]

Hi wwat,

 

2842-222 is the new model number for Motion Sensors.

 

Can you tell me precisely what the issues is now?

 

With kind regards,

Michel

[wwat]

The problem is that the sensor changes to an off state and stays off once it detects a movement. I can turn it on using the little set button but once the sensor detects a movement the sensor state will change to off and stay there without sensing anything else.

 

I have changed the sensor model back to 2420M-SP.

I found that the original battery is working fine.

 

Hope that is clear, thanks Wayne.

[LeeG]

wwat

 

Smarthome changed the Item # to the new scheme now that they are supporting different RF frequencies for different countries. The US model (-222) uses the same cat/subcat (device type) as the 2420M and operates exactly the same. There is no need to override with a specific Device Type setting.

 

Does the Red LED blink when motion is sensed even though it does not send a motion On message?

 

I am running 3.3.7 so cannot verify directly but I tested setting the On Only option on both a non-I2CS and I2CS motion sensor. The On Only option is working on both variations at 3.3.7. The Set button will send a Motion Off regardless of options. If the Red LED does flash when Motion is sensed run Tools | Diagnostics | Event Viewer at LEVEL 3. Post the event trace. The Red LED will blink when Motion is sensed and not send a Motion On if not in Sensing Mode (Occupancy Mode) and the motion sensor is counting down the timeout interval.

 

If not in the timeout interval and no Motion On is sent put the Motion Sensor into linking mode and click the Set Options. What is each of the six options set to and post the event trace generated when doing the Set Options. Except for being in the timeout interval there is no option that stops a motion sensor from sending a Motion On.

[wwat]

Hi LeeG,

 

Does the Red LED blink when motion is sensed even though it does not send a motion On message? I am running 3.3.7 so cannot verify directly but I tested setting the On Only option on both a non-I2CS and I2CS motion sensor. The On Only option is working on both variations at 3.3.7. The Set button will send a Motion Off regardless of options. If the Red LED does flash when Motion is sensed run Tools | Diagnostics | Event Viewer at LEVEL 3. Post the event trace. The Red LED will blink when Motion is sensed and not send a Motion On if not in Sensing Mode (Occupancy Mode) and the motion sensor is counting down the timeout interval.

 

The red light did flash and here are the results of that event. (Looks like its sending an off command). What I noticed is that even though the sensor is off it always sends an off signal (DOF 1) when motion is sensed.

Jumpers settings - 1(ON), 2(OFF), 3(OFF, 4(ON), 5(OFF)

 

Fri 12/28/2012 07:43:21 AM : [iNST-SRX    ] 02 50 0A.3D.AD 00.00.01 CB 13 01    LTOFFRR(01)
Fri 12/28/2012 07:43:21 AM : [std-Group   ] 0A.3D.AD-->Group=1, Max Hops=3, Hops Left=2
Fri 12/28/2012 07:43:21 AM : [   A 3D AD 1]      DOF   1
Fri 12/28/2012 07:43:21 AM : [   A 3D AD 1]       ST   0
Fri 12/28/2012 07:43:21 AM : [iNST-SRX    ] 02 50 0A.3D.AD 00.00.01 CB 13 01    LTOFFRR(01)
Fri 12/28/2012 07:43:21 AM : [std-Group   ] 0A.3D.AD-->Group=1, Max Hops=3, Hops Left=2
Fri 12/28/2012 07:43:21 AM : [iNST-DUP    ] Previous message ignored.
Fri 12/28/2012 07:43:22 AM : [iNST-SRX    ] 02 50 0A.3D.AD 19.75.00 41 13 01    LTOFFRR(01)
Fri 12/28/2012 07:43:22 AM : [std-Cleanup ] 0A.3D.AD-->ISY/PLM Group=1, Max Hops=1, Hops Left=0
Fri 12/28/2012 07:43:22 AM : [iNST-DUP    ] Previous message ignored.

 

 

wwat

If not in the timeout interval and no Motion On is sent put the Motion Sensor into linking mode and click the Set Options. What is each of the six options set to and post the event trace generated when doing the Set Options. Except for being in the timeout interval there is no option that stops a motion sensor from sending a Motion On.

 

Here is this info anyway.

 

Fri 12/28/2012 08:03:56 AM : [iNST-TX-I2  ] 02 62 0A 3D AD 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9
Fri 12/28/2012 08:03:56 AM : [iNST-ACK    ] 02 62 0A.3D.AD 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06        (00)
Fri 12/28/2012 08:03:56 AM : [iNST-SRX    ] 02 50 0A.3D.AD 19.75.00 2B 2F 00           (00)
Fri 12/28/2012 08:03:56 AM : [std-Direct Ack] 0A.3D.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Fri 12/28/2012 08:03:57 AM : [iNST-ERX    ] 02 51 0A 3D AD 19 75 00 11 2F 00 00 01 00 07 01 50 10 01 24 0C 64 01 23 C9 
Fri 12/28/2012 08:03:57 AM : [Ext-Direct  ] 0A.3D.AD-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Fri 12/28/2012 08:04:03 AM : [iNST-SRX    ] 02 50 11.BE.62 19.75.00 0B 6F 1E           (1E)
Fri 12/28/2012 08:04:03 AM : [std-Direct  ] 11.BE.62-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Fri 12/28/2012 08:04:03 AM : [  11 BE 62 1]   CLIHUM  30
Fri 12/28/2012 08:04:25 AM : [iNST-TX-I2  ] 02 62 0A 3D AD 1F 2F 00 00 02 00 07 08 50 10 01 24 0C 64 01 23 A7
Fri 12/28/2012 08:04:25 AM : [iNST-ACK    ] 02 62 0A.3D.AD 1F 2F 00 00 02 00 07 08 50 10 01 24 0C 64 01 23 A7 06        (00)
Fri 12/28/2012 08:04:25 AM : [iNST-SRX    ] 02 50 0A.3D.AD 19.75.00 2B 2F 00           (00)
Fri 12/28/2012 08:04:25 AM : [std-Direct Ack] 0A.3D.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

[wwat]

okay, I performed a factory reset on the MS and that resolved the problem. The sensor now sends the DON command as it should.

 

Thanks.

[LeeG]

Without Jumper 5 On the Motion Sensor uses the other jumpers for configuration. Not sure what the motion sensor is going to do when trying to configure it with software without jumper 5.

 

The Motion Sensor was certainly sending an Off command when it should have been sending an On command. Not sure it that had to do with switching batteries or the MS is not happy getting conflicting directions (software setting configuration without jumper 5).

[wwat]

Without Jumper 5 On the Motion Sensor uses the other jumpers for configuration. Not sure what the motion sensor is going to do when trying to configure it with software without jumper 5.

The Motion Sensor was certainly sending an Off command when it should have been sending an On command. Not sure it that had to do with switching batteries or the MS is not happy getting conflicting directions (software setting configuration without jumper 5).

Good question, this came to mind last night while I was playing around but that #5 jumper has always been off and I have always been able to set the options programmatically (verified because the new figures seem to stick and the countdown changes as per the settings).

 

My other motion sensor is configured exactly the same and has been working perfectly, actually haven't had a problem with either until now. What got me thinking there was a hicup with the unit was when the current status for the MS read 10% instead of either off or on. Clearly something was wrong with the MS but the factory reset resolved it.