IoT Manager

IoT Manager is for the room devices — lights, thermostats, curtains, courtesy panels (Do Not Disturb, Make Up Room), occupancy sensors and scent diffusers. Its menu follows the IoT Simulator's manager portal (Rooms, Provisioning, Settings), plus History for test reports; the portal's Dashboard is the console's own Dashboard. It is used by engineering. You need the Devices area — see Areas and roles, and the hotel must have Room controls switched on in Settings → Site. For the order to set up a whole site, see Setting up a site.

Dashboard and History

#Room checks on the Dashboard

The console's Dashboard has a Room checks section that shows whether the room devices work. The History menu item carries a number when something is wrong — that is the badge to watch. It counts rooms whose latest check or batch test failed and commands that failed in the last 24 hours.

• The result of the last Check now is shown for every room with devices: every device is read from the building system right now, and any device that returns no value at all is reported by name.
• Check now runs only when you press it — there is no automatic schedule yet. With simulated devices the check is marked simulated. Results are kept in History.

Click a room number to open the room.

#History

History has two views.

Test reports (the default) shows one report per Batch test, newest first — like the IoT Simulator's Test Reports. A report that has problems opens by itself. Each report has:

• a result line — Pass — 8/8 confirmed, or how many were not, or that a device was not put back — with the room, the time, whether the devices were simulated or live, and the slowest command;
• findings in plain sentences, most urgent first — for example a device that accepted a command but never changed, one that did not go back to its original setting, or one that answered slower than a second;
• Per-device round-trip — for each device the time its command took (minimum, average, maximum) as a bar that is green under a second, amber under three and red above;
• Every command (open it to see it) — what was sent, whether the device accepted it, whether the device itself reported the new value, how long that took, and whether the original was put back.

Filter by room, or tick Problems only.

Checks & commands lists device checks and commands, newest first, so you can look back when something went wrong: when did the room stop answering, and what was happening around it. Tick Problems only to see just the failures. Every command shows the room, the device and value, how long it took, and how it ended. Command records are kept for 14 days and check records for 30 days.

Rooms

#Live rooms

Rooms shows one room's devices as they are now and lets you control them. Under Rooms in the screen is the room list on the left — the rooms that have devices, grouped by room type, with a search box. Pick a room and its devices appear as cards. The room you looked at last is opened next time.

Above the cards:

Each card works like the IoT Simulator's:

• The device's icon is a switch for how much of the device guests see. Click it to go visible → hidden → disabled → visible. Hidden devices still work here but are not listed for guests (the icon is grey with a mark); disabled devices are not served to guests at all and have no controls (dashed grey card) — the card stays so you can turn it back on.
• Click the name to rename it. Its address (used by apps) follows the name.
• Tags sit under the name: tags the device carries are ticked pills (click to remove); + tag offers the others, and typing a new name creates the tag.
• The small circular arrow reads the room; ms shows how long the last command took (amber over a second, red over three).

Turning a light on returns it to its last brightness, or full if it was at 0. A device that is disabled has no controls; one with no reading needs its vendor references checked in Provisioning → Devices. You need the Operations or Devices area at Operator or above to send commands.

Commands and their results are listed under History.

#Saving a preset from a room

Set the room the way you want it — lights at some level, the thermostat, the curtain — then press Preset. The dialog lists what will be saved (every controllable setting of every enabled device that has been read), lets you pick a scene name (bright, dimmed, cool, … or a new name) and, if that scene already has values in this room, choose to overwrite it or keep it and save under a new name. Settings that have not been read yet are left out and named. The scenes are the ones edited in Settings → Presets.

History is kept for 14 days.

#Simulated and live

A site's devices are either Simulated or Live.

• Simulated — commands change a virtual room that lives in memory; nothing reaches the building. This is how every site starts, and it is safe for training and testing. The virtual room goes back to its start when idle.
• Live — commands move the real lights, curtains and thermostats. Rooms shows a Live building warning: check the room is empty first.

