Native IP control is great until you meet the equipment in the rack. Professional and semi-professional AV gear frequently exposes only RS-232 or RS-485, with a terse command table buried in a PDF manual. No app, no API, no cloud — just bytes on a wire.
The bridge is a serial-over-IP gateway (also called a serial device server, IP-to-serial converter, or "IPserver" when it is software running on a PC). It converts serial signals to a plain TCP socket. Once that socket exists, your phone can talk to the device over the local network from the same app that controls the receiver and the TV.
What you need
- A serial-over-IP gateway configured for your device's serial parameters, with a known IP address and TCP port.
- The command strings from the device manual — as ASCII text (e.g.
PWR 1 ON) or as HEX bytes (e.g.A5 01 00 FF). - The controller (phone or PC) on the same local network as the gateway.
Two connection modes
Which side initiates the TCP connection depends on the hardware. Remote97 supports both, selected when you add the device.
| Mode | Who connects | Typical use | Status shown |
|---|---|---|---|
| TCP client | Remote97 dials the gateway's IP and port | A hardware serial device server, or IP-to-serial software on a PC | Connected / disconnected |
| TCP server | The gateway (or a PC controller) dials Remote97, which listens on a port you choose | Setups where the gateway is configured as a TCP client, or a PC sends commands to the app | Listening / not listening |
In server mode the app binds to all local interfaces and accepts multiple simultaneous clients; commands are sent to every connected client. The connected client IPs are listed, and you can attach a local note to each one so you remember which is which. There is no "power on / standby" concept for this device family — the status reflects the connection, not the device's power state.
Adding the device
Choose the IP communication category
In the add-device screen, pick the IP communication device category. It skips network scanning and goes straight to the manual form — there is no reliable way to auto-discover an arbitrary TCP port.
Enter host and port
For client mode, the gateway's address. For server mode, the local listening port (use a port above 1024).
Set encoding and line ending
ASCII or HEX, plus the device's default terminator: none, CR, LF, CRLF or a custom HEX suffix. Optional keep-alive bytes and a reconnect timeout are available for gateways that need them.
Test, then name and assign a room
Send a command from the quick-send box to confirm the wiring before you start building buttons.
The command library
Rather than pasting raw strings into every button, you build a small library of named commands. Each entry stores its payload, formatting and timing:
- Name, description and folder — so "Screen down" still makes sense six months later.
- Scope — global, or tied to one specific device.
- Payload — ASCII text or HEX byte pairs.
- Line ending override — inherit the device default, or set none / CR / LF / CRLF / custom HEX per command.
- Timing — a pre-delay, a post-delay and a repeat count, because serial gear often needs a pause between frames.
ASCII and HEX, always in sync
The command editor shows two fields at once: an ASCII line and a HEX line, kept in real time from a single byte array. Type PWR ON above and the bytes appear below; type A5 01 00 FF below and the text representation appears above. You never have to choose a mode or convert by hand.
The HEX field is built for real manuals, not just careful typing: it auto-inserts spaces every two characters, uppercases on blur, and accepts pasted values in almost any shape — A1B2C3, A1 B2 C3, 0xA1 0xB2, or comma-separated. Bytes that cannot be printed (control codes, high bytes that are not valid UTF-8) are shown as a middle dot so byte positions are preserved without garbage characters. A live byte counter tells you the frame length.
Terminators are deliberately separate from the payload. You put only the command body in the field; the app appends the chosen CR / LF / CRLF or custom HEX suffix exactly once when sending. That avoids the classic double-0D bug where a terminator is typed into the payload and then added again.
Where commands become controls
A saved command is not tied to one screen. The same library entry can be referenced from several places, so editing the command once updates everything that uses it:
- Custom buttons on control panels — build your own remote layout with buttons bound to library commands.
- Direction pads — each direction (up, down, left, right, centre) can be bound independently, so a D-pad can drive a matrix switcher or an on-screen menu instead of a transport control.
- Scenes — an ordered list of steps with explicit delays, mixing serial commands with native IP commands for other devices.
- Quick send on the device page — type ASCII or HEX directly and fire it once while testing.
Why the delay step matters: a power sequencer
A power sequencer switches rack outlets on and off in a defined order, to avoid inrush current tripping a breaker and to keep an amplifier from reproducing the thump of its sources powering up. Sources go on first, processing next, power amplifiers last; power-down is the reverse.
Because a scene lets you insert a delay as an explicit step, the sequence is readable and editable text rather than a black-box macro:
Step 1 send "PWR 1 ON\r" to Sequencer (IP communication)
Step 2 delay 1500 ms
Step 3 send "PWR 2 ON\r" to Sequencer (IP communication)
Step 4 delay 1500 ms
Step 5 send "PWR 3 ON\r" to Sequencer (IP communication)
Step 6 delay 3000 ms
Step 7 power on AVR (native IP)
The exact bytes come from your sequencer's manual. Some use ASCII with a carriage return, others use HEX frames with a checksum. Both are supported — you supply the string, Remote97 supplies the transport, encoding and timing.
Debugging without a laptop
Serial gear is trial-and-error by nature, so the app keeps a communication log: sent and received bytes are written together, with a short HEX preview for each entry. Logs survive an app restart, can be viewed in full on a dedicated activity-history screen, filtered per device, and cleared when you are done. A retention setting controls how many days of history are kept. That makes "which command did I send before it worked?" answerable from the phone rather than from memory.
The technical summary
| Item | What Remote97 does |
|---|---|
| Transport | Raw TCP, client mode (outbound) or server mode (inbound listener) |
| Encoding | ASCII text (UTF-8 / Latin-1) or HEX byte pairs, edited together in one live-syncing control |
| Framing | Device-level default terminator (none / CR / LF / CRLF / custom HEX), overridable per command; optional keep-alive bytes |
| Timing | Per-command pre-delay, post-delay and repeat count; explicit delay steps in scenes |
| Reliability | Automatic reconnection with a configurable timeout |
| Server mode | Binds to all local interfaces, accepts multiple clients, lists their IPs, broadcasts commands |
| Serial parameters | Not handled by the app — baud rate, parity and flow control belong to the gateway |
| Discovery | Manual add only; arbitrary TCP ports are not auto-scanned |
| Storage | Commands, connection settings and communication logs stay on the device — no cloud, no account |
Troubleshooting
Connection refused or always disconnected
Confirm the gateway's IP and TCP port, that the phone is on the same subnet, and that no firewall is blocking the port. In server mode, connect to the phone's actual LAN IP and use a port above 1024.
Connected, but nothing happens
Check the gateway's baud rate, parity and flow control against the device manual. Then check the terminator — a device expecting 0D will ignore a frame without it, and a device expecting no terminator may reject one. Finally check ASCII versus HEX: the same characters sent as text and as bytes are different frames.
Commands work in quick send but not from a button or scene
Make sure the widget is bound to the right library command and that the command's scope matches the device. Remember that bindings resolve the library entry at send time, so renaming or editing a command updates every bound control.
Local first
Commands travel from the phone to the gateway on your own network. There is no vendor server and no account, so the whole setup keeps working during an internet outage. It also means controlling the gear from outside the home requires your own VPN into the LAN.
Frequently asked
What hardware do I need?
A serial-over-IP gateway (a small hardware serial device server, or IP-to-serial software on a PC) wired to the device's RS-232 or RS-485 port, plus the device's command list from its manual.
Does Remote97 set baud rate or parity?
No. Those are serial-side settings and belong to the gateway. Remote97 only sends bytes over TCP. If the framing is wrong, configure the gateway to match the device manual.
Do I have to choose between ASCII and HEX?
No. The command editor shows both lines at once and keeps them synchronised from the same byte array. Paste HEX in almost any format and the text line follows; type ASCII and the byte line follows. Non-printable bytes are shown as a placeholder dot.
What is a line ending / terminator for?
Many serial devices only act on a complete frame, marked by CR (0D), LF (0A), CRLF, or a custom byte sequence. You set a default per device and can override it per command. The terminator is appended once at send time, so it is not typed into the payload.
Can I use these commands in scenes with other devices?
Yes. A scene is an ordered list of steps that can mix serial commands with native IP commands, with explicit delays between them. That is how a power sequencer can bring sources up before the amplifier.
Can the app act as a TCP server?
Yes. In server mode Remote97 listens on a port you choose, accepts multiple clients, lists their IP addresses and sends commands to all connected clients. This is for gateways or PC controllers configured to dial in.
Will it find my gateway automatically?
No. Arbitrary TCP ports cannot be discovered reliably, so this device family is added manually by host and port. Native-IP devices such as receivers, TVs and cameras are still auto-discovered.
Does it work without internet?
Yes. Control traffic stays on the local network; internet is only needed to download the app and updates.
Where to go next
- ONVIF cameras: live view, PTZ and local-only control — the other "no native driver" addition.
- Home theater & smart home control: the complete guide — where serial gateways fit in a whole room.
- Set up one-tap movie-night scenes — ordered steps and the right power sequence.
- Why local IP control beats cloud hubs — the architecture argument.
