Govee lights won't work with SimHub
Last updated · SimHub 9.11.22
SimHub has supported Govee lights since version 8.3.0, so the usual answer on forums — that Govee does not work and you need to buy something else — is wrong. What is true is that it works only under four conditions, all of which the wiki states outright: the model must be Dreamview-compatible, LAN control must be enabled in the Govee mobile app, the light must be on the same home WiFi as the PC, and nothing else may be controlling it at the same time — not the Govee app, not Alexa, not Google Home. A device can also expose at most 10 independent segments. If your lights are not appearing or are not reacting, work through those four in that order; the exclusive-control requirement is the one almost nobody guesses.
This page is deliberately narrow. If you are still deciding what to buy, the comparison of every ambient light system SimHub speaks to is the better starting point, because Govee is not always the right answer and the limits differ a lot between them.
The four requirements, in the order they fail
Every one of these is stated as a requirement in SimHub's own documentation. They are ordered by how often each is the actual problem.
| # | Requirement | How it fails | Fix |
|---|---|---|---|
| 1 | A Dreamview-compatible model | The light never appears in SimHub's device list at all, and no amount of restarting changes that. | Check your model against Govee's own Dreamview compatibility list before buying. Model numbers within one product line differ on this. |
| 2 | LAN control enabled in the Govee mobile app | The light appears on your network but SimHub cannot address it. This is off by default on many models. | Govee app → the device → settings → enable LAN Control. It is a per-device setting, so enabling it on one strip does not enable it on the next. |
| 3 | Same home WiFi as the PC | Nothing is discovered. Common on a 2.4 GHz-only light with the PC on a 5 GHz band that the router has isolated, or on a guest network. | Put both on the same network and the same subnet. Guest networks and client isolation break this by design. |
| 4 | Nothing else controlling it | The light is found, reacts for a moment, then reverts or stutters — the classic symptom. | Close the Govee app on your phone, and unlink the device from Alexa and Google Home while you are racing. Control is exclusive. |
The one that looks like a bug. If the light flickers between SimHub's colour and something else, or drops back to its previous scene a second after SimHub sets it, that is requirement 4 — two controllers fighting. It is not a SimHub fault and no setting inside SimHub fixes it. The wiki is explicit that the device cannot be controlled by the app, Alexa or Google Home at the same time.
The 10-segment ceiling
SimHub can address at most 10 independent segments per device. On a strip sold as having far more addressable zones, that is not a fault — it is the limit of what the integration exposes, and it is worth knowing before you plan a layout around per-LED effects.
In practice 10 segments is plenty for ambient light — the screen-average colour spread across a strip behind the monitors — and thin for anything that wants fine spatial detail, such as a spotter light where you want a precise position rather than a side.
What ambient mode actually sends. SimHub sends the average colour of a screen area to each light area, and you can mix or replace that with direct effects such as flags and spotter. So a Govee strip can be doing screen-average most of the time and go hard blue or yellow on a flag.
If all four are satisfied and it still does nothing
- Confirm the version. Govee support arrived in 8.3.0. An older install will never list them, and this is worth checking first because it costs nothing.
- Restart SimHub after enabling LAN control. Discovery runs at startup, so a light that was not addressable when SimHub launched will not appear later on its own.
- Power-cycle the light itself. LAN control does not always take effect on the device until it reconnects.
- Check the PC's network profile is Private, not Public. A Public profile blocks local discovery traffic and breaks this the same way it breaks the phone dashboard.
If it works and then stops mid-session, treat it as a network problem rather than a SimHub one: a light that changes IP on a DHCP lease renewal disappears until the next discovery. A DHCP reservation in the router fixes that permanently.
Common questions
Does SimHub support Govee at all?
Yes, since version 8.3.0, through the ambient lights plugin. The widely repeated answer that Govee is unsupported is out of date. What is true is that it only works on Dreamview-compatible models, with LAN control enabled in the Govee app, on the same home WiFi, and with nothing else controlling the light.
Why do my Govee lights flicker or revert while racing?
Something else is controlling them at the same time. Govee control is exclusive: close the Govee app on your phone and unlink the device from Alexa and Google Home. This is the single most common cause of the flickering symptom and no SimHub setting will fix it.
Which Govee models work with SimHub?
Dreamview-compatible ones. That is a Govee product designation rather than a SimHub one, so check the model against Govee's own compatibility list — models inside the same product line differ, so the range name alone does not tell you.
How many Govee segments can SimHub control?
Ten independent segments per device. Enough for ambient screen-average lighting across a strip; thin if you wanted per-LED spatial detail, such as a precise spotter position rather than a left/right side.
Do I need LAN control on, or will Bluetooth do?
LAN control, enabled in the Govee mobile app, and it is a per-device setting. SimHub addresses the light over your local network. Bluetooth-only control from the phone is not the path this integration uses.
My Govee lights work but lag behind the game. Why?
This path goes over WiFi to a device designed for room lighting rather than for frame-accurate response, so some latency is inherent. Keeping the light and the PC on the same band and subnet, and off a repeater, is what you can control. If you need genuinely tight response, an Adalight-style addressable strip driven by an Arduino over USB is the lower-latency route.
Sources
Related guides
SimHub is developed independently by Wotever and is not affiliated with OESimRacing. This page was checked against SimHub 9.11.22 on 4 August 2026; where the interface has moved on since, the version stamp tells you how far. More on what SimHub is and what it costs.