@homebridge-plugins/homebridge-govee 11.34.2-beta.1 → 11.34.2-beta.3

package/CHANGELOG.md

@@ -9,6 +9,14 @@ All notable changes to `@homebridge-plugins/homebridge-govee` will be documented
 - 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 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
 
 ## v11.34.1 (2026-08-06)
 

package/config.schema.json

@@ -49,7 +49,8 @@
         "type": "integer",
         "description": "An interval (in seconds) in which your HTTP devices will refresh with the plugin. Must be 30 or more.",
         "placeholder": 30,
-        "minimum": 30
+        "minimum": 30,
+        "maximum": 2073600
       },
       "awsDisable": {
         "title": "Disable AWS",
@@ -69,7 +70,8 @@
         "minimum": 60,
         "condition": {
           "functionBody": "return (!model.bleDisable);"
-        }
+        },
+        "maximum": 2073600
       },
       "lanDisable": {
         "title": "Disable LAN",
@@ -84,7 +86,8 @@
         "minimum": 10,
         "condition": {
           "functionBody": "return (!model.lanDisable);"
-        }
+        },
+        "maximum": 2073600
       },
       "lanScanInterval": {
         "title": "LAN Scan Interval",
@@ -94,7 +97,8 @@
         "minimum": 30,
         "condition": {
           "functionBody": "return (!model.lanDisable);"
-        }
+        },
+        "maximum": 2073600
       },
       "lanScanSubnets": {
         "title": "LAN Scan Subnets",
@@ -118,7 +122,8 @@
         "minimum": 30,
         "condition": {
           "functionBody": "return (!model.openApiDisable);"
-        }
+        },
+        "maximum": 2073600
       },
       "bleControlInterval": {
         "title": "BLE Control Interval",

package/lib/connection/lan.js

@@ -181,6 +181,12 @@ export default class {
         reject(err)
       })
 
