OLED Control First Setup: Pair an LG TV on Your Network

Quick setup

Install OLED Control from an official download.

Turn on the LG TV and connect it to the same home network as the device running OLED Control.

Allow local-network access when the operating system asks.

Select the discovered TV in OLED Control.

Accept the pairing prompt on the television with the physical remote.

Test volume or navigation before opening advanced settings.

Keep the physical remote available. First pairing usually requires confirmation on the TV, and some recovery actions cannot be completed from an app that is not connected.

The app and TV must be able to communicate on the local network. Two devices can show the same Wi-Fi name and still be isolated by a guest network, wireless client isolation, VLAN rules, a VPN or firewall software.

For the first attempt:

use the normal home network rather than guest Wi-Fi;

keep the TV awake;

temporarily disconnect a device VPN;

confirm the TV has a valid network connection;

avoid assuming that UPnP or DLNA is required for pairing.

Local-network permission

Apple platforms require permission before an app can discover devices on the local network. If permission was denied, open the operating system's privacy settings, enable local-network access for OLED Control and restart the app. Android permission names vary by OS version and device vendor.

Accept the TV prompt

When OLED Control requests access, webOS may show a confirmation dialog. Approve the connection only when you initiated it. If no prompt appears, restart discovery while the TV is on and check whether a previous rejected pairing must be cleared on the TV.

Menu labels and pairing storage differ by webOS generation and firmware. Do not enter a service menu to repair ordinary app pairing.

Verify the connection

Start with low-risk commands:

read the reported TV state;

adjust volume by one step;

use a navigation command;

open the input list.

Only after these work should you test picture controls or presets. Supported commands vary by TV and firmware. OLED Control cannot create a command the television does not expose.

If the TV is not found

Work through these checks in order:

Confirm both devices use the same non-guest network.

Turn off a VPN or private relay that changes local routing.

Restart OLED Control and wake the TV.

Restart the TV's network connection, then the router if other local devices also fail.

Check router settings for client isolation or VLAN separation.

Follow Connection Issues.

Reinstalling the app does not fix router isolation, so verify the network before deleting anything.

Wake and power limitations

Turning a connected TV off is different from waking it. Wake-on-LAN depends on the TV's standby-network behavior, firmware and router. A television disconnected from mains power has no reachable network adapter. Test wake only after ordinary control works.

Understand what discovery proves

Seeing a TV in the list means the app found a local-network advertisement or reachable endpoint; it does not yet prove authorization. Pairing adds the television's approval. A successful basic command proves both reachability and an accepted control session. Keep these stages separate when troubleshooting.

If two identical LG models appear, compare the room, current power state and network information shown by the app rather than guessing. Turn one set off temporarily if needed. Never approve a prompt on a television you did not intentionally select.

Router checks that actually matter

The most common network failure is isolation. Guest networks often allow internet access while blocking device-to-device traffic. Mesh systems can display one Wi-Fi name across access points and still apply client isolation or IoT VLAN rules. Verify that phone/Mac and TV belong to routable local segments.

Multicast discovery can also be filtered even when direct local traffic is allowed. Rebooting may temporarily restore advertisements, but the durable fix belongs in router configuration. Do not expose the television to the public internet or create broad port forwards for local remote control.

If Ethernet is available, connecting the TV by cable while the controlling device remains on normal Wi-Fi is a useful test, provided both networks share the same LAN. Ethernet and Wi-Fi do not have to be the same medium; they must be allowed to communicate.

Pairing-prompt problems

When the prompt appears and disappears, bring the physical remote close, repeat discovery once and accept promptly. If it was denied, look for the TV's authorized-device or connection-management area using the manual for that webOS generation. Remove only the stale OLED Control authorization, then pair again.

Do not clear every connected device, factory-reset webOS or enter a service menu as a first step. Those actions remove unrelated settings without fixing router isolation.

Verify more than one command

After volume and navigation, open the input list and read the reported active state. Then switch between two safe inputs. If only picture commands fail, pairing is working; the active mode may lock those controls. If input switching works but wake later fails, investigate standby networking rather than pairing.

Record the model suffix and firmware after setup. This makes later compatibility questions much easier than relying on the marketing family name alone.

Security and household approval

Approve only pairing requests you initiated. A local prompt from an unknown app should be rejected. Keep home Wi-Fi protected and update the router and TV through supported channels. OLED Control does not require disabling firewall protections, opening inbound internet ports or sharing a TV PIN with a third party.