Jump to content

Event Viewer "Magic Decoder Ring" ?


alsorrell

Recommended Posts

Posted

I've been trying to troubleshoot an intermittent issue with RemoteLincs and a garage door system (like some others), and I was looking at the Tools > Diagnostics > Event Viewer log and there appears to be a ton of info there. The ISG994i Guide section dealing with Event Viewer is pretty pathetic in terms of explanations. Is there anything to help decode what the various entries mean?

 

Thanks,

Al

 

e.g.

 

2E.9E.B5-1 is my Left Garage button from my RemoteLinc (8-Button No Toggle)

31.6E.A6-2 is the Garage Left IoLinc Relay

 

 Tue 02/24/2015 05:36:31 PM : [iNST-SRX    ] 02 50 2E.9E.B5 00.00.01 CB 13 00    LTOFFRR(00)

 
Tue 02/24/2015 05:36:31 PM : [std-Group   ] 2E.9E.B5-->Group=1, Max Hops=3, Hops Left=2
 
Tue 02/24/2015 05:36:31 PM : [D2D EVENT   ] Event [2E 9E B5 1] [DOF] [0] uom=0 prec=-1
 
Tue 02/24/2015 05:36:31 PM : [  2E 9E B5 1]      DOF   0
 
Tue 02/24/2015 05:36:31 PM : [iNST-SRX    ] 02 50 2E.9E.B5 00.00.01 C7 13 00    LTOFFRR(00)
 
Tue 02/24/2015 05:36:31 PM : [std-Group   ] 2E.9E.B5-->Group=1, Max Hops=3, Hops Left=1
 
Tue 02/24/2015 05:36:31 PM : [iNST-DUP    ] Previous message ignored.
 
Tue 02/24/2015 05:36:31 PM : [iNST-SRX    ] 02 50 31.6E.A6 00.00.01 CB 11 00    LTONRR (00)
 
Tue 02/24/2015 05:36:31 PM : [std-Group   ] 31.6E.A6-->Group=1, Max Hops=3, Hops Left=2
 
Tue 02/24/2015 05:36:31 PM : [D2D EVENT   ] Event [31 6E A6 1] [DON] [0] uom=0 prec=-1
 
Tue 02/24/2015 05:36:31 PM : [  31 6E A6 1]      DON   0
 
Tue 02/24/2015 05:36:31 PM : [D2D EVENT   ] Event [33 13 DC 3] [sT] [255] uom=0 prec=-1
 
Tue 02/24/2015 05:36:31 PM : [  33 13 DC 3]       ST 255
 
Tue 02/24/2015 05:36:31 PM : [D2D EVENT   ] Event [31 6E A6 1] [sT] [255] uom=0 prec=-1
 
Tue 02/24/2015 05:36:31 PM : [  31 6E A6 1]       ST 255
 
Tue 02/24/2015 05:36:31 PM : [D2D-CMP 0009] STS [31 6E A6 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
 
Tue 02/24/2015 05:36:31 PM : [D2D EVENT   ] Event [31 6E A6 2] [sT] [255] uom=0 prec=-1
 
Tue 02/24/2015 05:36:31 PM : [  31 6E A6 2]       ST 255
 
Tue 02/24/2015 05:36:32 PM : [iNST-SRX    ] 02 50 31.6E.A6 30.DC.96 41 11 01    LTONRR (01)
 
Tue 02/24/2015 05:36:32 PM : [std-Cleanup ] 31.6E.A6-->ISY/PLM Group=1, Max Hops=1, Hops Left=0
 
Tue 02/24/2015 05:36:32 PM : [iNST-DUP    ] Previous message ignored.
 
Tue 02/24/2015 05:36:32 PM : [iNST-SRX    ] 02 50 2E.9E.B5 30.DC.96 4B 13 01    LTOFFRR(01)
 
Tue 02/24/2015 05:36:32 PM : [std-Cleanup ] 2E.9E.B5-->ISY/PLM Group=1, Max Hops=3, Hops Left=2
 
Tue 02/24/2015 05:36:32 PM : [D2D EVENT   ] Event [2E 9E B5 1] [DOF] [0] uom=0 prec=-1
Posted

No decoder ring that I remember.  One can often figure out some things by inference, and I understand that smarthome publishes a developer guide, but that disclosure of that content may obligate the discloser to shoot you. 

 

Personally, I think I recognize insteon device addresses, in that they appear to be six-character hex addresses.  I have also come to learn that "hops left=0" to be generally bad and "hops left=2" to be, generally, good.

 

You might try a "scene" test, using any scene that is giving you trouble.  As a whole, you are probably going to have to fall back on they typical troubleshooting methods to identify any problem-causing devices.

Posted

Normally Hops Left=0 is bad but in this case it is on a message that has Max Hops=1 so no comm problem indicated.

 

At insteon.com there is an insteondetails.pdf doc that covers some of the Insteon messages.

 

Also SmartLabs has released what was confidential information (no longer confidential) covering Insteon internals.

 

insteon.com/developer/#devdocs

Posted (edited)

"I have always wondered what the Hops Left and Max Hops numbers meant."

 

Max Hops indicates the number of devices that are allow to repeat message at full strength. The larger Max Hops the longer it takes a message to arrive at its destination.

 

Hops Left indicates how many devices (Hops) had to repeat the message.

 

An Insteon Controller device normally starts out with Max Hops=1 for best Insteon network speed. If the Responder does not ACK, the Controller bumps the Max Hops count and tries again.

 

There is an insteondetails.pdf doc on insteon.com that covers this in detail. Shows Insteon network speed possible at each Max Hops count.

Edited by LeeG
Guest
This topic is now closed to further replies.

×
×
  • Create New...