Full local Home Assistant integration for BleBox µWiFi / wBox devices, including Kontakt-Simon Simon GO wall switches.
It replaces the official BleBox integration and adds what that one never exposed: physical button presses as real events, the button backlight, the BleBox cloud tunnel, overload protection, relay behaviour after a power cut, and the ability to change what each button does.
- Why not the official integration
- Supported devices
- Installation
- Entities
- Configuration
- Migrating from the official integration
- Troubleshooting
- How it works
- Contributing
The official BleBox integration gives you the relay, power, energy and firmware, by polling every five seconds. It cannot see what the wall switch itself is doing: pressing a button is invisible unless it happens to toggle that relay, and it exposes none of the device's configuration.
Official blebox |
BleBox Advanced | |
|---|---|---|
| Relay, power, energy, firmware | ✅ | ✅ |
| Button presses (short/long/press/release) | ❌ | ✅ pushed by the device |
| Button backlight (RGB) | ❌ | ✅ |
| BleBox cloud tunnel on/off | ❌ | ✅ |
| Overload threshold, restart behaviour | ❌ | ✅ |
| Change what a button does locally | ❌ | ✅ opt-in |
| Delivery diagnostics | ❌ | ✅ |
| Device coverage | ~37 device types | switchBox family, others by capability |
That last row is the honest trade. The official integration is written by
BleBox and covers their whole range through blebox_uniapi. This one is built
around devices with physical inputs and detects capabilities at runtime, so it
should work on other hardware, but it has been verified on one product line, not
thirty-seven. For a BleBox device without buttons, the official integration is
the better choice.
Any BleBox device with physical inputs. Capability is detected at runtime, not hardcoded: inputs are discovered from the device, entities appear only when the device reports the underlying setting, and value ranges come from the device's own constraint metadata.
The Simon GO range is switchBox hardware underneath, so the whole range is
supported rather than one model of it. Verified on a Simon GO switch reporting
switchBox, firmware 0.1502, API level 20220505. switchBoxD, buttonBox
and actionBox hardware should work too.
Requires Home Assistant 2025.3.0 or newer. Older cores are missing an entity-platform API that every platform here imports, so the integration cannot load at all on them, not even the button events. No cloud account, no BleBox app, nothing exposed to the internet.
Or add it by hand: HACS → ⋮ → Custom repositories →
https://github.com/sdebasek/blebox-advanced, category Integration.
Restart Home Assistant, then add the integration. HACS installs the files but does not configure anything, so this is a separate step:
That button only works once the integration is installed and Home Assistant has restarted. Before that it reports that the integration does not support configuration via the UI, because Home Assistant does not know the domain yet.
Copy custom_components/blebox_advanced/ into your Home Assistant
config/custom_components/ directory and restart.
| Entity | Purpose |
|---|---|
event Button 1…n |
One per physical input: short_press, long_press, press, release. An input with no events selected is disabled by default |
switch Relay |
The relay, polled every 5s |
sensor Active power |
Watts drawn right now |
sensor Energy this period |
kWh for the device's current measurement period |
update Firmware |
Version reported by the device, with install |
light Button backlight |
The illuminated buttons, RGB colour |
switch BleBox cloud tunnel |
The device's outbound tunnel to BleBox's cloud |
switch Status LED |
The device's status indicator |
switch Access point |
The device's own WiFi access point, often left on and unprotected |
number Overload threshold |
Power above which the device cuts its own relay; 0 disables |
select State after power cut |
Relay behaviour on power-up, one per relay |
binary_sensor Callback delivery |
On when button presses are not reaching Home Assistant |
binary_sensor Overload protection |
On when the device has tripped, reason preserved |
binary_sensor Power measurement calibrated |
Diagnostic |
sensor Uptime, Timer remaining |
Diagnostic, disabled by default |
select Button n … action |
Opt-in. What a button does to the relay locally |
Devices are discovered over zeroconf and DHCP, or you can enter an IP address. The flow identifies the device, discovers its physical inputs, and asks which events you want per input.
See docs/setup.md for the full walkthrough: automatic versus manual configuration, every option, how to use the events in automations, and how the device's action slots are managed.
- Install this integration and add your device.
- Delete or ignore the official BleBox entry. Running both works but gives you two relay switches, two power sensors and two device rows.
- Update anything referencing the old entity IDs. They differ, because the
domain is
blebox_advanced.
The official energy sensor carried no state_class, so it produced no long-term
statistics and there is none to migrate.
Start with the Callback delivery sensor and the Repairs panel. Between them they usually name the cause, distinguishing a device that never called from one Home Assistant rejected.
The most common cause of "setup works but no events arrive" is an isolated IoT VLAN: the device needs to reach Home Assistant, not just the other way round.
See docs/troubleshooting.md for the symptom table, firewall guidance, and how to ask the device what happened to its last call.
Button events are pushed by the device over the local network, so they arrive immediately. A button the device binds to the relay also moves the switch at once, rather than at the next poll. Everything else is polled: relay and power every 5 seconds, settings and the rest of the device metadata every minute.
Some of the device endpoints used are not in any published BleBox specification. All device communication is isolated in one module so a firmware change is contained there, and the event receiver does not depend on it.
See docs/device-api.md for the endpoints, what is documented versus reverse engineered, and the behaviours established by experiment.
Keywords: BleBox, wBox, µWiFi, Simon GO, SIMON GO SWITCH, Kontakt-Simon, Simon 55 GO, switchBox, switchBoxD, buttonBox, actionBox, Home Assistant, HACS, custom integration, wall switch, button events, local push.