If it is a Roku, this page is the remote — no app, no account, no pairing. For every other brand, the list further down is the real answer.
Find it on the TV under Settings → Network → About, or in your router's client list. It is saved in this browser only.
Channel IDs are fixed here because a browser cannot read the TV's own list back (the device sends no CORS headers). An ID that has changed launches nothing rather than the wrong thing — if a button does nothing, open the channel by hand once and use the pad instead.
| Platform | This page | How you control it |
|---|---|---|
| Roku / Roku TV | Yes | Open HTTP API (ECP) on port 8060. No pairing, no account, no app. A Roku TV can be powered on over the network. A Roku STICK cannot power the TV — the stick has no control over the panel. Use the TV buttons or HDMI-CEC for that. |
| Android TV / Google TV | No | Google TV app, or the v2 remote protocol on ports 6466/6467 — which needs a TLS pairing handshake with a code shown on screen. Not usable from a browser: the pairing handshake needs raw TLS. The Google TV app is the practical answer. |
| Fire TV | No | Fire TV app over Wi-Fi, or ADB on port 5555 if developer options are enabled. |
| Samsung | No | SmartThings app. The older port-8001/8002 websocket route needs an on-screen accept and is firmware dependent. |
| LG webOS | No | LG ThinQ app. The SSAP websocket on port 3000 requires on-screen pairing. |
| Vizio SmartCast | No | Vizio Mobile app. The local API needs a PIN-pairing step to issue a token. |
| Apple TV | No | Remote in the iOS Control Center. |
Roku is the only one with an open local API. Every other brand needs its own app or an on-screen pairing code, and no web page can do that for you.
Nothing is sent to us. The IP stays in your browser, the button presses go straight from your phone to your TV, and this server never touches either.