Walk into most home theaters and you will find four or five remotes in a drawer: one for the receiver, one for the TV, one for the streaming box, one for the projector, and one nobody can identify. Each controls a slice of the room. None controls the room.

The obvious fix — a universal remote — works by blasting infrared at whatever is in front of it. That is fine for a TV and a soundbar. It falls apart the moment you put the equipment in a cabinet, run a projector from the back of the room, or try to make five devices change state in the right order with one press.

This article is about the other approach: controlling the room over the network, where every command is a message with a destination and a confirmation, not an invisible beam that may or may not have landed.

What Remote97 actually is

Remote97 is control software for home theaters and AV rooms. It runs on Android, Windows and iOS, discovers equipment on your local WiFi or Ethernet, and drives it with each manufacturer's own IP protocol — the same interfaces the vendor apps use, without the vendor app.

Three things define it:

Why this matters for a real room: a native protocol gives you state. You can ask the receiver what input it is on, ask the TV whether it is awake, ask the projector for lamp hours. Infrared can only shout into the dark and hope.

Three kinds of control, one interface

1. Native IP control

Most equipment made in the last decade has a control port on the network. Remote97 discovers these devices automatically over SSDP, mDNS and targeted probes, then connects to the right port and speaks the right dialect. Volume, input switching, power, sound modes, playback transport and app launching all come from the device itself.

2. Serial over IP (RS-232 / RS-485)

A great deal of professional and semi-professional AV gear still exposes an RS-232 port: power sequencers, matrix switchers, motorised screens, lighting controllers, DSPs, and plenty of projectors. A serial-over-IP gateway — a small box, or a piece of software on a PC — puts that serial port on your network as a TCP socket.

