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.

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.

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.

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.

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.

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.

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.