ioBroker.govee-smart

Release:

Build:

Support:

Control all Govee WiFi products from ioBroker — lights, sensors and appliances. Bluetooth-only devices are not supported.

The adapter uses every available Govee channel (LAN, Cloud REST, AWS IoT MQTT, OpenAPI MQTT, App API) and picks whichever delivers the fastest answer for each device. Details in the Wiki.

Documentation

Full user documentation lives in the Wiki.

| Topic | English | Deutsch | | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | | Landing page | Home | Startseite | | Channels, credentials, API key, experimental devices | Setup | Einrichtung | | Supported models, status meanings, contributing yours | Devices | Geräte | | Every datapoint, where it lands, what it does | State tree | Datenpunkte | | Thermometers, heaters, kettles, etc. — state tree, updates, troubleshooting | Sensors and Appliances | Sensoren und Appliances | | Lights — segment count, wizard, cut strips, batch commands | Segments | Segmente | | Lights — scene library, speed slider, Cloud vs local snapshots | Scenes and Snapshots | Szenen und Snapshots | | Lights — group fan-out, capability intersection | Groups | Gruppen | | Folder naming, startup, diagnostics, troubleshooting | Behavior | Verhalten |

Features

• Capability-driven — states are generated from what the Govee API reports for each device. No SKU hardcoding, no hand-maintained device list to fall behind.
• LAN-first for lights — UDP multicast discovery, sub-50 ms commands, status updates via AWS IoT MQTT
• Cloud + MQTT push for sensors and appliances — readings via the App API, events via the OpenAPI MQTT broker
• Per-segment color and brightness for LED strips with the right capability, including batch commands and a visual segment-detection wizard (with a live, correctable strip map) for cut strips
• Scenes, DIY scenes, music mode, gradient toggle — activated locally via BLE-over-LAN where possible, Cloud fallback otherwise
• Cloud and local snapshots — Govee-app snapshots and ioBroker-side snapshots side by side
• Groups — bridge Govee groups into ioBroker with capability intersection across members
• Diagnostics export button per device — one-click JSON dump for bug reports
• Works without credentials — LAN-only out of the box, each credential tier unlocks more
• Rate-limited Cloud usage — daily and per-minute budgets aligned to Govee's quota

Sentry / Error reporting

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. Reporting only happens if you have enabled error reporting in the ioBroker diagnostics (System settings → Diagnostics and error reporting). Only an anonymous installation ID is transmitted — no name, e-mail address or IP address.

For details and how to disable it, see the Sentry plugin documentation. Error reporting requires js-controller 3.0 or newer.

Requirements

• Node.js >= 22
• ioBroker js-controller >= 7.2.2
• ioBroker Admin >= 7.8.23
• A Govee account and at least one Govee WiFi device. LAN control needs a light with LAN mode enabled in the Govee Home app — see Govee's LAN-supported device list.

Getting started

The adapter works LAN-only without any credentials. Adding an API key unlocks scenes, segments and appliance control. Adding your Govee email and password adds sensor readings (temperature/humidity via the App API), real-time status push and full group control. See the Setup page for credential levels, how to get an API key, and network requirements.

Device support

Each device shows its test status under diag.tier. The Devices page lists every supported model and what the status means.

Troubleshooting

Common issues (no devices discovered, empty scenes dropdown, segment colors not changing, limited group commands, delayed status updates) are covered on the Wiki Behavior / Verhalten page.

For anything else, set diag.export to true on the affected device, copy the JSON from diag.result, and open a GitHub Issue.

Acknowledgments

This adapter's MQTT authentication and BLE-over-LAN (ptReal) protocol implementation was informed by research from govee2mqtt by Wez Furlong. Their reverse-engineering of the Govee AWS IoT MQTT protocol and undocumented API endpoints was invaluable.

Changelog

2.21.0 (2026-07-12)

• The segment-detection wizard for cut LED strips now has a visual admin interface: a live map of the strip that fills in as you measure each segment and can be corrected before you apply it.

2.20.0 (2026-07-11)

• Channel names and the device-info labels such as Name, Model, Online and IP address now follow the ioBroker system language instead of always showing English.
• Clearer Cloud API feedback: the admin "test login" button reports the real login result, and a malformed API key now gives a plain "invalid key" message instead of a generic failure.
• Sensor-only setups are now told, both in the admin and at startup, that a Govee account login is required to receive sensor data.
• Actions that used to fail quietly now report it — the manual device-sync button surfaces errors, and commands queued behind a rate limit settle with their real success or failure.
• A network error on a manually pinned LAN interface is now raised as an actionable problem with a fix hint, instead of passing unnoticed.

2.19.0 (2026-07-04)

• Device log lines now consistently name devices as "name (model)" — cache maintenance, command errors and wizard messages included, no more bare model/address labels
• The credentials entry disappears from the object tree — login tokens stay saved in encrypted form, just no longer visible as an object

2.18.2 (2026-07-03)

• Internal refactoring. No user-facing changes.

2.18.1 (2026-07-03)

• Added several new Govee devices to the catalog — 4 more lamps and 3 sensors (including a CO2 monitor). They start as experimental; enable them in the adapter settings to try them.

Older changelogs can be found there

Support

• Wiki — user documentation (EN / DE)
• GitHub Issues — bug reports, feature requests
• ioBroker Forum — general questions

Support Development

This adapter is free and open source. If you find it useful, consider buying me a coffee:

License

MIT License

Copyright (c) 2026 krobi [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Developed with assistance from Claude.ai