Cherubini Roller Shutters Controlled by Home Assistant – My Solution with RFXcom

Share your Projects!
1

Note:
This post is aimed at users who own Cherubini roller shutters and want to integrate them with Home Assistant. I found little useful info online, so maybe this thread helps you all. Feel free to add your tips or experiences—whether you use Cherubini or just Home Assistant!

:house: Starting Point: New build, standard shutters, no smart home planning

Like many others, we didn’t really think about smart features when building our home. We chose Cherubini shutters mostly because we liked their radio-based controls:

  • Individual adhesive radio wall switches

  • Remote controls, either:

    • simple (up to 7 devices)
    • „Large“, with scenarios (time‑or week‑based)

  • Optional weather station/wind sensor (mostly useful for awnings, less so for shutters)

:bulb: First Smart Home Steps: Shelly, Ikea Tradfri & Home Assistant

Our first smart project was automated porch lighting. Berker’s solution was expensive, so we went low‑cost with a Shelly switch—my first real smart‑home setup. Then we added:

  • Shellys for lights and switches
  • Ikea Tradfri
  • Home Assistant

But the roller shutters remained unsolved…

:no_entry_sign: Problem: Rollers not natively smart-home controllable

We wanted solar shading, e.g. halfway down at midday to reduce heat.
But:

  • You can’t create enough custom groups via Cherubini remotes for multiple scenarios
  • Shellys don’t work, because Cherubini uses one‑wire sequence control: Up → Stop → Down → … :roll_eyes:

Cherubini released a hub, but it’s:

  • Expensive
  • Closed‑source
  • Not compatible with Home Assistant

:bulb: Solution: RFXcom + Home Assistant = :partying_face:

I discovered a great alternative:
RFX-433 with Extended Motor Control

  • Supports rolling‑code Cherubini
  • Wi‑Fi—place it anywhere
  • Integrates with Home Assistant
  • Low cost

Installation:

  • Problemlos, nur durch eigene Fehler musste ich einmal die Firmware neu flashen.
  • Beim Anlernen habe ich versehentlich zwei Rolläden auf denselben Kanal gelegt – war aber leicht zu korrigieren.

Installation was easy (I only reflashed firmware once by mistake). During pairing I accidentally assigned two shutters to the same channel—but that was easy to fix.

Setup steps:

  1. Install the RFXcom integration in Home Assistant :white_check_mark:
  2. Pair each shutter individually using the RFXcom tool :white_check_mark:
  3. They were immediately recognized in HA :white_check_mark:
  4. Naming and assignment was straightforward :white_check_mark:

Result: I can now control my Cherubini shutters in a “semi‑smart” way through Home Assistant!

:gear: Current Capabilities

:white_check_mark: Standard Features:

  • Control via mobile app
  • Automatic down‑slit when sun is high
  • Up/down based on sunrise/sunset
  • Better signal range than remotes
  • Central control of all shutters

:warning: Limitation:

  • No position feedback—must use time‑based control (e.g., “drive down for 10 seconds”)

:wrench: Example Automations

1. Grouped control (e.g. south side, upstairs, downstairs)

  • Handled via scripts
  • Includes repetition and delays so shutters open one by one, triggering around 5 times each

2. Sun‑angle shading

  • Triggered by azimuth (sun angle)
  • A toggle on the dashboard enables “summer mode”
  • Adjustable thresholds per facade
  • Shutters move to “slit” position at certain sun angles, and go up again when angle changes

3. Automatic ventilation

  • At sunset the night mode triggers and shutters go down
  • If a window opens (tilt/full), the associated shutter moves to “slit”
  • After a set time, it fully closes again

4. Scenarios

  • “Wake Kids”: shutters open slowly over 10 minutes in steps
  • “TV Mode”: shutters move to “slit” to reduce glare
  • “Fire Safety”: all shutters go up automatically if smoke is detected
  • Dashboard: manual control of all shutters; long‑press sets them to “slit”
  • More scenes possible: Vacation, Sleep, Energy Saving…

:hammer_and_wrench: Issue: Shutters occasionally didn’t respond

This was due to the number of radio commands sent.
Tip: Cherubini remotes let you configure repeat count (e.g. 5 signals) — I matched that in RFXcom, and it’s now rock‑solid.

:camera_flash: Screenshots & Examples

Azimuth
Azimuth627×655 46.2 KB

Dashboad
Dashboad647×771 48.4 KB

Wiederholungen
Wiederholungen548×653 31.5 KB

:mailbox_with_mail: Conclusion

With an RFXcom module you get a cost‑effective, semi‑smart solution for Cherubini shutters integrated into Home Assistant. No position feedback, but a wide range of functions and high flexibility.

Questions, comments, or your own solutions? Please share them below!
:point_right:

1 Like
2

