MQTT-Native Control (experimental, opt-in)
Adds a third control transport tier — BLE → MQTT-native → REST fallback — routing power/brightness/color commands through Govee's AWS IoT MQTT channel via native turn/brightness/colorwc commands (~50ms vs REST ~500ms–4s), bypassing REST rate limits.
Highlights
- New Enable MQTT control option (default off). Requires email/password login (MQTT credentials). Falls back to REST automatically when MQTT is unavailable.
- Native command builders with H5080/H5083 power quirk (16/17) handling.
- Group devices and non-capable commands (color temp, scenes, segments) stay on REST.
- 20 new tests; 813 passing. mypy / flake8 / black clean.
Notes
- Experimental: uses an undocumented channel. Leave off if commands behave unexpectedly.
- Deferred:
colorwc→colorlegacy fallback for older devices; group-device MQTT.
Research: docs/_research/2026-06-04_mqtt-push-control-latency.md
Full Changelog: v2026.6.3...v2026.6.4