Broadlink Manager Writing Compatible Device Not Detected Hot
Do not assume your device’s IP. Find it:
Once you have the correct IP, ping it:
ping 192.168.x.x -t
If ping fails, your device is disconnected from Wi-Fi. Reseat power.
Follow these solutions in order. Start with the simplest, most likely fix.
If you are seeing the error message "BroadLink Manager writing compatible device not detected hot" while trying to configure or update your BroadLink device (such as the RM4 Pro, RM Mini, or SP series), you are not alone. This frustrating error typically appears when using third-party software (like BroadLink Manager for PC) or home automation platforms (like Home Assistant or OpenHAB) to write configurations or firmware to your device.
In this comprehensive guide, we will break down exactly what this error means, why your device shows as "hot" but not detected, and how to fix it permanently.
If you are seeing this error within Home Assistant (via the BroadLink integration) or OpenHAB, the issue is slightly different. Here, "writing compatible device not detected hot" means the integration’s send_command or learn_command service cannot find an available device.
ir_code = "JgBQAAABK...."
Broadlink devices (RM Mini, RM Pro, SP series, etc.) are among the most popular choices for DIY home automation, primarily because they offer cheap, local control via Wi-Fi. Tools like Broadlink Manager (often referred to as python-broadlink or the Broadlink Manager GUI) allow advanced users to read and write RF (Radio Frequency) and IR (Infrared) codes—bypassing the cloud.
However, a notorious error plagues even experienced users: “Compatible device not detected hot.” broadlink manager writing compatible device not detected hot
If you have seen this message while trying to write or learn a command, you are not alone. This article dives deep into what this error means, why it happens, and exactly how to fix it.
If after trying these steps your device still isn’t detected, it may be a more specific compatibility issue or a hardware fault. Continuous troubleshooting with the support team or considering a replacement might be necessary.
"Writing compatible device not detected!" in BroadLink Manager
typically occurs because the device is "locked" to the official mobile app or blocked by network security Essential Troubleshooting Steps Unlock the Device
: In the official BroadLink mobile app, navigate to your device settings and find the "Lock Device" "Device Lock"
toggle. Disable it to allow external managers (like BroadLink Manager or Home Assistant) to access the hardware. Disable Firewall/Antivirus
: Your PC's security software often blocks the local UDP discovery packets used by BroadLink Manager. Temporarily disable your (e.g., Avast) and try scanning again. Prevent Cloud Binding
: If you are setting up a newer device (like the RM4 series), add it to your Wi-Fi using the app but quit the app immediately
once it's on the network. Do not complete the "Add to Room" step, as this often binds the device to the cloud and prevents local discovery. Network Requirements : Ensure both your PC and the BroadLink device are on a 2.4GHz Wi-Fi network; 5GHz is not supported. Home Assistant Community Advanced Fixes Do not assume your device’s IP
Troubleshooting BroadLink Manager: "Writing Compatible Device Not Detected"
If you are seeing the error "Writing compatible device not detected!" in BroadLink Manager, you aren't alone. This specific message typically appears when the software identifies your device's IP address but cannot establish a "handshake" to read or write IR/RF codes. Why This Error Happens
The most common reason for this "hot" issue is that the device is locked. Modern BroadLink firmware (v44057 and newer) often defaults to a "locked" state that restricts local communication to prioritize cloud security. 1. Unlock the Device (Most Effective Fix)
The device must be unlocked within the official app to allow local tools like BroadLink Manager to interact with it. Open the official BroadLink app on your phone. Select your device (e.g., RM4 Mini or RM4 Pro). Tap the three dots or Property in the top right corner. Scroll to the bottom and find the "Lock device" toggle. Ensure this is switched OFF. 2. Bypass "Cloud Binding" During Setup
If unlocking doesn't work, the device may be fully bound to the cloud. You can force it into "local mode" by resetting it and stopping the setup early. Reset your BroadLink device until the LED flashes rapidly. Use the BroadLink app to connect it to your Wi-Fi.
Crucial Step: As soon as the device connects to your Wi-Fi and the app asks you to "Assign to a room," force close the app.
Do not complete the registration. The device will be on your network but not "owned" by the cloud, allowing BroadLink Manager to detect it. 3. Check Network & Security Settings
Network interference often causes the "Not Detected" error even if the IP is visible.
Title: [Help] Broadlink Manager: "Compatible device not detected" but device is hot/warm to the touch Once you have the correct IP, ping it: ping 192
Body:
Hi everyone,
I am currently stuck trying to add a new Broadlink device to my network using Broadlink Manager (running on Windows).
The Issue: When I scan for devices, the software returns the error: "Compatible device not detected."
Troubleshooting Steps Taken:
Environment:
Has anyone encountered this specific detection error despite the device showing signs of life (heat/LEDs)? Is this a firewall issue or potentially a hardware fault?
Thanks in advance for any help!
The word "hot" specifically hints that the device’s hotplug state is not being refreshed. Some BroadLink devices, especially older ones, enter a sleeping or low-power state after inactivity. When the software attempts to write, the device doesn't wake up in time to respond — hence "not detected hot."