A Devices admin switches a site in Settings → Sites → Edit → Devices. If a site is set to Live but the IoT service has no building credentials yet, it keeps running simulated and Rooms says so. A room that has no SE space (see Provisioning → Rooms) also stays simulated when the site is Live — there is nothing in the building for it to reach — and Rooms says that too. That is how the demo room 633 keeps working next to real rooms.

#Batch test

Batch test checks that devices really respond. Open a room in Rooms and press Batch test: you see a preview of what will be done, then press Run batch test, watch the progress bar, and get a result table with Run again. To test several rooms, run it in each of them. For every device it:

1. sends a small test change — a light's level moves 20 points, the thermostat's setpoint half a degree, a light switch flips, the courtesy panel goes to Do Not Disturb;
2. reads the device back and checks it really changed (it waits a few seconds for a slow device);
3. puts the original setting back and reads it once more to be sure.

Every room ends up as it started. If a device does not return to its original setting, that is shown in red as NOT restored — the most urgent kind of problem — and it stays in the count on the menu until a later test passes; set it back by hand in Rooms.

Good to know:

• It runs only when you press it; there is no automatic schedule yet.
• Rooms with a guest are not tested, and neither is a room whose Do Not Disturb is already on. Devices whose value cannot be read are skipped, because there would be nothing to put back.
• Curtains are not moved unless you tick Also move the curtains.
• With live devices you must first tick I understand this sends test commands to real devices. Simulated sites need no confirmation.
• Each test is kept as a report under History → Test reports, and rooms whose latest test failed count in the number on the History menu item.

Provisioning

#Rooms

The Rooms tab of Provisioning is the site's room list — the same screen as Settings → Rooms & Floors: create, rename and delete rooms, and give each room its SE space and device group. TV Manager and IoT Manager share it because both hang off rooms.

#Devices

Devices lists the room devices of the site: lights, thermostats, curtains, courtesy panels (Do Not Disturb, Make Up Room), occupancy sensors, and scent diffusers. Pick a room, or see all rooms. Needs attention shows devices that are disabled or not fully mapped.

Each hotel's devices come from its building management system. Adding one here does not create anything in the building — it records how to reach what is already there.

#Scent diffusers

A scent diffuser is not reached through SE but through Deepscent, which knows each diffuser by a device id (for example lounge_08D1F91AC360). Add the device as a Scent diffuser and enter that id as its Deepscent device id — one id covers both switching it on and choosing a scent. Two diffusers in a room are two devices.

• The scents a diffuser can give depend on the capsules inside it; the screen offers only those. A scent the capsules do not allow is refused with the list of the ones that are.
• Deepscent does not report which scent is playing, so the screen shows the last one chosen here or from a guest's phone.
• A diffuser that is not connected to Deepscent (the cloud) is shown with a warning.
• Deepscent needs its own credentials in the project (the integration is set up once by whoever runs the platform, like SE). Until then diffusers on a live site show as "not connected" and cannot be controlled; simulated sites work without.
• Check-out switches a room's scent off, so the next guest is not met by the previous guest's scent.

#Adding and editing a device

1. Add device — choose the room and type, and give it a name, such as Desk Lamp. Its address is made from the room number and the name.
2. ⋯ → Edit — enter its vendor references: the building management system's id for each point, and its path. A dimmable light has one point (its level); a curtain has a control and a state point; a courtesy panel has three (Make up room, Do not disturb, Skip cleaning); a thermostat has one per setting. Points marked * are required. Clearing a reference unmaps that point.

In the same dialog:

• Name — renaming gives the device a new address. Apps that stored the old address must use the new one.
• Enabled — off means guests do not have the device at all (broken or removed). Its references are kept for when it comes back.
• Hidden from lists — guests do not see it in their list, but scenes still control it (for example a cove light).
• Tags — tick the tags that apply.

⋯ → Remove deletes the device with its references, tags, and scene values.

The same reference may be used in several rooms — useful when one set of test devices is shared.

