Automation for TEOS Scenarios

Installation & User Manual

Document revision 1.1

Overview
This document will explain how the automation scenarios works within Manage for TEOS
Requirements
• From Manage for TEOS 2.2
• Devices (attached with licenses) for the actions
• No need to use licenses for automation scenarios

Table of Contents
1. Automation Scenarios general details .......................................................................... 3
1.1. Usage ........................................................................................................................... 3
1.2 Hardware compatible with the automation scenarios ................................................... 3
2. Conditions under Automation scenarios ....................................................................... 4
3. Actions under Automation scenarios ............................................................................ 4
4. Creating Automation scenarios .................................................................................... 5
4.1. Room/desk booking, check-in and check-out............................................................... 6
4.2. Actions on AV devices .................................................................................................. 7
5. Examples of Automation scenarios .............................................................................. 8

2 | Automation for TEOS Scenarios– Installation and user manual

1. Automation Scenarios general details
1.1. Usage
From TEOS 2.2, using the automation scenarios will give you a lot more flexibilities in the usage of your
devices be able to use for example the KNX sensor (if you have) used for the Light where data is
retrieved into TEOS to start the meeting and the display.

A lot of workflows can be achieved using it.

You can do condition from a sensor, a device, date and time, meeting schedules and other type of
conditions are available. In output from these conditions, the actions going to actuators, devices devices
localization, meeting schedules etc.

1.2 Hardware compatible with the automation scenarios

Sony devices
Devices compatible with automation scenarios are:
Tablets for TEOS
BRAVIA
Sensors for TEOS (LoRaWAN)
Player for TEOS

Building devices
TEOS Version 2.2 offer an integration with building management. The 3 new building interfaces/gateway
integrated into TEOS are:

Third party devices

All the third-party devices officially compatible with TEOS (please review the Third-party documentation)
are compatible for power ON/OFF and volume if it is integrated into TEOS.

3 | Automation for TEOS Scenarios– Installation and user manual

2. Conditions under Automation scenarios
Object Condition item Comparison method Value
Power status Equals True/False
(select device)
On external input Equals True/False
device (select device and input)
Volume level Equals/greater than/ 0-100
(select device) Greater equals/
less equals/ less than
Value/average value/ Equals/greater than/ 0-1, value depending on
Highest/lowest value/ Greater equals/ the sensor output
Sensor
percentile value less equals/ less than
(select the Sensor)
Day of week/ Equals/greater than/ Day, hour (value), day
Date/time day/week/ year Greater equals/ (value), year (value)
less equals/ less than
Is booked currently/ Equals True/False
Is booked shortly/
Device localization Later today
(select Device localization
and within XX minutes)
Is booked currently/ Equals True/False
Is booked shortly/
Meetings schedules Later today
(select Calendar and
within XX minutes)
Action schedules/ Equals True/False
Content schedule/
Other
Automation scenario
(select schedule)

3. Actions under Automation scenarios

Object Action item Value
(delay action if needed)
Set Power status (select device) ON/OFF
Play presentation (select device) Select presentation
Device
Set volume level (select device) Volume (start),volume (stop)
Start App (select device) Signage or Connect
Book ad-hoc (select device localization) subject
Turn lights on/off (select device localization) On/off (start), on/off (stop)
Dim lights (select device localization) Dim level % (start),
Device localization Dim level % (stop)
Start Meeting (select device localization) Stop Meeting afterwards
(yes/no)
Stop Meeting (select device localization)
Actuator Write value (on actuator) On/off value
Meetings schedule Book ad-hoc (select calendar) Subject
Start Meeting (select calendar)
Stop Meeting (select calendar) Stop Meeting afterwards
(yes/no)
Others email To (email), subject, content

4 | Automation for TEOS Scenarios– Installation and user manual

4. Creating Automation scenarios
You can find automation scenario feature under > Schedules and Alarm > Automation Scenario

Click “Add automation scenario” to create a scenario. In the following screen enter the following
details:

General
Add a name
Activate your automation rule
Define the level of priority
(This will be used to determine which schedule has the highest priority in case schedules have
conflicting actions)

Conditions
This is the part where you can setup your automation rule, in this example we want to have a device
turned off in case the value of a sensor equals a specific value.

Please note that it is possible to add multiple conditions, the rule can become active in case it matches
all conditions or one of them.
For example when you want to turn a TV off in case there is no presence in a room or when the lights
go out.

You can also configure that a condition should match a specific value for 5 minutes before the
automation rule becomes active. For example in case the lights have been turned off for 5 minutes.

5 | Automation for TEOS Scenarios– Installation and user manual

