AnonymousInactiveOctober 21, 2008 at 3:00 amPost count: 30
I’ve got a ControlLinc (09.4C.DF) linked to a LampLinc dev module(11.11.11) and a macro set up on the EZServ so I’ll get an XML notification of the LampLinc’s state changes. Here’s the XML I received:
InsStdMsg 0X2 0X50 0X9 0X4C 0XDF 0X00 0X00 0X1 0XC7 0X13 0X00
The EZServ is at the latest firmware level 1.56. Notice the values of parameter6 – parameter8, I think they should all be 0X11 to represent the true address of the dev LampLinc, but that’s not what I’m getting. Parameters3-5 seem to correctly identify the ControlLinc sender.
Is this a bug?AnonymousInactiveOctober 21, 2008 at 10:23 amPost count: 1001
The Insteon message that you posted is a Group Broadcast OFF message. It is the first of two messages that are issued by an Insteon device functioning as a Controller. The “to” Insteon address of a Group Broadcast message is the Group number, Group 1 in this case. Parameter 9 is the Flag byte of an Insteon message, the 0xC7 value, the first 4 bits, 0xCx indicates a Group Broadcast type message. Parameter 10 is the Insteon command, 0x13 being an OFF command. This message is the first message I would expect from pressing the Off side of button one on the ControLinc. The Group Cleanup Direct message, the second Insteon message in the sequence, contains the responder device address in the “to” device address.
I would suggest reading the Insteon Details document on the insteon.net web site for details on the content of an Insteon message. That document has a good chart on Flag byte content which describes the type of each Insteon message. Once you know the type of Insteon message, then you will know what the other fields in an Insteon message will contain.AnonymousInactiveOctober 21, 2008 at 12:23 pmPost count: 30
OK thanks, I think I spent too much time looking at on and off commands and didn’t notice this was something else.
- You must be logged in to reply to this topic.