HOME Forums Gateways EZSrve Custom Commands in V2 actions

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • Anonymous
    Inactive
    Post count: 3

    Back in the version 1.x firmware, the timers would allow you to enter your own custom Insteon command. For example, command 0x2E, which tells a dimmer switch to turn on to a certain level with a specified ramp, without modifying the link’s Level or Ramp settings.

    Was that feature done away with for V2 actions? In the V2 API doc, the Actions.xml section shows a DevAct=”1300″ line that us promising. But if I try to upload a custom Actions.xml with that entry, then the EZSrve tells me the file is invalid.

    Is there any way to tell an action to execute any arbitrary Insteon SD command?

    Anonymous
    Inactive
    Post count: 3

    Well, after using the V2 firmware since it came out, I never carefully read the scenes section in the documentation. For the specific case I’m looking for (customizing the ramp rate on a per-effect basis), this can be done with scenes and groups. I never put it together that the EZSrve can support a whole load of group IDs, and you can set a specific ramp and level for each device link within a group/scene. The scene can then be used in the Effect. Very cool.

    When all else fails, RTFM, I suppose.

    I would still like the ability to send a custom command, though. Given the lack of updates to this device over the last couple of years, it is more and more likely that we get our hands on a responder device type that isn’t recognized by the controller, and therefore won’t have the correct listing of available attributes in the Effects dropdown box.

    Along those similar lines, I really hope SimpleHomeNet hasn’t abandoned us EZSrve users. I love this little box, and it can do so much as it is (XML interface!!), but time moves on. Native mobile device support still doesn’t exist (look at SmartLinc and MobileLinc to see how it should look). You guys apparently spent a ton of resources on the Harmony Gui, only to stop updating it a few months after it was released. I would love to know what your roadmap looks like for EZSrve support (without having to get a zigbee device)

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