Unexpected Response (i.e. DB range): ignored

[johnnyt]

Am on firmware 3.3.9 and have a v41 KPL 6 button relay setup as an 8 button kpl and was looking up the device links table with event viewer at level 3 when I noticed the message:

Unexpected Response (i.e. DB range): ignored

The first time I read the device links table it returned only 5 (of the 48) links with the last one being 00 00 00 ...

 

The second time I did the query I got all 48 link records (which matches what PLM has) but still got the above message part way through. What happened? What does this message mean?

 

If I'm to guess at it the DB stands for Dual Band. Interestingly the KPL is less than 3 feet away from an access point (on the wall behind it). I do have metal junction boxes and I know they reduce the range but 3 feet should be close enough to see it, no? Or do metal junction boxes completely block out RF even at that close a range? Overall there were a lot of hops left=2 but there were a few hop lefts=1 and 0, including a 0 just before the message.

 

Here's an extract of the event viewer starting a little before and a couple of events after the message

 

Sun 01/20/2013 10:44:27 AM : [iNST-SRX    ] 02 50 20.43.49 1E.48.AD 27 2F 00           (00)
Sun 01/20/2013 10:44:27 AM : [std-Direct Ack] 20.43.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Sun 01/20/2013 10:44:28 AM : [iNST-ERX    ] 02 51 20 43 49 1E 48 AD 11 2F 00 00 01 0F 47 20 A2 05 1A 1D 09 FF 1F 07 4E 
Sun 01/20/2013 10:44:28 AM : [Ext-Direct  ] 20.43.49-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sun 01/20/2013 10:44:28 AM : [iNST-TX-I2CS] 02 62 20 43 49 1F 2F 00 00 00 0F 3F 01 00 00 00 00 00 00 00 00 82
Sun 01/20/2013 10:44:28 AM : [iNST-ACK    ] 02 62 20.43.49 1F 2F 00 00 00 0F 3F 01 00 00 00 00 00 00 00 00 82 06        (00)
Sun 01/20/2013 10:44:28 AM : [iNST-SRX    ] 02 50 20.43.49 1E.48.AD 2B 2F 00           (00)
Sun 01/20/2013 10:44:28 AM : [std-Direct Ack] 20.43.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 01/20/2013 10:44:29 AM : [iNST-ERX    ] 02 51 20 43 49 1E 48 AD 11 2F 00 00 01 0F 3F 20 A2 05 17 A3 7B FF 1F 03 65 
Sun 01/20/2013 10:44:29 AM : [Ext-Direct  ] 20.43.49-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sun 01/20/2013 10:44:29 AM : [iNST-TX-I2CS] 02 62 20 43 49 1F 2F 00 00 00 0F 37 01 00 00 00 00 00 00 00 00 8A
Sun 01/20/2013 10:44:29 AM : [iNST-ACK    ] 02 62 20.43.49 1F 2F 00 00 00 0F 37 01 00 00 00 00 00 00 00 00 8A 06        (00)
Sun 01/20/2013 10:44:31 AM : [iNST-ERX    ] 02 51 20 43 49 1E 48 AD 13 2F 00 00 01 0F 3F 20 A2 05 17 A3 7B FF 1F 03 65 
Sun 01/20/2013 10:44:31 AM : [Ext-Direct  ] 20.43.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Sun 01/20/2013 10:44:31 AM : [Ext MH      ] Unexpected Response (i.e. DB range): ignored
Sun 01/20/2013 10:44:40 AM : [iNST-TX-I2CS] 02 62 20 43 49 1F 2F 00 00 00 0F 37 01 00 00 00 00 00 00 00 00 8A
Sun 01/20/2013 10:44:40 AM : [iNST-ACK    ] 02 62 20.43.49 1F 2F 00 00 00 0F 37 01 00 00 00 00 00 00 00 00 8A 06        (00)

[LeeG]

Put a transmitter/receiver inside a solid metal box and it will likely not work at all. If the junction box has a non-metal face plate there is some RF coverage on the front side. The effectiveness of the Access Point behind the metal junction box in the other room is reduced.

 

Hops Left=0 by itself can be okay. Depends on the Max Hops count. The trace shows variation across a very small time frame where Max Hops=3 and Hops Left=2 and 1. A single example is not enough to comment beyond saying a longer trace should be checked for how consistent Hops Left count is when Max Hops=3.

 

Sun 01/20/2013 10:44:27 AM : [iNST-SRX ] 02 50 20.43.49 1E.48.AD 27 2F 00 (00)

Sun 01/20/2013 10:44:27 AM : [std-Direct Ack] 20.43.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

 

Sun 01/20/2013 10:44:28 AM : [iNST-SRX ] 02 50 20.43.49 1E.48.AD 2B 2F 00 (00)

Sun 01/20/2013 10:44:28 AM : [std-Direct Ack] 20.43.49-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

 

Some of the Hops Left=0 are fine. The Extended response (02 51) containing the actual link record was sent with Max Hops=1. Hops Left=0 is the best response for a Max Hops=1.

 

Sun 01/20/2013 10:44:28 AM : [iNST-ERX ] 02 51 20 43 49 1E 48 AD 11 2F 00 00 01 0F 47 20 A2 05 1A 1D 09 FF 1F 07 4E

Sun 01/20/2013 10:44:28 AM : [Ext-Direct ] 20.43.49-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

Sun 01/20/2013 10:44:29 AM : [iNST-ERX ] 02 51 20 43 49 1E 48 AD 11 2F 00 00 01 0F 3F 20 A2 05 17 A3 7B FF 1F 03 65

Sun 01/20/2013 10:44:29 AM : [Ext-Direct ] 20.43.49-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

 

The message

 

Sun 01/20/2013 10:44:31 AM : [Ext MH ] Unexpected Response (i.e. DB range): ignored

 

is the result of the PLM receiving KPL link record messages out of sequence. Actually I think it is an extra message from an earlier read request rather than an absolute out of sequence response.

 

The link record at 0F40-0F47 is read successfully.

The link record at 0F38-0F3F is read successfully.

The link record at 0F30-0F37 is requested.

An additional copy of the link record at 0F38-0F3F is received which is the DataBase (DB) range issue. This extended message has a Max Hops=3 Hops Left=0 which suggests the previous 02 51 Extended message with the first copy of 0F38-0F3F link record did not receive the PLM generated ACK so the KPL resent the 02 51 Extended message with the higher Max Hops count.

 

The combination of the extra 02 51 message along with the variation in Hops Left count over such a small time period suggests a less than great comm. with the KPL location. With metal box (hopefully with plastic covers) I would try putting an Access Point on the front side of the box to see if that improves the Hops Left count variation.