Govee2MQTT
Govee2MQTT is a bridge that connects Govee lights and devices to Home Assistant via MQTT, enabling LAN-first control and scene support for home automation…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
53/100 Fair
- Maintained
- 51last commit 223 days ago
- Popular
- 631,491 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 60no serious findings, 7 minor, CI
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 22 days ago
- GitHub stars
- 1,491
- Open issues
- 358
- Last commit
- 2026-04-12
- License
- MIT
- Activity
- stale
Checked 7 days ago - source: GitHub (wez/govee2mqtt)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Fill in .env before starting Create the .env file with your Govee account details and your MQTT broker (the message service that carries device data) host and port before starting Docker. Without these, the app cannot sign in or send your Govee devices to Home Assistant or any other MQTT app. source
- Use host networking for LAN discovery Set network_mode: host in docker-compose.yml so the app can see your local network directly. This helps it find Govee devices on your LAN; without it, some devices may not appear even if they are on the same Wi‑Fi or network. source
- Keep settings in a /data volume Add a Docker volume for /data, like govee2mqtt_data:/data, so the app’s saved settings and state remain after restarts or upgrades. If you don’t, rebuilding the container can wipe out the configuration you entered. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What .env settings are required before starting Govee2MQTT in Docker?
Create the .env file with your Govee account details and the MQTT broker host and port. Without them, the app cannot sign in or send your Govee devices to Home Assistant.
Why should Govee2MQTT use Docker host networking?
Set network_mode: host so the app can see your local network directly. This helps it find Govee devices on your LAN; without it, some devices may not appear even if they are on the same network.
How can Govee2MQTT settings be preserved after container rebuilds or upgrades?
Mount a Docker volume for /data, such as govee2mqtt_data:/data, so saved settings and state remain. If you do not, rebuilding the container can wipe the configuration you entered.
Which Govee2MQTT features require a Govee API key?
DIY scenes, music modes, and segment color require an API key. Tap-to-run requires IoT account credentials, while live status updates can use LAN and/or IoT.
Can the Home Assistant add-on be updated without restarting Home Assistant?
Yes, you can update govee2mqtt without restarting the whole Home Assistant instance.
Answers sourced from context7.com, github.com, www.reddit.com
Community
- Govee LAN MQTT : r/homeassistant - Reddit (reddit)
- Does the govee integration actually work for anyone? - Reddit (reddit)
- What integration do you use for Govee? : r/homeassistant - Reddit (reddit)
- What integration are you guys using for Govee lights? - Reddit (reddit)
- Govee and MQTT - Frontend - Home Assistant Community (other)
- Govee - Is there a reason I should use ovee2MQTT over the Govee's ... (other)
Collected 49 days ago - public community threads