HOME › Forums › Gateways › EZSrve › 2.0: how to monitor device events?

Viewing 15 posts - 1 through 15 (of 24 total)
1 2 Next
  • Author
    Posts
  • Anonymous
    Inactive
    July 2, 2009 at 4:42 pm
    Post count: 29
    #40183

    I’m trying to configure EZSrve 2.0 to generate xml events when a KPL button is pressed. I was able to get 1.x to do this, but haven’t been able to get it to work with 2.0.

    I used the EZSrve web UI to create a scene, in which the KPL is the controller, and EZSrve is the responder. I wasn’t sure what controller unit to use, so I picked a number that wasn’t being used in any of the KPL’s other links, “20”. Also, I wasn’t sure what values to use for LD1/2/3, so I used 100%, 0.1, and 00.

    EZSrve successfully created the scene. Looking at the KPL’s links (via houselinc), I see that a link was created, with the ID equal to the EZSrve, the Group equal to 20, and data1/2/3 equal to 0xFF, 0xFF, 0xFF. Also, I should mention that I am able to use xml SendInsteon commands to turn the KPL’s LEDs on and off, and to obtain the KPL’s LED status. So, EZSrve and the KPL are communicating fine.

    Next, I used a simple program to monitor all output generated by the xml interface. But, when I press buttons on the KPL, I see no xml messages emitted by the EZSrve.

    Any idea what I’m doing wrong?

    Thanks!

    Anonymous
    Inactive
    July 2, 2009 at 7:57 pm
    Post count: 1001
    #42919

    When the KPL is the controller you need to use the Group numbers (unit numbers) the KPL hardware uses. A KPL in 8 button mode uses Group numbers 1-8 for buttons Main (A)-H. Create a Scene with the KPL as the controller specifying the Group number of the button you want to monitor as the Unit number with EZSrve as the responder. When you press button C, for example, the KPL hardware searches through its link database looking for a “controller of” link record that specifies Group 3. If found it sends a Group command sequence to the device address in the link record. Since no “controller of” link records exist for any of the Group numbers the KPL uses, which also point to the EZSrve as the responder, no Group messages are sent from the KPL to EZSrve. The “controller of” link record specifying Group (Unit) 20 does not match any of the Group numbers associated with the KPL buttons.

    When you created Scenes in the other direction (EZsrve as controller, KPL as responder) the Unit numbers were dictated by the EZSrve because it is the controller. In this case, the KPL dictates the Unit numbers (Group numbers) because it is the controller.

    Anonymous
    Inactive
    July 2, 2009 at 8:51 pm
    Post count: 29
    #42920

    Thanks!

    Are there any particular values I should use for LD1/2/3?

    Also, just curious…

    If the KPL has links for multiple responders in the same group, I assume it sends msgs to all responders. (My KPL already has group links for all of its buttons linking to the Houselinc PLM.)

    nd, when EZSrve gets a message from a device, does it output an xml message to every connected TCP client?

    Anonymous
    Inactive
    July 2, 2009 at 9:12 pm
    Post count: 1001
    #42921

    I don’t think it matters regarding the LD1/2/3 values when the EZSrve is the responder. Convention responder values would be FF 1F 00 which is 100% bright, fastest ramp rate, and output unit 0 but I think 00 00 00 will do just as well for the EZSrve. All Insteon controllers support linking multiple responders to a specific group number (button number in the case of a KPL) and each responder will get a Group Cleanup Direct message. I don’t know the answer to the question about multiple xml clients. If you have multiple xml clients, post back the results in your environment for the benefit of others who may have the same question.

    Anonymous
    Inactive
    July 8, 2009 at 3:44 pm
    Post count: 29
    #42922

    Well, I think I have it configured correctly now, but I still see no xml output by the EZSrve when I press a KPL button.

    I set up an EZSrve scene with a KPL as the controller, using group 3, which should correspond to button C. The EZSrve is the sole responder. Examining the links in the KPL (using houselinc), I see what appears to be the correct link, with he EZSrve as the target ID and the group equal to 0x03.

    I have a simply monitoring program that connects to the EZSrve xml interface and continuously reads the EZSrve port and writes whatever it finds. This is the same program I am using to monitor and control devices, so I’m pretty sure it’s working correctly.

    But, when I press the KPL button, I get no xml from the EZSrve.

    I also monitored the Insteon traffic using houselinc, and see that the KPL is sending a message with the destination equal to 00.00.03 when I press the button. So, it looks like the KPL is sending the correct message.

    Any idea why the EZSrve is not outputting any xml?

    Anonymous
    Inactive
    July 8, 2009 at 4:50 pm
    Post count: 1001
    #42923

    Mark, you should be seeing two messages from the KPL. The one you mentioned with a “to” address of 00 00 03 is the Group Broadcast message for Group 3 (button C) from the KPL which is not directed to any specific device. You should be seeing a second message with a “to” address of the EZSrve which as I type this may not be traced by HL2 because that message (Group Broadcast Direct) is not addressed to the HL2 PLM. I’ll set up a test tonight with one of my KPLs and see if I get an xml message from a button 3 press. I’ll also test an Action trigger from the same KPL button. Maybe the button press is being received, just not generating an xml message.

    Anonymous
    Inactive
    July 8, 2009 at 5:05 pm
    Post count: 29
    #42924

    Thanks for replying.

    Yes, I’m only seeing the group message and and a direct message to HL2. I’m guessing you’re right that HL2 doesn’t log the direct msgs to other devices.

    I’ll also try setting up an action trigger.

    Anonymous
    Inactive
    July 8, 2009 at 5:17 pm
    Post count: 29
    #42925

    When defining the action condition, what attribute value should I specify for a KPL button C turn-on event? Is it 1103?

    (I’m a little confused because in the HL2 logs, I see a 11/00 sent to the group, but then a 11/03 sent to the HL2.)

    Anonymous
    Inactive
    July 8, 2009 at 5:52 pm
    Post count: 1001
    #42926

    The value of 1103 is for Group 3 (button C) ON. The Group number is in the “to” field of the Group Broadcast message and the cmd2 field of the Group Broadcast Direct message.

    Anonymous
    Inactive
    July 8, 2009 at 6:41 pm
    Post count: 1001
    #42927

    The KPL button C press On and Off does trigger an action and does generate a ClusterResponse on my EZSrve. I used the SHN Utility Control tab to view the xml received. The DLAMPLINC activity is generated by the Effect of the Actions triggered by the ON and OFF messages.

    Anonymous
    Inactive
    July 8, 2009 at 8:07 pm
    Post count: 29
    #42928

    No worky here. No traffic visible in utility suite or my program. I tried setting up an action, and that doesn’t work, either.

    I’m stumped. The link looks correct in the KPL. Since EZSrve wrote the link, I can only assume that it also configured the PLM correctly. I know that EZSrve can communicate with the device, because I can use my own xml program to monitor and control the LEDs.

    The only thing I can think of is that the link’s ld1/2/3 values are different from yours.

    Here’s the KPL link as reported by HL2. (05.E8.EE is the EZSrve).

    05.E8.EE 0x03 0xFF 0xFF 0xFF

    Here’s the KPL link as displayed by EZSrve:

    Controller of EZServer on Unit 03 – Data:00-00-00.

    Here’s the corresponding link in the EZSrve PLM:

    Responder to kitchen keypad on Unit 03 – Data:FF-1F-00

    Here’s the scene definition:

    Controller: kitchen keypad 03
    Responder: EZServer 100% 0.1 second 00

    FWIW, the group 3 link in the KPL to HL2 is:

    0D.D9.54 0x03 0xFF 0x1F 0x03

    Anonymous
    Inactive
    July 8, 2009 at 8:59 pm
    Post count: 1001
    #42929

    Me too. The utility probably will not show it in the Insteon Traffic tab as explained below. I think only the last connection to port 8002 will show the xml as explained below. None of that explains why the Action would not be triggered.

    The display of the link record in the KPL as displayed by the SHN Utility

    Link Record 1 – Controller of Device: 5.EA.28 Group: 3 Data: FF.FF.FF

    The display of the link record in the EZSrve as displayed by the SHN Utility

    Link Record 4 – Responder to Device: C.8C.3B Group 3 Data 0.0.0

    The link between the KPL button C and the EZSrve was done by defining a Scene through EZSrve with KPL Unit 03 as the controller and EZSrve as the responder.

    If you are using the SHN Utility Insteon Traffic tab to view powerline traffic, don’t. That tab is designed to show Insteon messages issued by the Utility and the specific response to those messages. It is not a generalized Insteon powerline trace. You can use the Control tab to view xml coming from the EZSrve but I think it has to be the only program connected to port 8002. If I bring up two copies of the SHN Utility only the last invocation shows the xml messages.

    I changed the LD1/2/3 values in the EZSrve link record from 0.0.0 to FF 1F 00 to match your values and it still works.

    The other things being used to determine KPL message flow can be explained away but the fact that the Action does not trigger is a problem. Can you display or offload the Actions file and post the xml section associated with the KPL trigger? Maybe that Action did not get defined correctly for some reason.

    Anonymous
    Inactive
    July 8, 2009 at 9:46 pm
    Post count: 29
    #42930

    Here’s actions.xml. Only one action is defined.

    Anonymous
    Inactive
    July 8, 2009 at 9:55 pm
    Post count: 1001
    #42931

    Wednesday is not enabled. Days=”SMTWRFA”

    Anonymous
    Inactive
    July 8, 2009 at 10:06 pm
    Post count: 29
    #42932

    Oh, geez. And I even looked at that string. (BTW, note to smartlabs: It would be nice if the web page had an [x] All days checkbox.)

    OK, the action is working now. But, still no xml. Your comment about only the last client connected gets the xml status messages makes me wonder whether something is connected I’ve overlooked. But, to the best of my knowledge, my monitoring program is the last program to connect before I press the KPL button. Does a client have to send some xml message before the EZSrve will start sending status messages?

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 24 total)
1 2 Next
  • You must be logged in to reply to this topic.