Skip to main content
snowflakeaircon.sg

Why is my aircon remote not working?

Your remote gets no response, or works only at a close angle. The fault sits in one of three places: the remote signal, the indoor receiver that catches it, or the unit's response to a command it did accept. Which one tells you whether you need batteries or a technician.

By Team Snowflake | Reviewed 30 May 2026

1. Remote battery or signal path issue

You press a button and the indoor unit gives nothing back: no beep, no display flicker, no change at all. The most common cause is the simplest one: weak batteries, a remote with a damaged transmitter, or a blocked line of sight. Infrared needs a clear path, so a curtain pulled across the unit or new furniture in the way can quietly cut the range.

How to tell

This path gives no response at all. Unlike a downstream cooling fault, there is no beep, display flicker, or fan movement. A phone-camera test can show whether the remote emits infrared. If it does not flash, start with batteries or the transmitter.

  • No beep or display response from the indoor unit when you press a button.
  • The remote screen looks dim, faint, or flickers.
  • The unit responds only when you stand very close or point carefully.

How we confirm it

We test the remote's infrared output with a phone camera and try a fresh set of batteries. If the signal flashes clean but the unit still ignores it, the fault moves to the receiver side and we check there next.

Do not let anyone replace the indoor board before the remote is confirmed to send a clean signal. Quoting a board swap before the cheapest check skips the actual fault.

2. Indoor receiver or command input fault

The remote checks out: the phone-camera test shows a clean infrared flash, so you know it is transmitting. The indoor unit still gives no response. The receiver module, a small part usually mounted behind the front panel and wired to the main board by a short harness, has failed. The failure is usually silent: no error code, no light change, the unit simply never registers that a command arrived.

How to tell

This path has a working remote but a silent unit. Unlike a battery or signal fault, the phone-camera test shows infrared. Unlike a downstream cooling fault, the unit does not beep. Intermittent response unrelated to aim points to the receiver.

  • The remote flashes clean on a phone camera, but the indoor unit stays silent.
  • Response is intermittent in a way distance or angle does not explain.
  • Fresh batteries and a clear line of sight do not restore any beep.

How we confirm it

We test the receiver module directly and check its harness back to the indoor board. If the receiver is confirmed faulty, we replace that part without touching the main board.

Replacing the remote will not fix an intermittent response. A receiver that answers only sometimes is failing, and a fresh remote changes nothing while the real fault stays hidden.

3. Command is accepted but cooling fails

You press the remote and the unit beeps, or the display changes, so the signal clearly reached the indoor board. Then nothing useful happens. The indoor fan may not start, or it spins but the outdoor unit never kicks in, or no cold air arrives. The remote is doing its job. The fault sits downstream in the startup or cooling path.

How to tell

This path starts after acknowledgement. Unlike remote or receiver faults, the unit beeps or display changes on each press. The failure comes next: fan hesitation, outdoor non-start, no cold air, flashing lights, or an error code.

  • The unit beeps or the display changes when you press the remote.
  • The indoor fan may run, but no cold air arrives.
  • The outdoor unit stays silent, or you see flashing indicator lights.

How we confirm it

Once the beep confirms the command path is intact, we shift to the outdoor startup circuit and refrigerant state rather than chasing the remote any further. We read any error code the board reports and trace the no-cool path from there.

Do not pay for a new remote or receiver while the unit is beeping and accepting commands. The acknowledgement proves the remote path already works, so that quote chases the wrong end of the chain.

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.

WhatsApp us