@homebridge-plugins/homebridge-govee 11.32.2-beta.32 → 11.32.2-beta.33

package/CHANGELOG.md

@@ -48,6 +48,8 @@ All notable changes to `@homebridge-plugins/homebridge-govee` will be documented
 - feat: add ble encryption for the H3001 solar string lights, which silently ignore unencrypted frames (#1328) (@dominick-han)
 - fix: mention an unrecognised bluetooth broadcast once, and only for one of your own sensors, since a scan also hears your lights and the neighbours
 - fix: say "device(s)" in the connection summary, since the count is often one
+- fix: stop the macOS bluetooth scan leaving its timer running once the device has been found
+- docs: say that macOS bluetooth support is new and ask for reports, rather than stating it works
 
 ## v11.32.1 (2026-08-02)
 

package/README.md

@@ -29,7 +29,7 @@ Homebridge plugin to integrate Govee devices into HomeKit
 - To use this plugin, you will need to already have:
   - [Node](https://nodejs.org): latest version of `v22`, `v24` or `v26` - any other major version is not supported.
   - [Homebridge](https://homebridge.io): `v1.6` or above - refer to link for more information and installation instructions.
-  - For bluetooth connectivity, it may be necessary to install extra packages on your system, see [Bluetooth Control](https://github.com/homebridge-plugins/homebridge-govee/wiki/Bluetooth-Control). Bluetooth works best when using a Raspberry Pi, and has not been tested on Windows. On macOS, the plugin resolves BLE devices via their advertised name (macOS does not expose bluetooth MAC addresses), and the `node` binary running Homebridge needs Bluetooth permission in System Settings → Privacy & Security → Bluetooth.
+  - For bluetooth connectivity, it may be necessary to install extra packages on your system, see [Bluetooth Control](https://github.com/homebridge-plugins/homebridge-govee/wiki/Bluetooth-Control). Bluetooth works best on a Raspberry Pi, and has not been tested on Windows. macOS is newly supported from `v11.32.2` and has only been tried on a handful of devices so far - you will need to give the `node` binary running Homebridge permission under System Settings → Privacy & Security → Bluetooth, and please do report anything that does not work.
 
 ### Setup
 

package/lib/connection/ble.js

@@ -421,6 +421,7 @@ export default class BLEConnection {
     }
     const peripheral = await new Promise((resolve, reject) => {
       let done = false
+      let scanTimeoutId
       function onDiscover(p) {
         const name = (p.advertisement?.localName ?? '').toLowerCase()
         if (name.endsWith(suffix) && (name.startsWith('govee') || name.startsWith('ihoment'))) {
@@ -432,13 +433,17 @@ export default class BLEConnection {
           return
         }
         done = true
+        // The device is usually found in well under a second, so without this
+        // the timer stays live for the rest of its window and holds the event
+        // loop open. The two timeouts above clear theirs the same way.
+        clearTimeout(scanTimeoutId)
         btClient.removeListener('discover', onDiscover)
         btClient.stopScanningAsync().catch(() => {})
         fn(value)
       }
       btClient.on('discover', onDiscover)
       btClient.startScanningAsync([], true).catch(err => finish(reject, err))
-      setTimeout(() => finish(reject, new Error(`no peripheral advertising name suffix ${suffix} found in scan`)), Math.max(timeout - 1000, 4000))
+      scanTimeoutId = setTimeout(() => finish(reject, new Error(`no peripheral advertising name suffix ${suffix} found in scan`)), Math.max(timeout - 1000, 4000))
     })
     this.darwinPeripheralCache.set(suffix, peripheral)
     await peripheral.connectAsync()

package/package.json

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