Overview
The 4Drivers Sensibo Connect Hub driver integrates Sensibo devices (Sky, Air, Pure, Room, etc.) with the Sensibo Cloud platform directly into the Control4 system. Communication happens directly from the Control4 controller to the Sensibo cloud (home.sensibo.com/api/v2) through a personal API Key — it does not depend on any PC, gateway, or local service running on the customer's network.
- Authenticates with the Sensibo cloud via API Key
- Automatically discovers every device (pod) on the account
- Controls on/off, mode (Cool/Heat/Fan/Dry/Auto), temperature, fan speed and swing (vertical and horizontal) for each device
- Built-in responsive HTML interface, available on any Control4 Navigator
- 100% generic: any feature the Sensibo cloud lists in the device's
remoteCapabilities (swing, display light, and anything Sensibo may add in the future) automatically becomes a control in the interface — no driver update required
- Can feed a native Control4 thermostat driver (optional companion proxy) so each AC shows up as a standard thermostat card
- Fires Hub Online and Hub Offline events based on Sensibo cloud availability
HTML Interface
Available on any Control4 Navigator — physical touchscreen, iOS/Android app, and browser.
| Section | Description |
|---|
| Device List | Every pod found on the Sensibo account, with name (room name configured in the Sensibo app), summary status and a quick temperature adjustment |
| Status Panel | Selected device: on/off, mode, current temperature and humidity, setpoint, fan |
| Extras (dynamic) | One selector per feature the device actually supports — vertical swing, horizontal swing, display light, and anything else Sensibo reports |
| Language | Portuguese or English — switched through the Language property, applied instantly without a reload |
Requirements
- An active Sensibo account with at least one device registered in the Sensibo app
- An API Key generated by the customer/dealer at home.sensibo.com/me/api — see the step-by-step below
- Control4 OS 3.0.0 or higher
- A controller with internet access (direct communication with the Sensibo cloud)
Properties
Sensibo Cloud
| Property | Type | Default | Description |
|---|
| API Key | Text | — | Personal API Key generated at home.sensibo.com/me/api. See the creation walkthrough below |
| Poll Interval (s) | Number | 60 | Interval, in seconds, between periodic status queries to the Sensibo cloud (20 to 600s) |
Driver License
| Property | Type | Default | Description |
|---|
| License Key | Text | Trial | 4Drivers license key. Left blank/Trial, the driver runs in a time-limited evaluation mode |
| License Status | Text | — | Current license state (read only) |
Interface Preferences
| Property | Type | Default | Description |
|---|
| Language | List | Portuguese | HTML interface language: Portuguese or English |
Driver Info
| Property | Type | Default | Description |
|---|
| Debug Mode | List | Off | When set to Print, shows traffic with the Sensibo cloud in the Composer log. Turn it off after commissioning |
| Status | Text | — | Current driver state (read only) |
| Version | Text | — | Installed driver version (read only) |
| Message | Text | — | Driver messages for the integrator (read only) |
Actions
| Action | When to use |
|---|
| Discover Devices | Fetches the device list directly from the Sensibo cloud and syncs the interface. Use it whenever you add a new device to the Sensibo account. |
| Update Status | Queries the current status of every device found. Useful to force an immediate refresh. |
| Test Connection | Checks whether the API Key and the connection to the Sensibo cloud are working. |
Events
| Event | When it fires |
|---|
| Hub Online | Communication with the Sensibo cloud was restored after being offline |
| Hub Offline | The driver detected a communication failure with the Sensibo cloud (3 consecutive failures) |
Use these events in programming to notify the end user when the Sensibo cloud connection is lost or restored.
Control4 Thermostat (optional)
For a Sensibo device to show up in Control4 as a standard thermostat card (the same screen used by any factory thermostat), also install the companion driver 4Drivers Sensibo Thermostat — one instance per device you want exposed that way.
- The companion driver connects to this hub automatically (autobind) — no manual binding required
- Once added, it asks the hub for the device list by itself a few seconds after loading
- When the device is chosen in the companion driver's Device Name property, the card renames itself automatically to the chosen device's name
- Supports Presets (saved combinations of mode/temperature/fan/extras, applied with one tap)
- Fully dynamic Extras tab, plus dedicated buttons for Dry and Auto modes (no native equivalent on the Control4 thermostat card)
See the 4Drivers Sensibo Thermostat driver documentation for installation and usage details.
Step-by-Step Setup
1 — Add the driver to the project
- Copy the driver into the Composer drivers folder
Windows: C:\Users\[user]\Documents\Control4\Drivers\
- In Composer Pro, search for 4Drivers Sensibo Connect and drag the 4Drivers_Sensibo_Gateway_UI driver into the project
2 — Create the API Key on Sensibo
The API Key is what authenticates the driver with the customer's Sensibo account — without it, the driver cannot discover or control any device. It is generated directly on the Sensibo website/app, using the customer's own account:
- Go to home.sensibo.com/me/api in a browser (desktop or mobile) and log in with the Sensibo account's email and password. This screen can also be reached from the Sensibo app, under the account settings menu
- If the page opens on a different section, click the Menu button (the three-line icon, usually top-left) and look for the API option
- Click Create an API Key
- Type a name to identify this key — for example
Control4 or 4Drivers — and confirm by clicking Create an API Key again
- The generated key appears on screen as a long string of letters and numbers. Click to copy it
- Back in Composer Pro, open the Properties of the 4Drivers_Sensibo_Gateway_UI driver and paste the copied value into the API Key field
The API Key grants full access to every Sensibo device on the account — treat it like a password. If you ever need to revoke access, the same home.sensibo.com/me/api screen lets you delete or generate a new key at any time, without affecting the account login.
As soon as a valid API Key is entered, the driver automatically tests the connection and triggers a device discovery on its own — you don't have to click any Action manually, though you can confirm it by running Test Connection.
3 — Discover the devices
- In the driver's Actions, click Discover Devices
- Check the Status property for the count of devices found
4 — Configure Navigator visibility
In the room/location properties, Navigator tab, set the driver as Visible in the desired Experience Menu — we recommend Climate/Comfort.
5 — (Optional) Install the native thermostat
- Copy the 4Drivers Sensibo Thermostat driver into the drivers folder and drag it into the project — one instance per device
- The connection to the hub is automatic (autobind)
- In the companion driver's Properties, choose the device in Device Name — the card renames itself automatically
6 — Verify the HTML interface
- On the Navigator, open the Sensibo Connect item
- Confirm the devices show up with the correct status
- Test on/off, mode, temperature, fan and the controls on the Extras tab
7 — Finish up
- Make sure Debug Mode is set to
Off
Setup complete. The driver will keep device states up to date through automatic periodic polling.
Troubleshooting
| Problem | Solution |
|---|
| Authentication error / invalid API Key | Generate a new key at home.sensibo.com/me/api (see the step-by-step above) and paste it again into the API Key property. Use Test Connection in Actions to confirm |
| Devices don't show up | Run Discover Devices. Confirm the device is registered and online in the Sensibo app |
| Interface stays on "Loading..." and never lists the device | Normal for a few seconds right after opening the screen (the driver may still be querying the cloud). If it persists for more than a minute, run Discover Devices and check the Status property |
| Device shows up but doesn't respond to commands | Confirm the device is online in the Sensibo app. Use Update Status to force a fresh reading |
| Companion thermostat shows no devices | Confirm the hub has discovered the devices at least once. The connection between the two drivers is automatic (autobind) |
Technical Information
| Item | Value |
|---|
| Protocol | HTTPS — Sensibo Cloud API v2 (home.sensibo.com/api/v2), called directly from the controller |
| Authentication | API Key as a URL parameter (apiKey) |
| State refresh | Automatic periodic polling (Poll Interval property) |
| Communication with the companion thermostat | Virtual Control4 binding (class 4Drivers_Sensibo, autobind) |
| Persistence | Device list and license configuration stored in PersistData — survive a controller reboot |
| Minimum OS | Control4 3.0.0 |
Change Log
| Version | Changes |
|---|
| 1100 | Initial Release |