This is a V2 Action that turns on 3 different devices (Effects) at 14:00. The EZSrve Operating Guide in the Downloads section has step by step sequence for creating a new Action.

This post has more examples ….. http://simplehomenet.com/forum/viewtopic.php?f=15&t=668&start=0

[attachment=1:22zh6p86]ActionsOn.JPG[/attachment:22zh6p86]
[attachment=0:22zh6p86]ActionsOnCondition.JPG[/attachment:22zh6p86]

One user reported that setting the Absolute= time to just a few minutes ahead of current time did not trigger unless the EZSrve was Restarted (not Reset) before the trigger time arrived. I have never been able to recreate that and regularly set time based Actions a few minutes ahead while testing. The parameters you posted look correct. A FF Effect value does turn On an Insteon device and a 00 Value turns an Insteon device Off.

There are a few areas that if done in the wrong sequence will result in the Action information not saved correctly. You go to the Condition Screen first, set those values and Save on the Condition screen, then click the Back Icon to return to the initial Action screen. Set the Effect information, check the Condition Enable, the Action Enable and click Save on the Action screen.

Can you post the XML from the Actions.xml file for the Action in question. I will check the actual values saved for both the Condition and Effects to see if I can see a problem. You might try setting an Absolute= time value say 10 minutes in the future, save the Condition and the save the Action. Do a Restart (not Reset) and see if the Action triggers.

EDIT: There is another possibility I just thought of. Did you check that EZSrve is showing the correct time of day. There were some changes around 1.60 and carried into the V2 images that start off with Manual time zone and no NTP option checked. That will result in EZSrve not running the expected time until the correct time zone is selected, the NTP option checked and the SET TIMEZONE button clicked.

Action definition looks fine. The next step is to trace the Action activity. This will show if the Action is actually triggered when expected and what it did if/when it triggered. Version 2 has a telnet based trace that is very good at showing Action processing.

Open a command window and enter the following commands…

telnet
set logfile c:temptelnet.txt
open 192.168.2.3 10001

EZServe
Simplehomenet

The set logfile command defines the path/file where the telnet trace messages will be written. The example is what I use on my system. Use a path that reflects your system. The open command specifies the IP address of your EZServe. Don’t forget the port number 10001. After the open command, EZServe will prompt for the normal login information. The name EZServe followed by the password. I use the default Simplehomenet password, specify whatever you have defined for the password.

Set the Absolute= time to something in the future and see what happens. Either post the telnet trace or send it to lwgwork@embarqmail.com. If you restart EZSrve the telnet connection has to be reestablished after the restart.

The Action triggered at 10:45:00 but did not issue any command to the Effect device. Ignore the Error Sending trace entry. Does not mean what everyone thinks it does. There is a problem with the DevClusters.xml file or the Devices.xml file. How did you install 02.06, with the 1.1 Discovery tool or by directly uploading the image? I’m thinking the DevClusters file is not at the latest level or was not at the latest level when the Test device was added to EZSrve. The Form Cluster trace entry is showing all zeros when it should look something like this with the Insteon command activity that follows. I pulled this from my telnet trace of an Action that is turning Off an ICON Switch.

12/14/2009 21.58.20: Form clustr: CB-0: [F] CB-I: [4] CB-II: [56] CB-III: [50] C
B-IV: [11] CB-V: [0] CB-VI: [0] CB-VII: [0] CB-VIII: [0] CB-IX: [0]
12/14/2009 21.58.20: In actor requst process: actor queue ActorArray0 f,ActorArr
ay4 11,ActorArray5 0
12/14/2009 21.58.20: In plm msg handler: msg type Ins std id 04.56.50,0×11 cmd1,
0x00 cmd2
12/14/2009 21.58.20: Done: MSG Code 62, ID 04.56.50 Cmd1 11, Cmd2 0 Ack 6
12/14/2009 21.58.20: Done: PTH_StdMsg 50, ID 04.56.50 Flag 2B, Cmd1 11, Cmd2 0

I think you need to upload the DevClusters.xml file and then delete and readd the Test device.

You can send me the DevClusters.xml file and the Devices.xml file and I will verify that or upload the DevClusters.xml file, Restart (not Reset) and readd “Test” device.

The “Test” device definition has no cluster information. Don’t know how that happened. Did you use the HTML interface or the Harmony client to add that device and what type of device is it. Suggest deleting the device and readd. See the cluster information for “Xmas Tree’. This information is missing for the “Test” device.

EZSrve will not delete a device definition if that device is referenced in an Action, Area or Scene. All references to the “Test” device must be deleted before the device itself can be deleted.

You can download the Devices.xml file and manually delete the “Test” device entry, upload the Devices.xml file and do a Restart (not reset). The problem with that is if the device still appears in Scenes, Areas or Actions you have effectively corrupted those definitions by manually removing the “Test” device definition.

I’ll add an ApplianceLinc to my EZSrve devices to see if I can recreate a device definition without the cluster information. That should be impossible. Were there any error messages, warnings, odd behavior when you added the “Test” device?

You cannot use V1 xml files (or any part of those files) on V2. They are not upward compatible. Just too many differences between V1 and V2 xml files.