← Back to home

Local network control

Last updated: 2026-10-25

Many Govee lights can be reached directly on your home network, without going through Govee's cloud. The plugin finds those lights automatically. There is nothing to set up in the plugin: lights that answer on the local network are marked Connection: LAN in an action's What this light supports panel; all others use the Govee cloud as before.

For those lights, power, brightness, colour and colour temperature go over the local network: keys and dials react in milliseconds and keep working when the internet is down, even after a restart. Setting up a key still needs the internet, because the light list comes from Govee's cloud. Each command is checked; if a light didn't react, the plugin sends it again through the cloud. Scenes, segments, music modes and snapshots always use the cloud, because Govee's local API doesn't offer them. Automation (turning lights on at wake and off before sleep) also goes over the local network, which makes "off before sleep" much more reliable.

Turn on LAN Control for a light

  1. Open the Govee Home app and select the light.
  2. Open the light's settings (the gear icon).
  3. Turn on LAN Control. If you don't see it, wait a few minutes and reopen the settings; if it never appears, the model doesn't support local control.
  4. Your computer and the light must be on the same network.

Within about a minute, open the light in any action and expand What this light supports. It should say Connection: LAN.

macOS: allow local network access

The first time the plugin looks for lights, macOS asks whether Stream Deck may find devices on your local network. Choose Allow. If you chose Don't Allow, the panel shows Local network access blocked. To allow it again:

  1. Open System Settings → Privacy & Security → Local Network.
  2. Turn on Stream Deck.
  3. Quit and reopen Stream Deck.

Windows: allow Stream Deck through the firewall

Windows may ask whether to allow Stream Deck (or Node.js) on private networks. Choose Allow. If you dismissed it:

  1. Open Windows Security → Firewall & network protection → Allow an app through firewall.
  2. Select Change settings, then allow Stream Deck and Node.js on Private networks.
  3. Restart Stream Deck.

Other apps using Govee's LAN port

Govee lights reply on UDP port 4002. If another program on the same computer already uses it (for example Home Assistant, Homebridge or govee2mqtt), the panel shows LAN port in use and every light uses the cloud. Run that program on another machine, or quit it and restart Stream Deck.

What is sent on your network

Only Govee's documented LAN messages: a discovery request to the multicast address 239.255.255.250 (port 4001), status requests and commands to each light (port 4003), and the lights' replies (port 4002). Nothing leaves your network for this, and no API key is involved. See the privacy policy.