How do I set up an attendance simulation at LUPUS

Presence simulation on the LUPUS XT1 PLUS, XT2 PLUS and XT4
# LUPUS XT1 PLUS, LUPUS XT2 PLUS, LLUPUS XT4, PRESENCE SIMULATION

Reading time: approx. 5 minutes (for all variants)

Automation: “Random Execution” General

To create a presence simulation, the XT control panel offers the option of randomly executing an automation command. You can choose whether the automation is guaranteed to be executed in the selected time period or whether it is not guaranteed to be executed.

The following generally applies to the execution:

• In the automation, you define a time frame during which the random execution can take place.
• In this time frame, the probability is then divided into individual minutes. This means that the longer the time frame, the lower the probability of execution per minute.
  With a time interval of 10 minutes, every minute would have a 10% chance of randomly triggering the automation.
• With a guaranteed execution, execution is guaranteed in the last minute of the period (if execution has not already occurred).
• Please always define a time period! An undefined time period (eg “Always”) would result in the probability of execution being defined for an indefinite period of time and therefore the probability of execution per minute would be very low.

Example of a presence simulation

Within each of the minutes of this period, there is a 10% chance that the action will be executed.

Application example

For a complete presence simulation over one or more evenings, you could create an automation like this:

• These automations ensure that between 18:34 and 23:23 a relay / radio socket is switched on for a time period defined by you.
  • After the time you defined, the relay / radio socket will be automatically switched off again and could be switched on again by the automation in this time interval.
• If you select the setting “guaranteed execution: on” for “random execution”, the rule will be executed in the last minute of the respective interval at the latest. This allows you to ensure that a light actually goes on once - but also means that such a rule could be more easily recognized as a simulation.
• You can also combine the condition with “Mode – Arm” so that the random executions only take place when the control unit is in Arm mode.
  Of course, you can also define other dependencies here: e.g. only below certain lux values.

Please note that these are only example values, which of course should not be transferred 1:1 in this form.