Hallo @JuggedHareBoy89 , danke für die ausführliche Beschreibung. Das könnte genau mein Problem mit meinen unsmarten Cherubini-Rollläden lösen. Leider bekomme ich die RFX-Box nicht angelernt, wie hast du das gemacht? Welches Protokoll ist das richtige? Für ein paar Tipps wäre ich sehr dankbar. LG Max

3

Gerne =) Inwiefern angelernt?
Anlernen in Home Assistant oder die Rolläden in der Box anlernen?

4

Question:
Just how do you get this to work?

I have recently had an external blind fitted, and the installer has given me a Cherubini remote (POP) and says the motor is of that make.

I saw your post, so I went ahead a bought an RFXcom unit (RFX-433EMC).

I can’t get it to work with the blind.

So, I get the RFX unit to work on USB. I have flashed the WiFi firmware and get it to work with WiFi. I have used the RFXmngr program, and I can see everything working. The unit picks up the signals between the hand-remote and the motor.

I have used RFXmngr to set the protocols to BlindsTx and KeeLoq.
I have set the motor to programming mode, and successfully added a middle-stop position using the remote, so I know that I am in motor programming mode.

I have added RFXCOM integration to HA (it does not find it automatically) and connected to the unit via the network.

If using the ‘auto connect’ the unit finds the remote if I manually press a button, so I know that the unit is working and the integration is working. Deleted all and started again.

I have tried to add the unit to the motor, both by using the RFXmngr and by using HA. This just does not seem to work.

Actions:

  • put the motor into programming mode (success and tested)
  • pair the motor using Home Assistant
    • click configure and enter
    • confirm/pair event code
      • used both the code given in the manual, and the code generated in RFXmngr

I get the blind device with 4 entities, but everything is unknown and nothing works.

Just how do you add the RFXcom unit to the motor as an additional remote?!

5

Cherubini is not supported by the RFXCOM integration. See the “Use RFXCOM in Home Assistant” pdf available on the Downloads page.
This pdf describes how to use the RFXCOM integration to control Cherubini.

Better option is to use MQTT. See the RFX MQTT User Guide.pdf how to add the Cherubini.

6

I am one of those annoying people who downloads and reads the manuals first before buying the product, to ensure that it is what I want and will do what I want.

I have the RRX-433EMC (the latest with Extended Motor Control module)

The ‘Use RFXCOM in Home Assistant Manual’ covers the Cherubini

RFX433 with Cherubini - how to pair the motor using Home Assistant
RFX433 with Cherubini - how to pair the motor using Home Assistant1145×945 121 KB

I have the RFX433
I have the RFXCOM integration in Home Assistant.
I am trying to pair the RFX as an additional remote with the motor, and I am following the instructions but I can’t seem to get it to work.

I have tried also to do this directly from the RFXmngr program, using the ‘program’ transmit message.

I know I have the motor in program mode.
I know I have the RFXcom unit working, and it can see the commands from the hand-remote I already have (yes I know that the integration cannot connect to the remotes, just the motor).

No joy in trying to pair the RFX as an additional remote with the motor, and I don’t see that the MQTT option (which I don’t use) does anything different beyond either the RFXmngr program or using HA RFXCOM integration.

7

Please contact support rfxcom.com

8

They say perseverance pays off.

Another go and yes I have managed to pair the RFXcom and motor. Eventually.

The unit comes as USB connection only as standard, although I have no idea how to connect this to HA USB port, so I flashed with the WIFI firmware.
Took the back off and reset the WIFI back to factory, so I could re-enter the settings again. Pluged into a power supply and checked it connects to my house network, and presents on the correct IP address.
Used the RFXmngr software to ensure all existing remotes (previous attempts) were removed (from the unit). Checked that I have added only the Tx and the KeeLoq protocols. Checked that the device can see messages from my hand-remote.

  • Select T18 (Cherubini) for transmit
  • Select an ID number in the approved range
  • Set ready to send ‘stop’ action [but don’t send just yet]

Then, using the POP remote I have, entered the motor into programming mode (press all buttons until led flashes 3 times, then press Up and Stop together until led turns on solid)

Then, using the POP remote, start the ‘pair another remote’ sequence.

  • Press Up and Stop together (blind drops a little)
  • Press Stop (blind drops a little)
  • Using RFXmngr, send the ‘stop’ action.

The issue I suspect that I had was that the above sequence must be completed with less than 4 seconds between each separate action, which is not easy without line of sight between PC (RFXmngr) and the blind. I had previously also tried using ‘program’ and ‘open’ actions to pair without success.

Once associated, tested in RFXmngr to check up, down, stop, and ‘send to middle position’ all work.

Then I added RFXCOM integration to HA manually.
Then added the blind, using the HA ‘event code’ taken from RFXmngr. This was the ‘open’ code for HA so required sending a new ‘open’ transmit from RFXmngr to generate the HA correct code.

Now I have the integration, with the blind, and four entities for an “unknown device”. The Cover Entity has buttons for up, down, and stop and these do all work. The other entities are all ‘unknown’.