When you refer to Group records, are you referring to what you see when using the Manage Device Links tab? Have you tried listing the link records more than once. The Utility is sensitive to receiving expected messages in return to messages that are issued. Unexpected Insteon traffic can cause the Display process to stop, particularly when traffic can be generated by triggering of one of the motion sensors. Requesting another Display may provide more information the next time. What is displayed in the lower right corner of the SHN Utility window when the Display Existing Link Records display stops. Also, what are the last few lines under the Insteon Traffic tab, Received Insteon Traffic window. Finally are you Connecting the SHN Utility through an EZSrve or a PLC.

I can decipher the trace entries but it does not explain why only two. The right hand window contains the responses received to specific commands issued by the SHN Utility. The issued commands are displayed in the left hand window. There is generally a one for one relationship and I was expecting to see an extra inbound record labeled with but no such luck. In the right side window cmd1 field is the command that was originally issued and cmd2 is the data byte received in response to the command. You can find the command numbers and a description in the EZX10RF Command Set in the SHN Download section. Basically the Utility is Peeking data from individual bytes of memory where the link database is located.

The commands in the trace are

0x28 sets the Most Significant Byte (MSB) of the memory address.
0x2B is a Peek. In the outbound command, cmd2 is the low order byte of the memory address, In the inbound command it is the value contained in the memory byte accessed by the Peek. You can follow the memory addresses being accessed by following the cmd2 value of the Peeks (0x2B) in the left hand window, outbound commands.

A link record is 8 bytes long consisting of:

Flags – E2 – “Controller of” link record
Group – 1 – Group number
Device ID: 0D.FE.A1 – Insteon address of device being controlled – PLM/PLC used by ISY
Data 1 – 0xFF – bright level – has no relevance in a “Controller of” link record
Data 2 – 0x1F – ramp rate – has no relevance in a “Controller of” link record
Data 3 – 1 – varies by device. In this case Group number

Flags – E2 – “Controller of” link record
Group -2 – Group number
Device ID: 0D.FE.A1 – Insteon address of device being controlled – PLM/PLC used by ISY
Data 1 – 0xFF – bright level – has no relevance in a “Controller of” link record
Data 2 – 0x1F – ramp rate – has no relevance in a “Controller of” link record
Data 3 – 2 – varies by device. In this case Group number

Flags – 00 – end of active link record list

The last 0x28 is resetting the MSB byte to 0x00, which seems to be a convention when finished Peeking or Poking.

The link records are stored in memory, high to low. 0xFF8 is the beginning address of the first link record (there is an exception to that but not relevant to your situation).

Is there something in ISY that you are looking at that is showing Groups 3-5 are actually being used. Just because there is a Group number assigned to an index number does not mean there is an active link record for that Group number. Any chance that some of the motion sensors are using the same X10 device address. The Insteon Traffic tab is not a generalized Insteon traffic trace. Because you have a PLC, you can open the SDM3 window (double click on blue T shaped ICON in system tray when SHN Utility is running) which is the interface between the PLC and the application. That is a general Insteon trace although Insteon traffic can flow faster than the PLC/SDM3 can generate trace records. The lack of a trace entry cannot does not mean that an Insteon message did not actually flow. The Group number is contained in the Group message sequence so you should be able to look at the SDM3 trace data to see if the EZX10RF is issuing Group commands for Groups 3-5.

Let me know what you find.

EDIT: how did you establish the links which you are currently using?

Using the Set button on the EZX10RF?
Using the SHN Utility?
Using ISY function?

I don’t think you have anything to worry about since it is working for you. Just cannot explain how it is working with the link records that are being displayed. I am sending you a PM with some additional data.

If you want to continue analyzing this situation but don’t want to pursue the approach in the PM, start the SHN Utility and Connect to the PLC. Double click on the blue T shaped Icon in the system tray to open the SDM3 window. Trigger each of the 5 motion sensors and post the trace data from the SDM3 window.