+      // Handle errors on the sending socket. Without a listener here, node throws
+      // the error object instead of emitting it, which takes the bridge down.
+      this.sender.on('error', (err) => {
+        this.log.warn('[LAN] client error: %s.', parseError(err))
+      })
+
       // Handle started listening for messages
       this.receiver.on('listening', () => {
         const { address, port } = this.receiver.address()
@@ -233,16 +239,25 @@ export default class {
   sendScanCommand() {
     const scanCommand = JSON.stringify({ msg: { cmd: commands.scan, data: { account_topic: 'reserve' } } })
     this.log.debug('[LAN] scanning for devices over LAN...')
-    this.sender.send(scanCommand, scanCommandPort, multicastIp)
+    this.sender.send(scanCommand, scanCommandPort, multicastIp, err => this.logScanSendError(multicastIp, err))
 
     // Also scan any configured subnets directly. Multicast doesn't cross
     // between subnets, so devices on a different subnet than Homebridge are
     // reached by sending the scan straight to each host (they reply on 4002).
     this.scanHosts.forEach((host) => {
-      this.sender.send(scanCommand, scanCommandPort, host)
+      this.sender.send(scanCommand, scanCommandPort, host, err => this.logScanSendError(host, err))
     })
   }
 
+  // A scan send can fail on a host with no route to the target, for example when
+  // multicast is unavailable. Report it and carry on rather than letting dgram
+  // emit an unhandled 'error' event, which would crash the bridge every scan.
+  logScanSendError(target, err) {
+    if (err) {
+      this.log.debug('[LAN] scan request to %s failed [%s].', target, parseError(err))
+    }
+  }
+
   // Get all available LAN devices
   async getDevices() {
     return new Promise((resolve) => {

package/lib/device/fan-H7105.js

@@ -111,6 +111,14 @@ export default class extends GoveeDevice {
       this.lightService.getCharacteristic(this.hapChar.Hue).onSet(async (value) => {
         await this.internalColourUpdate(value)
       })
+      // Saturation needs a handler of its own. HomeKit writes hue and saturation
+      // separately, so with only hue listened for, dragging saturation alone -
+      // the same colour made paler or richer - reached nothing and the light
+      // never changed. Both handlers share one update, and the debounce inside
+      // it collapses a hue-and-saturation pair into a single command.
+      this.lightService.getCharacteristic(this.hapChar.Saturation).onSet(async () => {
+        await this.internalColourUpdate(this.lightService.getCharacteristic(this.hapChar.Hue).value)
+      })
       this.cacheHue = this.lightService.getCharacteristic(this.hapChar.Hue).value
       this.cacheSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
     }
@@ -319,13 +327,16 @@ export default class extends GoveeDevice {
         return
       }
 
-      // Don't continue if the new value is the same as before
-      if (value === this.cacheHue) {
+      // Don't continue if the new colour is the same as before. Saturation is
+      // part of that question: comparing hue alone meant a change of saturation
+      // at the same hue looked like no change at all, and nothing was sent.
+      const currentSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
+      if (value === this.cacheHue && currentSat === this.cacheSat) {
         return
       }
 
       // Calculate RGB values
-      const newRGB = hs2rgb(value, this.lightService.getCharacteristic(this.hapChar.Saturation).value)
+      const newRGB = hs2rgb(value, currentSat)
 
       // Generate the hex values for the code
       const hexValues = [0x3A, 0x1B, 0x05, 0x0D, ...newRGB]
@@ -336,7 +347,10 @@ export default class extends GoveeDevice {
         value: generateCodeFromHexValues(hexValues),
       })
 
-      // Cache the new state and log if appropriate
+      // Cache the new state and log if appropriate. Saturation is cached on
+      // every send, not only when the hue moved, or a change of saturation at
+      // the same hue would be sent once and then look unchanged ever after.
+      this.cacheSat = currentSat
       if (this.cacheHue !== value) {
         this.cacheHue = value
         this.accessory.log(`${platformLang.curColour} [rgb ${newRGB.join(' ')}]`)
@@ -450,12 +464,14 @@ export default class extends GoveeDevice {
 
             const hs = rgb2hs(newR, newG, newB)
 
-            // Check for a colour change
-            if (hs[0] !== this.cacheHue) {
+            // Check for a colour change. Saturation counts as much as hue, or a
+            // change of saturation made in the Govee app is reported back and
+            // ignored, leaving the tile showing the old colour.
+            if (hs[0] !== this.cacheHue || hs[1] !== this.cacheSat) {
               // Colour is different so update Homebridge with new values
               this.lightService.updateCharacteristic(this.hapChar.Hue, hs[0])
               this.lightService.updateCharacteristic(this.hapChar.Saturation, hs[1]);
-              [this.cacheHue] = hs
+              [this.cacheHue, this.cacheSat] = hs
 
               // Log the change
               this.accessory.log(`${platformLang.curColour} [rgb ${newR} ${newG} ${newB}]`)

package/lib/device/fan-H7107.js

@@ -111,6 +111,14 @@ export default class extends GoveeDevice {
       this.lightService.getCharacteristic(this.hapChar.Hue).onSet(async (value) => {
         await this.internalColourUpdate(value)
       })
+      // Saturation needs a handler of its own. HomeKit writes hue and saturation
+      // separately, so with only hue listened for, dragging saturation alone -
+      // the same colour made paler or richer - reached nothing and the light
+      // never changed. Both handlers share one update, and the debounce inside
+      // it collapses a hue-and-saturation pair into a single command.
+      this.lightService.getCharacteristic(this.hapChar.Saturation).onSet(async () => {
+        await this.internalColourUpdate(this.lightService.getCharacteristic(this.hapChar.Hue).value)
+      })
       this.cacheHue = this.lightService.getCharacteristic(this.hapChar.Hue).value
       this.cacheSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
     }
@@ -323,13 +331,16 @@ export default class extends GoveeDevice {
         return
       }
 
-      // Don't continue if the new value is the same as before
-      if (value === this.cacheHue) {
+      // Don't continue if the new colour is the same as before. Saturation is
+      // part of that question: comparing hue alone meant a change of saturation
+      // at the same hue looked like no change at all, and nothing was sent.
+      const currentSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
+      if (value === this.cacheHue && currentSat === this.cacheSat) {
         return
       }
 
       // Calculate RGB values
-      const newRGB = hs2rgb(value, this.lightService.getCharacteristic(this.hapChar.Saturation).value)
+      const newRGB = hs2rgb(value, currentSat)
 
       // Generate the hex values for the code
       const hexValues = [0x3A, 0x1B, 0x05, 0x0D, ...newRGB]
@@ -340,7 +351,10 @@ export default class extends GoveeDevice {
         value: generateCodeFromHexValues(hexValues),
       })
 
-      // Cache the new state and log if appropriate
+      // Cache the new state and log if appropriate. Saturation is cached on
+      // every send, not only when the hue moved, or a change of saturation at
+      // the same hue would be sent once and then look unchanged ever after.
+      this.cacheSat = currentSat
       if (this.cacheHue !== value) {
         this.cacheHue = value
         this.accessory.log(`${platformLang.curColour} [rgb ${newRGB.join(' ')}]`)
@@ -454,12 +468,14 @@ export default class extends GoveeDevice {
 
             const hs = rgb2hs(newR, newG, newB)
 
-            // Check for a colour change
-            if (hs[0] !== this.cacheHue) {
+            // Check for a colour change. Saturation counts as much as hue, or a
+            // change of saturation made in the Govee app is reported back and
+            // ignored, leaving the tile showing the old colour.
+            if (hs[0] !== this.cacheHue || hs[1] !== this.cacheSat) {
               // Colour is different so update Homebridge with new values
               this.lightService.updateCharacteristic(this.hapChar.Hue, hs[0])
               this.lightService.updateCharacteristic(this.hapChar.Saturation, hs[1]);
-              [this.cacheHue] = hs
+              [this.cacheHue, this.cacheSat] = hs
 
               // Log the change
               this.accessory.log(`${platformLang.curColour} [rgb ${newR} ${newG} ${newB}]`)

package/lib/device/heater2.js

@@ -221,6 +221,14 @@ export default class extends GoveeDevice {
     this.lightService.getCharacteristic(this.hapChar.Hue).onSet(async (value) => {
       await this.internalColourUpdate(value)
     })
+    // Saturation needs a handler of its own. HomeKit writes hue and saturation
+    // separately, so with only hue listened for, dragging saturation alone -
+    // the same colour made paler or richer - reached nothing and the light
+    // never changed. Both handlers share one update, and the debounce inside
+    // it collapses a hue-and-saturation pair into a single command.
+    this.lightService.getCharacteristic(this.hapChar.Saturation).onSet(async () => {
+      await this.internalColourUpdate(this.lightService.getCharacteristic(this.hapChar.Hue).value)
+    })
     this.cacheHue = this.lightService.getCharacteristic(this.hapChar.Hue).value
     this.cacheSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
 
@@ -574,13 +582,16 @@ export default class extends GoveeDevice {
         return
       }
 
-      // Don't continue if the new value is the same as before
-      if (value === this.cacheHue) {
+      // Don't continue if the new colour is the same as before. Saturation is
+      // part of that question: comparing hue alone meant a change of saturation
+      // at the same hue looked like no change at all, and nothing was sent.
+      const currentSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
+      if (value === this.cacheHue && currentSat === this.cacheSat) {
         return
       }
 
       // Calculate RGB values
-      const newRGB = hs2rgb(value, this.lightService.getCharacteristic(this.hapChar.Saturation).value)
+      const newRGB = hs2rgb(value, currentSat)
 
       // Generate the hex values for the code
       const hexValues = [0x3A, 0x1B, 0x05, 0x0D, ...newRGB]
@@ -591,7 +602,10 @@ export default class extends GoveeDevice {
         value: generateCodeFromHexValues(hexValues),
       })
 
-      // Cache the new state and log if appropriate
+      // Cache the new state and log if appropriate. Saturation is cached on
+      // every send, not only when the hue moved, or a change of saturation at
+      // the same hue would be sent once and then look unchanged ever after.
+      this.cacheSat = currentSat
       if (this.cacheHue !== value) {
         this.cacheHue = value
         this.accessory.log(`${platformLang.curColour} [rgb ${newRGB.join(' ')}]`)
@@ -731,12 +745,14 @@ export default class extends GoveeDevice {
 
           const hs = rgb2hs(newR, newG, newB)
 
-          // Check for a colour change
-          if (hs[0] !== this.cacheHue) {
+          // Check for a colour change. Saturation counts as much as hue, or a
+          // change of saturation made in the Govee app is reported back and
+          // ignored, leaving the tile showing the old colour.
+          if (hs[0] !== this.cacheHue || hs[1] !== this.cacheSat) {
             // Colour is different so update Homebridge with new values
             this.lightService.updateCharacteristic(this.hapChar.Hue, hs[0])
             this.lightService.updateCharacteristic(this.hapChar.Saturation, hs[1]);
-            [this.cacheHue] = hs
+            [this.cacheHue, this.cacheSat] = hs
 
             // Log the change
             this.accessory.log(`${platformLang.curColour} [rgb ${newR} ${newG} ${newB}]`)

package/lib/device/humidifier-H7142.js

@@ -122,6 +122,14 @@ export default class extends GoveeDevice {
     this.lightService.getCharacteristic(this.hapChar.Hue).onSet(async (value) => {
       await this.internalColourUpdate(value)
     })
+    // Saturation needs a handler of its own. HomeKit writes hue and saturation
+    // separately, so with only hue listened for, dragging saturation alone -
+    // the same colour made paler or richer - reached nothing and the light
+    // never changed. Both handlers share one update, and the debounce inside
+    // it collapses a hue-and-saturation pair into a single command.
+    this.lightService.getCharacteristic(this.hapChar.Saturation).onSet(async () => {
+      await this.internalColourUpdate(this.lightService.getCharacteristic(this.hapChar.Hue).value)
+    })
     this.cacheHue = this.lightService.getCharacteristic(this.hapChar.Hue).value
     this.cacheSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
 
@@ -318,15 +326,18 @@ export default class extends GoveeDevice {
         return
       }
 
-      // Don't continue if the new value is the same as before
-      if (value === this.cacheHue) {
+      // Don't continue if the new colour is the same as before. Saturation is
+      // part of that question: comparing hue alone meant a change of saturation
+      // at the same hue looked like no change at all, and nothing was sent.
+      const currentSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
+      if (value === this.cacheHue && currentSat === this.cacheSat) {
         return
       }
 
       // Generate the hex values for the code
       const newRGB = hs2rgb(
         value,
-        this.lightService.getCharacteristic(this.hapChar.Saturation).value,
+        currentSat,
       )
       const hexValues = [0x33, 0x1B, 0x01, this.cacheBright, ...newRGB]
 
@@ -336,7 +347,10 @@ export default class extends GoveeDevice {
         value: generateCodeFromHexValues(hexValues),
       })
 
-      // Cache the new state and log if appropriate
+      // Cache the new state and log if appropriate. Saturation is cached on
+      // every send, not only when the hue moved, or a change of saturation at
+      // the same hue would be sent once and then look unchanged ever after.
+      this.cacheSat = currentSat
       if (this.cacheHue !== value) {
         this.cacheHue = value
         this.accessory.log(`${platformLang.curColour} [rgb ${newRGB.join(' ')}]`)
@@ -487,12 +501,14 @@ export default class extends GoveeDevice {
             const newB = hexToDecimal(getTwoItemPosition(hexParts, 7))
             const hs = rgb2hs(newR, newG, newB)
 
-            // Check for a colour change
-            if (hs[0] !== this.cacheHue) {
+            // Check for a colour change. Saturation counts as much as hue, or a
+            // change of saturation made in the Govee app is reported back and
+            // ignored, leaving the tile showing the old colour.
+            if (hs[0] !== this.cacheHue || hs[1] !== this.cacheSat) {
               // Colour is different so update Homebridge with new values
               this.lightService.updateCharacteristic(this.hapChar.Hue, hs[0])
               this.lightService.updateCharacteristic(this.hapChar.Saturation, hs[1]);
-              [this.cacheHue] = hs
+              [this.cacheHue, this.cacheSat] = hs
 
               // Log the change
               this.accessory.log(`${platformLang.curColour} [rgb ${newR} ${newG} ${newB}]`)

package/lib/device/humidifier-H7160.js

@@ -85,6 +85,14 @@ export default class extends GoveeDevice {
     this.lightService.getCharacteristic(this.hapChar.Hue).onSet(async (value) => {
       await this.internalColourUpdate(value)
     })
+    // Saturation needs a handler of its own. HomeKit writes hue and saturation
+    // separately, so with only hue listened for, dragging saturation alone -
+    // the same colour made paler or richer - reached nothing and the light
+    // never changed. Both handlers share one update, and the debounce inside
+    // it collapses a hue-and-saturation pair into a single command.
+    this.lightService.getCharacteristic(this.hapChar.Saturation).onSet(async () => {
+      await this.internalColourUpdate(this.lightService.getCharacteristic(this.hapChar.Hue).value)
+    })
     this.cacheHue = this.lightService.getCharacteristic(this.hapChar.Hue).value
     this.cacheSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
 
@@ -266,15 +274,18 @@ export default class extends GoveeDevice {
         return
       }
 
-      // Don't continue if the new value is the same as before
-      if (value === this.cacheHue) {
+      // Don't continue if the new colour is the same as before. Saturation is
+      // part of that question: comparing hue alone meant a change of saturation
+      // at the same hue looked like no change at all, and nothing was sent.
+      const currentSat = this.lightService.getCharacteristic(this.hapChar.Saturation).value
+      if (value === this.cacheHue && currentSat === this.cacheSat) {
         return
       }
 
       // Generate the hex values for the code
       const newRGB = hs2rgb(
         value,
-        this.lightService.getCharacteristic(this.hapChar.Saturation).value,
+        currentSat,
       )
       const hexValues = [0x33, 0x1B, 0x01, this.cacheBright, ...newRGB]
 
@@ -284,7 +295,10 @@ export default class extends GoveeDevice {
         value: generateCodeFromHexValues(hexValues),
       })
 
-      // Cache the new state and log if appropriate
+      // Cache the new state and log if appropriate. Saturation is cached on
+      // every send, not only when the hue moved, or a change of saturation at
+      // the same hue would be sent once and then look unchanged ever after.
+      this.cacheSat = currentSat
       if (this.cacheHue !== value) {
         this.cacheHue = value
         this.accessory.log(`${platformLang.curColour} [rgb ${newRGB.join(' ')}]`)
@@ -411,12 +425,14 @@ export default class extends GoveeDevice {
             const newB = hexToDecimal(getTwoItemPosition(hexParts, 7))
             const hs = rgb2hs(newR, newG, newB)
 
-            // Check for a colour change
-            if (hs[0] !== this.cacheHue) {
+            // Check for a colour change. Saturation counts as much as hue, or a
+            // change of saturation made in the Govee app is reported back and
+            // ignored, leaving the tile showing the old colour.
+            if (hs[0] !== this.cacheHue || hs[1] !== this.cacheSat) {
               // Colour is different so update Homebridge with new values
               this.lightService.updateCharacteristic(this.hapChar.Hue, hs[0])
               this.lightService.updateCharacteristic(this.hapChar.Saturation, hs[1]);
-              [this.cacheHue] = hs
+              [this.cacheHue, this.cacheSat] = hs
 
               // Log the change
               this.accessory.log(`${platformLang.curColour} [rgb ${newR} ${newG} ${newB}]`)

package/lib/device/light.js

@@ -72,10 +72,22 @@ export default class extends GoveeDevice {
     this.service = this.accessory.getService(this.hapServ.Lightbulb)
       || this.accessory.addService(this.hapServ.Lightbulb)
 
-    // If adaptive lighting has just been disabled then remove and re-add service to hide AL icon
+    // Adaptive lighting has just been switched off, so take away the three
+    // characteristics that make Home offer it. Only these need to go: the whole
+    // Lightbulb service used to be thrown away and rebuilt here, which does hide
+    // the icon but presents Home with what looks like a different light, and an
+    // owner can lose that light's room and its automations as a result.
     if ((this.colourSafeMode || this.alShift === -1) && this.accessory.context.adaptiveLighting) {
-      this.accessory.removeService(this.service)
-      this.service = this.accessory.addService(this.hapServ.Lightbulb)
+      [
+        'SupportedCharacteristicValueTransitionConfiguration',
+        'CharacteristicValueTransitionControl',
+        'CharacteristicValueActiveTransitionCount',
+      ].forEach((charName) => {
+        const char = this.hapChar[charName]
+        if (char && this.service.testCharacteristic(char)) {
+          this.service.removeCharacteristic(this.service.getCharacteristic(char))
+        }
+      })
       this.accessory.context.adaptiveLighting = false
     }
 
@@ -200,6 +212,14 @@ export default class extends GoveeDevice {
     this.service.getCharacteristic(this.hapChar.Hue).onSet(async (value) => {
       await this.internalColourUpdate(value)
     })
+    // Saturation needs a handler of its own. HomeKit writes hue and saturation
+    // separately, so with only hue listened for, dragging saturation alone -
+    // the same colour made paler or richer - reached nothing at all. Both
+    // handlers share one update, and the debounce inside it collapses a
+    // hue-and-saturation pair into a single command.
+    this.service.getCharacteristic(this.hapChar.Saturation).onSet(async () => {
+      await this.internalColourUpdate(this.service.getCharacteristic(this.hapChar.Hue).value)
+    })
     this.cacheHue = this.service.getCharacteristic(this.hapChar.Hue).value
     this.cacheSat = this.service.getCharacteristic(this.hapChar.Saturation).value
 
@@ -663,7 +683,7 @@ export default class extends GoveeDevice {
       let rgb
       let mired
       let colourChange = false
-      let sigColourChange = false
+      let changedElsewhere = false
       if (params.kelvin) {
         mired = Math.round(1000000 / params.kelvin)
         hs = m2hs(mired)
@@ -672,28 +692,28 @@ export default class extends GoveeDevice {
         // Check for a colour change
         if (params.kelvin !== this.cacheKelvin) {
           colourChange = true
-
-          // Check for a significant colour change
-          const kelvinDiff = Math.abs(params.kelvin - this.cacheKelvin)
-          if (kelvinDiff > 100) {
-            sigColourChange = true
-          }
+          // Commands go out rounded to the nearest 100K, so a report that lands
+          // within that is this light repeating back what it was just told.
+          // Anything further apart came from somewhere else - see below
+          changedElsewhere = Math.abs(params.kelvin - this.cacheKelvin) > 100
         }
       } else {
         rgb = [params.rgb.r, params.rgb.g, params.rgb.b]
         hs = rgb2hs(rgb[0], rgb[1], rgb[2])
 
-        // Check for a colour change
-        if (hs[0] !== this.cacheHue) {
+        // Check for a colour change. Saturation matters as much as hue: going
+        // from a pale colour to a vivid one at the same hue is a real change,
+        // and comparing hue alone missed it entirely - so the light was left
+        // following adaptive lighting after its owner had chosen a colour, and
+        // wandered off that colour a few minutes later (#1333)
+        if (hs[0] !== this.cacheHue || hs[1] !== this.cacheSat) {
           colourChange = true
-
-          // Check for a significant colour change
-          const rgbDiff = Math.abs(rgb[0] - this.cacheR)
-            + Math.abs(rgb[1] - this.cacheG)
-            + Math.abs(rgb[2] - this.cacheB)
-          if (rgbDiff > 50) {
-            sigColourChange = true
-          }
+          // A light repeating our own command back can drift by a unit or two
+          // through the colour conversions on the way out and back. Beyond that
+          // drift, somebody else set this colour
+          changedElsewhere = Math.abs(rgb[0] - this.cacheR) > 5
+            || Math.abs(rgb[1] - this.cacheG) > 5
+            || Math.abs(rgb[2] - this.cacheB) > 5
         }
       }
 
@@ -703,7 +723,7 @@ export default class extends GoveeDevice {
         this.service.updateCharacteristic(this.hapChar.Hue, hs[0])
         this.service.updateCharacteristic(this.hapChar.Saturation, hs[1]);
         [this.cacheR, this.cacheG, this.cacheB] = rgb;
-        [this.cacheHue] = hs
+        [this.cacheHue, this.cacheSat] = hs
 
         if (mired) {
           if (!this.colourSafeMode) {
@@ -716,8 +736,11 @@ export default class extends GoveeDevice {
           this.accessory.log(`${platformLang.curColour} [rgb ${this.cacheR} ${this.cacheG} ${this.cacheB}]`)
         }
 
-        // If the difference is significant then disable adaptive lighting
-        if (!this.colourSafeMode && this.alController?.isAdaptiveLightingActive?.() && sigColourChange) {
+        // Somebody chose this colour outside HomeKit - in the Govee app, on a
+        // remote, or at the wall. HomeKit's own colour changes are caught by
+        // Homebridge itself, but nothing else sees these, so adaptive lighting
+        // would carry on and move the light off that colour within minutes.
+        if (!this.colourSafeMode && this.alController?.isAdaptiveLightingActive?.() && changedElsewhere) {
           this.alController.disableAdaptiveLighting()
           this.accessory.log(platformLang.alDisabled)
         }

package/lib/device/sensor-monitor.js

@@ -108,7 +108,7 @@ export default class extends GoveeDevice {
         case 'aa0e':
           break
         default: {
-          if (hexParts.length < 21) {
+          if (hexParts.length < 20) {
             break
           }
           const tempInCen = Math.round((hexToDecimal(`0x${deviceFunction}`) + (this.accessory.context.offTemp / 100)) / 10) / 10

package/lib/platform.js

@@ -29,7 +29,7 @@ import {
   updateFailureError,
 } from './utils/functions.js'
 import platformLang from './utils/lang-en.js'
-import { logUnknownData } from './utils/report-unknown.js'
+import { isFirstReport, logUnknownData } from './utils/report-unknown.js'
 import { parseDeviceUpdate } from './utils/response-parser.js'
 
 const require = createRequire(import.meta.url)
@@ -825,8 +825,21 @@ export default class {
               battery: goveeReading.battery,
               source: 'BLE',
             })
-          } else {
-            this.log.warn('[BLE] %s [%s].', platformLang.bleScanUnknown, goveeReading.address)
+          } else if (accessory) {
+            // A monitor's readings arrive over its own connection, so there is
+            // nothing to do with this one and nothing for the owner to act on
+            accessory.logDebug(`[BLE] ${platformLang.bleScanUnknown}`)
+          } else if (isFirstReport(`ble-reading|${goveeReading.address}`)) {
+            // A sensor broadcasts every few seconds, so say this once per session
+            // rather than on every advertisement. Only an address that belongs to
+            // this account is worth a warning - anything else may be a neighbour's
+            // device, which the owner cannot do anything about.
+            const line = `[BLE] ${platformLang.bleScanUnknown} [${goveeReading.address}].`
+            if (this.hasBleSensor(goveeReading.address)) {
+              this.log.warn(line)
+            } else {
+              this.log.debug(line)
+            }
           }
         } catch (err) {
           this.log.warn('[BLE] error processing reading: %s', parseError(err))

package/lib/utils/config-parser.js

@@ -33,6 +33,9 @@ export function applyUserConfig(platform, config) {
   const logIncrease = (k, min) => {
     platform.log.warn('%s [%s] %s %s.', platformLang.cfgItem, k, platformLang.cfgLow, min)
   }
+  const logDecrease = (k, max) => {
+    platform.log.warn('%s [%s] %s %s.', platformLang.cfgItem, k, platformLang.cfgHigh, max)
+  }
   const logQuotes = (k) => {
     platform.log.warn('%s [%s] %s.', platformLang.cfgItem, k, platformLang.cfgQts)
   }
@@ -77,6 +80,7 @@ export function applyUserConfig(platform, config) {
       case 'disableDeviceLogging':
       case 'ignoreMatter':
       case 'lanDisable':
+      case 'openApiDisable':
         if (typeof val === 'string') {
           logQuotes(key)
         }
@@ -86,7 +90,8 @@ export function applyUserConfig(platform, config) {
       case 'bleRefreshTime':
       case 'httpRefreshTime':
       case 'lanRefreshTime':
-      case 'lanScanInterval': {
+      case 'lanScanInterval':
+      case 'openApiRefreshTime': {
         if (typeof val === 'string') {
           logQuotes(key)
         }
@@ -97,6 +102,9 @@ export function applyUserConfig(platform, config) {
         } else if (intVal < platformConsts.minValues[key]) {
           logIncrease(key, platformConsts.minValues[key])
           platform.config[key] = platformConsts.minValues[key]
+        } else if (platformConsts.maxValues[key] !== undefined && intVal > platformConsts.maxValues[key]) {
+          logDecrease(key, platformConsts.maxValues[key])
+          platform.config[key] = platformConsts.maxValues[key]
         } else {
           platform.config[key] = intVal
         }

package/lib/utils/constants.js

@@ -15,6 +15,8 @@ export default {
     lanDisable: false,
     lanRefreshTime: 30,
     lanScanInterval: 60,
+    openApiDisable: false,
+    openApiRefreshTime: 30,
     bleControlInterval: 5,
     colourSafeMode: false,
     lightDevices: [],
@@ -42,6 +44,7 @@ export default {
     lanRefreshTime: 30,
     lanScanInterval: 60,
     lowBattThreshold: 20,
+    openApiRefreshTime: 30,
     showAs: 'default',
   },
 
@@ -54,6 +57,19 @@ export default {
     lanRefreshTime: 10,
     lanScanInterval: 30,
     lowBattThreshold: 1,
+    openApiRefreshTime: 30,
+  },
+
+  // A Node timer holds its delay in a signed 32-bit integer. Over 2147483647 ms
+  // it does not throw - it quietly becomes 1 ms, so any of these set past that
+  // point would poll a thousand times a second rather than slowly. 2073600
+  // seconds is 24 days, comfortably inside the limit once multiplied up.
+  maxValues: {
+    bleRefreshTime: 2073600,
+    httpRefreshTime: 2073600,
+    lanRefreshTime: 2073600,
+    lanScanInterval: 2073600,
+    openApiRefreshTime: 2073600,
   },
 
   allowed: {

package/lib/utils/lang-en.js

@@ -6,8 +6,8 @@ export default {
   accTokenNoExist: 'does not exist, this is normally not an issue',
   accTokenStoreErr: 'could not store access token as',
   accTokenUserChange: 'username has changed',
-  alDisabled: 'adaptive lighting disabled due to significant colour change',
-  alDisabledScene: 'adaptive lighting disabled due to scene change',
+  alDisabled: 'adaptive lighting turned off, as the colour was changed outside HomeKit',
+  alDisabledScene: 'adaptive lighting turned off, as a scene was selected',
   awsEventClose: 'close event',
   awsEventConnect: 'connect event',
   awsEventError: 'error event',
@@ -34,6 +34,7 @@ export default {
   cfgIgn: 'is not configured correctly so ignoring',
   cfgIgnItem: 'has an invalid entry which will be ignored',
   cfgItem: 'Config entry',
+  cfgHigh: 'is set too high so reducing to',
   cfgLow: 'is set too low so increasing to',
   cfgRmv: 'is unused and can be removed',
   cfgQts: 'should not have quotes around its entry',

package/package.json

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