Getting the Samsung Remote App to Actually Work
I spent about three hours last week trying to figure out why my phone couldn't control a 2022 Samsung QN90B through the SmartThings app when the infrared remote worked fine across the same room. The issue turned out to be that I was on 5GHz WiFi and the TV was stubbornly sitting on a different subnet because our ISP routed that band through a separate VLAN. Switching the phone to 2.4GHz for the connection, or just moving both devices onto the same band, fixed it immediately. This is the kind of thing Samsung's documentation completely glosses over. The Samsung Remote App (sometimes bundled inside SmartThings, sometimes a standalone download depending on your region and Samsung model year) turns your phone into a universal IR and network-based remote for Samsung TVs, soundbars, and certain home appliances. It handles power, volume, input switching, and the full on-screen menu navigation. The SmartThings version adds device discovery automation, which is where most people run into trouble because the app tries to be clever about network topology and often fails silently. Download links vary by platform. For Android, search "Samsung SmartThings" in the Google Play Store - the standalone "Samsung Remote" app was discontinued around 2021 and folded into SmartThings. For iOS, the same app works, though Apple's networking restrictions mean some features like wake-on-LAN trigger don't always behave the way they do on Android. Both are free. If you're on an older Samsung TV from before 2016, you might need a third-party IR blaster app since those models don't support network-based control.
Here's what actually matters when you're setting this up and it isn't working. First, your TV and phone need to be on the same local network. Not the same router necessarily, but same subnet. If you have a mesh system with separate SSIDs per band, this is where things fall apart. Second, the TV needs to have Network Remote Control enabled, which lives in Settings > General > External Device Manager > Samsung Apps Remote Control. It's off by default on some firmware versions and the app gives no indication of why it can't find the TV. One thing nobody mentions: the app uses TCP port 8001 for control signals and UDP port 55000-55003 for discovery. If you run a custom firewall on your router or have strict IoT isolation enabled, those ports get blocked and the app appears dead even though your WiFi is fine. I had this happen with a UniFi setup where the guest network isolation was on - turning off client isolation for the phone's SSID fixed it right away. For the pairing process, make sure both devices are connected to the same network, open the app, and it should auto-discover your TV within ten seconds. If it doesn't, manually add a device, select TV, and enter the PIN that appears on your television screen. The PIN expires in about two minutes, so if you're fumbling around the TV menu while trying to enter it on your phone, you'll waste a lot of time resetting. I've learned to have the PIN ready on screen before opening the app.
There are legitimate downsides to this approach. The app introduces a noticeable input lag compared to a physical IR remote - usually 200 to 400 milliseconds depending on network conditions. That matters if you're playing competitive games or using the TV as a PC monitor. The Bluetooth Low Energy connection path reduces this somewhat but not completely. Also, if your Samsung TV goes into deep standby (which happens if you enable Eco Solution settings), the app can't wake it unless you've specifically enabled Wake-on-LAN support in the TV's network settings, and even then it's hit or miss on older firmware. Another counter-intuitive detail: the app's virtual remote layout changes based on the TV model it detects. A 2024 S95Z will show a different button arrangement than a 2019 Q70R. This means if you're managing multiple Samsung TVs in one household, you'll need to adjust your muscle memory each time you switch devices in the app. There's no universal remote layout option. For advanced users who want more control than the app provides, you can use the Samsung TV's web interface by entering the TV's IP address followed by port 8001 in a browser. It's not pretty but it exposes settings the app buries three menus deep. Some people also run open-source tools like samsungctl over SSH on a rooted device or through a Home Assistant integration if they want programmatic control. That's beyond the scope of this guide but worth knowing exists if the app's feature set ever frustrates you enough.
Get the Full Details
The app occasionally loses connection to the TV after a firmware update on either end. If you notice the app can see the TV in the device list but commands don't register, the fix is usually to delete the TV from SmartThings and re-pair it rather than trying to troubleshoot the existing connection. The pairing protocol doesn't handle mid-session handshake failures gracefully, so a clean re-add is faster than anything else. I also recommend turning off the "Always On" display mode on compatible Samsung TVs if you're using the app heavily. It sounds unrelated but the constant LED polling from the app's connection check-in interval can keep the screen panel active in ways that degrade burn-in protection on OLED models over time. You won't notice it day to day but after six months of daily app use it accumulates. If you're running a non-Samsung TV or an older model that the app doesn't support natively, your options are more limited. Some older LG and Sony models work through generic IR blaster apps if your phone has the hardware, but network-based control depends entirely on whether the manufacturer exposes a public API. Samsung is unusually generous here compared to most competitors, which is why this app exists in the first place.
Bottom line: the app works well when everything aligns correctly. When it doesn't, the problem is almost always network segmentation, a firmware version mismatch, or a setting buried in the TV's external device menu that nobody remembers to check. Keep those three in mind and you'll save yourself significant frustration.
