2482 motion sensor programs not triggers

[cmidgley]

Hi all,

 

I've got a fairly large Insteon network w/isy994 (something like 80 devices + Elk M1) but just added the 2842-222 motion sensors for first time (five of them). The short version of the problem is that I can program and link device just fine, but the ISY never sees the motion events.

 

I can use the ISY just fine to add the device, link to other devices, bring up and set the Options on the device, etc. All of these are seen clearly in the Event Log. But when motion occurs (either real motion, or manually when pressing the button for on/off), there is no entry in the event log, and therefore no programs execute.

 

Whe I configure the motion sensor to turn on/off a device (by linking, using the ISY to do that link) - it works 100%. So motion to devices are working and communicating just fine ... even with the PLM ... but for some odd reason the PLM doesn't see the on/off events (even though the other devices do).

 

When I look at the device table, I do see the PLM configured in there (19.74.99 is my PLM):

 

1 : 0FF0 : E2 01 19.74.99 04 00 01

2 : 0FE8 : 62 01 22.90.51 FF 00 01

3 : 0FE0 : E2 02 19.74.99 FF 00 02

4 : 0FD8 : E2 03 19.74.99 06 00 03

5 : 0FD0 : 00 00 00.00.00 00 00 00

 

Here is an extract of the event log (level 3) of both the successful usage of the Options button (showing communication with the device at 23.24.d1) - plus at the end I clicked the motion button on/off several times (not that you could tell, because nothing appears in the log for that):

 

Sun 06/23/2013 11:27:05 AM : [iNST-TX-I2CS] 02 62 23 24 D1 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9

Sun 06/23/2013 11:27:05 AM : [iNST-ACK ] 02 62 23.24.D1 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06 (00)

Sun 06/23/2013 11:27:05 AM : [iNST-SRX ] 02 50 23.24.D1 19.74.99 2B 2F 00 (00)

Sun 06/23/2013 11:27:05 AM : [std-Direct Ack] 23.24.D1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 06/23/2013 11:27:05 AM : [iNST-ERX ] 02 51 23 24 D1 19 74 99 11 2F 00 00 01 00 07 01 50 10 01 41 0E 64 00 80 34

Sun 06/23/2013 11:27:05 AM : [Ext-Direct ] 23.24.D1-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Sun 06/23/2013 11:27:05 AM : [All ] Writing 0 bytes to devices

 

When I link the device into a scene to turn on/off a light, I do not see anything in the event log when I trigger motion. The light goes on/off just fine - but nothing at all in the logs.

 

The motion sensor is a 2842-222 Rev 2.3. I've tried this so far with two of my devices. I do have three more in box that I could try, but thought before I opened those I'd ask here for advice!

 

Thanks...

 

- Chris

[LeeG]

Count the number of links in the PLM using Tools | Diagnostics | Show PLM Links Table followed by Count when the Show display completes. No Insteon traffic can reach the PLM during the Show PLM Links Table as the count will not be accurate. Run the Show PLM Links Table followed by Count 3-4 times to insure the Show/Count sequence results in the same number.

 

The maximum for a 2413 is 992 links.

 

It sounds like the PLM link table is full so the necessary responder links for the Motion Sensor cannot be added to the PLM

[cmidgley]

Impressive! You nailed it - there are exactly 992 links.

 

Besides trying to reducing my usage of links, is there any other way to address this? Add another PLM? Or is it get a second ISY and then somehow manage the links and messages between them?

 

Thanks!!!

[LeeG]

The first thing to do is issue a File | Restore Modem (PLM). PLMs accumulate duplicate and outdated link records which the Restore Modem will eliminate. After the Restore Modem (PLM) completes run the Show PLM Links Table and Count again to see what the new link record count is.

 

The ISY supports only 1 PLM. If the PLM link record count is at the maximum even after the Restore Modem (PLM) the next step to remove/combine ISY Scenes to reduce the PLM link count.

[cmidgley]

I did a PLM restore as you suggested and a substanial amount of space was freed up. Now the motion sensors correctly show up in the event log, and the programs operate as expected. Thank you very much for your guidance!

[LeeG]

Your welcome. Thanks for taking the time to post back the results.