CASAMBI BLE Light Support

stefdewilde · February 20, 2026, 7:20pm

@superkikim Wow! That would be amazing! I also have a Winsol setup. Adding the wind sensor would be amazing. That way I would be able to open my screens when there is too much wind

superkikim · February 20, 2026, 8:31pm

@rankjie, I have updated the PR.

All,

Until it is merged and updated by @rankjie and/or @lkempf, you can add this repo as a custom repo in hacs:

The base is the same as rankjie/lkempf, therefore, when they release a new version with these features, you can remove mine and use the official one. Your entities will be retained.

New features

cover platform: Casambi blinds/shutters exposed as HA cover entities (open/close/position)
cover platform: Winsol Lamel venetian blinds with louvre position slider in degrees (0–142°)
switch platform: Automatique / Intelligent switches for Winsol Lamel Intelligent (Star)
button platform: Commencer/Arrêter toggle button (louvres 0°↔142°)
number platform: Shadow/Sun (%), louvre position (°), Cool/Warm (°C) sliders
sensor platform: environmental sensors for Sensor Platform V4 (wind, solar, rain, PIR) + Lamel module internal temperature

Bug fixes

Light platform: EXT/ mode units no longer appear as lights
Switch sensor: BT repeaters (mode Sensor) no longer create spurious switch entities
Cover: fixed Winsol position convention (dimmer=0 = open, not closed)
Startup: transient BLE failure at boot (exchangeKey) now triggers automatic HA retry instead of permanently blocking the integration

Work in progress:

The rain sensor currently shows raw values (1 = dry, 5 = rain — to be confirmed through weather observation). A fix will follow.

The PIR sensor always reads 0. Not sure I’ll have any way to use it. I think there’s no PIR sensor connected to the module on the Winsol pergola.

The lamel main entity sliders need some creative work. I’ll improve them.

rankjie · February 21, 2026, 10:03am

I’ve merged your code and released it as a new dev version. Anyone using the newly supported device types, feel free to check it out!

I’m so happy to see more people contributing to improving this integration!

stefdewilde · February 21, 2026, 10:30am

Thanks @rankjie and @superkikim

I’ve updated with the new dev version.

The Wind sensor: is this in km/h?
Rain sensor: I noticed only two values: 1 for no rain and 5 for rain

superkikim · February 21, 2026, 12:13pm

Yes as said on my post, rain I will fix it during the weekend . I needed some rain to be sure.

As per wind, I don’t know the unit. It’s the same as in the casambi app. My guess is it’s indeed kmh.

I will also add the sensor switches given I want to make automations from HA therefore I need to be able to turn them off.

Disclaimer on this: Winsol advises on the risks of disabling the sensors given there are automations to prevent lamels to freeze and jam or zips to ve damaged by wind. So if you switch them off, you need to make your own safety automations in HA

stefdewilde · February 25, 2026, 4:31am

Hello,

Is there no stop button available?

Thanks

superkikim · February 25, 2026, 10:10am

For the covers ? There are no stop button in the casambi app. You select the % of where you want the cover to be. At least for my winsol modules.

I’m used to use the slider of the entity (if you click the cover, you get a slider). I made myself a cover dashboard…

And for automation, I use %

superkikim · March 3, 2026, 8:41pm

hey @rankjie

The new PR is ready.

