@homebridge-plugins/homebridge-govee 11.34.2-beta.10 → 11.34.2-beta.12

package/CHANGELOG.md

@@ -24,6 +24,7 @@ All notable changes to `@homebridge-plugins/homebridge-govee` will be documented
 - feat: show whether the kettle is heating, keeping warm or idle (#1337)
 - fix: give the H5106 a battery service, so its low battery setting does something
 - fix: stop a light's broadcast being mistaken for an h5101 sensor reading
+- fix: follow a device renamed in the govee app, instead of keeping its first name forever (#1344)
 
 ## v11.34.1 (2026-08-06)
 

package/lib/utils/device-context.js

@@ -1,6 +1,7 @@
 import platformConsts from './constants.js'
 import { getDeviceCapabilities } from './device-capabilities.js'
 import { hasProperty } from './functions.js'
+import platformLang from './lang-en.js'
 
 /**
  * Fills in everything a handler needs to know about a device before it is
@@ -69,9 +70,38 @@ export function applyDeviceContext(platform, accessory, device, deviceConf, join
     accessory.context.useLanControl = true
   }
 
-  // If the device is LAN-only, then sync the display name with the label in the configuration
-  if (device.isLanOnly) {
-    accessory.displayName = device.deviceName
+  // Keep the name in step with Govee - or, for a LAN-only device, with the
+  // label in the configuration.
+  //
+  // ⚠️ This used to run for LAN-only devices only, so every other device kept
+  // whatever name it was discovered under, forever. A name HAP complains about
+  // (brackets, say) could then not be cleared without deleting the cached
+  // accessory and losing its room and automations (#1344).
+  //
+  // ⚠️ This does NOT rename anything in the Home app. HomeKit fixes the name a
+  // user sees when the accessory is first added, and a rename made there never
+  // comes back to us either. What this fixes is the name Homebridge itself
+  // shows and, through the Name characteristic, the HAP warning.
+  //
+  // `updateDisplayName` is the supported way to do it - assigning to
+  // `displayName` sets only Homebridge's copy and leaves the HAP accessory
+  // behind. It arrived in Homebridge v1.10.0, and this plugin still supports
+  // ^1.6.0, hence the check.
+  if (device.deviceName && accessory.displayName !== device.deviceName) {
+    platform.log('[%s] %s [%s].', accessory.displayName, platformLang.devRenamed, device.deviceName)
+
+    if (typeof accessory.updateDisplayName === 'function') {
+      accessory.updateDisplayName(device.deviceName)
+    } else {
+      accessory.displayName = device.deviceName
+    }
+
+    const hapChar = platform.api?.hap?.Characteristic
+    const infoService = accessory.getService?.(platform.api?.hap?.Service?.AccessoryInformation)
+    if (hapChar && infoService) {
+      infoService.updateCharacteristic(hapChar.Name, device.deviceName)
+      infoService.updateCharacteristic(hapChar.ConfiguredName, device.deviceName)
+    }
   }
 
   // See if we have extra HTTP client info for this device

package/lib/utils/lang-en.js

@@ -82,6 +82,7 @@ export default {
   devNotRet: 'skipping sync as device status not retrievable',
   devNotUpdated: 'could not be updated as',
   devRemove: 'has been removed from Homebridge',
+  devRenamed: 'has been renamed to',
   disableClient: 'disabling client as',
   disabledInConfig: 'disabled in config',
   disabling: 'Disabling plugin',

package/package.json

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