Aqara Aircon Control: Infrared, Sensors and Automations

Current infrared-capable Aqara products include M2, M3 and M200, along with selected camera hubs such as G3. M100 does not provide an infrared emitter. Hub choice also affects Ethernet, PoE, Matter, Thread, speaker and Zigbee roles, so the air-conditioner should not be the only comparison.

M2 provides broad 360-degree infrared output and can run supported local automations. M3 adds enhanced infrared control, status tracking and the ability to present a supported infrared air-conditioner as a thermostat through Matter when paired with an Aqara temperature sensor. M200 combines current hub, Matter and infrared roles in a different form factor.

Confirm that the exact model is offered and supported locally. Global product pages and firmware announcements do not establish Singapore stock or identical app behaviour.

Infrared light does not pass through walls. Put the hub in the same room as the indoor unit, within useful range and without a cabinet door, television or shelf blocking the path. A central tabletop position often works better than a network cupboard near the entrance.

The 360-degree description refers to emission around the hub, not through opaque objects. Reflective walls can help within a room, but the installation should not depend on a narrow bounce path that disappears when a door or curtain moves.

Test from the final position with normal furniture and doors in place. Send repeated power, mode, setpoint and fan commands. If one bedroom needs infrared control and another is behind a wall, plan another infrared controller for that room even when one Zigbee hub could cover both.

Start with Aqara Home's supported air-conditioner library and test the exact brand and remote profile. Air-conditioner remotes often send a complete command containing power, mode, temperature and fan state rather than a single isolated key. The correct profile needs to reproduce the full set reliably.

If automatic matching does not work, use the supported manual matching or learning process. Record the original remote model and retain it. Some functions such as swing patterns, quiet modes, ionisers or proprietary comfort sensors may not exist in the virtual remote even when basic cooling works.

Test the edge cases: power off from cooling, changing from dry to cooling, minimum and maximum temperature, fan speed and restart after a power interruption. A control that can turn the unit on once is not yet commissioned.

Traditional infrared is one-way: the controller transmits light and does not receive an electrical acknowledgement from the air-conditioner. The app can know the command it sent, but that is not automatically proof that the indoor unit was powered, in range or ready to receive it.

Aqara's newer M3 infrared functions can track supported air-conditioner state and may observe compatible remote commands, improving coordination. The limit remains important: a blocked transmission, manual control outside the hub's receiving range or a power failure can leave the recorded state different from the appliance.

Avoid automations that depend on an unverified infrared state for safety. Use temperature trend, power measurement from suitable equipment or a physical check where confirmation matters. Design a repeated 'set complete state' action instead of alternating an ambiguous power toggle whenever the profile supports it.

Place an Aqara Temperature and Humidity Sensor or Climate Sensor W100 where it represents the occupied zone. Avoid direct supply air, sunlight, exterior walls, televisions and enclosed shelves. The air-conditioner's return-air sensor measures a different location and may not represent the sofa, desk or bed.

M3 can combine a supported external Aqara climate sensor with an infrared air-conditioner and present thermostat behaviour to compatible Matter platforms. Aqara Home remains the manufacturer layer for the infrared profile and sensor relationship.

Temperature reporting intervals and placement affect response. A battery sensor is appropriate for comfort automation but is not a high-speed industrial control loop. Observe the real room response before choosing thresholds.

Do not turn cooling on at 25.0°C and off at 24.9°C. Sensor noise and normal air movement would create rapid cycling. Use hysteresis: for example, turn on above a higher threshold and turn off only below a meaningfully lower threshold, with values selected for the real room and occupants.

Add minimum on and off times so a new reading cannot restart the compressor immediately. The air-conditioner's own electronics provide protection, but the automation should not issue unnecessary commands every minute. A scene that selects cooling mode, a reasonable setpoint and fan state is clearer than several competing actions.

Include occupancy and time conditions conservatively. Presence can permit cooling, while sustained confirmed vacancy can stop it after a delay. Keep a physical remote or scene button available for guests and unusual conditions.

Household members will continue to use the original remote. Place it where the hub can also receive its infrared signal if the model supports status tracking, and teach users that a command sent from an unusual angle may not update the app.

Avoid hiding the remote to force app use. A physical control remains the fastest fallback during network, account or hub problems. The finished system should allow a resident to cool the room without opening a phone or diagnosing an automation.

If state disagreement becomes common, simplify the automation to complete-state commands and use temperature as evidence of the outcome. Re-commission the remote profile if individual modes or temperatures fail more often than others.

Test infrared control with the internet disconnected while the local network remains available. Aqara documents local operation for supported M2 automations, while remote access and cloud integrations stop. Verify the actual automation contents and hub firmware rather than assuming every routine is local.

Restart the hub, access point and air-conditioner power separately. Confirm whether the app state recovers, whether schedules repeat and whether the air-conditioner resumes after a supply interruption. Ensure the original remote always remains functional.

Handover should record the remote profile, hub position, sensor position, thresholds, minimum times, owner account and manual override. This turns an invisible set of app rules into a maintainable control system.