Cover platform (fix) — _is_cover_unit was matching all EXT/* modes; narrowed to EXT/1ch/Dim only to avoid false positives with other EXT-based devices (e.g. Sensor Platform V4)
Environment sensors (fix) — rain and PIR were exposed as SensorEntity; converted to BinarySensorEntity with device_class: moisture and device_class: motion respectively. Also fixed an AttributeError on wind and solar sensors caused by missing SensorEntity property overrides (state_class, native_unit_of_measurement, etc.) — TypedEntityDescription does not extend SensorEntityDescription, so HA’s cached properties were raising instead of falling back
White Color Balance (new) — white_balance attribute on the light entity, casambi_bt.set_white_balance service, and a number slider entity using translation_key
Switch sensor (fix) — button numbering corrected for PTM215B; detection changed to mode-based logic ("Kinetic" in mode) instead of relying on fallback UNKNOWN controls
Diagnostics (new) — diagnostics.py wiring up HA diagnostics support
Translations (new/completed) — French and Italian added from scratch; German and Dutch completed with entity names and missing config flow strings
ruff.toml (fix) — added exclude = ["test_*.py"] so CI does not lint the existing test scripts at repo root

superkikim · March 3, 2026, 9:13pm

All. I have published prerelease 1.9.0-dev3. You can update if you used my repository as custom repo in HACS GitHub - Superkikim/casambi-bt-hass · GitHub

Disclaimer: These are hacks in the HA integration. I didn’t make any changes in the casambi-bt-revamped lib. I might do this so it can support more devices rather than parse data from raw data in the integration. That said, these hacks should be as reliable as they get.

Tested with following devices:

LEDsGO / Winsol Lamel Intelligent V4.1 TA16 180
LEDsGo / SO! V4.1
LEDsGO / Winsol Starlight
LEDsGO / Sensor Platform V4
ARDITI GmbH / RGB-TW (Evo)
LEDsGO / Winsol T/W
EnOcean / EnOcean PTM215B/PTM216B

Rain and PIR sensors are now correct. Yet again, not sure PIR sensor on Winsol is used. ^^

I have added WhiteColorBalance to Arditi RGB-TW modules.

0% = 0 white in the color
100% = full white (remove color completely)

venitian pergola cover has been improved. Now there is a separate slider for blade position (0 to 142°)

subtrEM · March 5, 2026, 2:23pm

Thanks a lot for your build, i am running 1.9.0-dev3, no serious trouble.
Lost the up/down light vertical distribution in Occhio Mito fixture (was shown as a cover, “entitiy no longer provided”), going back to 1.9.0-dev2 did not solve this.

EnOcean PTM215B/PTM216B switches are ordered as follows:
—±–
| 4 | 2 |
—±–
| 1 | 3 |
—±–
No big harm, just don’t change it too often (would break automations)
I have a presence (PIR) + lux sensor (DALI2 Sensor) fitting in the Casambi network, it is not discovered in HA. Anything needed to make it show up?

superkikim · March 5, 2026, 3:51pm

Let me check the buttons. I tried to applythe same order as in the cadambi app. I’ll check ifI didn’t make a mistake. If so I’ll make a last correction in next iteration. Seems to me it’s important to have is numbered the same in HA as in Casambi app.

Please the following fir your occhio and enocean:

Click the device, click the menu and “recreate entities”

Let me know if slider is still.missing and if buttons order still wrong.

subtrEM · March 6, 2026, 9:32am

Recreated entities as you suggested, reinstalled 1.9.0-dev3 for good measure, same behavior:

PTM216B same switch assignment, tried on a couple of switches (as said, no big deal for me)
Occhio Mito vertical distribution entity not provided

superkikim · March 11, 2026, 9:20am

Can you share de details and attributes of your occhio mito in HA ?

and is it correctly seen as a light now ?

subtrEM · March 11, 2026, 5:55pm

Here the entities and attributes of the fixture, with the “cover” standing in for the vertical light distribution. “Light” is the on-off switch. “mito_aura_illuminance” is the dimmer.

superkikim · March 11, 2026, 9:32pm

ok, Got it. prerelease 1.9.0.dev4 has been released.

Thank you. Just fixed it. I fine tuned the cover filter to avoid catching wrong devices. The new filter is: EXT/1ch/Dim + DIMMER AND No other light controls = Covers

So now, if TEMPERATURE or RGB or VERTICAL is found, it will never be considered a cover.

When you update to v1.9.0.dev4, you should first delete the faulty entity. If you can, best might even be to remove entirely your casambi network, update the integration, and then restart HA. Adding the network should recreate all your entities correctly.

Regarding enOcean, the Casambi App shows the following order

I have clicked the buttons in sequence, and they are correct on my side.

As per the EnOcean button events, my implementation seem to miss events because of the nature of BLE events that can come in wrong order.

I have reverted to what was happening with v1.8.2.dev5 from Rankjie, yet keeping my casambi_bt_button_event addition.

Regarding your question about

I have a presence (PIR) + lux sensor (DALI2 Sensor) fitting in the Casambi network, it is not discovered in HA. Anything needed to make it show up?

Let me see if I can give you a script that would parse the data for your network, and then I will analyze and see if/how we can filter and handle these. I might ask you for some tests/investigations if you don’t mind.

subtrEM · March 12, 2026, 10:38am

cover.mito_aura was unavailable in 1.9.0dev3 (and *dev2 also), after deletion of Casambi network and upgrade to 1.9.0dev4, "cover"does not show up as entity.
Going back to 1.9.0dev1 by rankjie, entity is back as cover with attributes

device_class: blind
friendly_name: Mito aura
supported_features: 7
current_position: 100

Let me know if (and how) i can further assist in this.
Cheers

superkikim · March 12, 2026, 10:57am

Let me write you a PM