@homebridge-plugins/homebridge-govee 11.32.2-beta.0 → 11.32.2-beta.2

package/CHANGELOG.md

@@ -7,6 +7,8 @@ All notable changes to `@homebridge-plugins/homebridge-govee` will be documented
 ### Changed
 
 - fix: implement the H7107's oscillation toggle, which threw a not-implemented error when tapped (#1334)
+- fix: also send the H7107's oscillation command as the multiSync frame the fan itself uses, since the first shape only turned it off sometimes (#1334)
+- fix: send the H7107's oscillation-off command without the swing-range bytes, matching the zero-tailed frame the fan echoes back (#1334)
 
 ## v11.32.1 (2026-08-02)
 

package/lib/device/fan-H7107.js

@@ -210,12 +210,15 @@ export default class {
         return
       }
 
-      // The AWS code mirrors the device's own `aa1d..` oscillation report,
-      // carrying over the extra bytes from the last report seen (#1334).
-      // Mirroring a status code is not guaranteed on every model, so the
-      // documented OpenAPI oscillation toggle is also sent when the device
-      // advertises it
-      const tailBytes = this.cacheSwingCode
+      // The AWS code mirrors the device's own `aa1d..` oscillation report.
+      // Turning ON carries over the swing-range bytes from the last report
+      // seen, which hardware-confirmed works. Turning OFF must NOT carry
+      // them: the fan answered a parameterised off command by echoing back a
+      // zero-tailed `331d00..` frame while continuing to oscillate — its own
+      // way of showing the shape it expects (#1334). Mirroring a status code
+      // is not guaranteed on every model, so the documented OpenAPI
+      // oscillation toggle is also sent when the device advertises it
+      const tailBytes = value && this.cacheSwingCode
         ? this.cacheSwingCode.slice(6, 14).match(/.{1,2}/g).map(byte => Number.parseInt(byte, 16))
         : []
       await this.platform.sendDeviceUpdate(this.accessory, {
@@ -226,6 +229,16 @@ export default class {
           : undefined,
       })
 
+      // Hardware testing showed the `331d..` frame above turns oscillation ON
+      // reliably but OFF only sometimes - and the fan's own oscillation state
+      // travels as multiSync traffic, which is what the `3a`-prefixed frame
+      // belongs to. Both shapes mean the same thing, so the one the fan
+      // ignores is harmless, and one test tells us which it honours (#1334)
+      await this.platform.sendDeviceUpdate(this.accessory, {
+        cmd: 'multiSync',
+        value: generateCodeFromHexValues([0x3A, 0x1D, value ? 0x01 : 0x00, ...tailBytes]),
+      })
+
       // Cache the new state and log if appropriate
       if (this.cacheSwing !== newValue) {
         this.cacheSwing = newValue

package/package.json

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