Broadlink integration not detecting a particular remote

ZoltrixGFC commented 2 years ago

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

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

probot-home-assistant[bot] commented 2 years ago

broadlink documentation broadlink source _{^{(message by IssueLinks)}}

probot-home-assistant[bot] commented 2 years ago

Hey there @danielhiversen, @felipediel, @l-i-am, mind taking a look at this issue as it has been labeled with an integration (broadlink) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

ZoltrixGFC commented 2 years ago

Have upgraded to the latest HA version recently (2022.2.3) but the issue still exists.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 2 years ago

Can confirm issue is still present on version 2022.5.2. Assuming that @Danielhiversen, @felipediel, @L-I-Am are on leave if they haven't had a chance to look?

sidlauskas commented 2 years ago

I can also confirm that it's nearly impossible to learn 433.92MHz RF remote commands using HA integration while it's very easy to do in the Broadlink app

sidlauskas commented 2 years ago

Is there any news regarding this? It would be great if you could set frequency manually when learning commands

ZoltrixGFC commented 2 years ago

Be good to assign this to someone else that is still working on the project?

sidlauskas commented 2 years ago

@ZoltrixGFC I found that this integration uses python-broadlink library which even has a PR with this functionality implemented but it's not merged https://github.com/mjg59/python-broadlink/pull/613

@felipediel could you please update us on what's missing? this would be an amazing addition

ZoltrixGFC commented 2 years ago

Very cool 👍

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 1 year ago

Can confirm still an issue on latest version of HA.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 1 year ago

Still an issue, best to leave open.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 1 year ago

Correct, still fooked. Lets teamwork this one.

issue-triage-workflows[bot] commented 12 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 12 months ago

Yep still an issue. Lets get the dreamwork to make the teamwork on this one.

ZoltrixGFC commented 12 months ago

@Danielhiversen @felipediel @L-I-Am enough sleepy time, lets do this 😍😍

Freez commented 11 months ago

I have also issues to lean RF 433.92 devices to HA, in the broadcom app this works fine. I would be fine if you can specify the frequency.

edmondss commented 8 months ago

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.

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

I have the same issue. Have you figured out the solution?

ZoltrixGFC commented 8 months ago

Still the same issue. As a convoluted workaround, I have buttons in HA send voice commands to Alexa to trigger Broadlink to control the devices.

edmondss commented 8 months ago

Still the same issue. As a convoluted workaround, I have buttons in HA send voice commands to Alexa to trigger Broadlink to control the devices.

Thanks. I have actually make it work after reading hundreds of posts. The RF learning process is tricky which nobody seems to talk about it clearly.

ZoltrixGFC commented 8 months ago

What did you learn, and what was the trick?

edmondss commented 8 months ago

What did you learn, and what was the trick?

Can you read this? https://www.reddit.com/r/homeassistant/comments/19feltb/comment/kjrx31z/?utm_source=share&utm_medium=web2x&context=3

issue-triage-workflows[bot] commented 5 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 5 months ago

Heya HA bot, still an issue I'm afraid.

issue-triage-workflows[bot] commented 2 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

ZoltrixGFC commented 2 months ago

Lets keep the dream alive.

ChayoteJarocho commented 2 months ago

Workaround

When the notification shows up asking you to press the button, press it for at least 8 seconds. Then wait 3 seconds for the notification to go away. If it goes away, wait for the second notification to show up asking you to press the button one more time. When it shows up, press the button for at least 8 seconds, again. If any of the button press attempts does not work, release the button, wait 2-3 seconds, then do it again for at least 8 seconds. Tiresome, yes but it eventually worked for me.

My remote uses 433.92.

It's convoluted and complicated enough to listen to a remote using HA. I hope this gets fixed, because the BroadLink app had absolutely no trouble detecting a quick button press in this frequency. It's only a problem in HA.

Edit:

Additional workaround

I just noticed that HA can only learn one command at a time and then it becomes completely unable to learn subsequent commands. The workaround for this is to clear the selection from the Service dropdown by pressing X. Then you have to fill everything again to be able to learn the next command.

home-assistant / core