base on Govee2MQTT: Connect Govee lights and devices to Home Assistant # Govee to MQTT bridge for Home Assistant This repo provides a `govee` executable whose primary purpose is to act as a bridge between [Govee](https://govee.com) devices and Home Assistant, via the [Home Assistant MQTT Integration](https://www.home-assistant.io/integrations/mqtt/). ## Features * Robust LAN-first design. Not all of Govee's devices support LAN control, but for those that do, you'll have the lowest latency and ability to control them even when your primary internet connection is offline. * Support for per-device modes and scenes. * Support for the undocumented AWS IoT interface to your devices, provides low latency status updates. * Support for the new [Platform API](https://developer.govee.com/reference/get-you-devices) in case the AWS IoT or LAN control is unavailable. |Feature|Requires|Notes| |-------|--------|-------------| |DIY Scenes|API Key|Find in the list of Effects for the light in Home Assistant| |Music Modes|API Key|Find in the list of Effects for the light in Home Assistant| |Tap-to-Run / One Click Scene|IoT|Find in the overall list of Scenes in Home Assistant, as well as under the `Govee to MQTT` device| |Live Device Status Updates|LAN and/or IoT|Devices typically report most changes within a couple of seconds.| |Segment Color|API Key|Find the `Segment 00X` light entities associated with your main light device in Home Assistant| * `API Key` means that you have [applied for a key from Govee](https://developer.govee.com/reference/apply-you-govee-api-key) and have configured it for use in goovee2mqtt * `IoT` means that you have configured your Govee account email and password for use in govee2mqtt, which will then attempt to use the *undocumented and likely unsupported* AWS MQTT-based IoT service * `LAN` means that you have enabled the [Govee LAN API](https://app-h5.govee.com/user-manual/wlan-guide) on supported devices and that the LAN API protocol is functional on your network ## Usage * [Installing the HASS Add-On](docs/ADDON.md) - for HAOS and Supervised HASS users * [Running it in Docker](docs/DOCKER.md) * [Configuration](docs/CONFIG.md) ## Have a question? * [Is my device supported?](docs/SKUS.md) * [Check out the FAQ](docs/FAQ.md) ## Want to show your support or gratitude? It takes significant effort to build, maintain and support users of software like this. If you can spare something to say thanks, it is appreciated! * [Sponsor me on Github](https://github.com/sponsors/wez) * [Sponsor me on Patreon](https://patreon.com/WezFurlong) * [Sponsor me on Ko-Fi](https://ko-fi.com/wezfurlong) * [Sponsor me via liberapay](https://liberapay.com/wez) ## Credits This work is based on my earlier work with [Govee LAN Control](https://github.com/wez/govee-lan-hass/). The AWS IoT support was made possible by the work of @bwp91 in [homebridge-govee](https://github.com/bwp91/homebridge-govee/). ", Assign "at most 3 tags" to the expected json: {"id":"6766","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"