home-assistant / home-assistant/core

Broadlink integration not detecting a particular remote

Open
#63,578 47 comments 1 reaction 0 assignees View on GitHub
integration: broadlink
Dominant language
Python
Stars
90.5k
Forks
38.6k
Avg merge
1d 2h
Merged PRs (30d)
597

Description

### The problem

Issue with Home Assistant Broadlink integration. Works fine for configuring a Sony TV remote, and a remote that controls LED candles.

But I also have a ceiling fan that uses a remote (the remote is RF and running on a 433.77MHz frequency). Home Assistant won’t register the remote presses when I put it into learning mode. The Broadlink app works ok and it detects the remote signals fine, so it appears the remote and Broadlink receiver are working ok.

I can confirm I am using the same learning commands that I used for the remotes that are working, and when trying to learn the fan remote I am selecting "Command Type = rf".

Attachment shows the remote presses being detected by the Broadlink app. Device is a RM4 Pro S running firmware v52079.
![9ed70f489a883039fcb4b3e1ac94118d6939f373_2_227x499](https://user-images.githubusercontent.com/77313738/148486343-028e9718-c173-4362-aabe-3033e9a92714.jpeg)

### What version of Home Assistant Core has the issue?

2021.12.7

### What was the last working version of Home Assistant Core?

_No response_

### What type of installation are you running?

Home Assistant OS

### Integration causing the issue

Broadlink

### Link to integration documentation on our website

https://www.home-assistant.io/integrations/broadlink/

### Example YAML snippet

_No response_

### Anything in the logs that might be useful for us?

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the Broadlink integration documentation linked in the issue and trace the learning-mode path for RF commands. Reproduce the problem with the RM4 Pro S, firmware v52079, and the 433.77MHz fan remote, then compare it with the working remotes. Done means the integration detects and learns this remote, or clearly documents the unsupported behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.