Deuce

Yep, placed it way down the road and tested - works like it did. At least I know that I can get back to full function, albeit, a bunch of rigmarole. I’m hoping someone has a trick, especially since we don’t know what caused things to stop working, and if it happens again, wouldn’t want to have to repeat all the steps to delete the device and then re-link Thanks

I have about a dozen in#teon switches, and a few outlets. No other RF devices outside of the motion sensors. But YES, when I deleted the motion sensor and then linked it in a test program, it does work. So the obvious question becomes, do I have to fetch all of the MS’s from the trees, shed, and corners of my house, delete and re-link them, or is there some trick, now that we know that the ISY is receiving RF signals through the PLM?

I agree with your thoughts on the PLM, however, if I have the MS with the ISY, then the RF would be direct with the ISY and the PLM would be irrelevant, no?

Yes, everything else is working fine. The sticker on the PLM says: 48.ED.48 Model: 24135 Revision 2.4.2817

The PLM shows “connected” when I check status, however, when I do a PLM Links Table, nothing happens. Did the PLM die the death?

Techman, The Firmware / UI version is: Insteon_UD994 v.4.6.2 (2017-06-21-13:52:47) The MS is 2842-222. The batteries are new as that was my first response. As per your suggestion, I brought a MS inside, placed it in linking mode and tried to query it. No response. I also powered down both the ISY and the PLM for 5 minutes, powered back up the PLM and then the ISY, as I saw suggested in a similar post, to no avail. There are no entries occurring in the event viewer as I attempt to query.

Hi All. I have about a dozen Insteon motion sensors about the outdoors of my home. These trigger various scenes and programs. A couple weeks ago, the ISY stopped responding to all of them. Checking logs, there are no recorded motion sensor events. It's as thought the ISY has tuned these all out. Has this happened to anyone and what are the troubleshooting steps? Many thanks.

Suggestions of moving to a single program and using an "or" statement within parenthesis, setting the MS's correctly, etc., etc., all collectively enabled me to get things working as I wanted. Thanks to all for your assist!

Also... Should the "Sensing Mode" also be checked? If I'm understanding correctly, by leaving it unchecked, the MS will not report motion until the timeout expires, and that seems to be what is prohibiting my setup from working. Lastly, to make settings on the motion sensors, I have to physically switch them in to setup mode, correct?

Stu, "Motion Sensors / Driveway" and "Motion Sensors / Driveway" are both motion sensors. not scenes. Regarding motion sensors, the ON commands only checkboxes were not selected - I'll give that a shot.

I'm not sure that I understand the parenthesis. Should it look like this: If From Sunset To 11:29:00PM (same day) And Status 'Motion Sensors / Driveway' is On Or ( Status 'Motion Sensors / Driveway' is On )

Thanks all for the suggestions. I tried the single program approach without the desired result. It is notable however, that if I trigger a motion sensor (and the subsequent program), then halfway through the "wait" cycle activate it again, it does not seem to start the clock again. Here's the code: If From Sunset To 11:29:00PM (same day) And Status 'Motion Sensors / Driveway' is On Or Status 'Motion Sensors / Driveway' is On Then Set 'Driveway / Pole Lights' On Set 'Driveway / Carriage Lights' 10% Set 'Porch / Porch-Front' 40% Set 'Porch / Porch-Side' 40% Wait 1 minute Set Scene 'Dim Driveway' On Wait 1 minute Set 'Porch / Porch-Side' Off Set 'Porch / Porch-Front' Off Else - No Actions - (To add one, press 'Action')

Hi, first-time-poster here... I graduated from the Insteon Hub to the ISY and WOW, what a difference. It seems like there are no limitations with regard to programming, if you know what you're doing... I have a long driveway (1/3 mile) that has many lamp posts along the way. At both ends, I have an Insteon motion sensor stashed in a little bird house in a tree. The motion sensors have their jumpers set to have the device controlled by software. I have built simple programs that when motion is sensed, the post lights go from dim to full-on. After a few minutes, the program returns the lamps to their dim state. For the most part, this works perfectly for motorists. For pedestrians however, there is a hitch. Walking down the driveway, the first motion kicks on and your good for the journey. But, before the turn-off event of the program, you hit the second sensor as you turn around to return. It then starts the same program. But a half-minute into the return trip, down goes the lights. I think that while my expectation is that the trigger of the second sensor is starting the time period for lights full-on, what is happening is that the first program's time has expired and it is calling for lights down. So my question is, how do we get the two motion sensors to work together so that together, they act more as a single occupancy sensor, restarting the clock whenever motion is sensed, either side? Thanks.