Aqara Studio Connect and the Edge Hub M300 for Malaysian Installers

Answer up front — The Edge Hub M300 is Aqara's official hardware controller for the Aqara Studio spatial intelligence operating system, acting as a local edge hub and gateway, and Aqara Studio Connect is a lightweight version of Studio that runs only on it. It is managed through a web interface with no extra software to install, supports up to 500 connected devices, and speaks Zigbee 3.0, Thread, Wi-Fi, Ethernet, BACnet/IP, KNX/IP and Modbus. The part that matters before you plan a job: Aqara's own documentation lists the M300's sales regions as Chinese Mainland, North America, Europe and Russia. The M300 has not been listed as a Malaysian-channel product. Talk to us about availability and project fit.

Aqara announced the Edge Hub M300 at IFA 2025 in Denver on 3 September 2025, with a projected release in Q4 2025. For an installer, the interesting part is not the announcement. It is that Aqara built dedicated hardware for the Studio platform rather than expecting integrators to run Studio on their own servers, and then built a reduced edition of Studio that runs on that hardware alone. This post is about what that combination actually does on site, and about the sales-region limit you need to know before you write it into a quote.

First, the thing you cannot quote

Aqara's product documentation for the Edge Hub M300 states its sales regions as Chinese Mainland, North America, Europe and Russia. Malaysia is not on that list.

The M300 has not been listed as a Malaysian-channel product. Talk to us about availability and project fit.

What you can still do is brief a client honestly about where the platform is heading, and stage the project so that the M300 is a decision point rather than a sunk cost. The rest of this post assumes you are doing that.

What the M300 actually is

Aqara describes Studio as "an ontology-native spatial intelligent operating system built on spatial ontology." The M300 is the hardware that runs it. It does two jobs at once: a local edge hub handling transport, multi-protocol parsing, configuration and automation orchestration, and a gateway for the systems around it.

Two items in that table will decide whether your installation day goes well.

There is no power adapter in the box. You are supplying it. If the unit is going on a shelf in a utility area, a USB-C supply is fine. If you intend to run it on PoE, you need a PoE switch or PoE injector at the other end of the cable run, and that belongs in the materials list before you price the job — not after.

There is one 1 m USB-A to USB-C cable. That is a desk cable. Every realistic ceiling or comms-room install needs its own cable, and the RJ-45 run needs to be planned to the standard you already work to. See our guide to running cable in concrete walls before you commit to a route.

What Studio Connect is

Aqara Studio Connect is a lightweight version of Aqara Studio that runs exclusively on the M300. It is not a separate product you buy alongside the hub; it is the software experience that hub is built to run.

Four properties matter on site:

It runs in a web interface. Integrators manage client systems without installing extra software. There is no per-site desktop application to license, install, keep in version alignment, or uninstall when a project ends.

It supports remote access. That is the operational difference for an installer running multiple projects: managing them and troubleshooting them without a site visit. On the hub-integrated model, transport, parsing, configuration and automation orchestration all happen on the hub, so control does not depend on a round trip to a cloud service. If you are weighing that against running Studio on your own edge hardware, the deployment-model comparison in Aqara Studio Explained covers the trade-off properly.

It has a Flow editor with no code required. Aqara Studio carries two visual logic tools, Classic and Flow, positioned as zero to minimal code. Flow covers triggers and conditions, actions and data processing, and service calls. You build the logic by drawing it, which is what makes a scene handable to a client's maintenance person afterwards.

It caps at 500 connected devices. That is a design brief as much as a limit. Aqara positioned the M300 for single-family homes, small multi-family properties and light commercial work. Above roughly 500 devices you are into territory where you want to make the deployment-model decision deliberately, not discover it on commissioning day.

Protocols: the reason a building integrator should care

From the M300 hub-integrated documentation, the supported set is Zigbee 3.0, Thread, Wi-Fi, Ethernet, BACnet/IP, KNX/IP and Modbus. Aqara's community forum adds BACnet IP, KNX IP and Modbus TCP for professional building systems.

The last three are the commercially interesting line for anyone quoting a commercial fit-out. Aqara devices stop being a consumer island and become one control layer sitting on top of equipment that already exists in the building. That is the argument to have with a building owner, and it is the argument that makes a spatial-intelligence conversation worth having before the cabling is done.

What to do, in order

If you have a live project where this platform is the right answer, work through it in this sequence:

1. Establish the building first. Surfaces, structure, existing controls, what is already on the network. Use how to survey a Malaysian home before quoting as the discipline, then extend it for commercial fit-out.
2. Decide the deployment model before quoting hardware. Hub-integrated, edge-deployed on your own server, or cloud-hosted. It changes the price, the operating load and who carries it.
3. Map the third-party systems that need to be reached — BMS, KNX panels, Modbus meters — and confirm the model and firmware actually support it rather than assuming.
4. Plan cable and power as a materials line. Ethernet to the comms room, PoE if you are using it, and a USB-C supply. None of it is in the box.
5. Keep the M300 as a conversation, not a line item, until availability in this region is confirmed with us.

What this page does not claim

• It does not claim the M300 or Studio Connect is in Malaysian stock, on sale here, or available to buy from us.
• It does not state a Malaysian price for the M300, Studio Connect, or any Aqara Studio subscription or licensing.
• It does not state warranty durations, after-sales terms or firmware support windows. Ask us for current terms in writing.
• It does not promise the 500-device figure will never change. Treat it as the documented figure for the Global model as published.