Open Controller Architecture
Choose your controller — MyURemote integrates.
IP and RS-232 (via TCP bridges). IR via compatible controller hardware.
MyURemote is not limited to one hardware platform. It can work with fully supported controller hardware (like Global Caché), with other TCP-based controller hardware, and with direct IP devices where a “controller” can be software only.
What is a “controller”?
A controller is the middle layer between the app and your AV device. MyURemote sends commands over your network to a controller, and the controller translates them into IR, RS-232, or passes them through as TCP/HTTP/WebSocket.
MyURemote → (LAN/Wi-Fi) → Controller → (IR / RS-232 / TCP) → AV Device
For native IP control, the “controller” can be software-only: MyURemote connects directly to the device.
Protocol Support
- TCP sockets
- HTTP
- WebSocket
- RS-232 over TCP (via controller hardware)
- IR via supported controller hardware
- UDP (UDP-based control is not supported by MyURemote)
MyURemote communicates over TCP-based protocols for consistent, reliable control behavior.
Contents
1. Controller options in MyURemote
In MyURemote you can choose between three controller types for AV integrations: Global Caché, Serial – TCP to RS-232 bridge, and TCP/IP Controller.
- Most supported controller platform in MyURemote
- Auto-detected on the network
- Recommended for IR control
- Also fully supported for serial (RS-232)
Use Global Caché when you want the smoothest experience, or when you need IR.
→ Global Caché guide (models, setup, ports, IR/serial essentials)
- Alternative path for RS-232 devices
- Works with generic TCP↔RS-232 bridges (transparent mode)
- Manual setup (IP address + port)
This controller demonstrates MyURemote’s open architecture: you are not locked into one hardware vendor.
- For devices with native TCP, HTTP or WebSocket control
- Often no hardware controller is needed
- Manual setup: IP + port (and command format)
Best for modern IP-controlled devices. The “controller” can be software-only.
Users can add their own commands. At the moment this is available via the legacy settings menu. The new Ionic interface will include this workflow as well.
2. How integration works (non-Global Caché & direct IP)
The core integration concept in MyURemote is simple: MyURemote connects to an endpoint over TCP and sends a command string/message. What happens next depends on the type of endpoint: it can be a direct IP device, or it can be controller hardware that converts TCP into IR or RS-232.
- Device exposes TCP, HTTP, or WebSocket
- MyURemote connects directly to the device
- Configure: IP + port (and command format)
Example: modern TVs, AV receivers, streamers, custom IP endpoints.
- Hardware exposes a TCP server socket
- It converts TCP commands to RS-232 or other outputs
- Configure: IP + port (and device-specific settings)
This is where MyURemote’s open architecture shines: any compatible TCP endpoint can be integrated.
- Auto-discovery and best-supported workflow
- Recommended for IR
- Also fully supported for serial
Global Caché is not required for direct IP control — but it is the most supported controller hardware platform. → MyURemote ↔ Global Caché guide
The next section details one concrete, proven example of option B: using a generic TCP↔RS-232 bridge (Waveshare) with the MyURemote Serial – TCP to RS-232 bridge controller.
3. Serial – TCP to RS-232 bridge (worked example)
The Serial – TCP to RS-232 bridge controller is designed for generic serial bridges that expose a raw TCP socket. MyURemote connects to the bridge (ip:port) and sends serial command strings. The bridge outputs the bytes over RS-232 to the device.
MyURemote → LAN/Wi-Fi → TCP↔RS-232 bridge → RS-232 cable → AV device
Bridge requirements
- TCP Server mode (bridge listens; MyURemote connects as TCP client)
- Transparent / Raw mode (no proprietary packet wrapping)
- Reachable on the same LAN/Wi-Fi (avoid guest isolation)
Serial requirements
- Baud rate, parity, stop bits, flow control must match the device spec
- Most devices require a command terminator (often
\r)
Note: Serial control does not “always require” this bridge approach. It is an alternative to Global Caché that proves MyURemote is not locked into one vendor.
4. Setup in MyURemote (step-by-step)
Step 1 — Create the controller
In MyURemote, create a new controller and select: Serial – TCP to RS-232 bridge.
Step 2 — Enter IP address and port
- IP address: the LAN IP of your bridge (recommended: DHCP reservation)
- Port: the TCP server port configured on the bridge (varies per hardware)
Create a DHCP reservation in your router so the bridge always keeps the same IP address.
Step 3 — Select the device
Select the target device in your MyURemote configuration and map the required commands (power, volume, sources, macros, etc.).
Step 4 — Add or edit commands
Users can add custom commands. This is currently available in the legacy settings menu. (The new Ionic interface will include this workflow.)
The bridge serial parameters must match the device specification (baud/parity/stop/flow),
and many devices require a terminator (often \r).
5. Real-world case — Bose amplifier via Waveshare WiFi serial bridge
To demonstrate MyURemote’s flexibility, we integrated a Bose amplifier using a generic third-party TCP↔RS-232 module. No Global Caché hardware was used for this serial installation.
Controller hardware used
- Waveshare WiFi-UART / RS-232 module
- Configured as TCP Server
- Used as transparent TCP→RS-232 bridge
Important: the module must operate as a simple raw TCP-to-serial bridge. Advanced negotiation features should be disabled.
Bridge configuration (example)
- Network Mode: STA (DHCP Client)
- Working Mode: TCP Server
- Local Port: 8899
- Baud Rate: 19200
- Data Bits: 8
- Parity: None
- Stop Bits: 1
- Flow Control: Disabled
- Baudrate Adaptive (RFC2217): Disabled
MyURemote configuration
- Controller Type: Serial – TCP to RS-232 bridge
- Technology: serial
- IP Address: bridge IP (example:
192.168.29.12) - Port: 8899
- Command Terminator:
\r(CR)
After configuration, MyURemote successfully controlled:
- Power On / Off
- Volume Up / Down
- Source selection (individual source commands)
Global Caché is the most supported platform (and recommended for IR), but MyURemote can also integrate with other TCP-based controller hardware. When the bridge settings are correct and the right IP/port are configured in MyURemote, serial control is reliable.
6. FAQ
Do I always need Global Caché?
No. For direct IP control (TCP/HTTP/WebSocket), a hardware controller is often not needed. Global Caché is recommended when you need IR, and it is also a fully supported option for serial.
Will MyURemote auto-discover my generic serial bridge?
Usually not. Generic TCP↔RS-232 bridges are typically configured manually using IP address and port. Global Caché devices are auto-detected.
Is Serial – TCP to RS-232 bridge the only way to do RS-232?
No. RS-232 can also be implemented using Global Caché serial controllers (fully supported). The “Serial – TCP to RS-232 bridge” option exists to support other TCP-based serial bridge hardware.
Why is UDP not supported?
MyURemote uses TCP-based communication for predictable delivery and consistent remote behavior. If a device only supports UDP control, it is not supported by MyURemote.
Where can I find the Global Caché setup guide?
Bottom line
MyURemote is controller-agnostic within clear TCP-based boundaries: direct IP control can require no hardware, Global Caché is the most supported platform (recommended for IR), and compatible third-party TCP-based controllers can also be integrated.
Correct endpoint configuration + correct IP/port in MyURemote = reliable control.