Network, privacy and troubleshooting
Last reviewed 2026-11-02.
The TV and Mac must see each other
ArtFrameRemote reaches the TV directly over your home network. These break that:
| Problem | Symptom | Fix |
|---|---|---|
| Guest Wi‑Fi / client isolation | TV not found; connection times out | Put both on your main network. Guest networks usually stop devices seeing each other. |
| Different networks (e.g. Mac on 5 GHz “mesh”, TV on a separate IoT VLAN) | TV not found | Same network, or allow traffic between them in the router. |
| Mac on a VPN | “No route to host”; TV not found | Turn the VPN off, or enable its allow local network option. |
| Multicast/mDNS blocked by the router | TV not listed automatically, but connecting by IP works | Enter the address by hand (Not listed? Enter its address). |
| TV’s address changed | Worked before, now can’t connect | Check Settings › Network & Internet › your network on the TV. Better: reserve a fixed address for the TV in your router (DHCP reservation). |
| Android 14 Google device restarted | Connection refused after a restart | Wireless debugging switched itself off and the port changed. Turn it on and connect again (Connecting). |
macOS Local Network permission
macOS asks before any app can talk to devices on your home network.
- The first time, ArtFrameRemote shows “ArtFrameRemote would like to find and connect to devices on your local network.” Choose Allow.
- Denied it? System Settings › Privacy & Security › Local Network, turn on ArtFrameRemote, then reopen the app.
- Without it, connections fail with confusing messages such as “The Internet connection appears to be offline” or “No route to host”, even though the internet works.
What debugging lets a computer do
Debugging lets an approved computer install apps, change settings, read logs and see the screen. Treat an approved Mac like an administrator of the TV.
What keeps that in check:
- The TV only accepts computers you approved on its own screen.
- Only devices on your network can reach it.
- Wireless debugging (pairing code) is encrypted. Classic port-5555 debugging is not, which is another reason to keep it to your home network.
Good habits:
- Only press Allow for prompts you started yourself.
- Don’t enable debugging on public or shared networks (hotels, offices).
- Lost or replaced a Mac? Revoke USB debugging authorizations on the TV.
- When you’re done changing things, you can turn debugging off. ArtFrame keeps running.
Troubleshooting index
| Symptom | Likely cause | See |
|---|---|---|
| Developer options missing | Restricted profile; or menu hidden until restart (some Sony/Hisense) | Connecting, brand guide |
| “The TV didn’t accept the connection” | Debugging off; Android 14 needs pairing; another app connected | Connecting |
| No “Allow USB debugging?” prompt | TV asleep; previously cancelled | Connecting |
| Screensaver never appears | Energy saver shorter than delay; delay under 6 min; selection reset; TCL auto-launch | Screensavers and power, TCL |
| Old screensaver came back | System update reset it | Screensavers and power |
| Picture looks dark | Light sensor, OLED dimming, ArtFrame blur settings | Screensavers and power |
| Sony picture/sound changes refused | Pre-shared key missing or wrong; EU firmware changes | Sony BRAVIA |
| “Verify it’s you” Google screen | Google account needs signing in again; not ArtFrame | Choose Sign in on the TV |
Sources
- Android Developers: adb: authorization model, Wireless debugging encryption, mDNS discovery.
- Apple Developer Forums: Local Network privacy: macOS Local Network behaviour and error messages.