M Shaker

OneMote — Will it work with my TV?

OneMote is a free universal smart-TV remote for iPhone and Android. It talks to your TV over your home WiFi using each brand’s own protocol — no account, no cloud remote server, no subscription.

Requirements

Phone and TV on the same WiFi network (not cellular).
Guest / IoT / “client isolation” WiFi often blocks discovery — use your main home network.
A smart TV or streaming stick with a network control API (not IR-only).

This page mirrors the app’s Supported TVs table. Status labels are honest: Works well means owner-validated hardware; Beta and Limited confirmation mean the code ships but we have not validated every model ourselves.

Quick status

Brand	Pairing (first connect)	Status
Roku	None	Works well
Samsung (Tizen)	On-TV Allow	Works well
LG (webOS)	On-TV PIN (prompt fallback on old firmware)	Works well
Google TV / Chromecast built-in	On-TV PIN	Works well on Google-services devices; not China PatchWall
Fire TV (Fire OS)	PIN; optional ADB Allow once	Works well on Fire OS
Fire TV (Vega OS sticks)	PIN (basic remote)	Limited on some models — no ADB tier
Apple TV	PIN	Beta
Sony BRAVIA	Pre-shared key (TV setting)	Shipped — limited hardware confirmation
Vizio SmartCast	On-TV PIN	Shipped — limited hardware confirmation
Hisense VIDAA	4-digit code (newer) / open (older)	Beta

Find your TV by the name on the box

Most shoppers know the name on the bezel, not the protocol name — you own a TCL, not a “Google TV Remote v2 device.” The good news: nearly every retail nameplate below already ships one of the nine systems in the Quick status table above, so it already works with OneMote today. The catch is one nameplate ships different systems across models, regions and model years — your TV’s own home screen (or its box) is always the authority for which one your set actually runs. This table points you at the right row above; it is not a per-model guarantee.

Nameplate	Systems it ships (OneMote controls these)
TCL	Google TV, Roku TV, Fire TV
Hisense	Google TV, Hisense VIDAA, Roku TV, Fire TV
onn. (Walmart)	Google TV, Roku TV
Insignia (Best Buy)	Fire TV
Toshiba	Fire TV (see below for Japan-market Regza)
Philips	Google TV, Roku TV (see below for Saphi and Titan OS)
Sharp	Roku TV, Google TV (see below for Japan/EU Aquos)
Element	Roku TV, Fire TV (also sells non-smart sets — see below)
Westinghouse	Roku TV, Fire TV
Panasonic	Fire TV, Google TV (see below for My Home Screen)
Xiaomi / Mi	Google TV (see below for PatchWall/MIUI TV)
Nvidia Shield	Google TV
JVC · RCA · Magnavox · Sanyo · Hitachi · Polaroid · InFocus · Atvio	Roku TV (Roku licensee nameplates) (several also sell non-smart sets, and JVC ships Titan OS in Europe — see below)

Not on this list? A lot of TVs sold under a store’s own name (or a name you’ve never heard of) are still one of the nine systems above underneath — check the TV’s own home screen for the system name (Roku, Google TV, Fire TV, and so on), or open OneMote’s “+ Add TV by IP address” → “Don’t see your brand?” for the same lookup, in the app.

Roku

Protocol: ECP over HTTP :8060
Pairing: None — connect and use the remote.
Works well for: TVs, sticks, Streambar; private listening (headphones on your phone); live typing; find-my-remote; channels on tuner TVs.
Notes: Tuner sticks/boxes without a live-TV tuner do not show a Channels list. Private listening is Roku-only.

Samsung (Tizen)

Protocol: Remote channel over WSS :8002
Pairing: An Allow prompt appears on the TV → OneMote stores a token.
Works well for: Daily remote, true pointer cursor, keyboard, casting/mirroring where the set supports it.
Notes: No third-party picture/sound settings API on this surface.

LG (webOS)

Protocol: SSAP — ws :3000 ( wss :3001 fallback )
Pairing: On-TV PIN typed into the phone (no TV remote needed). Older firmware may fall back to an on-TV connection prompt.
Works well for: Pointer, live typing, picture/sound presets, Peek still-frame, force-close app, channels, Wake-on-LAN.
Notes: Some single-source mappings (e.g. Guide) are flagged VERIFY in-app until confirmed on a given firmware.

