Four ways to control a TV
Before you pick hardware, pick a route. Which one fits depends on what is connected to your screen.
| Route | How it works | Suits | Watch out for |
|---|---|---|---|
| A. Infrared (IR) | An IR LED sends the same pulses as the original remote. | Almost any TV, including old ones without a network. | Needs a phone with an IR blaster or a separate IR hub, and line of sight to the TV. |
| B. Network API | The TV or box accepts commands over your home network. | Roku, Samsung (Tizen), LG webOS, Google TV / Android TV, Philips, Sony. | Different for every brand. First connection often needs approval on the TV. Manufacturers can change or restrict it. |
| C. HDMI-CEC | Commands travel through the HDMI cable: power, volume, input. | Anything with a CEC-capable HDMI port (brand names vary: Anynet+, Simplink, Bravia Sync). | Works unevenly between devices and covers only a few commands. |
| D. Bluetooth or Cast | A phone or small computer acts as a keyboard, or sends media to the screen. | Streamers such as Fire TV, Google TV, Apple TV. | Casting sends content, it does not press buttons. |
Common confusions
"I have a Chromecast"
An older Chromecast only receives casts and has no remote interface. A Chromecast with Google TV is an Android TV device and does have a remote protocol. Check which one you have before you plan anything.
"Can my phone's browser do this?"
Partly. A web page can talk to devices on your local network, but browsers ask permission for it and handle it differently. A web page cannot send infrared at all. That is why the RemoteYou starter kit uses a small bridge that does the device-specific work, and you only design the interface on top.
"My iPhone has no IR"
Correct. iPhones never had it. Use a network API or an inexpensive IR hub instead.
Next
IR sources · Roku · Google TV · LG · Samsung · HDMI-CEC · Hardware