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

package/CHANGELOG.md

@@ -8,6 +8,7 @@ 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
 
 ## v11.34.1 (2026-08-06)
 

package/lib/platform.js

@@ -55,7 +55,6 @@ export default class {
     try {
       this.api = api
       this.log = log
-      this.isBeta = process.argv.includes('-D')
 
       // Configuration objects for accessories
       this.deviceConf = {}
@@ -111,14 +110,16 @@ export default class {
       // Log that the plugin initialisation has been successful
       this.log('%s.', platformLang.initialised)
 
-      // Sort out some logging functions
-      if (this.isBeta) {
-        this.log.debug = this.log
-        this.log.debugWarn = this.log.warn
-      } else {
-        this.log.debug = () => {}
-        this.log.debugWarn = () => {}
-      }
+      // Homebridge already decides whether debug lines are shown, and it gets it
+      // right in a child bridge too. This used to work it out for itself by
+      // looking for `-D` in the plugin's own process arguments, which a child
+      // bridge does not receive unless that bridge has its own debug setting
+      // turned on - so debug logging silently disappeared for anyone running the
+      // plugin in a child bridge with debug enabled globally.
+      //
+      // `debugWarn` has no equivalent on Homebridge's logger, so it goes out as
+      // a debug line too rather than being invented here.
+      this.log.debugWarn = (...args) => this.log.debug(...args)
 
       // Require any libraries that the plugin uses
       this.cusChar = new platformChars(this.api)
@@ -663,22 +664,21 @@ export default class {
   }
 
   applyAccessoryLogging(accessory) {
-    if (this.isBeta) {
-      accessory.log = msg => this.log('[%s] %s.', accessory.displayName, msg)
-      accessory.logWarn = msg => this.log.warn('[%s] %s.', accessory.displayName, msg)
-      accessory.logDebug = msg => this.log('[%s] %s.', accessory.displayName, msg)
-      accessory.logDebugWarn = msg => this.log.warn('[%s] %s.', accessory.displayName, msg)
-    } else {
-      if (this.config.disableDeviceLogging) {
-        accessory.log = () => {}
-        accessory.logWarn = () => {}
-      } else {
-        accessory.log = msg => this.log('[%s] %s.', accessory.displayName, msg)
-        accessory.logWarn = msg => this.log.warn('[%s] %s.', accessory.displayName, msg)
-      }
-      accessory.logDebug = () => {}
-      accessory.logDebugWarn = () => {}
+    // Debug lines always go to Homebridge's debug logger, which prints them only
+    // when debug is on - so there is nothing to decide here. Working it out from
+    // the process arguments instead is what lost debug logging entirely for
+    // anyone running the plugin in a child bridge.
+    accessory.logDebug = msg => this.log.debug('[%s] %s.', accessory.displayName, msg)
+    accessory.logDebugWarn = accessory.logDebug
+
+    if (this.config.disableDeviceLogging) {
+      accessory.log = () => {}
+      accessory.logWarn = () => {}
+      return
     }
+
+    accessory.log = msg => this.log('[%s] %s.', accessory.displayName, msg)
+    accessory.logWarn = msg => this.log.warn('[%s] %s.', accessory.displayName, msg)
   }
 
   initialiseDevice(device) {

package/package.json

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