Device: Aqara Dual Relay Module T2 (connected via Zigbee).
Hub: Aqara Hub M3.
Integration: Hub M3 connected to Apple HomeKit via Matter.
Platform: iOS / Apple HomeKit.
The Issue: I am facing a severe security and usability issue with the T2 Relay when bridged to HomeKit through the Hub M3 using Matter.
Unlike the Aqara Wall Outlet H2 EU, which allows the user to change the “Display As” setting in HomeKit (Light, Fan, or Outlet), the T2 Relay is hardcoded strictly as a “Light” service via the Matter bridge. The option to change the device type to “Outlet” or “Switch” is completely missing in the Apple Home app settings.
The Risk: I use the T2 Relay to control Security Cameras (power) and a Garage Door Opener. Because HomeKit sees the T2 as a “Light” and I cannot change it:
When I say “Hey Siri, turn off all lights”, Siri cuts power to my security cameras and triggers the garage door relay.
This results in the garage door OPENING and cameras stopping the recording, creating a major physical security breach.
Request: Please update the Hub M3 / T2 firmware regarding the Matter implementation.
The T2 Relay should be exposed to Matter as a generic On/Off Switch/Outlet, not forced as a Light.
Alternatively, allow us to define the “Device Type” (Switch, Light, or Outlet) within the Aqara App before it is bridged to Matter/HomeKit, so the correct service type is passed to Apple Home.
This is a critical bug for users integrating T2 relays into security or infrastructure setups.
That’s an Apple Home issue then. It’s also an issue with voice assistants in general, anyone can yell to the assistant “turn everything off” and create chaos.
Before Matter 1.4 the only device types for something that turns on/off were a light and a smart plug (if you’ve read about an on/off switch that’s a wireless remote/button to control the device, not the device). In Matter 1.4 they introduced the Mounted On/Off Load Control which is the perfect fit in this case.
Either way, the issue is with the smart home platform really if they don’t let you exclude critical devices from generic voice commands.
I am attaching a comparison image between my Aqara Wall Outlet H2 EU (Image 1) and my Aqara Dual Relay Module T2 (Image 2), both connected to Apple HomeKit via the Hub M3.
Image 1 (H2 Outlet): As seen in Section A, I have the option “Display As” (Mostrar como), allowing me to define it as an Outlet, Light, or Fan. This works perfectly.
Image 2 (T2 Relay): As seen in Section B, this option is completely missing. The T2 is forced to appear as a “Light”.
The Issue: Whether this is a strict Matter protocol limitation or an implementation oversight, the lack of information/options creates a CRITICAL SAFETY ISSUE. Because the T2 is forced to be a “Light”, Siri opens my garage door and cuts power to my cameras when I issue a standard command like “Turn off the lights”.
Request: Please look at the difference in the screenshots. We need the T2 Relay to behave like the H2 Outlet within HomeKit over Matter. If Matter forces a “Light” classification, Aqara must update the M3 firmware to expose the T2 as a Generic Switch or Outlet by default, or allow us to change the “Device Type” inside the Aqara App before bridging it to Apple Home.
We cannot wait for Matter 1.4 updates; we need a fix for this security hazard now.
I get it, but the “bug” is in Apple Home that does not let you change the “display as” in your device.
Apple Home has that problem with wall switches of other manufacturers too, they usually identify as on/off lights but can control other things and Apple Home won’t let the user change it unless it identifies as a smart plug.
Unless Aqara updates its firmware to inform HomeKit that the Aqara T2 is a plug, instead of a relay. By default, HomeKit considers it a light, and those of us who need this functionality change it to a plug.
Or perhaps the Aqara app will allow us to identify the usage type and inform HomeKit accordingly.
Can’t really call it a safety issue as it’s working and no one is i danger when using the product.
You have an issue with the way the product work in the set-up you have chosen for your cameras etc, which in my opinion sounds more as an HA issue, but regardless calling this a safety issue is wrong.
