Revision as of 22:17, 23 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"

Day of Month

Can take a value from 1-31

Day of Week

Multiple entries can be separated by comma.

Respond to Event

Can take a value from 0-6
0 = Sunday

Timed event

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_EventParameter takes it's values from.

PK_DeviceCategory

PK_DeviceGroup

Not Implemented

PK_DeviceTemplate

PK_EventHandler

PK_EventList

Not working

PK_EventParameter

You can see what parameters each of these Events take by going into web admin, clicking on Advanced > DCE > Events.

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_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).

User Mode