Timers

[Anonymous November 27, 2008 at 7:43 pm Post count: 37]

#42462

NOW, for the 2nd experiment which will show the operation of this KPL button 1 with macro execution. I’ll clear out the Control window that is tracing my activity then will press the Button 1 on the OFF KPL. The light should come on for 15 seconds and then go off again….

OK, worked exactly like it was supposed to and here is its trace:

InsStdMsg
0X2
0X50
0X5
0X16
0X88
0X6
0X4C
0X94
0X2B
0X13
0X00

SndIns
0X2
0X62
0X5
0X16
0X88
0XF
0X13
0X00
0X6

InsStdMsg
0X2
0X50
0X5
0X16
0X88
0X6
0X4C
0X94
0X41
0X11
0X1

InsStdMsg
0X2
0X50
0X5
0X16
0X88
0X00
0X00
0X1
0XCB
0X11
0X00

==================================================
For those who are reading this, the first command in the sequence is the bottom of the list and the last one is at the top. So, time is flowing from bottom to top.

What’s going on here in sequence? I’m beginning to understand but am still just at a guessing stage.

Lee

[Anonymous November 27, 2008 at 8:09 pm Post count: 1001]

#42463

From the bottom up …
SndIns – Direct command to turn device 05:16:88 On at Full Bright
Parms3-5 to Insteon device address 05:16:88
Parm 6 – Flag byte – 0x – first 4 bits indicate Direct message
Parm 7 – cmd1 value – 11 – On command
Parm 8 – cmd2 value – FF – Full Bright
InsStdMsg – ACK response from Direct On command
Parms3-5 from Insteon device address 05:16:88
Parms6-8 to Insteon device address 06:4C:94
Parm 9 – Flag byte – 2x – first 4 bits indicate ACK of Direct message
Parm 10 – cmd1 value – 11 – On command
Parm 11 – cmd2 value – FF – Bright level

Next SndIns is querying the device status and the last InsStdMsg is the ACK response to the query.

You should note that NOT ALL KeypadLinc devices respond to Direct commands the way this one is. It is also necessary to create a Scene with EZSrve as the Controller and the KPL as the responder to turn On/Off other than button 1 even on this KPL.

On the SmartLabs web site (insteon.net ?) they have a public document Insteon Details which describes what some of the Insteon messages look like. They do not make public what all the commands look like. You can purchase a developer subscription to gain access to what they consider confidential information.

[Anonymous November 27, 2008 at 8:37 pm Post count: 1001]

#42464

From the bottom up …

InsStdMsg – Group Broadcast – 1st message from pressing KPL button 1
Parms3-5 from Insteon device address 05:16:88
Parms6-8 to Insteon device address – on a Group Broadcast parm 8 is Group number
Parm 9 – Flag byte – Cx – first 4 bits indicate Group Broadcast message
Parm 10 – cmd1 value – 11 – On command
Parm 11 – cmd2 value – 00 – no meaning – sometimes Group number – depends on KPL version

InsStdMsg – Group Cleanup Direct – 2nd message from pressing KPL button 1
Parms3-5 from Insteon device address 05:16:88
Parms6-8 to Insteon device address – 06:4C:94
Parm 9 – Flag byte – 4x – first 4 bits indicate Group Cleanup Direct message
Parm 10 – cmd1 value – 11 – On command
Parm 11 – cmd2 value – 01 – Group number

SndIns – Direct Off message I presume from Macro being triggered
Parms3-5 to Insteon device address 05:16:88
Parm 6 – Flag byte – 0x – first 4 bits indicates Direct message
Parm 7 – cmd1 value – 13 – Off command
Parm 8 – cmd2 value – 00 – no meaning on Off command

Last message is ACK of Direct message which has been interpreted in previous post.

For the benefit of others who read this, NOT ALL KPLs will respond to a Direct command the way this KPL is. The normal way to control a KPL button, even button 1, is with a Group command sequence.

EDIT: corrected description of parm 11 of 2nd inbound message (from bottom up). Parm 11 (01) is the Group number representing KPL button 1 in this case.

[Author]

Posts