Remote97 treats such a gateway as a device with two possible roles: client (the app dials the gateway's IP and port) or server (the gateway or controller dials the app, which listens on a port you choose). You then build a small command library — ASCII or HEX, with an optional CR / LF / CRLF terminator, an optional keep-alive byte, and automatic reconnection — and those commands become buttons, panel widgets and scene steps. The serial-over-IP guide walks through client/server mode, command encoding and delays in detail.

3. Scenes — the part you use every day

A scene is an ordered list of steps: set device A to input X, set volume to −28 dB, wait 800 ms, send a command to the sequencer, wait 2 s, power on the amplifier. Because delay is an explicit step you can insert anywhere, scenes handle the sequencing problem that infrared remotes cannot — and that "all at once" automation usually gets wrong.

What it controls

Device familyProtocolTypical port
Denon / Marantz AVRTelnet ASCII + HTTP status23, 8080
Yamaha receiversYamaha Extended Control (HTTP/XML)80
Sony BRAVIAREST / IRCC over HTTP, Simple IP Control80, 20060
Samsung TV (Tizen)WebSocket remote control8001
LG webOS TVSSAP over WebSocket3000
Xiaomi / Redmi TVXiaomi TV control protocol6095
Apple TVMRP / Companion over mDNS49152–49155
RokuExternal Control Protocol (ECP)8060
Zidoo media playersZidoo HTTP API9529
ProjectorsPJLink (Class 1 / 2)4352
SonosUPnP / SOAP1400
Bluesound (BluOS)BluOS HTTP API11000
WiiM / ArylicLinkPlay HTTP API80, 443
ONVIF camerasWS-Discovery + SOAP3702, 80
Anything with RS-232Serial over IP gateway (TCP)your gateway

Ports are the manufacturer defaults. Some devices can be reassigned — Remote97 probes the common ones and also lets you add a device by IP.

Movie night: the five-remote problem, solved

The classic scene is also the one that proves the concept. One button should do what you currently do by hand: amplifier on, correct input selected, projector or TV on, aspect and volume set, lights down if you control them.

In Remote97 that is a scene with ordered steps:

1

Wake the display

Power on the projector (PJLink) or TV, then wait for it to accept commands.

2

Set the receiver

Power on, switch to the media player input, apply the calibrated volume for that source.

3

Wake the source

Bring the Apple TV or Roku out of standby and launch the app you actually use.

4

Trim the room

Sound mode, subwoofer level, or a second zone for the bar area.

A second scene reverses it. "Good night" mutes the room, powers the amplifier down and leaves the projector to cool — in that order, with a delay long enough that the amplifier is not asked to reproduce the projector's shutdown thump.

KTV rooms: the case nobody else handles

Karaoke — a KTV room in most of Asia — is a harder control problem than a cinema, and it is where general-purpose "smart home" apps usually stop. A KTV room is not one source and one display. It is a karaoke player with its own song library and video output, a microphone mixer or DSP with echo and reverb, an amplifier, a TV or projector, and often a lighting circuit that should change mood between songs.

Worse, the equipment is spread across three control worlds. The player may be IR-only. The mixer is RS-232. The amplifier is IP. The lights are on a relay or DMX box. No single remote covers that, and no infrared blaster can reach the rack.

Remote97 approaches it as one room with three scene states rather than as four unrelated devices:

Why scenes beat macros on a remote: a scene is editable text you can inspect — device, command, value, delay. A macro on a universal remote is a black box that, when it misbehaves, you can only re-record and hope.

Power sequencers: order matters

A power sequencer is a rack unit that switches several outlets on and off in a defined order. It exists for two reasons: inrush current, and noise. Turning on a rack of amplifiers at once can trip a breaker; powering an amplifier before its sources are stable puts a thump through expensive speakers.

The professional convention is simple, and worth getting right even at home:

Most sequencers use one of two control methods: a contact-closure trigger, or a serial command. If yours takes RS-232, it slots into Remote97 as an IP communication device behind your serial gateway. You then write one command per stage — outlet 1 on, outlet 2 on — into the command library, and place them in a scene with delays between them:

Step 1   send  "PWR1 ON\r"   to  Sequencer (IP comm)
Step 2   delay 1500 ms
Step 3   send  "PWR2 ON\r"   to  Sequencer (IP comm)
Step 4   delay 1500 ms
Step 5   send  "PWR3 ON\r"   to  Sequencer (IP comm)
Step 6   delay 3000 ms
Step 7   power on  AVR        (native IP)

The exact bytes come from your sequencer's manual — some use ASCII, some use HEX with a checksum. Remote97's command library accepts both, with CR / LF / CRLF line endings, so you can copy the string straight out of the documentation.

A note on honesty: Remote97 does not ship a driver for every sequencer on the market. It gives you a transport (TCP to an RS-232 gateway), an encoding choice (ASCII or HEX) and a delay-capable scene engine. If your unit understands serial commands, it can be controlled — you supply the command string.

Cameras and the rest of the room

Many media rooms also have a camera or two — a door camera, a kids' room, a rack camera. Remote97 discovers ONVIF cameras over WS-Discovery (or you add one by IP), shows a live thumbnail on the home screen, and opens a full-screen view with pan/tilt/zoom, presets and image settings where the camera exposes them, plus main/sub stream switching. You can also place a live camera view on a custom remote panel. Streams are pulled directly from the camera over RTSP, not through a cloud relay; previews are warmed in the background so a view opens almost instantly, and the app caps how many warm up at once so a wall of cameras does not saturate your network. The ONVIF camera guide covers discovery, credentials, ports and troubleshooting in detail.

Local first: no cloud, no account, no subscription

Every command described above travels from your phone to a device on your own network. There is no vendor server in between, which has three practical consequences:

It also means no subscription. There is no tier that unlocks "advanced" control, because the app is not paying for cloud infrastructure on your behalf.

Platforms and installation

Remote97 runs on Android, Windows and iOS. In practice that means the controller can be a phone in your pocket, a wall-mounted tablet, or the small PC that already lives in the rack. Devices are found automatically on the same subnet; anything that refuses to be discovered can be added by IP address and port.

1

Install the app

Google Play, the App Store, or the Microsoft Store. No account required.

2

Put the controller on the same network

Same WiFi or Ethernet as the equipment. This is a local-control app by design.

3

Scan, or add by IP

Discovery covers receivers, TVs, streamers, speakers, projectors and cameras. Manual entry covers the rest.

4

Build one scene

Start with movie night. Once that button works, the rest of the room follows.

Frequently asked

Can it control a receiver over WiFi instead of IR?

Yes, when the receiver exposes an IP control interface. Denon and Marantz, for example, accept telnet commands and publish HTTP status, so input, volume, power and sound mode all come back as real state rather than assumptions.

Does it work without internet?

Yes. Control traffic stays on the local network. You only need internet to download the app and updates.

Can I control an RS-232 power sequencer?

Yes, through a serial-over-IP gateway. Add the gateway as an IP communication device, store your sequencer's commands in the command library, then place them in a scene with delays to enforce power-up and power-down order.

What about devices that are IR-only?

Remote97 has no IR blaster, so a device with no network and no serial port is out of reach. In practice most IR-only gear in a modern room — players, TVs, projectors — also has an IP or serial control port; the IR remote is simply the consumer interface.

Is there a subscription?

No. No account, no in-app purchase for control features, no cloud relay.

Can one app handle both a cinema and a KTV room?

Yes. Rooms are separate spaces in the app, each with its own devices and its own scenes. A single controller can hold both, and a scene can span rooms if you want a "whole house off" button.

Where to go next

If you are building this out one device at a time, the device-specific guides go deeper on each protocol and what it can actually report: