Skip to content

[RFLink] BrelMotor covers require SWITCH= prefix in device_id to work #39504

@chrispl50

Description

@chrispl50

Feedback

I'd like to share a solution to a persistent problem I've been having with BrelMotor roller shutters controlled via RFLink in Home Assistant. I hope this helps others facing the same issue.
The Problem:
My BrelMotor covers were not responding to commands sent from Home Assistant, even though:
They were correctly paired with the RFLink gateway.
Controlling them directly from RFLinkLoader worked perfectly.
Home Assistant logs showed that commands were being sent and acknowledged (OK;) by the RFLink gateway.
The Discovery:
After extensive debugging, I discovered a critical difference in the command format.
The command that works in RFLinkLoader requires the SWITCH= prefix:
10;BrelMotor;fa6d5e;SWITCH=05;UP;
However, the Home Assistant RFLink integration, by default, sends a "shorthand" version of the command, without the SWITCH= prefix:
10;BrelMotor;fa6d5e;05;UP;
This second command format was simply ignored by my BrelMotor roller shutters.

The Solution / Workaround:
The solution is to "trick" the Home Assistant RFLink integration into building the correct command string by modifying the device_id in configuration.yaml.
By including SWITCH= as part of the device's switch identifier, you can force the integration to generate the correct payload.
Here is the working configuration for a cover in configuration.yaml:

configuration.yaml

cover:

  • platform: rflink
    devices:
    //The key is to include "SWITCH=" before the channel number.
    BrelMotor_fa6d5e_SWITCH=05:
    name: Living Room Shutter

With this configuration, Home Assistant correctly generates the command 10;BrelMotor;fa6d5e;SWITCH=05;UP; and the roller shutters work perfectly.
This seems to be a specific requirement for some BrelMotor devices (or perhaps certain RFLink firmware versions when interacting with them). Adding this information to the documentation or considering this format as a standard for the BrelMotor protocol within the integration could prevent a lot of user frustration.
I hope this information is useful

URL

https://www.home-assistant.io/integrations/cover.template/

Version

2025.6.0

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    integration: rflinkstaleThe PR had no activity for quite some time, and is marked as Stale

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions