Difference between revisions of "Event criteria"
(→Respond to Events) |
(→PK_Device) |
||
| Line 24: | Line 24: | ||
= PK_Device = | = PK_Device = | ||
| + | The device PK_EventHandler takes it values from. | ||
= PK_DeviceCategory = | = PK_DeviceCategory = | ||
Revision as of 11:06, 17 February 2010
This page will try to list valid parameters that can be used in the Event Criteria section of advanced Events. Note that there may be differences in the behaviour of "Respond to Events" and "Timed Events". Where nothing is specified, it refers to "Respond to Events"
Contents
- 1 Day of Month
- 2 Day of Week
- 3 House Mode
- 4 Month
- 5 PK_Device
- 6 PK_DeviceCategory
- 7 PK_DeviceGroup
- 8 PK_DeviceTemplate
- 9 PK_EventHandler
- 10 PK_EventList
- 11 PK_EventParameter
- 12 PK_Instalation
- 13 PK_Room
- 14 PK_RoomType
- 15 PK_Skin
- 16 Room Mode
- 17 Specific Date
- 18 State
- 19 System
- 20 Time of Day
- 21 User Mode
Day of Month
Can take a value from 1-31
Day of Week
Can take a value from 1-7
1 = Monday
House Mode
Can take a value from 1-6
1 = Unarmed - at home
2 = Armed - away
3 = Armed - at home
4 = Sleeping
5 = Entertaining
6 = Armed - Extended away
Month
PK_Device
The device PK_EventHandler takes it values from.
PK_DeviceCategory
PK_DeviceGroup
Not Implemented
PK_DeviceTemplate
PK_EventHandler
For more info see Event Table
Value
This can be an integer
Tripped
1 = Tripped
0 = Not tripped (this value is important if you use a movement sensor that triggers an event when there has been no movement for a set period of time)
PK_EventList
Not working
PK_EventParameter
PK_Instalation
PK_Room
PK_RoomType
PK_Skin
Room Mode
Not implemented
Specific Date
Not working
State
Not working
System
Time of Day
Timed Event
24hr based time (eks: 15:00).
Multiple entries can be separated by comma.
Respond to Events
Accepts special values
DAY or NIGHT
Or a time given in the
hh:mm or hh:mm:ss format (12:45, 21:22:10 etc).
