Jump to content

Why does a Query All hit some devices multiple times?


WayneW

Recommended Posts

Posted

Here are parts of the event viewer level 3 from the scheduled 3 AM "Query All" program.  

 

Some (all?) KPLs seem to have 2, 3 or 4 "Std-Direct Ack" lines.  What determines if it is 2, 3 or 4 entries?  Is this indicating a comm problem?

 

04.E8.B6 KPL Garage Side Lite (old, PLC only)

 
Sun 01/11/2015 03:01:01 AM : [iNST-TX-I1  ] 02 62 04 E8 B6 0F 19 00
Sun 01/11/2015 03:01:01 AM : [iNST-ACK    ] 02 62 04.E8.B6 0F 19 00 06          LTSREQ (LIGHT)
Sun 01/11/2015 03:01:01 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 2B 08 00           (00)
Sun 01/11/2015 03:01:01 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sun 01/11/2015 03:01:01 AM : [iNST-TX-I1  ] 02 62 04 E8 B6 0F 19 01
Sun 01/11/2015 03:01:01 AM : [iNST-ACK    ] 02 62 04.E8.B6 0F 19 01 06          LTSREQ (01)
Sun 01/11/2015 03:01:01 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 23 08 00           (00)
Sun 01/11/2015 03:01:01 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Sun 01/11/2015 03:01:01 AM : [iNST-TX-I1  ] 02 62 00 FC D0 0F 19 00
Sun 01/11/2015 03:01:02 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 2B 08 C0           (C0)
Sun 01/11/2015 03:01:02 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sun 01/11/2015 03:01:02 AM : [iNST-ACK    ] 02 62 00.FC.D0 0F 19 00 06          LTSREQ (LIGHT)
Sun 01/11/2015 03:01:02 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 23 08 C0           (C0)
Sun 01/11/2015 03:01:02 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
 
00.C9.CD Icon Switch (old, PLC only)
 
I noticed the missing second LTSREQ line.  Is that significant?  I assume that is a Status Request, but it isn't defined in the Wiki.
 
Sun 01/11/2015 03:00:04 AM : [iNST-TX-I1  ] 02 62 00 C9 CD 0F 19 00
Sun 01/11/2015 03:00:04 AM : [iNST-ACK    ] 02 62 00.C9.CD 0F 19 00 06          LTSREQ (LIGHT)
Sun 01/11/2015 03:00:04 AM : [iNST-SRX    ] 02 50 00.C9.CD 28.CE.92 27 00 00           (00)
Sun 01/11/2015 03:00:04 AM : [std-Direct Ack] 00.C9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
Sun 01/11/2015 03:00:04 AM : [iNST-TX-I1  ] 02 62 04 4B FB 0F 19 00
Sun 01/11/2015 03:00:05 AM : [iNST-SRX    ] 02 50 00.C9.CD 28.CE.92 23 00 00           (00)
Sun 01/11/2015 03:00:05 AM : [std-Direct Ack] 00.C9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 

 

I see something similar when bulk turning things off at sunrise (as a safety measure).  

 

It seems like I have comm echos or delays?  Is seems like maybe the ISY moved on to control the next device (23.B0.38) when the first device (00.5C.C0) still had replies in flight?

 

Sun 01/11/2015 07:19:09 AM : [iNST-ACK    ] 02 62 00.5C.C0 0F 13 00 06          LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [iNST-SRX    ] 02 50 00.5C.C0 28.CE.92 27 13 00    LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [std-Direct Ack] 00.5C.C0-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
Sun 01/11/2015 07:19:10 AM : [iNST-ACK    ] 02 62 23.B0.38 0F 13 00 06          LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [iNST-SRX    ] 02 50 00.5C.C0 28.CE.92 23 13 00    LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [std-Direct Ack] 00.5C.C0-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Sun 01/11/2015 07:19:10 AM : [iNST-SRX    ] 02 50 23.B0.38 28.CE.92 2B 13 00    LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [std-Direct Ack] 23.B0.38-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

ISY-Events-Log.v4.2.5__Sun 2015.01.11 09.47.28 AM.txt

Posted

First I would move up to 4.2.22, the 4.2.5 image is pretty old.

 

The I/O Linc is sent two commands, one queries the Sensor, one queries the Relay.

 

