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

HOME Forums Gateways EZSrve 2.0 Operation

Viewing 15 posts - 1 through 15 (of 43 total)
  • Author
    Posts
  • Anonymous
    Post count: 7
    #40159 |

    I just installed 2.0 and got all the devices defined without a problem, but need some assistance with action setup. I have read all the 2.0 information published. The manual has not been updated. Is there any documentation on action setup. How do I program a timer for Insteon and X10? I have tried the obvious set a condition with time defined and the an effect with values of 0 and FF. These attempts did not work. Thanks

    Anonymous
    Post count: 1001

    Pictures of two Timer Actions and associated Conditions, one On and one Off.

    [attachment=2:269e9eq5]ActionsOn.JPG[/attachment:269e9eq5]
    [attachment=1:269e9eq5]ActionsOnCondition.JPG[/attachment:269e9eq5]
    [attachment=0:269e9eq5]ActionsOff.JPG[/attachment:269e9eq5]

    The forum process did not allow me to attach the 4th file which was the Condition for the Actions Off. Except for a later time of day the Condition definition for the Actions Off example is the same as the Actions On example.

    Anonymous
    Post count: 5

    On the Actions screen, when I select Effect 1, and drop the list down to select the Venstar thermostat that I had previously added, I then select Head Mode and what should I enter for the value? In the previous firmware (1.60), I would enter 8C for 70 degrees F, but that doesn’t appear to work with this firmware.

    Second question
    On the condition screen, when I select an X10 device, i.e. B-10, I select the attribute as X10 but I don’t know the Attribute Value to turn it off or on.
    I tried 0 but that made it respond each time the X10 is turned on or off
    I also tried FF thinking that would work for on, as well as 1 and 2, but none of them appeared to work.

    Anonymous
    Post count: 1001

    Look at Effect 3: in the screen images above. The first Actions screen Effect 3: turns on DX10WestFloodF3 which has an X10 address of F3. The Attribute field is “Status” and the Value field “2” is an X10 On command in the first Actions screen image and the value “3” in the second Actions screen image is an X10 Off command. The Value field is the low order 4 bits of the 2nd X10 message which contains House/Command. There is a chart of these values in the EZBridge Reference document in the Downloads sections.

    I will have to research what the Venstar requires in this situation. Updated post to follow.

    Anonymous
    Post count: 5

    I appreciate your feedback grif091, but I must be missing something.

    If I understand the values you are suggestion, they are as follows:
    Device ON OFF
    Insteon FF 0
    X10 2 3

    I added two devices, one is a SwitchLink Insteaon, I set it up calling it FR TV Power (for Family Room TV Power)
    The second device is an X10 device called B-16 TV Power

    I then added the Action calling it FR TV ON:
    Effect 1: FR TV Power
    Attribute: Status
    Value: FF

    I checked Condition 1:
    Device: B-16 TV Power
    Attribute: Status
    Attribute Value: 2

    I clicked SAVE, followed by the back button, then SAVE for the Action. Unfortunately no success. If I change the actions to Attribute X10, and the value of 0, it will respond when I send both X10 B-16 ON and OFF. I tried X10, with the value of 2 and no response.

    BTW, the EZBridge Reference document for “EZBridge/ EZSrve XML Samples” dated 1/31/08 is listed under the Servers and Controllers, but the download icon doesn’t currently function. I thought I’d take a look at the document to see if it offered suggestions.

    Anonymous
    Post count: 1001

    I think I did misunderstand. I thought you were trying to turn On/Off the X10 device with an Action Effect. From your last post it looks like you are trying to define a Condition that triggers an Action when X10 B16 On is received, with the Effect to turn On an Insteon SwitchLinc device FR TV Power. I’ll set up that configuration and see what I get. The screen capture examples above to turn On/Off an X10 device with the 2/3 values are correct for an Effect. Those screen captures are taken from working Actions. I don’t have any Actions that have a Condition triggered by X10 but will code one to test with.

    The EZBridge/EZSrve XML Samples is based on the V1 XML. The download did not work for me either which may indicate the files are being updated. The EZSrve XML API is the original V2 document which reflects the early thinking of the way the V2 XML API would work. The V2 XML has evolved over the last several months, making this document back level for several of the API calls.

    The EZBridge Reference document that contains the X10 command reference table appears to have been withdrawn. The X10 command values are not unique EZBridge/EZSrve. They are documented in various X10 documents on the web. I can post other values if you need them.

    SHN is working on an updated set of documentation for V2. I don’t have any estimate when they will be available.

    I will post back as soon as I have the results of the X10 Condition tests.

    Anonymous
    Post count: 1001

    The screen captures show the Action definition for B16 X10 On Condition to trigger the Action. I used an ICON Switch for the Effect. The Off Action definition is the same, except the Condition value is 3. The trace is from SDM3 which reflects the B16 On which turned the ICON Switch on, followed by the B16 Off which turned the ICON Switch Off.

    PLC:eventraw=08
    PLC:receiveX10raw=00 EC
    PLC:receiveX10=B16
    PLC:eventraw=08
    PLC:receiveX10raw=01 E2
    PLC:receiveX10=B On
    PLC:eventraw=02
    PLC:eventraw=03
    PLC:receiveinsteonraw=02 05 EA 28 04 56 50 0B 11 FF
    PLC:eventraw=03
    PLC:eventraw=02
    PLC:eventraw=03
    PLC:receiveinsteonraw=02 05 EA 28 04 56 50 0B 19 00
    PLC:eventraw=03
    PLC:eventraw=08
    PLC:receiveX10raw=00 EC
    PLC:receiveX10=B16
    PLC:eventraw=08
    PLC:receiveX10raw=01 E3
    PLC:receiveX10=B Off
    PLC:eventraw=02
    PLC:eventraw=03
    PLC:receiveinsteonraw=02 05 EA 28 04 56 50 0B 11 00
    PLC:eventraw=02
    PLC:eventraw=03
    PLC:receiveinsteonraw=02 05 EA 28 04 56 50 0B 19 00
    PLC:eventraw=03
    PLC:eventraw=03[attachment=1:2uxyhzn3]ActionB16X10On.JPG[/attachment:2uxyhzn3][attachment=0:2uxyhzn3]ConditionB16X10On.JPG[/attachment:2uxyhzn3]

    Anonymous
    Post count: 1001

    The next Release Candidate image 02.00.40 looks like it resolves the Thermostat problem. Be sure to upload the DevClusters xml file that comes with that image. The new image is issuing the Insteon 0x6D command to update the Heat Set Point which was missing in the previous image.

    Anonymous
    Post count: 5

    I checked the values I had entered previous, which were the same as your two screen shots. I thought, strange, as I’m using the same firmware, yet no success.

    Then I thought, well, when in doubt, reboot. I issued a restart, and presto – both the ON and OFF commands were perfectly with B-16, controlling the Insteon devices.

    Thanks for your assistance

    Anonymous
    Post count: 256

    Below is a simple summary of the process to build Actions as it will appear in the guide for EZSrve 2.0:
    1. Select “Add New Action” to appear in the “Actions” dropdown list.
    2. Give a name to the action by typing in the “Action Name” slot (do not press “Save” yet).
    3. Select a Condition (1-5) by pressing on the corresponding triangle. At least one condition must be established first before the Action.
    4. Provide input into the various fields in the Condition screen and press “Save”. Note at this point on the Condition screen, the “Action Name” will still read “Add New Action”.
    5. Once the condition is saved, press the “Back” button and note the “Action Name” shows the name it was given, but also note it is not yet saved.
    6. Next, set-up the desired Effects to happen once the Condition occurs.
    7. Check mark the conditions to be enabled and check mark “Action is Enabled” and press “Save” which saves the entire action just created.
    8. Checking and unchecking the different conditions to occur and “Save” modifies the Action, and checking/unchecking the “Action is Enabled” box and “Save” enables or disables the entire action.

    Anonymous
    Post count: 36

    I’ve tried sttting up an action based on recieving an x10 command like the OP, but have had only partial success. I’m running 2.00.51. I’m trying to create two actions based on receiving the same x10 ON command. One action turns on some lights and the other action turns off other lights. I followed the examples in this post and I’ve got the action that turns on the lights working. However, the action that turns off lights does not seem to trigger. What is really wierd is that the action that turns off lights does run when I reboot my EZServ. Any thoughts grif091?

    Anonymous
    Post count: 1001

    Can you provide the details of what the two Actions are actually doing? Are they turning On/Off X10 or Insteon devices? As much detail as you can provide and I’ll see if I can recreate here. Also did you consider using the multiple Events that are available from a single Action. Could be your two Actions are running together and they are creating a Insteon conflict on the powerline. For test purposes you can try putting say a 10 second delay on the Action Events of one of the Actions and see if creating a separation helps. Not suggesting you need a 10 second delay, just that should be enough to remove overlaps if one exists.

    Anonymous
    Post count: 1

    Hello, I have to say that the new “actions” screen is really confusing. I’m trying to create a simple timer that turns my outside lights on at dusk and off at midnight. The lights are on an X10 device using G2 as the house & device code. They worked fine with 1.60 but when I upgraded to the 2.0 beta I just can’t figure it out.

    Thanks for any help.

    James

    Anonymous
    Post count: 1001

    The V2 Actions is a merge of the Macro and Timer functions found in V1. Things you could do in V1 Macros and V1 Timers can be done in V2 Actions along with the addition of having multiple Conditions Anded/Ored together to form a complex trigger and multiple Effects where more than one device can be controlled from a single Action.

    A post earlier in this topic by Simplehome describes the specific steps to define an Action and its associated Condition(s). For a Timer equivalent in V2, define a new Actions and a Condition with an At Time: of Sunset to turn on at dusk. The Actions Effect 1: will be the X10 Device that represents your G2 outside light. The Attribute: is Status with a Value: 2 to turn On an X10 device. Another new Actions definition with a Condition with an At Time: Absolute = Start Time: 23 59 59 and a Value: 3 will turn the X10 device Off at midnight. The same X10 device would be entered in the second Actions Effect 1:. The screen captures in the second post of this topic show an X10 device as Effect 3: being turned On by the first Actions and turned Off by the second Actions.

    Anonymous
    Post count: 36

    grif091,
    Thanks for replying. Here are screenshots of how I have the actions set up. All the devices being controlled are Insteon. I am using a IR to X10 converter to send the x10 command from my remote. Let me know if you have any more questions.
    [attachment=2:3qckzh3q]Off Action.jpg[/attachment:3qckzh3q]
    [attachment=1:3qckzh3q]Off Condition.jpg[/attachment:3qckzh3q]
    [attachment=0:3qckzh3q]On Action.jpg[/attachment:3qckzh3q]
    Guess we’re limited to three attachments. The on condition looks just like the off one.

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