junkycosmos Posted June 24, 2014 Posted June 24, 2014 Need some help understanding why I am seeing multiple "[iNST-INFO ] Previous message ignored." for many many entries in my log. For example. I added a new hidden door sensor this evening. ISY994 is on beta 4.2.4 so I could set the 2845-222 Hidden Door Sensor (2B.03.55) to unchecked for repeating of sensor closed or open messages however please see these two event viewer messages Switched from sensor from Open to Closed: Mon 06/23/2014 08:28:14 PM : [iNST-SRX ] 02 50 2B.03.55 00.00.01 C7 13 01 LTOFFRR(01) Mon 06/23/2014 08:28:14 PM : [std-Group ] 2B.03.55-->Group=1, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:14 PM : [D2D EVENT ] Event [2B 3 55 1] [DOF] [1] uom=0 prec=-1 Mon 06/23/2014 08:28:14 PM : [ 2B 3 55 1] DOF 1 Mon 06/23/2014 08:28:14 PM : [D2D EVENT ] Event [2B 3 55 1] [sT] [0] uom=0 prec=-1 Mon 06/23/2014 08:28:14 PM : [ 2B 3 55 1] ST 0 Mon 06/23/2014 08:28:14 PM : [iNST-SRX ] 02 50 2B.03.55 00.00.01 C7 13 01 LTOFFRR(01) Mon 06/23/2014 08:28:14 PM : [std-Group ] 2B.03.55-->Group=1, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:14 PM : [iNST-DUP ] Previous message ignored. Mon 06/23/2014 08:28:14 PM : [iNST-SRX ] 02 50 2B.03.55 2C.08.0C 41 13 01 LTOFFRR(01) Mon 06/23/2014 08:28:14 PM : [std-Cleanup ] 2B.03.55-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Mon 06/23/2014 08:28:14 PM : [iNST-DUP ] Previous message ignored. Mon 06/23/2014 08:28:14 PM : [iNST-SRX ] 02 50 2B.03.55 2C.08.0C 42 13 01 LTOFFRR(01) Mon 06/23/2014 08:28:14 PM : [std-Cleanup ] 2B.03.55-->ISY/PLM Group=1, Max Hops=2, Hops Left=0 Mon 06/23/2014 08:28:14 PM : [iNST-DUP ] Previous message ignored. Mon 06/23/2014 08:28:15 PM : [iNST-SRX ] 02 50 2B.03.55 13.01.01 C3 06 00 (00) Mon 06/23/2014 08:28:15 PM : [std-Group ] 2B.03.55-->13.01.01, Max Hops=3, Hops Left=0 Mon 06/23/2014 08:28:15 PM : [iNST-INFO ] Previous message ignored. Mon 06/23/2014 08:28:15 PM : [iNST-SRX ] 02 50 2B.03.55 13.01.01 C7 06 00 (00) Mon 06/23/2014 08:28:15 PM : [std-Group ] 2B.03.55-->13.01.01, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:15 PM : [iNST-INFO ] Previous message ignored. and Switched from sensor from Closed to Open: Mon 06/23/2014 08:28:25 PM : [iNST-SRX ] 02 50 2B.03.55 00.00.01 C7 11 01 LTONRR (01) Mon 06/23/2014 08:28:25 PM : [std-Group ] 2B.03.55-->Group=1, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:25 PM : [D2D EVENT ] Event [2B 3 55 1] [DON] [1] uom=0 prec=-1 Mon 06/23/2014 08:28:25 PM : [ 2B 3 55 1] DON 1 Mon 06/23/2014 08:28:25 PM : [D2D EVENT ] Event [2B 3 55 1] [sT] [255] uom=0 prec=-1 Mon 06/23/2014 08:28:25 PM : [ 2B 3 55 1] ST 255 Mon 06/23/2014 08:28:25 PM : [iNST-SRX ] 02 50 2B.03.55 00.00.01 C7 11 01 LTONRR (01) Mon 06/23/2014 08:28:25 PM : [std-Group ] 2B.03.55-->Group=1, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:25 PM : [iNST-DUP ] Previous message ignored. Mon 06/23/2014 08:28:25 PM : [iNST-SRX ] 02 50 2B.03.55 2C.08.0C 41 11 01 LTONRR (01) Mon 06/23/2014 08:28:25 PM : [std-Cleanup ] 2B.03.55-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Mon 06/23/2014 08:28:25 PM : [iNST-DUP ] Previous message ignored. Mon 06/23/2014 08:28:25 PM : [iNST-SRX ] 02 50 2B.03.55 11.01.01 C7 06 00 (00) Mon 06/23/2014 08:28:25 PM : [std-Group ] 2B.03.55-->11.01.01, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:25 PM : [iNST-INFO ] Previous message ignored. Mon 06/23/2014 08:28:26 PM : [iNST-SRX ] 02 50 2B.03.55 11.01.01 C7 06 00 (00) Mon 06/23/2014 08:28:26 PM : [std-Group ] 2B.03.55-->11.01.01, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:26 PM : [iNST-INFO ] Previous message ignored. This looks like a lot of chatty traffic for simple open/closed. Given the our overall setup is rather large I have a lot of these scrolling by in the logs. Would like info on what they mean and what actions to consider please. thanks Junkycosmos
LeeG Posted June 24, 2014 Posted June 24, 2014 All the battery powered RF only devices send multiple copies of messages. Here is an example from a RemoteLinc2 button press. The messages with the "message ignored" tag are not used by the ISY and are ignored. Mon 06/23/2014 11:20:05 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 11 00 LTONRR (00) Mon 06/23/2014 11:20:05 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Mon 06/23/2014 11:20:05 PM : [D2D EVENT ] Event [1C 27 E3 2] [DON] [0] uom=0 prec=-1 Mon 06/23/2014 11:20:05 PM : [ 1C 27 E3 2] DON 0 Mon 06/23/2014 11:20:05 PM : [iNST-SRX ] 02 50 1C.27.E3 00.00.02 CB 11 00 LTONRR (00) Mon 06/23/2014 11:20:05 PM : [std-Group ] 1C.27.E3-->Group=2, Max Hops=3, Hops Left=2 Mon 06/23/2014 11:20:05 PM : [iNST-DUP ] Previous message ignored. Mon 06/23/2014 11:20:05 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 41 11 02 LTONRR (02) Mon 06/23/2014 11:20:05 PM : [std-Cleanup ] 1C.27.E3-->ISY/PLM Group=2, Max Hops=1, Hops Left=0 Mon 06/23/2014 11:20:05 PM : [iNST-DUP ] Previous message ignored. In addition to the normal sending of the same message, the RF network in the posted environment shows marginal communication with the door sensor. This message took 3 hops (Hops Left=0) to get to the PLM. Mon 06/23/2014 08:28:15 PM : [iNST-SRX ] 02 50 2B.03.55 13.01.01 C3 06 00 (00) Mon 06/23/2014 08:28:15 PM : [std-Group ] 2B.03.55-->13.01.01, Max Hops=3, Hops Left=0 Mon 06/23/2014 08:28:15 PM : [iNST-INFO ] Previous message ignored. Likely the ACK from PLM back to the door sensor was not received by the sensor as the same message was repeated again. This time it made it to the PLM with 2 hops which could simply indicate the Dual Band device that picked up the message is on the opposite 120v leg which takes an additional hop. Mon 06/23/2014 08:28:15 PM : [iNST-SRX ] 02 50 2B.03.55 13.01.01 C7 06 00 (00) Mon 06/23/2014 08:28:15 PM : [std-Group ] 2B.03.55-->13.01.01, Max Hops=3, Hops Left=1 Mon 06/23/2014 08:28:15 PM : [iNST-INFO ] Previous message ignored. Some of the duplicates are expected result from a battery device. The others may be eliminated with an improved RF network.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.