@homebridge-plugins/homebridge-govee 11.29.3 → 11.30.0-beta.0

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to `@homebridge-plugins/homebridge-govee` will be documented in this file.
 
+## v11.30.0 (Pending Release)
+
+### Changed
+
+- chore(ble): let noble apply its own adapter timeout instead of racing a second one
+- fix: restore aws brightness scaling, so lights reach the brightness asked for (#1262) (@gradyg21)
+
 ## v11.29.3 (2026-07-21)
 
 ### Changed

package/lib/connection/ble.js

@@ -174,20 +174,16 @@ export default class BLEConnection {
       return true
     }
 
-    let timeoutId
     try {
-      await Promise.race([
-        btClient.waitForPoweredOnAsync(),
-        new Promise((_, reject) => {
-          timeoutId = setTimeout(() => reject(new Error('timeout waiting for bluetooth adapter')), timeout)
-        }),
-      ])
+      // noble applies the timeout itself and removes its own state listener when
+      // it expires. Racing it against a second, shorter timer here just meant
+      // noble kept waiting - and holding its listener - for another five seconds
+      // after we had already given up.
+      await btClient.waitForPoweredOnAsync(timeout)
       return true
     } catch (err) {
       this.log.warn('[BLE] failed to power on adapter: %s.', err.message)
       return false
-    } finally {
-      clearTimeout(timeoutId)
     }
   }
 

package/lib/platform.js

@@ -217,6 +217,7 @@ export default class {
                     }
                     break
                   }
+                  case 'awsBrightnessNoScale':
                   case 'hideLight':
                   case 'hideModeGreenTea':
                   case 'hideModeOolongTea':
@@ -1363,6 +1364,7 @@ export default class {
 
               if (this.awsClient) {
                 accessory.context.useAwsControl = true
+                accessory.context.awsBrightnessNoScale = deviceConf.awsBrightnessNoScale
                 accessory.context.awsColourMode = deviceConf.awsColourMode || platformConsts.defaultValues.awsColourMode
                 awsDevices.push(device.device)
 

package/lib/utils/command-builder.js

@@ -111,7 +111,15 @@ function buildBrightnessCommand(params, context) {
   return {
     awsParams: {
       cmd: 'brightness',
-      data: { val: params.value },
+      // Most devices take 0-254 over AWS, so HomeKit's 0-100 has to be scaled
+      // up. A handful expect 0-100 already and are opted out per device with
+      // `awsBrightnessNoScale`. Dropping this scaling made every AWS device
+      // land at roughly a third of the requested brightness (#1262).
+      data: {
+        val: context.awsBrightnessNoScale
+          ? params.value
+          : Math.round(params.value * 2.54),
+      },
     },
     bleParams: {
       cmd: CMD.BRIGHTNESS,

package/lib/utils/response-parser.js

@@ -49,8 +49,18 @@ export function parseDeviceUpdate(params, context) {
 
   // BRIGHTNESS
   if (params.state && hasProperty(params.state, 'brightness')) {
-    data.brightness = params.state.brightness
+    // AWS reports 0-254 on most devices, so it has to come back down to
+    // HomeKit's 0-100. Without this every AWS reading of 100 or more clamped
+    // to full brightness (#1262). The other sources already report 0-100.
+    if (params.source === 'AWS') {
+      data.brightness = context.awsBrightnessNoScale
+        ? params.state.brightness
+        : Math.round(params.state.brightness / 2.54)
+    } else {
+      data.brightness = params.state.brightness
+    }
   }
+  // Govee occasionally sends a value outside [0, 100] anyway
   if (hasProperty(data, 'brightness')) {
     data.brightness = Math.max(Math.min(data.brightness, 100), 0)
   }

package/package.json

@@ -2,7 +2,7 @@
   "name": "@homebridge-plugins/homebridge-govee",
   "alias": "Govee",
   "type": "module",
-  "version": "11.29.3",
+  "version": "11.30.0-beta.0",
   "description": "Homebridge plugin to integrate Govee devices into HomeKit.",
   "author": {
     "name": "bwp91",