Feature Request: Expose Hub M3 IR Hardware via Open API v3 for Native Home Assistant IR Proxy Support

Developer Hub
, ,
1

Hi Aqara team,

I would like to request that the IR hardware on the Hub M3 be exposed
via the Aqara Open API v3, specifically to enable the M3 to function
as a native IR Proxy in Home Assistant.

I personally purchased the Hub M3 primarily for its IR blaster
capability. However, after integrating it with Home Assistant, I
discovered that IR control is only accessible through the Aqara app,
where it is limited to 15 scenes that can then be shared as Matter
devices to Home Assistant. This is a significant limitation that makes
the IR feature practically unusable for any serious home automation
setup.

Home Assistant 2026.4 introduced a native infrared framework. A
supported IR device registers directly as an “IR Proxy” in Home
Assistant - similar to how Bluetooth proxies work. Home Assistant
handles all IR code storage and management. The hardware simply
transmits and receives. This is exactly the role the M3 should be
able to fill, and the framework to support it already exists in
Home Assistant.

There is already an active and well-maintained custom Home Assistant
integration for the M3 by developer Darkdragon14, available at
GitHub - Darkdragon14/ha-aqara-devices: Custom Home Assistant integration for Aqara devices. Supports G3, G2H Pro, G410, G4, M3, M100, FP2, FP300, and A100 Pro via Aqara Cloud with advanced controls, presence telemetry and extended features beyond the official integration. · GitHub, which uses the Aqara
Open API v3 and provides solid M3 support. IR is the one missing piece,
purely because the Open API does not expose it for the M3.

My request is straightforward:

Please expose the M3 IR hardware via the Open API v3 so that the M3
can be registered and used as a native IR Proxy in Home Assistant,
with full two-way support:

  1. IR Transmitting - accept raw IR codes via the API and transmit
    them. No IR codes stored on the M3. All storage handled by
    Home Assistant.

  2. IR Receiving - forward captured IR signals as API events so
    Home Assistant can receive, store, and act on them.

Currently, the IR Device Management API only supports the Air Condition
Controller P3 and the Hub M2. Adding M3 support would make it a
first-class IR Proxy for the large and growing Home Assistant community,
and would deliver on what many users - myself included - bought the M3
for in the first place.

Thank you for considering this request.

6 Likes
2

imo the IR controls could be also exposed for other Matter ecosystems too.

Maybe not the received signals, but I can see how a programmed IR signal could be exposed to, say, HomeKit as a switch.

Currently a very similar feature is used as a way to sync Aqara scenes to Matter. Scenes are exposed as switches. When I toggle the switch in Apple Home, it triggers the scene in Aqara home.

So why can’t we have the IR signals synced in the same way? For example I could add my TV to the Aqara M3, and then choose to expose some buttons as switches.

9 Likes