USERS


To identify the origin of remote control requests, up to 1000 users can be defined, each of them is stored in specific folders according to the type of user, see Filesystem > Unit U.


Each incoming request will trigger an event, according to the origin:

  • Active user
    within the allowed period and has sufficient tickets
  • Disabled user
    outside the allowed period or does not have sufficient tickets
  • Unknown
    not present among users


The content of the last request (if any) is stored in the map and can be used within a rule. If the request contains executable commands, these will only be executed if the device password is present at the beginning of the received message.


The following settings are available for each user:



TYPE

There are different type of users, depending on the media they use to interact with the device:

  • recognized by telephone number
    THEY USE A PHONE TO CALL, SEND AN SMS OR CHAT MESSAGE
  • recognized by e-mail address
    THEY USE A EMAIL MESSAGES
  • recognized by BLE identifier
    THEY USE A SMART DEVICE THROUGH BLUETOOTH
  • recognized by device identifier WebID
    THEY USE A SIBLING AVIOR DEVICE
  • recognized by application identifier APPid
    THEY USE A SPECIFIC APP RUNNING ON SMART DEVICE
  • recognized by Wiegand code
    THEY USE A WIEGAND DEVICE FOR ACCESS CONTROL

IDENTIFIER

An user is recognized by his identifier, it could be a phone number or an email address, depending on the user type.

The star character * can be used as a wildcard within the IDENTIFIER.

Using only the wildcard character as identifier means to enable anyone as a user, this should be avoided considering that an unknown caller can trigger his specific event.

It's a mandatory information and must be provided.

NAME

This is the name used to identify the user.

A single word, up to 20 alphanumeric characters.

It's a mandatory information and must be provided.

GROUP

Each user can be optionally assigned to a group, this allows to manage a single event for all users belonging to the same group.

If not specified, it means that the user does not belong to any group.

A single word, up to 8 alphanumeric characters.

START

It is possible to enable the user from a specific date.

It is possible to enable the user at specific time of each day.

The user will be considered disabled before the specified date and if the current time is before the set time (every day).

Valid setting from 00-01-01 00:00 to 99-12-31 23:59 (YY-MM-DD hh:mm) or leave empty to enable the user immediately.

The setting must be complete, the date must also be defined if you want to set only one time of the day (for example: 00-01-01 January 1, 2000).


Instead of specifying an exact date you may want to specify a time from when you make the setting.

You can specify the time in hours (H), days (D), weeks (W) or months (M). Examples:

8H = 8 hours from now

2D = 2 days from now

4W = 4 weeks from now

1M = 1 month from now

STOP

It is possible to disable the user after a specific date.

It is possible to disable the user at a specific time of each day.

The user will be considered disabled after the specified date and if the current time is past the set time (every day).

Valid setting from 00-01-01 00:00 to 99-12-31 23:59 (YY-MM-DD hh:mm) or leave empty to enable the user without expiration.

The setting must be complete, the date must be defined even if you only want to set a time of the day (for example: 99-12-31 December 31 2099).


Instead of specifying an exact date you may want to specify a time from when you make the setting.

You can specify the time in hours (H), days (D), weeks (W) or months (M). Examples:

8H = 8 hours from now

2D = 2 days from now

4W = 4 weeks from now

1M = 1 month from now

WEEKDAYS

It is possible to enable and disable the user on specific days of the week.

Default YYYYYYY

N means NO

disabled

Y means YES

enabled this specific weekday (Monday to Sunday)

from START HOUR to STOP HOUR

C means CONTINUOUS

enabled non-stop since specified hour of START DATE

to specified hour of STOP DATE

On the day when the user is enabled the other conditions apply (start, stop, tickets).

TICKETS

It's possible to set up to 999 allowed operations for each user.

Every command issued by the user will decrease the available tickets. The user will be considered disabled when all tickets have been used.

It's possible to reload tickets at any time, editing the user.

Leave empty for unlimited operations.

This  option may be used in combination with other conditions (start, stop, weekdays).