Roraima Vendor Guide
Manage devices
What you can do here
Use Devices to find, add, test, edit or remove the connected devices available to your business. A device is the connected hardware or service. It is not the product that a Buyer purchases, and adding a device does not make a product bookable.
Menu path
Owner: Vendor Back Office → Locks and devices → Devices
Authorized Supplier, for its own devices: Vendor Back Office → Seller Tools → My IoT Devices
An Authorized Supplier working for a customer uses the Devices area in the selected customer context. The device belongs to that customer.
Find a device
The list includes ID, Name, Type, Product model, Status and Actions. Use the filters above the list, then select Search. Search reloads the result list and keeps the filters while you move through result pages.
| Label | Purpose | Instruction | Requirement or condition |
|---|---|---|---|
| Search | Finds a device | Enter a name, device ID, type or product-model detail | Optional |
| Type | Limits results to one device type | Leave All selected or choose a type already used by your devices | Optional; combines with Search and Status |
| Status | Limits results by availability | Leave All selected or choose Active or Disabled | Optional; combines with Search and Type |
Use Edit to open a device, Test to check whether it can be reached, and Delete only when existing access to that device may be ended. Deleting a device can stop current Buyer access from working. A short note above the list states the current monthly price of a connected device.
Zigbee devices of the Roraima Hub
Zigbee sensors and plugs, such as temperature, humidity, door, water-leak or presence sensors, connect through the Owner's Roraima Hub. First plug a Zigbee USB stick into a USB port of the Roraima Hub. The stick is bought separately; any stick that zigbee2mqtt, the software the Hub uses for Zigbee, can drive will do, and Roraima keeps no list of models. The state of the Zigbee network and of the stick is shown in Locks and devices → Technologies, in the Zigbee tab (see Connect cloud accounts and gateways).
Then select Add device and choose the Zigbee card (With the Roraima Hub). Select Add Zigbee device and put the device into pairing mode as its leaflet explains. The card shows the search time left and confirms when the device has been added; below the search it shows only the devices that joined during this search. Give the device a clear name there, such as Bathroom sensor, and select Save name. With more than one Roraima Hub, each Hub has its own button under the name of its property.
The device then appears in this list by itself, with the type Zigbee device (Roraima Hub) and its latest readings under the name. Until the first reading arrives, the row shows No readings received yet.; battery sensors send a reading when the value changes. Its edit page links to Open the Roraima Hub settings, which opens the Zigbee tab of Technologies, and lets you change only the name and the status. Delete also removes the device from the Hub's Zigbee network. Remove, under the search, appears only for a device that joined the network but could not be added to this list.
Matter devices of the Roraima Hub
Plugs and other devices with Matter certification that use the property's Wi-Fi connect through the Owner's Roraima Hub, without a USB stick. The device has to be on the same network as the Hub.
The first time, open Locks and devices → Technologies and, in the Matter tab, select Activate Matter. The Hub activates Matter and saves a backup copy of it, which takes a few minutes; the box then shows Matter active.
Then select Add device and choose the Matter card (With the Roraima Hub). Enter the 11-digit code and select Add Matter device. The code is the one on the device's box. If the device is already in the brand's app, that code no longer works: enter the sharing code that the app gives you instead. The Hub looks for the device on the property's Wi-Fi, which can take a few minutes, and the card confirms with Device added. Give it a clear name there, such as Kitchen plug.
The device then appears in this list with the type Matter device (Roraima Hub), with its state and readings, such as the power and energy of a plug. You can switch it on and off from its edit page, and use it in scenarios. A device that connects other devices, such as the hub of another brand, is not added, and the card says so. Delete on its edit page also takes the device off the Roraima Hub; if the device was switched off at that moment, it has to be restored from its own app before it can be added again.
Choose the connection method when adding
Select Add device, enter a name, then choose one of the cards shown under Protocol. With the Zigbee and Matter cards no name is asked, as described in the sections above.
| Card | Use it when |
|---|---|
| Shelly — Through the Shelly cloud | You are adding a Shelly device. It connects through the Shelly cloud, so your Shelly Cloud account must be connected in Technologies |
| Home Assistant — Through your Home Assistant | The device is already represented in a Home Assistant instance you run, reachable from the internet through an https address. Without such an address, connect Home Assistant with the Roraima integration instead, as described below |
| Zigbee — With the Roraima Hub | You are adding a Zigbee sensor, plug or switch. The card appears when the Owner's Roraima Hub is online with Zigbee ready |
| Matter — With the Roraima Hub | You are adding a plug or another device with Matter certification that uses the property's Wi-Fi. The card appears only when the Owner's Roraima Hub has Matter active |
| MQTT — Through your MQTT broker | The device, for example a Shelly, Tasmota or ESPHome device, sends its data to an MQTT broker of yours that can be reached from the internet. Zigbee sensors and plugs do not need a broker: add them with the Zigbee card |
| iGloohome — iGloohome smart locks | You are adding a compatible iGloohome smart lock |
| Nuki — Nuki smart locks | You are adding a compatible Nuki bridge or smart lock |
| Tedee — Tedee smart locks | You are adding a compatible Tedee bridge or smart lock |
| TTLock — TTLock locks and key safes | You are adding a compatible TTLock smart lock or key safe |
Selecting a card shows a short description of that connection method underneath the row. For Shelly and the four lock brands, the description ends with a link to Technologies (Cloud Accounts for an Authorized Supplier), which opens in a new browser tab and takes you to the matching provider's account form. Connect the cloud account there before adding the device. Home Assistant and MQTT do not need a cloud account and do not show that link. The Zigbee card shows the Add Zigbee device button; the Matter card shows the 11-digit code field and the Add Matter device button. Both end with Open the Roraima Hub settings, a link to their tab of Technologies. An Owner without a Roraima Hub still sees the two cards, with the sentence "Zigbee and Matter devices need the Roraima Hub, a small unit installed at the property that connects them to Roraima. You can buy it from the Roraima Hub page." and the link Go to the Roraima Hub page. An Owner whose Hub does not have Zigbee or Matter ready does not see that card, and an Authorized Supplier working for a customer never sees them.
The protocol cards appear only while creating a device. Tuya is not among the connection methods offered for a new device today. Devices already added through Tuya remain in your device list and can still be edited normally; a Tuya cloud account you have already connected also stays connectable and manageable from Technologies. When you open an existing device to edit it, no protocol selector appears at all — the connection method is set when the device is created, and editing lets you update its type and configuration instead.
Add-device field reference
| Label | Purpose | Instruction | Requirement or condition |
|---|---|---|---|
| Name * | Identifies the device | Use a clear location or function, such as Living Room Switch | Required; not asked with the Zigbee and Matter cards, where the device takes the name it declares |
| Protocol * | Chooses the connection workflow | Select one of the cards above | Required when creating a device |
| Device type * | Selects the exact supported model | Choose the model that matches the device | Required; the list of models is limited to the protocol you selected. The Zigbee and Matter device types are never offered here, because the Roraima Hub creates them |
| Status | Controls whether the device is available | Keep Active for normal use or choose Disabled to suspend it | Defaults to Active |
| Shelly Device ID | Identifies the Shelly device in the Shelly cloud | Copy the Device ID from the Shelly app, under the device's settings and information | Shelly only; required. A Shelly device always connects through the Shelly cloud: the local-network option is not offered at the moment, because it needs a local gateway |
| Channel | Chooses an output on a multi-channel device | Use the channel required by the exact model; to use every output, add one device for each channel | Appears only for device types that use channels. The device keeps only the entities and readings of its own channel, plus the ones shared by the whole unit |
| Home Assistant address | Tells Roraima where your Home Assistant can be reached | Enter an https address that opens from outside your home network, for example the one provided by Home Assistant Cloud or your own domain | Home Assistant only; required. Home network addresses such as 192.168.1.10 or homeassistant.local, and addresses that start with http instead of https, are refused when you save |
| Long-lived access token | Lets Roraima read and control the entities you choose | In Home Assistant, open your profile, go to the Security tab and create a long-lived access token; copy it straight away, because Home Assistant shows it only once | Home Assistant only; required. Stored encrypted and left empty when you edit the device: leave it empty to keep the saved token |
| Device ID | Tells Roraima which entities belong to this device | With an administrator's token, enter the part shared by the entity names, such as shelly1pmg3_48f6ee981358; with another user's token, enter the full entity names separated by commas, such as switch.shelly1pmg3_48f6ee981358, sensor.shelly1pmg3_48f6ee981358_power | Home Assistant only; required. Entity names are listed in Home Assistant under Settings, Devices & services, Entities |
Connect your Home Assistant with the Roraima integration
An Owner can connect a whole Home Assistant instance to Roraima once, instead of adding its devices one at a time. Home Assistant opens the connection towards Roraima, so it needs no address reachable from the internet, and Roraima never holds a Home Assistant password or token. The Home Assistant tab is the last of the four tabs of the Technologies page, after Manufacturers, Zigbee and Matter, and is shown only to the Owner of the account, not to an Authorized Supplier or to someone working for a customer. The Roraima integration in Home Assistant links straight to this tab.
- Install the Roraima for Home Assistant integration in your Home Assistant. Add to Home Assistant,
at the bottom of the Home Assistant tab, opens it in the Marketplace of your Home Assistant (in HACS before Home Assistant 2026.11): install it there and restart Home Assistant.
- In Technologies, open the Home Assistant tab and select Create pairing code at the top. There is
no name to choose: the connection is called "Home Assistant", or "Home Assistant 2" and so on if you already have one.
- Your pairing code appears in place of the button, with a Copy button. It is shown only this once: if
you lose it, disconnect that connection and create a new one.
- In Home Assistant, add the Roraima integration and paste the code into its Pairing code box. Then choose the devices to
share with Roraima. None is selected at the start, groups are not offered, and you can share up to 256 devices per connection. You can change the choice at any time from the integration's options in Home Assistant.
- Back in the Home Assistant tab of Technologies, the connection shows Connected with the time of the last contact, and the
shared devices appear on their own in your device list, with the names they have in Home Assistant.
- Next to a shared device that turns on and off and that no product uses yet, the Home Assistant tab shows
Sell the use of this device, which works as described in the section below.
Each shared device works like any other device: choose its Buyer controls on its edit page, use it in products and scenarios, and test it. Its edit page says which connection it comes from and has no address, token or Discover entities, because its entities come from Home Assistant; renaming an entity in Home Assistant does not break the products and scenarios that use it. The connection itself costs nothing and does not count towards the device limit, while every device that appears has its monthly fee, like any other device, until you delete it. An account can have up to 10 active connections.
A device you stop sharing in Home Assistant stays in your list and says that it is no longer shared: its commands do not run, and every product that uses it, accommodation included, leaves sale until you share it again. Disconnect closes the connection at once, after a confirmation. Its devices stay in your list and their products leave sale until you create a new connection and enter its code in the integration. Removing the integration from Home Assistant has the same effect. In both cases the monthly fee of those devices continues until you delete them from Devices.
Connect a device managed by Home Assistant by address and token
Roraima reaches your Home Assistant over the internet and never enters your home network, so the address must be an https address reachable from outside your home. Save the device first. Then, on its edit page, select Discover entities: a table lists the entities found, each with an Include checkbox. For Home Assistant the checkboxes start empty. Tick only the entities Roraima should use, then save; the other entities are not kept. A device can keep up to 64 entities.
With an administrator's token, Discover entities finds the entities from the shared part of their names. With another user's token, status and commands still work, but the automatic list does not: write the full entity names in Device ID and select Discover entities again.
If the connection fails, the page shows a sentence that names the cause: an address on a home or private network, an address that starts with http instead of https, a token that Home Assistant rejected or that does not belong to an administrator, a Home Assistant that does not answer at that address, or an entity that does not exist. Fix the field it names and try again.
Roraima controls each entity only with the actions of its kind, and only those the entity supports. Switches, plugs, on/off helpers and fans turn on, turn off and toggle. Lights do the same and, when the light offers them, also take a brightness and a white colour temperature. Locks lock and unlock, and open the door when the lock has that function; they do not receive door codes, so booking codes need one of the lock brands in the cards above. Covers, gates and valves open, close, stop and move to a position; climate devices turn on and off and take a temperature and a mode; buttons are pressed. Sensors are only read. Scenes, scripts, automations, media players and vacuum cleaners cannot be controlled from Roraima, and Discover entities does not offer them.
A command counts as carried out only when Home Assistant shows the entity in the expected state a few seconds later, so a lock that did not move is never reported as unlocked. Otherwise the page says that Home Assistant did not carry out the command, the command costs no credits, and a paid use that cannot start leaves the Buyer's time or tokens available. A device saved earlier keeps its previous actions until you select Discover entities again, and an action that is no longer allowed is refused.
If you rename or remove an entity in Home Assistant, Roraima still knows it by its old name and its commands stop working. Test in the device list names the entities that are no longer there: open the device, select Discover entities, tick them again and save, then update the scenarios that use them.
Review Buyer controls when editing
After a device has been saved, its edit page can show Buyer controls. Use the available capability checkboxes to choose which actions a Buyer may use. Where the page provides labels for an entity or capability, use short names that describe the real device action.
Use Discover entities when that action is available and the connection details are complete. Finish with Save to remain on the page or Save and close to return to the device list.
Sell the use of a device
On the edit page of a device that turns on and off, such as a Shelly plug, a Tuya switch or a Home Assistant device, the Owner sees Sell the use of this device next to Save. It opens a new product in Equipment and spaces by time or by use with the device already chosen and a Ready-made scenarios row, described in Time and use. The button is not shown for locks, sensors, MQTT devices or Roraima Hub devices, for a Home Assistant device that is no longer shared, or when your plan does not include that category.
How many functions a device can have
Every entity, reading or command of a device counts as one of its functions, and a device can have up to 64, whatever its brand. Diagnostic and configuration functions that the brand marks as such do not count. If a device you have already added reports more after a new reading, Discover entities or a save, it keeps the functions it had before, so the listings and scenarios that use it keep working, and a notice at the top of its edit page says how many it reported. A new device that reports more than 64 is not added and nothing is charged.
Before using the device in a product or automation
Connect any required manufacturer account first. Then test the device and confirm that the required capabilities are available. A separate product may use the device, but the booking workflow applies only when the Owner's offer is a bookable product.
Related guidance
Continue with Connect cloud accounts and gateways for manufacturer accounts. Use Manage automations after the required devices are connected and tested.
Matter™ and Zigbee are trademarks of the Connectivity Standards Alliance. Other trademarks mentioned belong to their respective owners.