Google TV / Chromecast built-in (Android TV Remote v2)

Protocol: Remote v2 — TLS :6467 (pair) / :6466 (control)
Pairing: On-TV PIN + client certificate.
Covers: Xiaomi Mi TV / TV Stick / Mi Box (global), TCL, Philips, Nvidia Shield, onn., Chromecast with Google TV, and other Google TV OS devices discovered via mDNS.
Works well for: Daily remote, d-pad and touchpad gestures, keyboard, app launching, Google Cast casting and screen mirroring, Wake-on-LAN.
Validated: Discovery, PIN pairing and control confirmed on owner hardware (an onn. Google TV) in August 2026 — not just shipped code.
Not supported: China-market Xiaomi sets running PatchWall / MIUI TV without Google services — different local API, not covered.

Fire TV

Protocol: HTTPS REST :8080; optional ADB :5555 on Fire OS for advanced controls.
Pairing: PIN on first connect. ADB (Fire OS only): one-time USB-debugging Allow — can be tapped from OneMote’s in-sheet d-pad.
Works well for (Fire OS): Basic remote on REST; ADB unlocks Now Playing, Peek, app manager, force-close, and more.
Limited — Vega OS: 2025+ Fire TV Stick 4K Select and 2026 Fire TV Stick HD run Amazon’s Vega OS (no network ADB bridge). OneMote detects this and offers the basic REST remote only — not full ADB features. Detection is VERIFY (no owned Vega hardware).

Apple TV (Beta)

Protocol: Companion over TCP (Bonjour-advertised port)
Pairing: PIN (SRP)
Status: Beta — shipped and usable; depth and edge cases still expanding. Not presented as owner-validated.

Sony BRAVIA

Protocol: IP Control over HTTP :80
Pairing: Pre-shared key set on the TV.
Status: Shipped — limited hardware confirmation (unowned). Do not assume every BRAVIA model or firmware behaves identically.
Includes (VERIFY): Channels, Now Playing label, keyboard/paste via setTextForm v1.0 plaintext on sets that accept it.

Vizio SmartCast

Protocol: REST over HTTPS :7345
Pairing: On-TV PIN → auth token.
Status: Shipped — limited hardware confirmation (unowned). No universal model guarantee.
Includes (VERIFY): Picture presets, curated app launch (~24 apps), label-only Now Playing. No phone keyboard on this protocol.

Hisense VIDAA (Beta)

Protocol: MQTT on :36669 (TLS or plain TCP)
Pairing: 4-digit on-TV code on newer firmware; older sets may connect without a code.
Status: Beta. Many Hisense sets ship Google TV / Roku / Fire OS instead — those use the matching brand above, not VIDAA.

Systems we do not cover

Some nameplates above also sell TVs running a system with no third-party local control API we can speak — this is not a defect of the TV, there is simply no published interface for an app like OneMote to use on that operating system:

Philips Saphi — Philips’ own Linux-based OS, mostly EU budget sets.
Titan OS — the European platform that replaced Saphi across most 2024-and-later entry/mid Philips sets, and also ships on some JVC and AOC models. Philips’ higher-end ranges still run Google TV, which does work — check your set’s home screen.
Panasonic My Home Screen — Panasonic’s own OS, legacy EU/JP sets (current US/EU flagships run Fire TV or Google TV instead — see the table above).
Xiaomi PatchWall / MIUI TV without Google services — China-market Xiaomi/Mi sets.
Japan-market proprietary systems — Sharp Aquos’ and Toshiba Regza’s own house OSes, sold only in Japan.
IR-only or non-smart TVs with no network control API.
Guest/IoT VLAN setups that isolate phones from TVs (network issue, not a brand or system gap).

Claiming “every model of every brand” would be dishonest — ports and pairing above are the grounded contract; feature depth is capability-gated per TV. If you own one of the systems above and it turns out to answer a local control API after all, let us know — we’d rather re-open a row than leave it wrong.