New: per-device transport connectivity sensors (opt-in)
Three binary_sensor entities per device show real-time connectivity for each transport — Cloud API, MQTT, Bluetooth — with DIAGNOSTIC category, timestamps, and failure reasons. Enable via Options → Expose per-device transport connectivity sensors (off by default). Use them in dashboards or automations to know which channel is actually delivering commands.
Fixes
- #53 H80A1 segments not all updating — segment commands are now serialized per-device (120 ms pacing), staying under Govee's silent burst limit. Scenes/groups that touch every segment of a 14-segment RGBIC strip now complete in full. Optimistic state still applies immediately.
- #60 H707C BLE commands fail — BLE writes are fire-and-forget, so an out-of-range device would let an API poll 60 s later flip the UI back "off". Optimistic power/brightness are now preserved for up to 15 s (cleared instantly by any MQTT confirmation), eliminating the flipflop.
- #58 H6053 / H6076 / H6126 not discovered over Bluetooth — added Govee manufacturer ID 34819 to
manifest.json'sbluetoothblock and to the runtime discovery callback.
Internal
- New
TransportHealthmodel + coordinator tracking for last success/failure per (device, transport). DataUpdateCoordinatornow usesalways_update=False.- 10 new unit tests; 647 total passing.
Research: docs/_research/2026-04-13_open-bugs-triage.md, docs/_research/2026-04-13_ha-validation-and-connectivity-entities.md.