Roraima Vendor Guide
Manage automations
Build and review automation scenarios
An automation scenario combines an optional trigger, up to three conditions and one or more actions for connected devices. Use the scenario list to find, create, edit, duplicate, test or remove scenarios in the current business or selected customer context.
Menu path
Owner: Vendor Back Office → Locks and devices → Scenarios
Authorized Supplier: select the customer in the supplier dashboard, then open the Scenarios area for that customer.
Find a scenario
Enter text in Search scenarios by name... and select Search. The form reloads the results and can match the scenario name, description or an exact numeric ID. The search remains applied while you move through result pages.
| Label | Purpose | Instruction | Requirement or condition |
|---|---|---|---|
| Search scenarios by name... | Finds a scenario | Enter part of the name or description, or the exact ID | Optional |
| Search | Applies the search | Select it to reload the filtered scenario list | Use after entering or clearing the search text |
The list shows ID, Name, Description, Steps, Status and Actions. Next to the number of steps, each scenario shows its kind: Automation, when its first step is a trigger, or On request. Running means an automation is currently listening for its trigger; it is separate from the scenario's Active status. Above the list, Scenarios running: [count] of [max] shows how many automations are running, together with what a running automation costs.
Use Edit to open the scenario, Duplicate to create a copy, Test to run a controlled test, Start or Stop to switch an automation on or off, and Delete only when the scenario is no longer required.
An automation linked to a listing in the Automations during the stay field of the listing's Units and access tab (see Booking configuration) runs only while a guest is there. Its row shows "During stays:" followed by the listing names instead of Start, it is not counted in Scenarios running, and its Operation field in the editor says the same. To switch it on with Start, first remove the link from the listing.
Create or edit a scenario
Select Add scenario or Edit. The editor contains three tabs:
- AI Draft creates a suggestion from a description.
- Guided builder provides cards and fields for triggers, conditions and actions.
- JSON code is the advanced structured editor and is the default tab on a clean browser.
| Label | Purpose | Instruction | Requirement or condition |
|---|---|---|---|
| Name * | Identifies the scenario | Use a short name that describes the result | Required |
| Description | Explains the scenario | Add a brief operational summary | Optional |
| Status | Enables or suspends the saved definition | Select Active for normal use or Disabled to keep it unavailable | Defaults to Active; does not arm the trigger by itself |
Choose what starts the scenario
In Guided builder, a new scenario begins with Manual execution. Select Change trigger when the scenario must listen for an event or schedule.
| Trigger card | Use it for |
|---|---|
| Manual execution | Buyer-requested execution or another allowed product lifecycle action without an automatic trigger |
| At specific times and days | Daily, weekday, weekend, selected-day or advanced schedules |
| Device state change | A change such as open to closed or off to on |
| Value crosses a threshold | A measurement moving above, below or across a chosen value |
| Condition sustained for N minutes | A condition that must remain true for a set duration |
| Time + device state | A device condition that may trigger only inside a time window |
Changing the trigger type discards the current trigger settings, so review the confirmation before continuing.
Readings of the Zigbee and Matter devices connected to the Roraima Hub, such as temperature, humidity, a water leak or the power used by a plug, can be chosen like any other measurement, for example in Value crosses a threshold. They reach Roraima as soon as the device sends them.
Add conditions and actions
Conditions are optional filters for the first action. Choose ALL (AND) when every condition must be true or AT LEAST ONE (OR) when one matching condition is enough. You can add up to three conditions.
Select Add action, choose the device, then choose one of its available actions. Add any requested value, delay or continue-on-error choice shown for that action. A scenario can contain up to nine actions, for a maximum of ten steps when a trigger is present.
Select Notify me by email to add a Notify me step. It has no device: when the scenario reaches it, Roraima emails your company address with the scenario name, the device and measurement that started it, the value read and the time. The same scenario sends at most one email every five minutes, and the step states the credits each email uses.
A Zigbee or Matter device of the Roraima Hub offers a single action, Set a value, and only when the device has something that can be set, such as switching a plug on or off. Choose What to set and the Value from the options the device provides; a sensor that only measures has no actions.
A device connected through Home Assistant can have several entities, for example a switch and a restart button. After you choose the action, the step shows Device entity \*: choose the entity that should carry out the action. The list offers only the entities you included on the device's edit page that can perform that action, and when only one can, it is already selected. If the entity does not belong to the device, cannot perform the action, or has not been chosen while several could, the scenario is not saved and the message names the device and what to change.
Use Save to remain in the editor or Save and close to return to the list.
Understand activation
Saving alone does not start a scenario. An Automation works only while it is running: select Start in the scenario list or in the editor's Operation field. From then on it starts by itself every time its trigger occurs, even after a service restart, until you select Stop; after it has run it keeps listening for the next occurrence. An automation is not linked to a product or to a bookable offer. Products and bookings use On request scenarios, which start when the product, the booking or Test calls them.
Before relying on an automation, use Test, check the result and confirm that every selected device is connected and exposes the required action.
Related guidance
Read Use the AI-assisted builder for the AI drafting workflow. Use Manage devices when a required device or capability is missing. Authorized Suppliers should also read Work for a customer.
Matter™ and Zigbee are trademarks of the Connectivity Standards Alliance. Other trademarks mentioned belong to their respective owners.