Overview
The 4Drivers Orvibo Account driver centralizes the connection to the Orvibo cloud for the whole project: it authenticates once with the customer's account and acts as a bridge for every companion device driver (lights, relays, sensors and keypads) installed in the project, which connect to it automatically (autobind).
- Authenticates with the Orvibo cloud through a Login Code generated by the dealer on behalf of the customer — no need to store the Orvibo account password in the driver
- Discovers the families (accounts/residences) and devices registered in the Orvibo cloud
- Acts as the intermediary for each device's companion driver — every one of them connects to this driver via autobind and picks the matching device
- Real-time feedback since version 1070: besides the traditional periodic polling (still used as a fallback), the driver receives instant state updates through the 4Drivers Cloud Bridge — a dedicated 4Drivers WebSocket that avoids the 1-minute-plus delay that Orvibo's own polling had on its own
- Developer support actions: list families and list every device on the account
Install only one instance of this driver per project — it represents the Orvibo account as a whole, not a specific device.
How the Integration Works
Unlike a single driver with every control built in, the Orvibo integration is split into two layers:
- 4Drivers Orvibo Account (this driver): one instance per project, handles authentication with the Orvibo cloud, discovers the account's devices and keeps the instant-feedback bridge with the 4Drivers Cloud server alive.
- Companion drivers per device type: one driver for each physical Orvibo module/appliance installed in the house, which connects automatically to this account driver (autobind through the
ORVIBO_DEVICE connection) and, on its own Properties screen, uses a Devices ID list to pick exactly which device on the account it represents.
Supported Devices
| Companion Driver | Device Type | Notes |
|---|
| 4Drivers Orvibo Dimmer-ONOFF | Lights (light channel) | Dimmer or On/Off mode via the Light Type property. Supports Auto Detect and keypad LED binding (on/off color) when wired to a MixSwitch button |
| 4Drivers Orvibo Relay Module | Relays | Up to 4 relay outputs per driver instance, each with its own device selector (Devices ID 1-4) and state readout |
| 4Drivers Orvibo Sensors (Contact Sensors) | Contact sensors (doors/windows) | Up to 4 sensors per instance, each with contact state and battery percentage |
| 4Drivers Orvibo Sensor Temperature Humidity | Temperature/Humidity sensor | Independent selection of the temperature sensor and the humidity sensor (may or may not be the same physical unit), with a configurable timeout and battery readout |
| 4Drivers Orvibo MixSwitch Keypad | MixSwitch Keypad | Integrates the Orvibo keypad's physical buttons into Control4 |
Each companion driver is added to the project manually — one instance per physical module (e.g. a 4-channel Relay Module = one instance covering all 4 relays). Once added, it connects to this account driver on its own.
Requirements
- An active Orvibo account with the devices already registered in the customer's Orvibo/MixSwitch app
- A Login Code generated by the dealer at 4drivers.com.br/orvibo_code, filled in with the customer's account details
- A controller with internet access (communication with the Orvibo cloud and with the 4Drivers Cloud Bridge)
Properties
Orvibo Account
| Property | Type | Default | Description |
|---|
| User: e-mail | String | — | The customer's Orvibo account e-mail |
| Login Code | String | — | Code generated at 4drivers.com.br/orvibo_code to authenticate the account without exposing the password |
| Orvibo Validation | String | — | Shows whether the token was generated and validated correctly (read-only) |
| Check States | Number (60-3600) | 120 | Polling interval in seconds against the Orvibo server — used as a fallback alongside the instant feedback from the 4Drivers Cloud Bridge |
Cloud Settings
| Property | Type | Default | Description |
|---|
| Cloud Status | String | — | 4Drivers cloud/license status (read-only) |
| Automatic Updates | List | Off | Enables/disables automatic driver updates via DriverCentral |
Driver Info
| Property | Type | Default | Description |
|---|
| Debug Mode | List | Off | Print shows the traffic with the Orvibo cloud in the Composer log. Turn off after commissioning |
| Driver Key | String | Trial | 4Drivers license key |
| Validation | String | — | License validation status (read-only) |
| Message | String | — | Used to inform the dealer of something, when needed (read-only) |
| Driver Version | String | — | Installed driver version (read-only) |
Actions
| Action | When to use |
|---|
| List Families | Fetches the families (accounts/residences) tied to the login. Mainly used for troubleshooting |
| List Devices | Fetches every device on the account from the Orvibo cloud. Mainly used for troubleshooting |
Connections
| Connection | Description |
|---|
| Orvibo Devices | Automatically connects (autobind) to the companion drivers for lights, relays, contact sensors, the temperature/humidity sensor and MixSwitch keypads |
Step-by-Step Setup
1 — Add the account driver to the project
- Copy the driver to the Composer drivers folder
Windows: C:\Users\[user]\Documents\Control4\Drivers\
- In Composer Pro, search for 4Drivers Orvibo Account and drag it into the project — only one instance per project
2 — Generate the Login Code and authenticate
- Go to 4drivers.com.br/orvibo_code and fill in the customer's Orvibo account details to generate a Login Code
- Open the driver's Properties tab in Composer
- Fill in User: e-mail with the account's e-mail and paste the code into Login Code
- Confirm that Orvibo Validation shows the token as validated
If validation fails, generate a new Login Code at 4drivers.com.br/orvibo_code and confirm the e-mail entered exactly matches the customer's Orvibo account.
3 — Add one companion driver per device/module
- For every light, relay module, contact sensor, temperature/humidity sensor or MixSwitch keypad physically installed, drag the matching companion driver (see the Supported Devices table) into the project
- The connection to the account driver is automatic (autobind) — no manual binding needed
- On the companion driver's Properties, click Devices ID (dynamic list) to refresh and pick the matching Orvibo device. Repeat for every channel when the driver has more than one (e.g. a Relay Module with 4 outputs)
- Confirm in Device ID Selected that the correct device was bound
4 — Adjust polling
On the account driver's Check States property, set the fallback polling interval (in seconds) against the Orvibo server. Since the main feedback already arrives in real time through the 4Drivers Cloud Bridge, the default value (120s) is usually enough.
5 — Finish up
- Make sure Debug Mode is set to
Off
- Test turning lights and relays on/off, contact sensor states, and temperature/humidity readings
Setup complete. The driver will keep states updated in real time through the 4Drivers Cloud Bridge, with periodic polling as a fallback.
Troubleshooting
| Issue | Solution |
|---|
| Orvibo Validation doesn't validate / authentication error | Generate a new Login Code at 4drivers.com.br/orvibo_code and confirm the e-mail entered exactly matches the customer's Orvibo account |
| Devices ID shows empty on the companion driver | Confirm the account driver already authenticated (Orvibo Validation ok) and that the device is registered and online in the Orvibo app. Use the List Devices action on the account driver to check |
| State updates take a while | Confirm the controller has stable internet access. Instant feedback depends on the 4Drivers Cloud Bridge; if it drops temporarily, the driver falls back to polling (Check States) until it reconnects |
| MixSwitch keypad doesn't trigger the linked light | On the light's companion driver, confirm the Id do Botao Conectado binding and the configured LED colors |
Technical Information
| Item | Value |
|---|
| Protocol | HTTPS — Orvibo cloud API, called directly from the controller |
| Authentication | Login Code exchanged for a session token (the Orvibo account password is never stored) |
| State updates | Instant feedback via a dedicated WebSocket (4Drivers Cloud Bridge) + periodic fallback polling (Check States property) |
| Communication with companion drivers | Control4 virtual binding (class ORVIBO_DEVICE, autobind) |
| Persistence | Session token, families and device list stored in PersistData — survive a controller restart |
Change Log
| Version | Changes |
|---|
| 1050 | Initial Release |
| 1062 | Fix in device listing and state feedback |
| 1070 | Instant feedback via 4Drivers Cloud Bridge, replacing the sole reliance on Orvibo's periodic polling |
| 1071 | MixSwitch keypad integration |
| 1072 | Server connection optimized |
After the driver was reorganized into an account driver plus separate companion drivers, the version numbering for this account driver restarted — the entries above preserve the feature history even though it spans both numbering schemes.