2.0 Operation 2009-05-08T14:43:22+00:00

HOME Forums Gateways EZSrve 2.0 Operation

Viewing 15 posts - 16 through 30 (of 43 total)
  • Author
    Posts
  • Anonymous
    Post count: 1001

    Joe, thanks for the great documentation. I have been able to recreate the situation and I think you have discovered a glitch in the latest V2 release candidate. I defined a simple 2 Action case, with both having a Condition of G02 ON. If both Actions are Enabled, only one is actually triggered. If I disable one of them the other will trigger. Appears that the X10 processing stops once it finds one Enabled Action. I passed this information on to SHN support, will let you know what they say.

    Anonymous
    Post count: 1001

    Joe, the X10 Actions problem you identified is fixed in 02.00.53. I tested the scenario with 2 Actions and both were triggered from the same G02 ON. It will probably be a few days before this image is posted for general availability. Thanks for documenting the problem.

    Anonymous
    Post count: 36

    That’s great grif01. Glad I could help. Thanks for your assistance.

    Anonymous
    Post count: 1001

    Joe, some bad news. The X10 two action trigger fix has been removed because it caused another problem. The 02.00.55 image that will be posted soon does not have the fix for your problem. Until the problem is resolved one thing you can do now is create a Scene with EZSrve as the controller and the three devices you are turning off as responders. Then turn the Scene Off as Effect 4 with the other Scene. You should disable the Action that is currently turning off those three devices if you decide to go that way so there is only 1 Action with the X10G02 Condition. Simplehome mentioned that the Flex client, the Flash based client, has the ability to define 6 Effects so you could move the 3 Off Effects to the other Action when the Flex client is released. This is a few days away so it depends on how soon you want your scenario to work.

    Anonymous
    Post count: 73

    Wow… 2.0 made the timers a bit more complicated. I think I at least figured out that an Insteon device attribute value of 0 = OFF and FF = ON.

    I have four ToggleLinc Relays, two LampLinc V2s and two Venstar Thermostats. I wanted to create a timer that turns on my front lights (on a ToggleLinc Relay) and my downstairs livingroom lamp (on a LampLinc).

    Here’s how I set it

    Condition 1
    Logic: AND
    Device: OutsideFront (togglelinc) Attribute: status Value: 00
    At Time: Absolute = Start Time: 22:30:00 Offset Time: 00:00:00
    Monday – Friday

    Which to me means “if the outside front switch is OFF at 10:30PM on weekday nights”

    Then Effect 1 is
    Device: OutsideFront Attribute: Status Value: FF Delay: 00:00:00
    And I added Effect 2 –
    Device: LivingroomLamp Attribute: Status Value: FF Delay: 00:30:00

    Which means to me “turn on the OutsideFront immediately if Condition 1 is met” and “turn on the Livingroom Lamp 30 minutes later”

    Meaning, at 10:30PM on weeknights, if the outside front lights are off, they will turn on.

    Correct?

    Where can I get a list of the status codes for the Venstar Thermostats? I would really like to set up a schedule for the two thermostats I have.

    Anonymous
    Post count: 256

    Please look at the appendices on the Operating Guide. It has values for various devices including the thermostat.
    The thermostat has to be commanded as a responder in a scene. Although we’ve heard there is now a way to send direct commands to it, we don’t have any details from SmartLabs

    Anonymous
    Post count: 73

    I have found in the Actions when you select a thermostat as a device and then select CoolSetPoint (or heat) you can give it a numerical value.

    Is that value and absolute (i.e. ’76’ would result in the setting to be 76º), or is it a hex value?

    Anonymous
    Post count: 55

    In 1.xx, macros you could send an Insteon command to a dimmer (i.e. Bright / Dim) in response to an event. In 2.xx actions, the only option available for dimmers appears to be setting the “status” attribute. Is there a way to send a bright or dim command via an action?

    Anonymous
    Post count: 1001

    I could not find a way to send a specific Bright or Dim command. You can set the Value to something between 00-FF to get the device to a desired Bright/Dim level but I could find no way to actually issue those specific commands.

    Anonymous
    Post count: 55

    @grif091 wrote:

    I could not find a way to send a specific Bright or Dim command. You can set the Value to something between 00-FF to get the device to a desired Bright/Dim level but I could find no way to actually issue those specific commands.

    Thanks for trying. What is the best way to get that on the SimpleHomeNet feature request list?

    Anonymous
    Post count: 69

    Can someone help me understand how the “SunsetToSunrise” option means on the condition menu? I’ve got some landscape lights hooked up to an appliancelinc that I’d like to turn at (or around) sunset and turn off by sunrise. I saw this option, and thought it a great idea, because I wouldn’t have to set up 2 events like in the past.

    So, I set up the condition to be “SunsetToSunrise”, I don’t select any device on this screen, leave the offset and start time at zero, and check every weekday. (BTW, and “hit this to check all days” would be nice…)

    On the action screen I pick my path lights with a status of “FF”, and also my outdoor spot lights with the same status.

    So, over the last couple nights, it’ll turn on the lights, but not turn them off.

    Does “SunsetToSunrise” mean it’ll issue the “FF” status command at both sunset and sunrise? Or is there another way to get this single action to turn off the lights at sunrise? Any guesses?

    Anonymous
    Post count: 1001

    The Effect is defined to turn On (Status FF) devices so the Action will not turn Off devices. The SunsetTo Sunrise time option makes more sense when used as a Condition for something like a Motion Sensor event where you only want the Motion Sensor On command to have an Effect during Sunset to Sunrise. A single Action allows the Motion Sensor to turn On devices only between Sunset and Sunrise.

    For a specific time based event, I think you will need one Action with an Effect to turn On the devices at Sunset and a second Action with an Effect to turn Off the devices at Sunrise. Actions would need something like an Effect with If Then Else for a device On with the If and device Off with the Else and that capability does not exist.

    You can use something like Effect 1 of an Action to turn On the devices at Sunset and then after a delay of some number of hours/minutes have Effect 2 turn Off the devices. Not as accurate as a second Action Effect turning Off the devices at Sunrise but it would be a single Action.

    Anonymous
    Post count: 69

    I understand now, thanks Grif!

    Anonymous
    Post count: 69

    Continuing with my trouble with timers… I want to set up my sprinkler timers again, using my ezflora. I just want to be able to run program 1 a couple times a week.

    According to the ezserve doc, I need to send LD2:00, LD3:08 to enable program 1.
    Also according to the doc:

    To enter a custom command, first select the
    first entry in the menu (“Enter Command”), then press the delete key in your keyboard.

    I don’t see anything saying “Enter Command”. When I select the ezflora device, my only two attribute options are “status” and “config”. The value field will only let me type 2 digits, no matter how I’ve tried hitting delete. I’ve tried just entering “08” in the value for both config and status, but neither enable the ezflora. I forgot to have the SHN utility running to see what commands it actually sent (if the beta will do that).

    So, am I missing something obvious? This sounds like about the simplest thing to do, but it’s totally escaping me.

    Thanks again guys,
    -Dave

    Anonymous
    Post count: 1001

    A reference to setting values in LDx fields are talking about the responder link record values for LD1/2/3. These values are set when a link is established with the EZFlora. You do not send LD1/2/3 values in an Insteon command. The reference to selecting Enter Command and hitting the delete key is a carryover of text from V1 that does not apply to V2 Actions. You can directly enter 4 hex digits into the Condition Attribute Value field (which again does not have anything to do with LD1/2/3 values).

Viewing 15 posts - 16 through 30 (of 43 total)
  • You must be logged in to reply to this topic.