jtara92101 Posted October 1, 2016 Share Posted October 1, 2016 How do we fully interpret Query Insteon Engine results? I know if I watch the Event Viewer, I will sometimes see a message about a device not fully-supporting I2, so reverting to I1. But if I DON'T get that, how do I interpret results? (And even if so, as that message doesn't actually say what version the device reported.) Wouldn't it be more useful to report the engine version, rather than just saying "calibrating engine version". Leave me asking "...and?" What does this one tell me? (Tree Sculpture 2472D Dual Band OutletLinc Dimmer v.44) Sat 10/01/2016 12:17:04 PM : [All ] Writing 1 bytes to devices Sat 10/01/2016 12:17:04 PM : [INST-TX-I1 ] 02 62 41 FB 6C 0F 0D 00 Sat 10/01/2016 12:17:04 PM : [INST-ACK ] 02 62 41.FB.6C 0F 0D 00 06 (00) Sat 10/01/2016 12:17:04 PM : [INST-SRX ] 02 50 41.FB.6C 22.FE.EF 2B 0D 02 (02) Sat 10/01/2016 12:17:04 PM : [Std-Direct Ack] 41.FB.6C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 12:17:04 PM : [41 FB 6C 0 ] Calibrating engine version This one? (Spare B2457D2 Lamplinc BiPhy v.3B) Sat 10/01/2016 12:18:09 PM : [All ] Writing 1 bytes to devices Sat 10/01/2016 12:18:09 PM : [INST-TX-I1 ] 02 62 18 6E 61 0F 0D 00 Sat 10/01/2016 12:18:09 PM : [INST-ACK ] 02 62 18.6E.61 0F 0D 00 06 (00) Sat 10/01/2016 12:18:09 PM : [INST-SRX ] 02 50 18.6E.61 22.FE.EF 2B 0D 01 (01) Sat 10/01/2016 12:18:09 PM : [Std-Direct Ack] 18.6E.61-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 12:18:09 PM : [18 6E 61 0 ] Calibrating engine version Sat 10/01/2016 12:18:09 PM : [18 6E 61 0 ] May not fully support i2, reverting to i1 This one? (Office 2334-2 KeypadLinc Dimmer 5 Buttons v.45) Sat 10/01/2016 12:19:05 PM : [All ] Writing 1 bytes to devices Sat 10/01/2016 12:19:05 PM : [INST-TX-I1 ] 02 62 3D 90 2B 0F 0D 00 Sat 10/01/2016 12:19:05 PM : [INST-ACK ] 02 62 3D.90.2B 0F 0D 00 06 (00) Sat 10/01/2016 12:19:06 PM : [INST-SRX ] 02 50 3D.90.2B 22.FE.EF 2B 0D 02 (02) Sat 10/01/2016 12:19:06 PM : [Std-Direct Ack] 3D.90.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 12:19:06 PM : [3D 90 2B 0 ] Calibrating engine version This? (Entrance 2334-2 KeypadLinc Dimmer 5 Buttons v.45) Sat 10/01/2016 12:22:24 PM : [All ] Writing 1 bytes to devices Sat 10/01/2016 12:22:24 PM : [INST-TX-I1 ] 02 62 3D 8C A6 0F 0D 00 Sat 10/01/2016 12:22:24 PM : [INST-ACK ] 02 62 3D.8C.A6 0F 0D 00 06 (00) Sat 10/01/2016 12:22:25 PM : [INST-SRX ] 02 50 3D.8C.A6 22.FE.EF 2B 0D 02 (02) Sat 10/01/2016 12:22:25 PM : [Std-Direct Ack] 3D.8C.A6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 12:22:25 PM : [3D 8C A6 0 ] Calibrating engine version This one looks the same as the office one, but I have had some indications in the past where I think the event viewer was telling me that communication to the entrance keypad was falling-back to I1. I've removed all my troublesome older dual-band KPLs, as simply installing one in the wall goofs up everything big-time. Later I will put one on a zip cord and see what result it yields. That is IF this is really telling me anything useful. Link to comment Share on other sites More sharing options...
Brian H Posted October 1, 2016 Share Posted October 1, 2016 The original Insteon Modules where I1 only so I1 was always used. Some of the original I2 protocol Insteon Modules didn't support the total I2 protocol. So the Administrative Console would fall back to the original I1 protocol it also supported. Poor communications should not cause an I2 to drop back to I1. The present I2CS {I2 with Check Sum} don't support the old I1 protocol. For things like Link Database changes.So they should never fall back to I1. It may look like an old I1 or I2 that fell back to I1 protocol is having communications issues. I1 Standard Insteon messaging is MUCH slower than the module using I2 or I2CS Extended Insteon Messaging. Due to the amount of data each message can convey. Link to comment Share on other sites More sharing options...
Brian H Posted October 1, 2016 Share Posted October 1, 2016 Here is a test of an I1, I2 that fell back to I1 and two I2CS modules. I believe the number at the end of the [iNST-SRX] line is the protocol (00) I1, (01) I2 or (02) I2CS 2456S3 I1 ApplianceLincSat 10/01/2016 07:26:40 PM : [All ] Writing 1 bytes to devicesSat 10/01/2016 07:26:40 PM : [iNST-TX-I1 ] 02 62 00 FC 43 0F 0D 00Sat 10/01/2016 07:26:40 PM : [iNST-ACK ] 02 62 00.FC.43 0F 0D 00 06 (00)Sat 10/01/2016 07:26:40 PM : [iNST-SRX ] 02 50 00.FC.43 34.E9.19 2F 0D 00 (00)Sat 10/01/2016 07:26:40 PM : [std-Direct Ack] 00.FC.43-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Sat 10/01/2016 07:26:40 PM : [0 FC 43 0 ] Calibrating engine version2456S3 I2 ApplianceLinc.Sat 10/01/2016 07:27:06 PM : [All ] Writing 1 bytes to devicesSat 10/01/2016 07:27:06 PM : [iNST-TX-I1 ] 02 62 0D 57 DB 0F 0D 00Sat 10/01/2016 07:27:06 PM : [iNST-ACK ] 02 62 0D.57.DB 0F 0D 00 06 (00)Sat 10/01/2016 07:27:07 PM : [iNST-SRX ] 02 50 0D.57.DB 34.E9.19 2F 0D 01 (01)Sat 10/01/2016 07:27:07 PM : [std-Direct Ack] 0D.57.DB-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Sat 10/01/2016 07:27:07 PM : [D 57 DB 0 ] Calibrating engine versionSat 10/01/2016 07:27:07 PM : [D 57 DB 0 ] May not fully support i2, reverting to i12456S3 I2CS ApplianceLinc.Sat 10/01/2016 07:35:46 PM : [All ] Writing 1 bytes to devicesSat 10/01/2016 07:35:46 PM : [iNST-TX-I1 ] 02 62 22 B2 40 0F 0D 00Sat 10/01/2016 07:35:46 PM : [iNST-ACK ] 02 62 22.B2.40 0F 0D 00 06 (00)Sat 10/01/2016 07:35:46 PM : [iNST-SRX ] 02 50 22.B2.40 34.E9.19 2F 0D 02 (02)Sat 10/01/2016 07:35:46 PM : [std-Direct Ack] 22.B2.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Sat 10/01/2016 07:35:46 PM : [22 B2 40 0 ] Calibrating engine versionSat 10/01/2016 07:35:46 PM : [iNST-TX-I2CS] 02 62 22 B2 40 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Sat 10/01/2016 07:35:46 PM : [iNST-ACK ] 02 62 22.B2.40 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Sat 10/01/2016 07:35:47 PM : [iNST-SRX ] 02 50 22.B2.40 34.E9.19 23 2F 00 (00)Sat 10/01/2016 07:35:47 PM : [std-Direct Ack] 22.B2.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=0Sat 10/01/2016 07:35:47 PM : [iNST-ERX ] 02 51 22 B2 40 34 E9 19 15 2F 00 01 01 0F FF 00 A2 00 34 E9 19 FF 1F 00 CBSat 10/01/2016 07:35:47 PM : [Ext-Direct ] 22.B2.40-->ISY/PLM Group=0, Max Hops=1, Hops Left=1New I2CS 2635-222 On/Off ModuleSat 10/01/2016 07:27:32 PM : [All ] Writing 1 bytes to devicesSat 10/01/2016 07:27:32 PM : [iNST-TX-I1 ] 02 62 2D 04 5C 0F 0D 00Sat 10/01/2016 07:27:32 PM : [iNST-ACK ] 02 62 2D.04.5C 0F 0D 00 06 (00)Sat 10/01/2016 07:27:32 PM : [iNST-SRX ] 02 50 2D.04.5C 34.E9.19 2F 0D 02 (02)Sat 10/01/2016 07:27:32 PM : [std-Direct Ack] 2D.04.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Sat 10/01/2016 07:27:32 PM : [2D 4 5C 0 ] Calibrating engine version Link to comment Share on other sites More sharing options...
jtara92101 Posted October 2, 2016 Author Share Posted October 2, 2016 I believe the number at the end of the [iNST-SRX] line is the protocol (00) I1, (01) I2 or (02) I2CS Thank you. Exactly what I was looking for! But what were you doing when you captured these events? You have some additional messages at the end on the I2CS ApplianceLinc. Maybe this was just some other network activity? I used Diagnostics/Query Insteon Engine. Were you perhaps doing just plain Query? I think that is where I have seen results that suggest signal being repeated through a non-I2CS device. I will try that now... This is from the Office KPL, nearest the PLM: Sat 10/01/2016 05:33:07 PM : [INST-TX-I1 ] 02 62 3D 90 2B 0F 19 00 Sat 10/01/2016 05:33:07 PM : [INST-ACK ] 02 62 3D.90.2B 0F 19 00 06 LTSREQ (LIGHT) Sat 10/01/2016 05:33:07 PM : [INST-SRX ] 02 50 3D.90.2B 22.FE.EF 2B 00 00 (00) Sat 10/01/2016 05:33:07 PM : [Std-Direct Ack] 3D.90.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 05:33:07 PM : [D2D EVENT ] Event [3D 90 2B 1] [ST] [0] uom=0 prec=-1 Sat 10/01/2016 05:33:07 PM : [ 3D 90 2B 1] ST 0 Sat 10/01/2016 05:33:07 PM : [D2D EVENT ] Event [3D 90 2B 1] [OL] [255] uom=0 prec=-1 Sat 10/01/2016 05:33:07 PM : [ 3D 90 2B 1] OL 255 Sat 10/01/2016 05:33:07 PM : [D2D EVENT ] Event [3D 90 2B 1] [RR] [27] uom=0 prec=-1 Sat 10/01/2016 05:33:07 PM : [ 3D 90 2B 1] RR 27 Sat 10/01/2016 05:33:07 PM : [INST-TX-I2CS] 02 62 3D 90 2B 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Sat 10/01/2016 05:33:08 PM : [INST-ACK ] 02 62 3D.90.2B 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Sat 10/01/2016 05:33:09 PM : [INST-SRX ] 02 50 3D.90.2B 22.FE.EF 2B 2E 00 (00) Sat 10/01/2016 05:33:09 PM : [Std-Direct Ack] 3D.90.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 05:33:09 PM : [INST-ERX ] 02 51 3D 90 2B 22 FE EF 11 2E 00 01 01 00 00 20 20 1B FF 05 00 C0 00 00 00 Sat 10/01/2016 05:33:09 PM : [Ext-Direct ] 3D.90.2B-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 And this is from the entrance KPL: Sat 10/01/2016 05:35:14 PM : [INST-TX-I1 ] 02 62 3D 8C A6 0F 19 00 Sat 10/01/2016 05:35:14 PM : [INST-ACK ] 02 62 3D.8C.A6 0F 19 00 06 LTSREQ (LIGHT) Sat 10/01/2016 05:35:15 PM : [INST-SRX ] 02 50 3D.8C.A6 22.FE.EF 2B 00 00 (00) Sat 10/01/2016 05:35:15 PM : [Std-Direct Ack] 3D.8C.A6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 05:35:15 PM : [D2D EVENT ] Event [3D 8C A6 1] [ST] [0] uom=0 prec=-1 Sat 10/01/2016 05:35:15 PM : [ 3D 8C A6 1] ST 0 Sat 10/01/2016 05:35:15 PM : [D2D EVENT ] Event [3D 8C A6 1] [OL] [255] uom=0 prec=-1 Sat 10/01/2016 05:35:15 PM : [ 3D 8C A6 1] OL 255 Sat 10/01/2016 05:35:15 PM : [D2D EVENT ] Event [3D 8C A6 1] [RR] [31] uom=0 prec=-1 Sat 10/01/2016 05:35:15 PM : [ 3D 8C A6 1] RR 31 Sat 10/01/2016 05:35:15 PM : [INST-TX-I2CS] 02 62 3D 8C A6 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Sat 10/01/2016 05:35:15 PM : [INST-ACK ] 02 62 3D.8C.A6 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Sat 10/01/2016 05:35:15 PM : [INST-SRX ] 02 50 3D.8C.A6 22.FE.EF 2B 2E 00 (00) Sat 10/01/2016 05:35:15 PM : [Std-Direct Ack] 3D.8C.A6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 10/01/2016 05:35:16 PM : [INST-ERX ] 02 51 3D 8C A6 22 FE EF 11 2E 00 01 01 00 00 20 20 1F FF 05 00 C0 00 00 00 Sat 10/01/2016 05:35:16 PM : [Ext-Direct ] 3D.8C.A6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 I guess what I am looking for here is that the PLM sent INST-TX-I2CS and there was an INST-ERX response, right? So, seems PLM is talking to entrance KPL using I2CS now. Pretty sure it was not before, but I have added more I2CS devices in the mean time. Link to comment Share on other sites More sharing options...
jtara92101 Posted October 2, 2016 Author Share Posted October 2, 2016 Does anyone know exactly what "may not fully support" means? Anyone know what wouldn't work if I2 were used instead of I1? Link Management/Advanced Options gives the option for automatic, device reported, or I1 only Insteon messaging. The default is Automatic. Does it apply when you change it, or only on the next configuration of Insteon messaging? (That is, to have to take effect, you'd have to do Query Insteon Engine.) Can you configure specific devices by changing the setting, Query insteon Engine for that device, then setting the default back? Link to comment Share on other sites More sharing options...
jtara92101 Posted October 2, 2016 Author Share Posted October 2, 2016 Ah, I see that if ISY thinks the device "does not fully support I2" it will revert to I1 regardless of the Advanced setting. I'll leave it on Automatic! Link to comment Share on other sites More sharing options...
Brian H Posted October 2, 2016 Share Posted October 2, 2016 I was doing a Query Insteon Engine in diagnostics. I don't know what the extra data is. This is a I2CS 2635-222 On/Off Module. No extra data. Sat 10/01/2016 08:51:34 PM : [All ] Writing 1 bytes to devicesSat 10/01/2016 08:51:34 PM : [iNST-TX-I1 ] 02 62 2D 04 5C 0F 0D 00Sat 10/01/2016 08:51:34 PM : [iNST-ACK ] 02 62 2D.04.5C 0F 0D 00 06 (00)Sat 10/01/2016 08:51:35 PM : [iNST-SRX ] 02 50 2D.04.5C 34.E9.19 2F 0D 02 (02)Sat 10/01/2016 08:51:35 PM : [std-Direct Ack] 2D.04.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Sat 10/01/2016 08:51:35 PM : [2D 4 5C 0 ] Calibrating engine version I would keep it on Automatic. A INST-SRX is a Standard Insteon message received. A INST-ERX is an Extended Insteon message received. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.