If you are using the command-line version, run:
pip install --upgrade broadlink
For the GUI version, download the latest release from GitHub (search for broadlink-manager – note that the project may be archived; if so, switch to broadlink-cli or python-broadlink).
Broadlink devices only listen for new code capture when the blue LED is blinking rapidly. If your device is idle (solid blue or blue off), the command packet will fail. The error is correct: it is not “hot” (ready).
The “broadlink manager writing compatible device not detected hot” error is not a hardware failure. It is a network-state and tool-limitation problem. In 90% of cases, either:
Quick fix summary:
Once you overcome this hurdle, Broadlink devices remain among the most reliable local IR/RF blasters for home automation. The “hot” error is frustrating, but now you have the complete roadmap to solve it.
Last updated: 2025. If you are using a Broadlink device manufactured after 2024, check for new firmware restrictions – some models have phased out local UDP commands entirely, requiring you to use the cloud API or switch to an ESP32-based blaster.
Here are some steps you might consider to troubleshoot the issue:
Use this guide to troubleshoot the “Writing compatible device not detected” error step‑by‑step.
Broadlink Manager “Device Not Detected” error is a common roadblock for smart home enthusiasts, usually occurring because the Broadlink device is in "Locked" status or on a different network segment
. When the software cannot “write” or communicate with the hardware, it is typically a handshake failure rather than a hardware defect. The Root Causes The most frequent culprit is the "Lock Device" broadlink manager writing compatible device not detected hot
setting within the official Broadlink (or IHC) app. To prevent unauthorized changes, the app often toggles a cloud-side lock that blocks local scripts and third-party managers from accessing the device’s API.
Additionally, network architecture plays a role. Broadlink devices operate strictly on the 2.4GHz band
. If your computer running the Manager is on the 5GHz band or a guest network, the broadcast packets used for discovery often fail to cross the router's internal bridge, leaving the device "invisible." Proven Solutions To resolve the detection failure, try these steps in order: Unlock the Device:
Open the official Broadlink app on your phone, go to your device settings, and look for an "Unlock" or "Lock Device" toggle. Ensure it is switched Toggle AP Mode: If the device isn't seen at all, perform a
(hold the reset button until the LED flashes rapidly) and try adding it via rather than the standard "SmartConfig." Network Alignment:
Ensure your PC and the Broadlink device are on the exact same SSID. Disable any VPNs or firewalls on your computer temporarily, as these often block the UDP ports (usually 80, 8080, or 53) required for the Broadlink Manager to "listen" for the device. Static IP:
Assign a static IP to your Broadlink device via your router's DHCP reservation. This ensures that once the Manager finds it, the connection remains stable. Conclusion
"Writing compatible device not detected" is essentially a communication timeout. By ensuring the device is in the official app and residing on a unified 2.4GHz network
, you can bridge the gap between the Manager software and your hardware. UDP port numbers
to whitelist in your firewall to ensure the connection stays open? If you are using the command-line version, run:
The "Writing compatible device not detected!" error in Broadlink Manager typically occurs because the device is "locked" by the official Broadlink app or registered to the Broadlink cloud, which prevents local third-party tools from accessing it. Primary Hotfixes Unlock the Device: Open the official Broadlink app (or older e-Control app).
Go to your device's settings and look for a "Lock device" or "Unlock" toggle.
Ensure this is turned OFF to allow local network communication. Prevent Cloud Binding (The "Quit Method"):
Reset your Broadlink device (hold the reset pin until it flashes rapidly).
Start the setup process in the Broadlink app to connect it to your Wi-Fi.
Crucial Step: As soon as the device connects to your Wi-Fi (light stops flashing), immediately force-quit the app. Do not assign it to a room or finish the setup, as this binds it to the cloud and locks out local managers. Disable Interfering Software:
Temporarily disable your computer's firewall or antivirus (e.g., Avast), as these can block the discovery packets.
If running Broadlink Manager via Docker, ensure no ad-blockers like Pi-hole or AdGuard are active on the network, as they can cause script errors. Quick Connectivity Checklist
The error message "Writing compatible device not detected!" in Broadlink Manager
typically occurs when the software discovers a device's IP address but fails to establish a secure control handshake or lacks the specific device identifier in its database Home Assistant Community Common Root Causes Cloud Locking For the GUI version, download the latest release
: Newer firmware (v44057+) often "locks" the device to the Broadlink cloud, preventing local control by third-party apps. Unsupported Hardware : Newer or "clone" models like the Bestcon RM4C mini
may be identified as "Unknown" and lack a corresponding driver in older manager versions. Network Security
: Active firewalls (e.g., Avast) or ad-blockers (e.g., Pi-hole) can block the discovery scripts. Initialization State
: The device may be fully registered in the official app, which disables its "pairing mode" for local managers. Home Assistant Community Troubleshooting & Fixes
Before diving into solutions, let's diagnose why you're seeing this message. The error is most common in three scenarios:
If you compiled Broadlink Manager yourself via Python, you might have an outdated broadlink library (e.g., v0.9 vs v0.18). Old libraries don’t recognize newer devices like the RM4 series, resulting in the “compatible device not detected” message.
Recent updates to BroadLink firmware have broken compatibility with older manager tools.
Action plan:
Your computer is on 192.168.1.x, but your Broadlink (especially if on a guest network or VLAN) is on 192.168.2.x. The broadcast packet won’t traverse subnets without a helper. The Manager scans the local subnet only.