Qbus
qbus
The Qbus integration allows you to integrate your Qbus Control into Home Assistant. Qbus is a Belgian manufacturer of Home Automation systems.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
cover | Blind | |
climate | Thermostat | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (CO₂, humidity, light level, temperature) | |
scene | Scene (as a switch) | |
select | Mode picker (as switches) |
What people report
Qbus CTD controllers are supported; a duplicate MQTT add-on caused a light switching bug.
- Works3
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Qbus CTD01E to CTD03E (CTD 3.0) | Works | Main controllers listed as supportedSaved copySupported devices: CTD01E to CTD03E (CTD 3.0): main controllers (yellow).; CTD10 to CTDMax (CTD 3.5): main controllers (black).. Limitations: The integration does not provide a way to update the firmware on the devices. This can only be done with the configuration software System Manager. Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Qbus CTD01E+ dimmer | Works | Light toggled back off when a second Qbus MQTT add-on was running; resolvedSaved copyThe problem When I turn on a Qbus light entity (Qbus dimmer) with the on-off power button in any dashboard or via the settings-integrations menu it turns on, but in the integration the status immediately goes to off again while in reality the light is still on. Afterwards there is no way you can turn the light off again via the normal way. If you hit the power switch again in HA, it really doesn't do anything. The switch goes on and immediately back to the off state while in reality nothing changes, the light is still on. The only way to kill the light, is by setting a dim-% in the entity, … Excerpt saved from GitHub on 2026-10-23. | Issue #148374 · 2025-07 | |
| Qbus CTD10 to CTDMax (CTD 3.5) | Works | Main controllers listed as supportedSaved copySupported devices: CTD01E to CTD03E (CTD 3.0): main controllers (yellow).; CTD10 to CTDMax (CTD 3.5): main controllers (black).. Limitations: The integration does not provide a way to update the firmware on the devices. This can only be done with the configuration software System Manager. Excerpt saved from home-assistant.io on 2026-10-23. | Docs |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- MQTT
Details
| Installs (analytics) | 93 (0.01%) |
|---|---|
| Quality scale | Bronze |
| Added in | Home Assistant 2025.2 |
| Set up in the UI | Yes |
| Maintainers | @Qbus-iot, @thomasddn |
Devices listed in its documentation
- CTD01E to CTD03E (CTD 3.0): main controllers (yellow).
- CTD10 to CTDMax (CTD 3.5): main controllers (black).
Limitations from the docs
- The integration does not provide a way to update the firmware on the devices. This can only be done with the configuration software System Manager.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
