@homebridge-plugins/homebridge-govee 11.32.0-beta.30 → 11.32.0-beta.32

package/CHANGELOG.md

@@ -38,6 +38,9 @@ All notable changes to `@homebridge-plugins/homebridge-govee` will be documented
 - chore: count a repeated commit subject once when syncing the changelog
 - chore(github): check the changelog against the commits in ci
 - fix(openapi): report govee's own reason when it refuses a command, instead of the command appearing to succeed (#1324)
+- fix: report why a command failed instead of claiming no connection method was available (#1324)
+- fix(ble): use the segment-based colour command for the H617A, whose LEDs ignore the simple RGB colour commands (#1332)
+- feat: add support for the H1250 ceiling light pro as an rgb light (#1333)
 
 ## v11.31.0 (2026-07-24)
 

package/lib/platform.js

@@ -25,6 +25,7 @@ import {
   parseDeviceId,
   parseError,
   pfxToCertAndKey,
+  updateFailureError,
 } from './utils/functions.js'
 import platformLang from './utils/lang-en.js'
 import { parseDeviceUpdate } from './utils/response-parser.js'
@@ -1864,7 +1865,7 @@ export default class {
     // No BLE fallback for this command — surface any earlier failure so HAP reverts
     if (!data.bleParams) {
       if (attempted) {
-        throw lastError || new Error(platformLang.noConnMethod)
+        throw updateFailureError(lastError, platformLang.noConnMethod)
       }
       return true
     }
@@ -1883,10 +1884,17 @@ export default class {
           return true
         } catch (err) {
           // Bluetooth didn't work or not enabled
+          lastError = err
           accessory.logDebugWarn(`${platformLang.notBLESent} ${parseError(err)}`)
         }
       }
-      throw new Error(platformLang.noConnMethod)
+
+      // Every method available for this command has now been tried and failed.
+      // Report the last real reason rather than "no connection method
+      // available" - there WAS one, it was tried, and something specific went
+      // wrong. Saying otherwise sends the user to the connection-method docs
+      // when the answer was "the device is offline" (#1324).
+      throw updateFailureError(lastError, platformLang.noConnMethod)
     })
   }
 

package/lib/utils/constants.js

@@ -129,6 +129,7 @@ export default {
 
   models: {
     rgb: [
+      'H1250', // 18-Inch Ceiling Light Pro, https://github.com/homebridge-plugins/homebridge-govee/issues/1333
       'H1270', // Ceiling Light Ultra
       'H1401',
       'H14C0', // https://github.com/homebridge-plugins/homebridge-govee/issues/1301

package/lib/utils/device-capabilities.js

@@ -19,6 +19,11 @@ const modelOverrides = {
   H6053: { bleColorCmd: COLOR_SUB.RGB_EXTENDED, bleColorCmdSuffix: [0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x7F] },
   H6072: { bleColorCmd: COLOR_SUB.RGB_EXTENDED, bleColorCmdSuffix: [0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x7F] },
   H6199: { bleColorCmd: COLOR_SUB.RGB_EXTENDED, bleColorCmdSuffix: [0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x7F] },
+  // H617A is the same RGBIC family as the H617E below - the simple RGB command
+  // is accepted but the LEDs never change, so it needs the extended format too.
+  // Brightness works on the default 0xFF scale, so only the colour command is
+  // overridden (#1332)
+  H617A: { bleColorCmd: COLOR_SUB.RGB_EXTENDED, bleColorCmdSuffix: [0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x7F] },
   // H617E is an RGBIC strip which ignores the 0x0D command - it needs the
   // segment-based extended format, as seen in its own TTR rule data (#1290)
   H617E: { bleColorCmd: COLOR_SUB.RGB_EXTENDED, bleColorCmdSuffix: [0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0x7F], bleBrightnessScale: 0x64 },

package/lib/utils/functions.js

@@ -162,6 +162,23 @@ function describeControlFailure(responseData) {
   return state.errorMsg || responseData?.msg || responseData?.message || 'the device rejected the command'
 }
 
+/**
+ * Choose the error to report once every connection method has been exhausted.
+ *
+ * "No connection method available" is only true when nothing could be tried. If
+ * a method WAS tried and failed, that failure is the answer worth having — an
+ * offline device, a refused command, a Bluetooth timeout. Reporting the generic
+ * message instead discards it and points the user at the connection-method
+ * documentation, which is the wrong place to look when the connection was fine
+ * and the device simply said no (#1324).
+ *
+ * The original error object is passed through untouched, so flags set on it
+ * upstream (`deviceRefusal`) still reach the caller.
+ */
+function updateFailureError(lastError, fallbackMessage) {
+  return lastError ?? new Error(fallbackMessage)
+}
+
 export {
   base64ToHex,
   cenToFar,
@@ -182,4 +199,5 @@ export {
   pfxToCertAndKey,
   sleep,
   statusToActionCode,
+  updateFailureError,
 }

package/lib/utils/functions.test.js

@@ -18,6 +18,7 @@ import {
   nearestHalf,
   parseDeviceId,
   parseError,
+  updateFailureError,
 } from './functions.js'
 
 /**
@@ -247,3 +248,45 @@ describe('describeControlFailure', () => {
     expect(describeControlFailure(undefined)).toBeNull()
   })
 })
+
+/**
+ * The bug (#1324): when a command had a Bluetooth fallback, every earlier
+ * failure was thrown away and replaced with "no connection method available".
+ * That is worse than vague — it is untrue, and its link sends the user off to
+ * configure connection methods when the real answer was that Govee had said
+ * the device was offline.
+ */
+describe('updateFailureError', () => {
+  it('reports govee\'s own refusal rather than the generic message', () => {
+    const refusal = new Error('Device is offline. Please check the Wi-Fi connection.')
+    const chosen = updateFailureError(refusal, 'no connection method available')
+
+    expect(chosen.message).toBe('Device is offline. Please check the Wi-Fi connection.')
+  })
+
+  it('passes the original error through, so upstream flags survive', () => {
+    const refusal = new Error('Device is offline. Please check the Wi-Fi connection.')
+    refusal.deviceRefusal = true
+
+    const chosen = updateFailureError(refusal, 'no connection method available')
+
+    // Same object, not a copy - platform.js reads `deviceRefusal` off it to
+    // decide whether to print a stack line.
+    expect(chosen).toBe(refusal)
+    expect(chosen.deviceRefusal).toBe(true)
+  })
+
+  it('falls back to the generic message only when nothing was tried', () => {
+    expect(updateFailureError(undefined, 'no connection method available').message)
+      .toBe('no connection method available')
+    expect(updateFailureError(null, 'no connection method available').message)
+      .toBe('no connection method available')
+  })
+
+  it('keeps a bluetooth timeout rather than masking it', () => {
+    const bleFailure = new Error('BLE update failed: Connection timeout')
+
+    expect(updateFailureError(bleFailure, 'no connection method available').message)
+      .toBe('BLE update failed: Connection timeout')
+  })
+})

package/package.json

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