I’ve been replacing older motion sensors with Aeotec multisensors. They’re more reliable, provide additional data, and can run on USB power where available. (The less batteries I have to change, the better)
Sent from my iPhone using Tapatalk
jay (support) wrote:So, you're never seeing an OFF Insteon command coming from the Motion Sensor (easy test - bring it close to your PowerLinc, set it off (ON command), cover it with a towel and wait for an off)? You're right, that jumper would control that behavior. But it might also be a signal issue because that's a broadcast message from the sensor to the PowerLinc, though I would expect it would *sometimes* work. Insteon can be particularly bad at these types of unsolicited broadcast messages which is why we often recommend using Z-Wave sensors instead of Insteon.
Anyway, one thing to try is a factory reset of the MS. I don't recall how exactly to do that on those old motion sensors but I expect some internet searching will turn up the right procedure.
matt (support) wrote:Try using the Execute Raw INSTEON Command with the following settings:
Command 1 Byte: 0x2E
Command 2 Byte: 0x00
Send extended messages: checked
D1 Byte: 0x00
D2 Byte: 0x06
D3 Byte: 0x20 for ON only, or 0x00 for ON and OFF
D4 Byte: 0x0F
D5 Byte: OFF timeout interval in 10 second increments (0x03 would be 30 seconds). This value is probably unused if you have D3 set to 0x20.
D6 to D14 Bytes: 0x00 (for all of them)
Let me know if that works, and wake the module first by putting into linking mode (unless you have it USB powered).
matt (support) wrote:The easiest way to do it with the open/close sensor is to remove the jumper. From the manual:
Or you can use Indigo to handle the logic (trigger an action when the sensor sends the ON command), in which case you would not have the sensor directly linked to the light module.
Users browsing this forum: No registered users and 1 guest