DallasHoff / homebridge-openrgb

Control the RGB lighting of your PC components and peripherals with HomeKit.
https://www.npmjs.com/package/homebridge-openrgb
Apache License 2.0
13 stars 0 forks source link

Device name #14

Closed ghost closed 9 months ago

ghost commented 9 months ago

Openrgb works fine and the zones have names. I can control the backlight, but because the device name is empty, there is an error with the plugin. Is it possible if the device is empty (I have 1) to set some default name for the plugin to work. Or maybe there are other workarounds?

Logs:

AssertionError [ERR_ASSERTION]: Accessories must be created with a non-empty displayName. at new Accessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:491:11) at new PlatformAccessory (/usr/local/lib/node_modules/homebridge/src/platformAccessory.ts:71:9) at /usr/local/lib/node_modules/homebridge-openrgb/src/platform.ts:155:27 at Array.forEach () at OpenRgbPlatform.discoverDevices (/usr/local/lib/node_modules/homebridge-openrgb/src/platform.ts:116:18) at processTicksAndRejections (node:internal/process/task_queues:95:5) at HomebridgeAPI. (/usr/local/lib/node_modules/homebridge-openrgb/src/platform.ts:71:9)

Plugin Config:

default

Screenshots:

image

Environment:

iddion commented 9 months ago

Fixed. Since not only this plugin is used. It is better to correct the display of the name in the driver itself or force the name to be specified in the application. In the application, the name can be set in RGBController_GigabyteRGBFusion2USB

DallasHoff commented 9 months ago

Fixed in 1.4.2