The call comes in from a semi in Boghall, or a new-build off Wester Inch, or a bungalow up on Whitburn Road — the same story every time. The Samsung or LG in the living room keeps dropping Wi-Fi. Netflix stalls mid-episode around eight in the evening, iPlayer says the TV isn’t connected, and by the time anyone gets up to look at the router the TV has re-joined on its own. Every phone in the house is fine. The laptop upstairs is fine. Only the TV drops. And when they finally ring us, half of them apologise for “such a small thing” — which it isn’t, because it is a small thing that ruins every evening.
The reason this is worth a proper guide, and not another “have you tried unplugging the router” forum thread, is that a smart TV that drops when everything else stays put almost never has a broken router behind it. The router is happily serving five other devices. What has changed is one of four things on the TV side of the negotiation — the band it’s on, the security mode the router now uses, the DHCP lease it’s been given, or the antenna inside the TV itself. If you’d rather we came out and looked, that’s exactly what a home visit around Bathgate is for. Otherwise, this is the exact order we work through it on the bench, and it fixes about nine out of ten of these calls without touching the router settings a single family member is happy to admit changing.
Why a Smart TV Drops When Nothing Else Does
A modern phone or laptop has a dual-band 802.11ax (Wi-Fi 6) radio, at least two antennas, and firmware that Apple or Samsung ships fresh security patches for every couple of months. A smart TV made between roughly 2016 and 2020 — which is most of the ones we see in West Lothian living rooms — has a single-band 802.11n radio, a printed antenna trace on the back of the mainboard, and firmware the manufacturer stopped updating three years ago. The two are trying to speak to the same router, but they are speaking very different dialects, and the router has quietly moved on.
What has almost always changed between “working” and “not working” is either your ISP swapping in a newer router (BT Smart Hub 2, Sky Broadband Hub, Virgin Hub 5X), a firmware push to the existing one, or a new mesh box (eero, Deco, Google Nest) landing in the hallway. Any of those enable defaults the older TV can’t cope with: band steering that assumes the client is smart enough to choose 2.4 or 5GHz, WPA3 transition mode, or a shorter DHCP lease. The router thinks it’s being helpful. The TV thinks it’s been kicked off. This is a close cousin of the pattern we described in the smart home Wi-Fi keeps dropping guide for Morningside — the same root cause, different device.
1. Check What Band the TV Is Actually On
This is the first check every time, and it is the one that catches roughly half the calls. On the TV go to Settings → General → Network → Wi-Fi Settings (Samsung), or Settings → Network → Wi-Fi Connection → Advanced (LG). Look at the current connection details. If the TV reports a signal frequency of 5GHz and the TV is sat more than four metres from the router, or with an internal wall in between, that is almost certainly your problem. 5GHz has far higher throughput than 2.4GHz, but its range through Scottish sandstone or a modern block-and-render internal wall is roughly a third of what 2.4GHz manages, and its ability to sit through an interfering microwave or wireless doorbell is much weaker.
Most modern routers ship with a single SSID (the same name for 2.4 and 5GHz) and use “band steering” to decide which band each device gets. The TV, being older, does what its firmware was written for in 2018: it associates once to whichever band the router offered at the moment it powered on, and never re-evaluates. If it associated to 5GHz because you had powered it on next to the router during setup, then moved it to the wall bracket by the front window, the signal is now weak and every packet loss looks like a disconnect. Nothing else drops because the phones re-evaluate every few minutes and quietly roam to 2.4; the TV doesn’t.
2. Split the Two Bands (or Force the TV Onto 2.4GHz)
The fix is to give the TV a stable path onto 2.4GHz and leave the phones and laptops on 5GHz where they belong. There are two ways to do that, and which one is right depends on your router. On a BT Smart Hub 2 or a Sky Broadband Hub, go into the router admin (192.168.1.254 for BT, 192.0.2.1 for Sky) → Advanced Settings → Wireless → and turn off “Smart Wireless” or “Single Network Name”. You now get two visible SSIDs — something like BTHub-XXXX and BTHub-XXXX-5GHz. Reconnect the TV to the 2.4GHz one specifically. On the phones, delete the old joined network and rejoin the 5GHz one so they don’t oscillate.
On a mesh system where you can’t split the SSIDs (eero, most Deco setups, Nest Wi-Fi), the fix is different: leave the single SSID in place but tell the mesh to “prefer 2.4GHz” for that specific device from the client list, or as a last resort create a dedicated 2.4GHz-only guest network with a different name and put the TV on that. It is uglier, but it works. This is exactly the same problem, from the router’s side, that we described in the Wi-Fi drops from channel interference guide for a Tollcross flat — when a device really only likes one band, forcing it there is more reliable than hoping the router decides correctly.
3. Check the Router’s Security Mode — WPA3 vs WPA2
This is the check every troubleshooting article on the internet skips, and it is the one that produces the most maddening symptom — the TV connects fine, plays for ten to forty minutes, then drops and refuses to reconnect until you power-cycle it. That is a textbook WPA3 transition-mode failure. The router is offering “WPA2/WPA3 mixed” because that is the modern default, phones and laptops from 2020 onwards use WPA3, and the older TV can’t. It negotiates WPA2, connects, then the router periodically re-keys and the TV either can’t follow the re-key or reads it as WPA3 and gives up.
Log into the router admin, go to Wireless Security, and if you see “WPA2/WPA3 (mixed)” or “WPA3 Personal Transition”, drop it to plain WPA2-PSK (AES) for the 2.4GHz radio. On split-band setups you can leave 5GHz on WPA3 if you want the extra security for the phones; the TV only cares about the band it’s on. Save, wait for the router to re-broadcast, and reconnect the TV. On a bench I keep a very old Samsung 2018 UHD panel to test this exact failure; every time WPA3 transition is enabled, the panel drops within an hour; every time it’s WPA2 only, it stays up for weeks. The router still meets modern security best practice for the devices that can use it — you are only relaxing it for the band the older TV actually uses.
4. Give the TV a Static DHCP Reservation
If bands and security are both sorted and the TV still drops once or twice a day, look at the DHCP lease time. Most home routers ship with a 24-hour lease. When it expires the client is supposed to renew silently, and on a phone or laptop that works. On an older TV the renewal often fails in a way that looks like a full disconnect — the TV goes offline for a minute or two, sometimes displays “network cable is unplugged” briefly (yes, on Wi-Fi), then reconnects with a new IP. If you were streaming through that window, iPlayer or Netflix throws an error and stops.
The cure is a DHCP reservation. In the router admin find the DHCP client list, locate the TV by its MAC address (Settings → About This TV → Network shows it), and set a fixed reservation for it. On BT’s Hub it’s under Advanced Settings → Home Network → Devices → select the TV → “Always use this IP address”. On Sky’s Hub it’s Advanced → LAN IP Setup → DHCP Reservation. The reservation means the TV always gets the same IP without ever renegotiating the lease, which quietly deletes an entire class of dropouts. It also means when the DNS resolver on the TV misbehaves you can point it at 1.1.1.1 or 8.8.8.8 from the router side, which is worth doing on any panel more than three years old.
5. When It’s Not the Wi-Fi — The Antenna and PSU Check
About one call in eight ends up not being Wi-Fi at all, and this is the one every guide misses. Some Samsung and LG panels — particularly the 2017-2019 curved and QLED ranges — have a printed antenna trace that runs along the back of the mainboard, uncomfortably close to the switching power supply. As the PSU capacitors age (four to seven years is when we see the first ones fail properly), the ripple on the low-voltage rails climbs, and the RF section starts picking up interference from its own power supply. The symptom is unmistakable once you know it: the TV drops during high-motion scenes or the moment the panel goes to a very bright frame, because that’s when the backlight draws hardest and the PSU noise spikes.
If you have already worked through bands, WPA3 and DHCP and the TV still drops on bright scenes but is rock-solid on a wired Ethernet cable, that is a hardware fault on the mainboard side, not a network fault. The fix at that point is either a mainboard swap or, more pragmatically for a five-year-old panel, buying a cheap USB-Ethernet dongle for the TV’s USB port and running a physical cable to it — we do this all the time in Bathgate new-builds where the media wall has a socket behind it anyway. If the drops happen even on Ethernet, the mainboard is on its way out and it’s a call between a repair and a replacement panel; that’s the kind of judgement we can help with under a short remote support session before you spend money on kit that won’t help.
What About Interference From Neighbours?
Bathgate’s newer estates — Wester Inch, Boghall, the Balbardie side — are dense enough that on 2.4GHz you can see fifteen or twenty neighbouring networks from your own living room. That’s the same pain the older tenements in central Edinburgh have, but with fewer stone walls to soak the signal, so the interference is actually worse. If splitting the bands and locking the TV to 2.4GHz makes it drop more, not less, you are probably fighting channel congestion rather than a TV problem. Force your 2.4GHz radio to channel 1, 6 or 11 (the only three that don’t overlap in the UK), pick whichever is quietest on a scan, and don’t leave it on Auto — the router’s Auto picker is optimistic. A separate router-age question we cover in the when to replace your home router guide is worth reading too: if your router is more than five years old, its 2.4GHz radio is genuinely deaf in a busy estate and no amount of channel tuning will help.
When to Call Us Rather Than Keep Poking
These five checks (band, split SSIDs, security mode, DHCP reservation, antenna/PSU) resolve most smart-TV Wi-Fi calls we get from Bathgate, Armadale, Whitburn and the Livingston side. If you have worked through them and the TV still drops, the fault is usually one of three things: a router firmware bug specific to a very recent BT or Sky push (which sometimes needs the router set back to defaults, not just rebooted), a genuine mainboard fault on the TV where the antenna trace has cracked, or a mesh node that has been placed just far enough from the TV to be a bad handoff point. All three are things we can look at properly under a networking and Wi-Fi visit, and it saves a fortnight of poking at settings that were fine to begin with.
For the wider set of home Wi-Fi patterns we see across Bathgate, Broxburn, Livingston and the Whitburn side, the home and office callout service covers the whole area — and if it turns out to be a router that is genuinely past its useful life rather than a TV that needs coaxing, we can scope a proper replacement (a mid-range mesh, split SSIDs enabled, WPA2 kept for the older devices in the house) without turning it into a monthly emergency.
Last updated: 22 September 2026