Control4 Govee: Enable Local Network Control and Troubleshooting Local Lights
Not all Govee lights Support LAN control (an example is that many of their GU10's only support cloud). Some lights may also offer the LAN control setting, however, the protocol may be broken. To confirm full LAN control is supported, use: https://app-h5.govee.com/user-manual/wlan-guide . If the light is not listed, it may not be fully incompatible
Enabling LAN Control
- Ensure all Lights have the latest firmware
- In the Govee App, click on Settings on each device and enable LAN
Control. If the LAN Control option is not shown, LAN Control might not
be supported. To confirm support, use: https://app-h5.govee.com/user-manual/wlan-guide
- Setup LAN Lights as per Govee documentation using Govee Agent V3. If you are still using Govee Agent V1, it is recommended to remove your current lights and upgrade. AutoSetup LAN Devices should automatically detect and setup the drivers
Common LAN Problems
Unable to detect / Control LAN Lights in Agent
If lights are not detected, there could be a number of reasons:
- Particularly for X4 or later, you must be running 20240404 or later.
- Ensure you are only running agent v1, or v3. Running both agents cause port conflicts. Ensure only V3 is being used
- If you recently upgraded from Agent V1 to V3, reboot the controller
- Run Display Diagnostics from Agent, to identify any issues
- Govee Lights should be on the same network segment as Control4. If not, additional configuration may be required
- We have found that if IGMP snooping is enabled, this may prevent auto detection
- Some mesh routers may not forward broadcast traffic correctly
- Ensure that light is in the supported LAN lights list and LAN Control is enabled
- Ensure you are using the latest version of OS3 or later.
Control Works, but feedback is incorrect / missing
- Check for IP Conflicts
- Check WiFi Signal
- Some mesh systems such as Orbi have been found in the past to have problems routing some traffic
- If the device is not on the supported LAN list, the feedback may be buggy and returning bad data. Use the "Ignore Device feedback" property to use the device with one-way communications as a workaround
- Ensure that the Light Type is set correct in properties
Related Articles
Control4 Govee: Upgrade Govee V1 / V2 to Govee V3
Govee V3 Advantages Some devices require Govee V3 to be controlled via Control4. Govee V3 offers many advantages over V1/V2 including: Govee V1/V2 utilises the old Govee Cloud API. This has more quota limitations than the "Awesome New API" (sic) ...CONTROL4 UNIFI: Setting up Local Account / Login for Authentication
It is strongly recommended to set up a local login for UniFi Control. Whilst the UniFi API Key cannot be shared between Access and Protect/Network, the UniFi Login can. We use a combination of both login and API key to provide the best combination of ...Control4 Govee: Obtaining an API Key
An API is required for Govee's Cloud devices to be controlled via Control4. Ensure that you are using Govee V3 Agent. V1 uses an older protocol which doesn't support many devices If the device supports LAN, it is generally recommended to use LAN ...Control4 Govee: Some Cloud Lighting/Outlet Devices are not being detected / Discovered
Some Devices (in particular, many light bulbs including the H600D) require an upgrade to our Govee V3 Driver to operate. V1/V2 will not detect many modern devices. Govee V3 utilises the "Awesome New API" (sic) from Govee and is a free upgrade for ...Control4 ELK M1: Zone status does not correctly respond properly or Realtime status is not correct
Ensure you are using the latest version of our ELK M1 V2 driver. You can identify this by right clicking on the device in System Design on Composer, and pressing Get Info. The filename must say chowmain_elk_m1_v2.c4z. If the original filename of the ...