Broadlink Manager Writing Compatible Device Not Detected Hot Jun 2026

The BroadLink device has already been onboarded to the official cloud app, which locks out local discovery tools. Step-by-Step Troubleshooting Guide

Users are reporting that fails to detect compatible Broadlink devices (e.g., RM4 Pro, RM3 Mini) during the setup or scanning phase. Despite the devices being powered on and functional, the software returns a "No devices found" or "Compatible device not detected" message. This issue appears to be prevalent ("hot") in recent community discussions.

The most reliable method to bypass the Broadlink Manager's limitations is to use Home Assistant's native Broadlink integration. This approach allows you to learn IR/RF codes without the Broadlink Manager's compatibility restrictions. A community-proven workaround that has helped many users overcome this error is as follows: broadlink manager writing compatible device not detected hot

Reset the BroadLink device until the LED flashes rapidly, then reset it again until the LED flashes slowly (once every few seconds). This signifies AP Mode.

Kaelen’s plan: capture the raw IR codes from a working remote, then brute-force a Broadlink into retransmitting them. But first, the manager had to see the device. The BroadLink device has already been onboarded to

This explains why you might see the following symptoms:

To fix the issue, it helps to understand what the error message actually means: This issue appears to be prevalent ("hot") in

Broadlink Manager - Nicer way to Learn and Send IR/RF commands

However, many users encounter a frustrating issue when trying to pair their device, encountering the error: This error is often accompanied by the Broadlink device becoming surprisingly hot to the touch.