Skip to content

Add support for Broadlink RM Max (0xAF8B)#838

Open
amasolov wants to merge 1 commit into
mjg59:new_product_idsfrom
amasolov:add-rm-max-support
Open

Add support for Broadlink RM Max (0xAF8B)#838
amasolov wants to merge 1 commit into
mjg59:new_product_idsfrom
amasolov:add-rm-max-support

Conversation

@amasolov

@amasolov amasolov commented May 24, 2026 •
edited
Loading

Copy link
Copy Markdown

Context

The Broadlink RM Max is the successor to the RM4 Pro, featuring IR and RF 433MHz capabilities. It is currently not recognized by the library, reporting as "Unsupported device: 0xAF8B" in Home Assistant.

This is a highly requested addition — see #829 with 20+ community members requesting support.

Proposed change

Add device type 0xAF8B to the rm4pro class mapping. The RM Max uses the same protocol as the RM4 Pro (confirmed by testing IR learning and sending on a physical device).

Type of change

  • New product id (the device is already supported with a different id)

Additional information

Checklist

  • The code change is tested and works locally.
  • The code has been formatted using Black.
  • The code follows the Zen of Python.
  • I am creating the Pull Request against the correct branch.
  • Documentation added/updated.

@amasolov amasolov mentioned this pull request May 24, 2026
Open
@dwery

dwery commented Jun 20, 2026

Copy link
Copy Markdown

This really is a one liner, can someone please hit merge?

@phenigma

phenigma commented Jun 20, 2026

Copy link
Copy Markdown

I tested this change and it detects the device but wants me to unlock it from the manufacturer's app but there is no option to do that in the app.

@dwery

dwery commented Jun 26, 2026

Copy link
Copy Markdown

Same. I couldn't find a way to unlock it. Even blocking the device's access to internet didn't work, I guess it locks itself immediately.

@amasolov @cursoragent
Add support for Broadlink RM Max (0xAF8B)
02796c8 
Place in the rmpro class which uses <I framing for IR learn/send
commands, matching the device's actual protocol. The rm4pro class
uses <HI framing which causes "device is locked" errors on this
hardware.

Co-authored-by: Cursor <cursoragent@cursor.com>
@amasolov
amasolov force-pushed the add-rm-max-support branch from 7aeb3c7 to 02796c8 Compare July 15, 2026 22:25
@blundsteen

blundsteen commented Jul 26, 2026

Copy link
Copy Markdown

Hi! I've been testing an RM Max extensively and noticed something that may help.

My device:

PID: 0x8baf0000
Devtype: 0xAF8B
Firmware: V62130
SDK: 2.18.x
Name returned by discovery: "FCBLE GW"

Discovery works correctly, but device.auth() immediately fails. The device responds with a short error packet and never returns a session ID or AES key.

I noticed your PR only changes the device mapping (rm4pro → rmpro) and doesn't modify auth().

Did device.auth() succeed on your RM Max without any local modifications?

If so, could you share:

firmware version,
SDK version,
whether the device also reported "FCBLE GW",
and whether there were any additional local changes not included in PR #838?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@amasolov @dwery @phenigma @blundsteen