Triggers

Triggers are specific actions or events that the Task Manager can continuously listen for. You may already recognize a lot of the triggers from the Composer, for example wait for a voice command.

List

The availability of the triggers is highly dependent on the connected device and the software version.

The following triggers are available:

Sensor

A task can be started by tapping any of the sensors (e.g. 'tap the head button'):

sensor settings
  1. Tap the list to view a list of sensors available on the device. For example, the following list will be shown when connected to James:

sensor settings list
  1. Toggle which sensor should be used to trigger the task.

  2. Tap the button 'OK' to apply the changes.

QR code

A task can be started by showing a qr code to the main camera of the device:

qrcode settings
  1. Toggle whether any qr code can start the registered task or if a specific code needs to be shown.

  2. Enter the qr code to be shown (1)

  3. Toggle whether a 'beep' noise should be made when a matching qr code has been detected.

Monitoring

A task can be started by a monitored event (e.g. 'if a person was detected wearing a mask'):

monitoring settings
  1. Enter the device that triggered the monitoring event.

  2. Enter the type of monitoring event that was triggered.

  3. Select an optional alarm type that must be included in the monitoring event.

  4. Tap the button 'Update' to apply the new trigger settings.

The monitoring options for the event must be enabled in the Monitoring section page.

Motion detection

A task can be started when motion is detected:

motiondetection settings
  1. Toggle whether an image of the detected motion is saved to the cloud.
    This image can then be viewed in the Surveillance page

  2. Choose how frequent the task should be triggered(1)(2).

(1): Note that the monitoring events for the motion detection will be triggered as well
(2): If the value is '0', every detected motion will trigger the task.

Face detection

A task can be started when a face was detected:

facedetection settings
  1. Set how many faces should be detected (e.g. 'the amount of faces is equal to one', 'more than zero', 'less than two', …​)

  2. Toggle whether only known faces should be counted(1).

  3. Choose how frequent the task should be triggered(2).

(1): If this setting is enabled, the setting for 'amount of faces' will be ignored.
(2): If the value is '0', the task will be triggered every time the amount of faces is detected.

Voice

A task can be started by using voice commands:

voice settings
  1. Enter the list of voice commands to start the task.

  2. Toggle whether the wake-word should be triggered before the voice command will be accepted.

Mqtt

A task can be started by a message on a mqtt broker:

mqtt settings
  1. Set the topic to be published on the broker so the task will start.

  2. Enter (optional) conditions for the payload (e.g. "mqtt.payload.value" < 5).

  3. Toggle whether to use an external broker or the broker installed on the device.

  4. Enter the requirements for the external broker.

Entries marked with a * are required.

Domotics

The settings for the Home automation systems must be enabled to view the configured devices.

A task can be started by a change in the configured smart home devices:

domotics settings 1
  1. Tap whether an event (e.g. 'any device comes online') or a device (e.g. 'lamp 1 was switched on') should be used to trigger the task. For example, when selecting 'device', the list of devices will be shown:

domotics settings 2
  1. Tap the category for the device.

domotics settings 3
  1. Tap the device that will trigger the task.

domotics settings 4
  1. Set whether any changes or specific conditions will start the task to start.

  2. Enter the (optional) conditions for the trigger.

Consult the manual for the smart home device(s) to view more information on available settings.

Kiosk home screen

A task can be started every time the home screen (i.e. main folder) of the kiosk is shown.

Boot

A task can be started every time the device is (re-)booted.