Sun 01/11/2015 03:01:01 AM : [iNST-TX-I1  ] 02 62 04 E8 B6 0F 19 00
Sun 01/11/2015 03:01:01 AM : [iNST-ACK    ] 02 62 04.E8.B6 0F 19 00 06          LTSREQ (LIGHT)
Sun 01/11/2015 03:01:01 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 2B 08 00           (00)
Sun 01/11/2015 03:01:01 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sun 01/11/2015 03:01:01 AM : [iNST-TX-I1  ] 02 62 04 E8 B6 0F 19 01
Sun 01/11/2015 03:01:01 AM : [iNST-ACK    ] 02 62 04.E8.B6 0F 19 01 06          LTSREQ (01)
Sun 01/11/2015 03:01:01 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 23 08 00           (00)
Sun 01/11/2015 03:01:01 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
The response from the PLM that ends in 06 is not missing.   Device 04.E8.B6 had two responses received by PLM.
 
Sun 01/11/2015 03:01:01 AM : [iNST-TX-I1  ] 02 62 00 FC D0 0F 19 00
Sun 01/11/2015 03:01:02 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 2B 08 C0           (C0)
Sun 01/11/2015 03:01:02 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Sun 01/11/2015 03:01:02 AM : [iNST-ACK    ] 02 62 00.FC.D0 0F 19 00 06          LTSREQ (LIGHT)
Sun 01/11/2015 03:01:02 AM : [iNST-SRX    ] 02 50 04.E8.B6 28.CE.92 23 08 C0           (C0)
Sun 01/11/2015 03:01:02 AM : [std-Direct Ack] 04.E8.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
 
00.C9.CD Icon Switch (old, PLC only)
 
I noticed the missing second LTSREQ line.  Is that significant?  I assume that is a Status Request, but it isn't defined in the Wiki.
 
Similar situation, device response is received twice.  Watch the device Insteon address in the the outbound message (02 62) versus what is in the inbound (02 50) message.   
 
Sun 01/11/2015 03:00:04 AM : [iNST-TX-I1  ] 02 62 00 C9 CD 0F 19 00
Sun 01/11/2015 03:00:04 AM : [iNST-ACK    ] 02 62 00.C9.CD 0F 19 00 06          LTSREQ (LIGHT)
Sun 01/11/2015 03:00:04 AM : [iNST-SRX    ] 02 50 00.C9.CD 28.CE.92 27 00 00           (00)
Sun 01/11/2015 03:00:04 AM : [std-Direct Ack] 00.C9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
Sun 01/11/2015 03:00:04 AM : [iNST-TX-I1  ] 02 62 04 4B FB 0F 19 00
Sun 01/11/2015 03:00:05 AM : [iNST-SRX    ] 02 50 00.C9.CD 28.CE.92 23 00 00           (00)
Sun 01/11/2015 03:00:05 AM : [std-Direct Ack] 00.C9.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 

 

I see something similar when bulk turning things off at sunrise (as a safety measure).  

 

It seems like I have comm echos or delays?  Is seems like maybe the ISY moved on to control the next device (23.B0.38) when the first device (00.5C.C0) still had replies in flight?

 

That is correct.   The process of receiving multiple responses does happen as the inbound path has multiple options.   The PLM normally picks those off but when there is a delay between responses the PLM will often pass the duplicate to the application (ISY).  Again, watch the Insteon addresses of outbound and inbound messages.  

 

Sun 01/11/2015 07:19:09 AM : [iNST-ACK    ] 02 62 00.5C.C0 0F 13 00 06          LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [iNST-SRX    ] 02 50 00.5C.C0 28.CE.92 27 13 00    LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [std-Direct Ack] 00.5C.C0-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
 
Sun 01/11/2015 07:19:10 AM : [iNST-ACK    ] 02 62 23.B0.38 0F 13 00 06          LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [iNST-SRX    ] 02 50 00.5C.C0 28.CE.92 23 13 00    LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [std-Direct Ack] 00.5C.C0-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
 
Sun 01/11/2015 07:19:10 AM : [iNST-SRX    ] 02 50 23.B0.38 28.CE.92 2B 13 00    LTOFFRR(00)
Sun 01/11/2015 07:19:10 AM : [std-Direct Ack] 23.B0.38-->ISY/PLM G
Posted

Thanks for the reply.

I don't have an I/O link, but I do have Keypads.  Are Keypads expected to always take two queries?

 

While documenting and posting all that, I did notice the overlap/interweave of addresses, which I highlighted.  Based upon what you said about multiple inbound paths, there is nothing concerning about what I posted?  Just kind of a "sometimes this stuff happens, but it is only noticed if you are running event viewer"?

Posted

Sorry about the garage KPL, you did indicate it is a KPL.   The first Query returns the On Level of the load control button.  The second Query returns the buttons states.

 

I would not be concerned about the multiple messages unless there is a symptom caused by them (beyond the event viewer).

Archived

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

×
×
  • Create New...