AnonymousFebruary 13, 2010 at 8:53 pmPost count: 73
After figuring out how to get the EZServe to control my thermostats, and get it to respond to input from a remotelinc (much thanks to Grif), I have a set of actions setup, mostly to control my thermostats based on my (wacky third shift) schedule.
Of late, the action T_Home_From_Work has not been triggered at the programmed times, and the action A_Home_Daytime has been triggering every time I restart the EZServ, and at noon. A_Home_Daytime is programmed to respond to my RemoteLinc button 5 ‘on’. It used to be set up to only trigger during daylight hours, and I had another action that responded during nighttime hours, but have consolidated those functions into one action. The action still functions normally with the button press on the RemoteLinc.
Here’s my Actions.xml:
< ?xml version="1.0"?>
I have made changes and tweaks to many of the actions lately since my shift moved from Mon-Thu to Tue-Fri. I got a little fed up with the goofiness today and reset the device, then imported the devices, areas and actions xml files… and it still triggers the T_Home_From_Work action when I restart the unit.AnonymousFebruary 13, 2010 at 9:36 pmPost count: 55
Not sure if this will help your situation as the T_Home_From_Work action isn’t triggered by Insteon device status, but it might explain the A_Home_Daytime symptoms you described.
The device state is maintained in the cluster entries in the devices file. The CID=0 cluster has a status field that reflects the last event for that device (i.e. 0x02, 0x03, etc. for X10, 0x1101, 0x1301 for Insteon). When you restart the EZSrve and it loads the actions, for those with a device status condition, the EZSrve appears to check the cluster status entry and fire the effect if the status matches the condition.
Thus, if the last command from your RemoteLinc was the 1105 (button 5 on) command, you’ll see that in the status field for the device in devices.xml and the action based on that device status will fire on restart.
I have several device based actions in my setup. So, depending on what I’ve been doing, restarting the EZSrve sometimes creates a bit of a light show in our house.AnonymousFebruary 13, 2010 at 11:54 pmPost count: 1001
Is the T_Home_From_Work Action triggering on the correct days, but not at the correct time? Check the Server Configuration for the correct TimeZone, NTP option, and Time of Day. Sounds like the time value is not correct.
If the time values are correct suggest running a Telnet trace to see if it provides any useful information. From a Windows line command window enter ….
set logfile c:temptelnet.txt
open 192.168.2.3 10001
In response to the login information request …
The path on the logfile command is something valid on your system,
The open command is your IP address followed by 10001
Have the telnet trace active leading up to the point when the Action should trigger. You can send me the telnet file at email@example.comAnonymousFebruary 14, 2010 at 3:05 amPost count: 73
SC, that makes a lot of sense. It’s triggering the action because the last ‘status’ it got from the RemoteLinc was that button. Would be nice if on restart the EZServe polled all the devices and reset their status.
Grif, the date and time were correct on the EZServe, and my other time based actions seemed to be functioning normally. The only oddities are that the Home From Work action not firing and the Home Daytime action (triggered by the Remote Linc) firing around noon.
I’ll have to use the desktop upstairs to telnet to the device, seems Win 7 on my netbook doesn’t have telnet. Oh well.AnonymousFebruary 14, 2010 at 3:14 amPost count: 73
Oh, and since I reset the unit today, and don’t work for a few more days, I’ll probably wait until later next week to pull the logs. I’m hoping the reset and reimporting of the devices, areas and actions files will clear up some issues.
Over the last few weeks, I have tweaked the actions a lot – adding a few different time triggers, threw in some vacation since I was out of town for a week, and then changed the days on many of the timers since my shift changed days this week.
I’ll probably wait until Thursday morning to see if the Home From Work timer functions correctly on Wednesday and Thursday mornings. If not, I’ll pull the log file and post it.AnonymousFebruary 14, 2010 at 3:09 pmPost count: 1001
The problem with polling devices is that for Controllers, like a ControLinc and RemoteLinc, there is nothing to poll regarding button status. No way to ask which button was last pressed and how it was pressed. A single tap On, a double tap Fast On, a press and hold for Dim or Bright and how long it was held. Also the RemoteLinc is asleep, having turned off the RF receiver to conserve battery life. No way to communicate with a RemoteLinc.
By reacting to the last status known to EZServe the Actions are restoring the Effects last executed. Perhaps a new option would be useful to control whether a specific Action is examined on a Restart. That way Actions which should execute to restore Effects would run while others demeaned inappropriate to run on a Restart would be ignored.
When you post back the results of next week’s test, did you do the Action updates through the Harmony client or the HTML interface. Although I have not been able to reproduce it locally I have had emails indicating a need to Restart EZSrve after updating Actions through the HTML. This has the effect of having in memory Action structures being built from the Actions XML file rather than changes made to those in memory structures by the HTML. A Restart after Action updates if Actions are not reacting as expected might be useful.AnonymousFebruary 14, 2010 at 5:01 pmPost count: 73
I have done all the editing through the HTML interface. I haven’t poked around with it much through the flash utility. Mostly I use the flash utility through the website to check my thermostat settings – in the least, the flash interface does allow me to see what temperature my thermostats are seeing and are set to. I usually leave work at 9am, and since my Home From Work action should be setting one of my thermostats up to 75 degrees, I’d check it right before I leave… and it had not changed.
We’ll see what it does this week. I’m hoping a reset will help. I think perhaps the foul-up is due to a lot of editing of the actions through the HTML interface.AnonymousFebruary 19, 2010 at 9:51 amPost count: 73
My ‘home from work’ timer has been functioning normally this week so far. I think the full reset helped.
It’s also good that I now understand that actions can be triggered on reboot if they were previously triggered by input from a device like my RemoteLinc, so at least I learned something!AnonymousFebruary 20, 2010 at 12:48 amPost count: 73
Spoke too soon. Got home this morning, and the action had not been triggered. I restarted the EZServ and then hit the sack. It appears the other two timer actions that occur during the day triggered normally.AnonymousFebruary 20, 2010 at 2:59 pmPost count: 1001
With other time based Actions triggering it might not be an Action problem. I worked with another user some months back thinking a time based Action was not triggering which turned out to be an issue with the responder, not the Action. In that case the telnet trace showed the correct command was issued and ACKed with the responder device not reacting as expected. There was a problem where an Action was not being reenabled during the previous Action trigger and failed to trigger the next time but this was resolved with 02.06.04.
- You must be logged in to reply to this topic.