When I have an event that I think should fire but doesn't, I set up a test event that just does a series of hs.writelog's of the variables that the events is checking. In your case you could do:
hs.writelog "JDS CaddxAlarmStatus = ", hs.devicevaluebyname "JDS CaddxAlarmStatus"
hs.writelog "JDS Vacation = ", hs.devicestatus "A1" (substitute whatever JDS Vacation's HC/DC is for A1)
Manually run this event and see if the results verify what you think the devices actual states are.
__________________
Dick
HS PRO 2.4.0.54, WinXP, Dell P4 - 3.0 GHz, 2GB, IE8, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLDeviceMatrix, BLIcon, BLMovies, BLOccupied, BLRadar, BLSecurity, BLUPS, BLPowerMonitor, BLWeather and BLRfid plugin. 400+ devices, 215+ events, 1-wire weather station + temp/humidity sensors and Oregon Scientific temp and humidity sensors and Brultech ECM-1240 Power Monitor
|