The tag list itself is kept in Settings → Tags.

#Discovery

Discovery finds a room's devices in SE (the building automation system) so you do not type references by hand. It needs the Devices area, Operator or above. A scan only reads SE — nothing changes until you press Apply.

1. Pick the Room and press Scan SE. The scan lists SE's buildings, floors and spaces (a space is what SE calls a room). If the room is already linked to a space, that space is chosen for you.
2. Choose the Building, Floor and Space. The screen reads the space's points and groups the ones it recognises into devices: lights, curtain, thermostat, courtesy panel, occupancy sensor.
3. Review each device. New devices are ticked and can be renamed; Different means the room already has a device of that name whose SE points are not the ones SE reports now (it is re-mapped, keeping its name, tags and scenes); Already mapped needs nothing. A device with a required point missing is left unticked, because it would not work.
4. Press Apply. Devices are created or re-mapped, and — if you leave the boxes ticked — the room is linked to the SE space and to the device group its points belong to.

Below the devices, Other points lists what nothing recognised. That is usually right: most of SE's points are plant, energy and scene points, not room devices. Tick Show every point to see all of them, including points on other servers. No longer in SE lists references the room still has that SE stopped reporting; they are never removed automatically.

The server the hotel uses is chosen in Settings → Discovery; points on other servers are hidden here by default.

Names you gave devices in other rooms are reused: a point with the same SE name as one already mapped elsewhere is suggested with the name you chose there.

#Room Templates

A Room Template saves the devices of a tested room: what each device is, its name, whether it is hidden or off, its tags and any scene values you changed — and which SE point each device uses, by name. Point ids differ from room to room, but rooms of the same kind expose points with the same names, so another room can be matched automatically.

• Save a room as a template — pick a room that already has its devices, give the template a name, and press Save.
• Open a template to see its devices and the SE points they use. Remove a device from a template, Rename or Delete the template. None of this changes rooms that were already set up from it.
• Import from another site copies a template from a hotel you manage. It works wherever rooms expose points with the same names.

#Roll out

Roll out gives a template to several rooms at once.

1. Choose the template, press Scan SE and choose the building.
2. Each room is matched to the SE space with the same name (Room 0101 matches room 101). If a name matches more than one space, or none, the room is left for you to pick the space. Rooms that already have devices are unticked.
3. Press Read for the ticked rooms. For each room you see how many of the template's devices were found; anything missing is listed by SE point name, and SE points the template does not know about are mentioned too.
4. Press Apply. Rooms are linked to their SE space and device group; devices are created with the template's names, tags and scene values. A device whose required point is missing is skipped and reported, never created half-working. Devices a room already has are re-mapped but keep their names and settings.

Then run Check now in the Dashboard's Room checks to see that every room answers.

Settings

#Presets

Presets holds each device's scene values: Bright and Dimmed for lights, Cool, Neutral, and Warm for thermostats. Every device follows its type's defaults until you change one of its values — changed values are marked custom. Reset to defaults makes it follow the defaults again.

Values outside what a device accepts (for example a level above 100) cannot be saved.

#Tags

The Tags tab holds the site's tag list. A tag says what a device is for (Reading lights) or which devices belong together as one control. Its name is what guests read, and can be changed at any time. Add tag creates a new one; Delete removes it from every device that carries it. A tag is put on a device when you edit the device in Provisioning → Devices.

#Sites

The Sites tab holds the hotel's connection to its building system: the time zone (for housekeeping times and daily reports), the SE device group new rooms are addressed through, and whether the devices are Simulated or Live (see Simulated and live). Only a Devices admin can switch to Live. The building system's credentials are not kept here — they are secrets of the IoT service.

#Discovery

SE can show the same physical point through more than one automation server (for example ES HQ Pullman and Automation Server), and only one of them works — mapping the wrong one gives a room that looks complete and controls nothing. List the server(s) your hotel uses, in order. Points on other servers are then hidden by default and never suggested. Leave it empty if your SE only shows each point once.