LAN Control

LAN control lets the plugin discover and control supported Govee devices directly over your local network - no cloud connection and no Govee credentials needed for these devices.

Requirements

• Your device model must support Govee's LAN API - see Govee's official list of LAN-supported models
• You must turn on the LAN Control toggle for the device in the Govee Home app (device settings page)
• Your Homebridge instance must be on the same network (or VLAN) as the device, with multicast traffic allowed between them

How it works

• Devices with LAN Control enabled join the multicast group 239.255.255.250 and listen on port 4001
• The plugin sends a scan request to this group and each device replies with its details (to port 4002)
• The plugin then sends commands directly to the device on port 4003
• The plugin re-scans the network periodically to find new devices and refresh existing ones

What you can control

• Power on/off, brightness and colour
• Scene codes can also be sent via LAN - see Scene, Music, DIY Modes

Configuration

All of these are optional - LAN control works out of the box for supported devices:

Setting	Explanation
lanDisable	Turn off LAN discovery and control completely
lanRefreshTime	How often (seconds) LAN devices refresh their status
lanScanInterval	How often (seconds) the plugin scans the network for devices
customIPAddress	Per-device setting: a fixed IP address, useful if auto-discovery cannot find the device

Using the plugin with LAN devices only

If all your devices support LAN control, you can leave the Govee username and password out of the configuration completely. The plugin will discover and control your devices locally. Note that:

• The device name shown in HomeKit will come from the label you give the device in the config (LAN-only devices cannot report their Govee app name)
• Features that need the cloud (for example scene code discovery via the log) will not be available

Troubleshooting

• Device not found: check the LAN Control toggle is on in the Govee app, and that your router allows multicast (look for 'IGMP snooping' settings). If Homebridge runs in Docker, host networking mode is usually needed for multicast discovery.
• Device on a different VLAN: multicast does not usually cross VLANs; either move the device/Homebridge to the same VLAN or set the device's customIPAddress in the plugin settings so the plugin can reach it directly.
• Control works but updates are slow: external changes (e.g. via the Govee app) are picked up on the next LAN refresh; you can lower lanRefreshTime if needed.