Tech Behind ThingsHow the ordinary machinery actually works

Home Tech

How an infrared remote shouts a number at the whole room

It does not aim, it does not connect and it never receives an answer. It flashes an invisible code and hopes something is listening.

A modern bedroom featuring a robot on a bedside table and a man sitting on a bed.
Photograph by Pavel Danilyuk via Pexels
Editorial note. Independent reporting and analysis. Nothing here is sponsored or paid for. How we work.

The options around infrared remote control are set out side by side below, with the conditions that genuinely favour one over the other.

The difference in one place

  • The code rides on a modulated carrier so the receiver can reject sunlight.
  • The signal reflects off walls, which is why aiming is often unnecessary.
  • Nothing is sent back, so a remote never knows whether it worked.

An invisible lamp flashing a pattern

The emitter is a light emitting diode producing infrared, just outside the range human eyes can detect. It is switched on and off in a precise pattern, and that pattern is the entire message being sent. A phone camera without an infrared filter often shows the emitter flickering, which is a simple way to test a remote.

Because it is light, the signal is blocked by anything opaque and passes through most plastics used for equipment fronts. The dark window on the front of a device is a filter that passes infrared while hiding the components behind it.

The carrier exists to defeat daylight

Sunlight, filament lamps and many fluorescent fittings all emit strongly in the infrared, flooding the receiver with noise. A remote therefore does not simply switch its emitter on, but pulses it rapidly at a fixed carrier frequency.

The receiver contains a filter tuned to that frequency and ignores anything arriving without it, including steady sunlight. Different manufacturers chose different carrier frequencies, which is one reason remotes are not interchangeable between brands. Strong sunlight can still saturate the receiver entirely, which is why remotes work poorly in a conservatory at midday.

What the flashes actually spell

A transmission usually begins with a longer burst that lets the receiver establish timing before any data arrives. Bits are encoded by varying the gap between bursts, so the pattern is carried in timing rather than in brightness. The message typically contains an address identifying the type of device and a command identifying the button pressed.

In practice, many schemes send each value twice, once inverted, so the receiver can discard anything that fails that check. Holding a button sends a short repeat code rather than the full message, which is how volume ramps smoothly.

Aiming matters less than it appears

Infrared reflects reasonably well off pale walls and ceilings, so a signal often arrives after bouncing rather than directly. This is why a remote works when pointed at the ceiling in a small light room and fails in a large dark one.

Under load, reflected paths are weaker, so a fading battery reduces range by removing the margin that reflections relied on. Glass doors on a cabinet attenuate the signal, and some coated glass blocks infrared far more than visible light.

A dirty or obstructed receiver window has the same effect as a weak transmitter and is much easier to fix.

Why one remote operates two devices

Address codes are not centrally allocated, so different manufacturers have historically reused the same values. Two devices from the same brand often share an address deliberately, which is why one remote controls both. Some equipment allows an alternative address to be selected, which separates two identical units in one room.

Universal remotes work by storing the code sets of many manufacturers and transmitting whichever set you select. Learning remotes instead record the raw timing of another remote's transmission and replay it exactly.

Firmware updates change this behaviour more often than hardware does.

What replaced it, and what did not

Radio-based remotes do not need line of sight and can operate equipment inside a closed cabinet or another room. They require pairing, since a radio signal reaching several devices needs a way to address one of them specifically. Control signals carried over the display cable let one device switch and control another without any remote at all.

Under load, that arrangement is convenient and notoriously inconsistent between manufacturers, despite being a published standard. Infrared survives because it is cheap, needs no pairing and fails in ways people immediately understand.

Side by side

ConsiderationWhat it means in practice
An invisible lamp flashing a patternThe code rides on a modulated carrier so the receiver can reject sunlight.
The carrier exists to defeat daylightThe signal reflects off walls, which is why aiming is often unnecessary.
What the flashes actually spellNothing is sent back, so a remote never knows whether it worked.

The takeaway

It is a torch spelling a number, and nothing ever confirms the number arrived.

Understanding the failure mode tells you more than the feature list does.

Questions readers ask

Why does my remote work better when I point it at the ceiling?

The signal reflects. A pale ceiling scatters it across the room, which can reach a receiver that a direct line does not.

Can a remote be affected by another device?

Yes. Strong infrared from sunlight, plasma displays or some lighting can swamp the receiver even at the correct carrier frequency.

Home Techremotesinfraredprotocolshome
Alba Ferrer
Privacy writer, Tech Behind Things

Alba writes about telemetry, tracking and encryption in terms that do not require a threat model.

Also by Alba Ferrer