@homebridge-plugins/homebridge-govee 11.30.0 → 11.30.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,12 @@
2
2
 
3
3
  All notable changes to `@homebridge-plugins/homebridge-govee` will be documented in this file.
4
4
 
5
+ ## v11.30.1 (2026-07-23)
6
+
7
+ ### Changed
8
+
9
+ - fix: use 0-100 aws brightness for h1401 and h6008, so they stop jumping to full or 1% (#1321) (@rroach3753)
10
+
5
11
  ## v11.30.0 (2026-07-21)
6
12
 
7
13
  ### Changed
@@ -112,11 +112,12 @@ function buildBrightnessCommand(params, context) {
112
112
  awsParams: {
113
113
  cmd: 'brightness',
114
114
  // Most devices take 0-254 over AWS, so HomeKit's 0-100 has to be scaled
115
- // up. A handful expect 0-100 already and are opted out per device with
115
+ // up. A handful expect 0-100 already - those are listed in
116
+ // device-capabilities.js, or opted out per device with
116
117
  // `awsBrightnessNoScale`. Dropping this scaling made every AWS device
117
118
  // land at roughly a third of the requested brightness (#1262).
118
119
  data: {
119
- val: context.awsBrightnessNoScale
120
+ val: context.awsBrightnessNoScale || caps.awsBrightnessNoScale
120
121
  ? params.value
121
122
  : Math.round(params.value * 2.54),
122
123
  },
@@ -32,6 +32,12 @@ const modelOverrides = {
32
32
 
33
33
  // H6121 requires cmdVersion 1 for status requests
34
34
  H6121: { awsStatusCmdVersion: 1 },
35
+
36
+ // These send and expect AWS brightness as 0-100 rather than the usual 0-254,
37
+ // so scaling drives them to full on the way out and to 1% on the way back in
38
+ // (#1321). Same effect as ticking `awsBrightnessNoScale` per device.
39
+ H1401: { awsBrightnessNoScale: true },
40
+ H6008: { awsBrightnessNoScale: true },
35
41
  }
36
42
 
37
43
  const defaults = {
@@ -42,6 +48,7 @@ const defaults = {
42
48
  awsPowerOff: 0,
43
49
  bleWriteUuid: UUID.WRITE_DEFAULT,
44
50
  awsStatusCmdVersion: 2,
51
+ awsBrightnessNoScale: false,
45
52
  }
46
53
 
47
54
  export function getDeviceCapabilities(model) {
@@ -1,4 +1,5 @@
1
1
  import platformConsts from './constants.js'
2
+ import { getDeviceCapabilities } from './device-capabilities.js'
2
3
 
3
4
  const hasProperty = (obj, prop) => Object.hasOwn(obj, prop)
4
5
 
@@ -97,7 +98,9 @@ export function parseDeviceUpdate(params, context) {
97
98
  // HomeKit's 0-100. Without this every AWS reading of 100 or more clamped
98
99
  // to full brightness (#1262). The other sources already report 0-100.
99
100
  if (params.source === 'AWS') {
100
- data.brightness = context.awsBrightnessNoScale
101
+ const noScale = context.awsBrightnessNoScale
102
+ || getDeviceCapabilities(context.gvModel).awsBrightnessNoScale
103
+ data.brightness = noScale
101
104
  ? params.state.brightness
102
105
  : Math.round(params.state.brightness / 2.54)
103
106
  } else {
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@homebridge-plugins/homebridge-govee",
3
3
  "alias": "Govee",
4
4
  "type": "module",
5
- "version": "11.30.0",
5
+ "version": "11.30.1",
6
6
  "description": "Homebridge plugin to integrate Govee devices into HomeKit.",
7
7
  "author": {
8
8
  "name": "bwp91",