Jump to content

Stubborn Motion Sensor with Bad Links


oronomus

Recommended Posts

I have a motion sensor that is turning on and off a group of about 20 lamplincs and togglelincs. I cannot seem to get rid of these links. I set the motion sensor to control 3 devices. In the Event Viewer (log below) the MS (11.8B.03) is set to control D.23.B8, D.24.6 and O.4F.24. These 3 show as controlled in the log. However, about 20 other lights are coming on and off when the sensor activates. I have tried a factory reset, a Restore Device on the sensor and a restore device on the PLM. Any other ideas??

 

 

2009/12/08 07:20:28 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 13 01 LTOFFRR(01)

 

2009/12/08 07:20:28 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:20:28 : [ 11 8B 3 1] DOF 1

 

2009/12/08 07:20:28 : [ 11 8B 3 1] ST 0

 

2009/12/08 07:20:28 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 13 01 LTOFFRR(01)

 

2009/12/08 07:20:28 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:20:28 : Duplicate: ignored

 

2009/12/08 07:20:28 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 13 01 LTOFFRR(01): Process Message: failed

 

2009/12/08 07:20:28 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:20:29 : [iNST-ACK ] 02 62 00.00.28 CF 13 00 06 LTOFFRR(00)

 

2009/12/08 07:20:29 : [ D 23 B8 1] ST 0

 

2009/12/08 07:20:29 : [ D 24 6 1] ST 0

 

2009/12/08 07:20:29 : [ 0 4F 24 1] ST 0

 

2009/12/08 07:30:29 : [ Time] 07:30:42 8(0)

 

2009/12/08 07:38:59 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 11 01 LTONRR (01)

 

2009/12/08 07:38:59 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:38:59 : [ 11 8B 3 1] DON 1

 

2009/12/08 07:38:59 : [ 11 8B 3 1] ST 255

 

2009/12/08 07:38:59 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 11 01 LTONRR (01)

 

2009/12/08 07:38:59 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:38:59 : Duplicate: ignored

 

2009/12/08 07:38:59 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 11 01 LTONRR (01): Process Message: failed

 

2009/12/08 07:38:59 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:39:00 : [iNST-ACK ] 02 62 00.00.28 CF 11 00 06 LTONRR (00)

 

2009/12/08 07:39:00 : [ D 23 B8 1] ST 229

 

2009/12/08 07:39:00 : [ D 24 6 1] ST 229

 

2009/12/08 07:39:00 : [ 0 4F 24 1] ST 255

 

2009/12/08 07:40:39 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 13 01 LTOFFRR(01)

 

2009/12/08 07:40:39 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:40:39 : [ 11 8B 3 1] DOF 1

 

2009/12/08 07:40:39 : [ 11 8B 3 1] ST 0

 

2009/12/08 07:40:39 : [iNST-ACK ] 02 62 00.00.28 CF 13 00 06 LTOFFRR(00)

 

2009/12/08 07:40:39 : [ D 23 B8 1] ST 0

 

2009/12/08 07:40:39 : [ D 24 6 1] ST 0

 

2009/12/08 07:40:39 : [ 0 4F 24 1] ST 0

 

2009/12/08 07:41:14 : Setting Time From NTP

 

2009/12/08 07:41:15 : Setting Time From NTP

 

2009/12/08 07:43:22 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 11 01 LTONRR (01)

 

2009/12/08 07:43:22 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:43:22 : [ 11 8B 3 1] DON 1

 

2009/12/08 07:43:22 : [ 11 8B 3 1] ST 255

 

2009/12/08 07:43:22 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 11 01 LTONRR (01)

 

2009/12/08 07:43:22 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:43:22 : Duplicate: ignored

 

2009/12/08 07:43:22 : [iNST-SRX ] 02 50 11.8B.03 00.00.01 C7 11 01 LTONRR (01): Process Message: failed

 

2009/12/08 07:43:22 : [standard-Group][11.8B.03-->Group=1] Max Hops=3, Hops Left=1

 

2009/12/08 07:43:23 : [iNST-ACK ] 02 62 00.00.28 CF 11 00 06 LTONRR (00)

 

2009/12/08 07:43:23 : [ D 23 B8 1] ST 229

 

2009/12/08 07:43:23 : [ D 24 6 1] ST 229

 

2009/12/08 07:43:23 : [ 0 4F 24 1] ST 255

Link to comment

Thanks Michael, I had in fact tried a Restore on several of the affected devices, and I tried a few Restores tonight on some of the others. No change in the problem.

 

When I run a Restore on an affected device, I do not see the Motion Sensor Address anywhere in the Event Log. Would a slave link show the MS address? Or could the affected devices be a part of a scene that is triggered by the MS (where the affected device would not identify the MS address in the log during the restore)? I remain baffled..

 

Any other ideas on how to isolate and fix this problem?

Link to comment

Seems strange. I would do the following:

 

- factory reset one of the responding devices

- test to ensure it no longer responds to the MS

- do a restore on the responding device from the ISY

- test again to ensure it no longer responds to the MS

 

Let me know your results...

Link to comment

Thanks again Michael for the help.

 

I had the following results:

 

- factory reset one of the responding devices - DONE

- test to ensure it no longer responds to the MS - CORRECT. NO RESPONSE

- do a restore on the responding device from the ISY - DONE

- test again to ensure it no longer responds to the MS - IT DOES RESPOND TO THE MS

 

So it seems that somewhere in the ISY, there is a scene or link that is telling these 20 some-odd affected devices to respond to the MS. How do I identify and correct? Do I manually unlink each affected device, or would they just re-link at the next restore?

Link to comment

I assume you checked to be sure there isn't a scene programmed somewhere that you are missing?

 

If not, did you originally have the ISY crawl and import existing links into the ISY? If so it sounds like you have half-links that were imported into the ISY.

 

Unfortunately, at this point I think your best solution is:

 

- remove each of the problem devices from the ISY

- factory reset each device

- add each device back into the ISY

- add each device into your scenes as needed

Link to comment

I have tested all the scenes that I see listed in the ISY tree. Of course, the 20 affected devices are included in many scenes, but there is no ONE scene that includes ONLY these 20 devices.

 

Is there a way to identify scenes from a restore event log? I.e., would the restore Event Log for either the MS or the affected device show the scenes in which they are included (so that I could compare them against scenes listed in the tree)? Could there be an active scene that doesn't show up in the ISY scene tree? Just trying to think it through...

 

Unless I hear otherwise, I will follow your proposed best solution and report.

Link to comment

I tried your best solution on one device and it worked! Thanks so much. Troublesome now to go do that for another 19 devices, but at least I have an answer to a stubborn problem:

 

- removed a problem devices from the ISY

- factory reset the device

- added the device back into the ISY

- added the device back into its scenes

 

I first tried to create a scene that contained the Motion Sensor and one of my problem devices, then deleted that scene. That did NOT solve the problem.

 

Again, thanks Michael for being patient and helpful..

Link to comment

Archived

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


×
×
  • Create New...