@homebridge-plugins/homebridge-govee 11.30.0-beta.3 → 11.30.1-beta.0

package/CHANGELOG.md

@@ -2,14 +2,20 @@
 
 All notable changes to `@homebridge-plugins/homebridge-govee` will be documented in this file.
 
-## v11.30.0 (Pending Release)
+## v11.30.1 (Pending Release)
+
+### Changed
+
+- fix: use 0-100 aws brightness for h1401 and h6008, so they stop jumping to full or 1% (#1321) (@rroach3753)
+
+## v11.30.0 (2026-07-21)
 
 ### 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)
 - fix: skip a periodic sync when the previous one is still running, so slow responses stop stacking up (#1256) (@schwaggy)
-- fix: work out whether the openapi sensor temperature is celsius or fahrenheit, so thermometers no longer read too high (#1269) (@tdporter)
+- fix: work out whether the openapi sensor temperature is celsius or fahrenheit (#1269) (@tdporter)
 
 ## v11.29.3 (2026-07-21)
 

package/lib/utils/command-builder.js

@@ -112,11 +112,12 @@ function buildBrightnessCommand(params, context) {
     awsParams: {
       cmd: 'brightness',
       // 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
+      // up. A handful expect 0-100 already - those are listed in
+      // device-capabilities.js, or 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
+        val: context.awsBrightnessNoScale || caps.awsBrightnessNoScale
           ? params.value
           : Math.round(params.value * 2.54),
       },

package/lib/utils/device-capabilities.js

@@ -32,6 +32,12 @@ const modelOverrides = {
 
   // H6121 requires cmdVersion 1 for status requests
   H6121: { awsStatusCmdVersion: 1 },
+
+  // These send and expect AWS brightness as 0-100 rather than the usual 0-254,
+  // so scaling drives them to full on the way out and to 1% on the way back in
+  // (#1321). Same effect as ticking `awsBrightnessNoScale` per device.
+  H1401: { awsBrightnessNoScale: true },
+  H6008: { awsBrightnessNoScale: true },
 }
 
 const defaults = {
@@ -42,6 +48,7 @@ const defaults = {
   awsPowerOff: 0,
   bleWriteUuid: UUID.WRITE_DEFAULT,
   awsStatusCmdVersion: 2,
+  awsBrightnessNoScale: false,
 }
 
 export function getDeviceCapabilities(model) {

package/lib/utils/response-parser.js

@@ -1,4 +1,5 @@
 import platformConsts from './constants.js'
+import { getDeviceCapabilities } from './device-capabilities.js'
 
 const hasProperty = (obj, prop) => Object.hasOwn(obj, prop)
 
@@ -97,7 +98,9 @@ export function parseDeviceUpdate(params, context) {
     // 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
+      const noScale = context.awsBrightnessNoScale
+        || getDeviceCapabilities(context.gvModel).awsBrightnessNoScale
+      data.brightness = noScale
         ? params.state.brightness
         : Math.round(params.state.brightness / 2.54)
     } else {

package/package.json

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