Note
Accessory names now follow the Govee app. Until now a device kept whatever name it was first discovered under, so renaming it in the Govee app changed nothing. That is fixed — but it means a device whose Govee name has drifted from its Homebridge one will visibly change name on the first restart, with a line in the log for each.
Nothing is re-added: this changes the name only, not the accessory itself, so rooms, scenes and automations are untouched. The name shown in the Home app is set by HomeKit when an accessory is first added and is not affected either.
Changed
- feat: control the H1250 zones with the device's own frame, as govee ignores its toggles (#1343) (@Principe1218)
- fix: explain in the log when zone tiles are missing because aws credentials are not set
- fix: restore debug logging when the plugin runs in a child bridge
- fix: turn adaptive lighting off when a colour is chosen outside HomeKit
- fix: send a colour change when only the saturation moves, on every night light
- fix: listen for saturation on the main light too, not only hue
- fix: accept 20-byte H5106 status frames (#1345) (@danieloleary)
- fix: stop rescaling the H1250's brightness, since it already counts to 100 over AWS (#1347) (@Principe1218)
- feat: give the H1250's zones independent color and brightness (#1346) (@Principe1218)
- fix: stop a lan scan that cannot reach the network from crashing the bridge
- fix: apply the openapi disable and refresh settings instead of asking for them to be removed
- fix: say once when a bluetooth reading arrives for an unknown device, not on every broadcast
- fix: reject a refresh time so large it would make the plugin poll every millisecond
- fix(H5054): don't let a slow leak warning block other sensors (#1348) (@danieloleary)
- fix: mark sensor batteries low at the configured threshold (#1349) (@danieloleary)
- feat: show whether the kettle is heating, keeping warm or idle (#1337)
- fix: give the H5106 a battery service, so its low battery setting does something
- fix: stop a light's broadcast being mistaken for an h5101 sensor reading
- fix: follow a device renamed in the govee app, instead of keeping its first name forever (#1344)
- fix: say why the bluetooth adapter would not start, rather than only that it timed out (#1344)