Skip to content

Wi-Fi Devices

Some RGB devices connect to SignalRGB over your local Wi-Fi network rather than USB. These devices are discovered automatically when they are on the same network as your PC.

Wi-Fi devices communicate with SignalRGB using each manufacturer’s local LAN API. SignalRGB sends lighting commands over your network directly to the device — no cloud connection required once initial setup is complete.

This means:

  • Your PC and the device must be on the same local network (same router, not a guest network or separate VLAN)
  • Network quality affects lighting responsiveness — a strong Wi-Fi signal reduces latency
  • Some routers block device-to-device communication by default (see AP Isolation below)
  • Device powered on and connected to your Wi-Fi network
  • Your PC on the same subnet as the device
  • SignalRGB allowed through Windows Firewall
  • AP Isolation (Client Isolation) disabled on your router — this setting prevents devices on the same network from talking to each other and will block discovery
  • LAN control enabled in the device’s own app (where required — see brand-specific pages)
  • Govee — Requires LAN Control enabled in the Govee Home app. Setup guide
  • Nanoleaf — Requires one-time button-press authorization. Setup guide
  • Philips Hue — Connects via Hue Bridge on local network

For a complete and current list of supported Wi-Fi devices, see the SignalRGB Devices page.

If SignalRGB is not finding your Wi-Fi device:

  1. Confirm the device is online and connected (check the device’s own app).
  2. Confirm your PC and the device are on the same network — not a guest network or separate VLAN.
  3. Disable AP Isolation (also called Client Isolation or WLAN Isolation) in your router settings.
  4. Add a Windows Firewall exception for SignalRGB.
  5. Restart SignalRGB after making network changes.