Once you have saved the automation rule you will be returned to the automation rule overview.
From this overview you can verify which rule is active and which one is not.

When selecting the arrow on the right side of your rule an overview will be shown, this overview
contains the current values for your automation rule. In case the value matches your configuration, the
action will be executed and it will be shown as green (currently active).

This overview will be refreshed every 30 seconds, a timer can be found on the bottom right corner.

4.1. Room/desk booking, check-in and check-out

Within TEOS solution one of the targets is to make space efficient and simple to use. Thanks to the
sensors technology the following workflows can be achieved in the automation scenarios

1) When room is booked and waiting for a checkin, the sensor detects a presence and the checkin is
automatically done. If there is no presence, the checkin is not done and the room become available
2) When the room is not booked and presence is detected, book the room for a selectable time in the
automation scenario
3) When desk is booked and waiting for a checkin, the sensor detects a presence and the checkin is
automatically done. If there is no presence, the checkin is not done and the desk become available
4) When the desk is not booked and presence is detected, book the desk for a selectable time in the
automation scenario"
To make that possible after having your sensor connected to TEOS you need to go to schedules and
alarms and to Automation Scenarios:

Create a new automation scenario where you select as condition the sensor to have a greater value
than 0 and i fit is the case as actions tob ook automatically the calendar of your room with a subject such
as “autobooking” and the meeting duration which is recommending to be 10 minutes or 5 minutes
ranges.
If you want also to do the autocheck-in you can add in the action the start meeting option for the same
room calendar with the option to autocheck-out if the is no presence. TEOS will manage the rest of the
usage and will check every with a background task the statuses and calendars to make that workflow
working.
This is different from for example the fact of starting a device based on the sensor detection, this will be
done only once and when for example there is no presence, the state of the device will not change. You
need to add another scenario fort he power Off if sensor as no presence.

6 | Automation for TEOS Scenarios– Installation and user manual

 4.2. Actions on AV devices
When an action scenario is used to do actions on AV devices such as a BRAVIA for example when you
want to power it on/off based on a condition, take into account that when the condition rule is validated
the command to the device is send one time.
If you want also to change the status of the device based on the reverse of the condition, you will need
to create a dedicated condition for that. The condition change will not change the two status but only
change it once based on the condition validation value.

7 | Automation for TEOS Scenarios– Installation and user manual

5. Examples of Automation scenarios

1) When a presence is detected (desk sensor for example), start the meeting (stop
meeting can be directly setup as well)

2) Send email on a device status (Off for example)

3) When MR_TEOS booked power on BRAVIA and play selected presentation

4) Book if free to book (10 minutes slots by default

5) When room currently booked, start signage app

6) When MR_TEOS is booked, power on BRAVIA

7) When day of the week greater than 1 (Monday), power on device.

8) When currently no meeting schedule is booked, switch off device.

9) When device localization is not currently booked, play presentation.

10) When meeting schedule is booked currently, set volume for device to 30 if meeting
ends set volume to 0 again.

11) When device is powered on, start Signage app for TEOS.

12) When volume level of device is greater than 30, start Connect for TEOS app.

13) When device localization is booked currently, turn on lights. When meeting ends keep
lights on.

14) When device localization is booked currently, turn off lights. When meeting ends turn
on lights.

15) When device localization is booked currently, turn on lights. When meeting ends turn
off lights.

16) When device localization is booked currently, turn off lights. When meeting ends keep
lights off.

17) When device is switched off, dim lights 50%. When device is switched on again dim
lights 0%.

18) When device localization is currently booked, switch on Lamp 4. When meeting is over
turn off lamp 4.

19) When the device reboots, send an email.

20) When device localization is currently booked and device is powered on, send an email.
21) When device localization is currently booked, power on device and send an email.

22) When temperature is less than 30°C then send an email

23) When presence detected, switch on lamp 1

24) When rocker switch is clicked to on/1, lamp 4 should switch on

8 | Automation for TEOS Scenarios– Installation and user manual

 25) When meeting room is currently booked, dim lights 50%. When meeting is over dim
lights 0%.

26) When a presence has been detected, send an email

27) When a rocker switch greater equal to 1 book ad-hoc meeting (device localization)
(when 0 stop/cancel meeting)

28) When a rocker switch greater equal to 1 book ad-hoc meeting (meeting schedule)
(when 0 stop/cancel meeting)

29) When rocker switch 1 is switched to 1 (on) start meeting, stop after

30) When rocker switch 1 is switched to 0 (off) stop meeting

9 | Automation for TEOS Scenarios– Installation and user manual

© 2021 Sony Corporation