Aircon IR blaster: what it imitates and what it misses
A blaster turns an ordinary aircon into one your phone can switch on. The catch sits in the direction of travel. Every command leaves the box and nothing comes back, so the screen shows a machine the box last spoke to, not the machine on the wall.
By Team Snowflake | Updated 8 Aug 2026
What is an IR blaster actually doing?
An IR blaster copies your handset. It sits in the room, joins your home network, and puts out the pulses your handset would have sent, whenever the app asks. The aircon receives what it would have received from a hand across the room, and treats it exactly the same way. This is the cheapest way into what gets sold as a smart aircon, because it changes nothing on the machine at all.
Getting that pulse right is fiddlier than a product page suggests. The receiver behind the indoor unit's display panel is tuned to one carrier frequency. Receiver modules for remote controls are supplied in versions centred on 30, 33, 36, 38, 40 and 56 kHz, and a signal on the wrong one goes unheard. The pattern carried on top of that carrier belongs to the manufacturer, and it changes by brand and often by series.
Aircon commands are also shaped differently from television commands. A television handset sends one instruction per button press. An aircon handset almost always sends every setting it is holding in a single message: power, mode, setpoint, fan speed, swing and timer, all at once. The indoor board never builds a picture up from a run of presses. It receives the whole picture each time, and adopts it.
That single design choice explains almost everything below. Setup becomes a matching job. A bad match fails oddly instead of failing cleanly. And app drift heals itself on some units, never on others.
Reading your handset, or looking it up in a table
Two setup methods are in circulation and they fail in different ways. The first reads your handset directly. You point the original at the new box, press a button, and the box captures the signal it sees. Makers who work this way publish a compatibility check for exactly this step, and acknowledge a small residue of handsets whose signal they cannot read.
The second looks your model up in a stored table of codes. This is why an app offers several numbered variants under one brand name, and why vendors list picking a different variant as an early thing to try when a unit ignores the box. A wrong table rarely produces silence. More often the unit answers some commands and ignores others, which reads like a hardware fault and is not one.
Why does the app show a state the aircon is not in?
The command path runs one way. The blaster transmits, the indoor unit receives, and nothing travels back along that path. So the app never reports the aircon. It replays the last instruction it sent, which is a different thing entirely, and the difference stays invisible until the two disagree.
A wifi module on the indoor board changes that arrangement. There the command arrives over the network, the board answers back, and the app displays something the machine actually confirmed. An infrared blaster sits on the blind side of that difference, and no amount of software on the phone can cross it.
The aircon does acknowledge a command, just to the wrong audience. Manufacturers document a signal receiver on the indoor unit and a sound it makes on receipt. Daikin's wall-mounted manual sets out three of them: two short beeps when operation starts, one short beep when a setting changes, and a long beep when operation stops. That is a genuine confirmation carrying real information about what the unit did. It goes into the room as sound, and the box on the shelf has no ear for it.
Four ordinary events push the app's picture away from the machine. Three of them leave no mark on the phone at all.
| What happened in the room | What the aircon did | What the app still shows |
|---|---|---|
| What happened in the roomSomebody picked up the handset | What the aircon didTook the newer command and acted on it | What the app still showsWhatever the app itself last sent |
| What happened in the roomThe unit stopped itself on a fault | What the aircon didShut down, with a code showing on its own display | What the app still showsRunning normally at the last setpoint |
| What happened in the roomSomething crossed the signal path | What the aircon didNothing. The pulse never landed | What the app still showsThe command, marked as sent |
| What happened in the roomThe blaster was nudged off aim | What the aircon didAnswered some commands and missed others | What the app still showsEvery command, marked as sent |
The fault case is the one that costs something
A unit that shuts itself down raises an error code on its own display, in a room where nobody happens to be standing. Everything useful about that event is shown at the machine. The phone, meanwhile, carries on showing a cooling system, because the last thing it sent was a request to cool.
Someone then checks the app from the office, sees what they expected to see, and stops thinking about an aircon that stopped hours earlier. A clear app screen is weak evidence at the best of times. On a blaster it is not evidence at all, because the screen was never reading the machine.
Whether the drift corrects itself depends on your handset
Two kinds of aircon handset exist, and they recover from drift very differently. Most wall-mounted splits in Singapore flats carry the forgiving kind, which is worth confirming before anything is bought.
Display handsets hold the full state and transmit all of it. So one instruction from the app overwrites whatever the machine was doing, whether or not the app knew about it. The screen can be wrong for hours, and a single press puts machine and app back in agreement. Self-correction here falls out of how the protocol was built. Nobody designed it as a feature.
A handset with no display works by stepping instead. Each press moves one setting to its next value, so a command means up one, and never set to this. Window units and portable units are commonly built this way. Once the app has lost count, it cannot know how many steps to send, and no run of commands lands reliably on the right value.
Controller makers state this openly, which is unusual enough to notice. At least one restricts support to aircon with a full-state display handset, on the stated grounds that synchronisation can be lost when the original handset is used, leaving the controller unable to work out how many step commands to send. The published fix for the stepping kind is manual. Walk to the machine, set it by hand to match what the app shows, then leave the physical buttons alone.
| Setup | What one command carries | Recovery once the app has lost track |
|---|---|---|
| SetupHandset with a display | What one command carriesEvery setting, in one message | Recovery once the app has lost trackOne press from the app puts it right |
| SetupHandset with no display | What one command carriesOne step on one setting | Recovery once the app has lost trackSet by hand at the machine, then start again |
| SetupWrong code table chosen at setup | What one command carriesA message the unit does not recognise | Recovery once the app has lost trackNothing corrects until the right variant is picked |
Settle this by looking at the handset
A screen showing temperature, mode and fan speed means the retrofit will behave itself, and any app state out of sync stays a display annoyance you can clear with one press. That covers most wall-mounted splits fitted in the last two decades.
Buttons and indicator lights with no screen is the harder case. Expect to walk over and re-sync by hand, expect scheduling to be the first thing that gets unreliable, and price the box accordingly. This is also where the honest answer is sometimes to leave the unit alone.
Placement decides whether it still works next month
The blaster has to see the indoor unit's receiver window. Infrared is light and obeys light's rules. Operation manuals put this plainly, and Daikin's tells owners to aim the transmitter at the indoor unit, warning that anything blocking the path between them, such as a curtain, stops the unit responding. The same manual gives a working range of roughly seven metres for the handset.
Angle matters as much as distance in a normal room. A receiver's sensitivity falls away to the side, and the published figure for common modules is the angle at which usable range halves, at around forty-five degrees off centre. A blaster on a side shelf, firing across the room at a slant, works with a fraction of the reach it would have head-on. That arrangement usually passes the install-day test, then starts dropping commands once furniture moves.
Light in the room competes with the signal. Receiver modules are built to reject steady light from bulbs and daylight, along with the flicker from fluorescent fittings with electronic ballasts. Rejection is never free, and every bit of it costs sensitivity. Daikin's manual goes further and warns that signal communication may be disabled outright when an electronic-starter fluorescent lamp is in the room. A blaster parked in afternoon sun is fighting the same fight.
Dust on that window does the same thing quietly, and a service visit is where it gets dealt with. Manuals note that dust on either the transmitter or the receiver reduces sensitivity. Mounted up near the ceiling, the window collects the same film as everything around it. A setup that has slowly turned unreliable is sometimes a cleaning job at the aircon end, which differs from an indoor receiver fault.
- Can the box see the receiver window with the door in every position it normally sits in?
- Is it roughly square on to the indoor unit, or slanted across the room from a corner?
- What gets put down on that surface. A bag, folded laundry, a standing fan
- Does direct sun or a fluorescent fitting cross the path for part of the day?
- Is that small window on the aircon itself clean?
What breaks a setup that used to work
Nothing in the box degrades, which is why the failures are all environmental. A working install fails later because the room changed around it. A new cupboard, a rearranged sofa, a curtain that now gets drawn, a lamp swapped for a different fitting.
The symptom is rarely total silence. It is intermittency: commands landing in the evening and failing at midday, or landing from one app screen and not another. That pattern accuses the signal path first, and it deserves ruling out before anybody opens a unit.
What the feature is honestly worth
This is a cheap retrofit and frequently a sensible one. It reaches a working aircon that was never built for a network, and it leaves the machine completely alone. Nothing gets opened, wired into, or fitted to the indoor board. For a healthy unit with years of life left, that is a fair trade, and none of the limitations above are an argument for spending more.
Remote switch-on is the feature people buy, and the one to hold most lightly. The app can send the command. It cannot confirm the aircon acted, because nothing comes back to confirm it with. If the path happened to be blocked at that moment, the phone shows a cooling room and you walk into a warm one. Treat it as a request that usually lands.
Adding a temperature sensor changes what the system knows, without changing what it knows about the machine. Some of these controllers carry a thermometer and a humidity sensor, and act on a threshold you set. Published behaviour is straightforward. The controller samples the room roughly every ninety seconds and sends a command when the reading crosses your line.
That closes a loop, and the loop goes around the room. A room reading tells you whether the space is cooling. It says nothing about why. If the temperature climbs, the controller keeps firing commands at a machine that might be shut down on a fault, might be missing every pulse, or might be running perfectly and losing to the heat. Something sits between the reading and the cause, and the sensor cannot see it.
One dependency deserves a mention and no more. The box belongs to a company, reaches your aircon through that company's app, and carries whatever lifespan the company decides to give it.
Everything else follows from what the thing is. A blaster is a long-range finger on the handset, with a perfect memory of what it pressed and no way to check what happened next. Bought on that description it earns its money. Bought as a readout of the machine, it will mislead you on the day that matters, in the direction of believing everything is fine.
Ready to get started?
Tell us what’s going on. Symptoms, setup, photos, anything we should know. We’ll assess and come back with the right next step.