This is almost always a , not a hardware defect.
. When it identifies a device but fails to "write," it’s often because of a security or configuration layer preventing deeper communication: The "Cloud Lock" Feature
Does the device show up in your ?
to bridge their IR/RF devices with platforms like Home Assistant. This technical "deadlock" usually occurs when the software can see your device's IP address but cannot establish a stable "write" connection to pull or push IR/RF codes. The Core Conflict: Discovery vs. Accessibility
Broadlink devices communicate using UDP packets on specific ports. These packets generally do not travel across different subnets or through heavy firewalls. If your smartphone, computer, or Home Assistant server is on a different frequency band (5GHz vs 2.4GHz) or a different subnet (e.g., 192.168.1.x vs 192.168.0.x) than the Broadlink device, the discovery process will fail. broadlink manager writing compatible device not detected
Run the following from the manager’s host machine (replace 192.168.1.255 with your subnet broadcast address):
Users attempting to configure or write commands to a Broadlink device (e.g., RM4 Pro, RM Mini 3, SP series) via (third-party or official configuration tool) encounter the error: “compatible device not detected.” The process halts during device discovery or before command transmission. This report identifies root causes, affected environments, and provides actionable solutions. This is almost always a , not a hardware defect
You’ve just purchased a Broadlink RM Mini, RM Pro, or RM4. You have downloaded (often referred to as Broadlink Manager for Android or the legacy Broadlink Manager PC tool). You are ready to write automation scripts, back up your infrared (IR) codes, or integrate the device with Home Assistant.