You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What issue do you have? Please be as thorough and explicit as possible.
I have a scene with two lights. The plugin recognizes the scene and lists it for each of the two light devices. The scenes are exposed as accessory switches for each accessory, checks out fine both Home and Controller. So far so good.
The accessory switch is taking on the name of the parent light devices. I would have expected the name to be set to the scene name, which plugin knows as seen in the logs.
Am I missing some config to set the label, or is this expected behavior?
Details of your setup.
Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge
Which version of Homebridge/HOOBS do you have?
[Homebridge v1.8.5][UI v4.65.0]
Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry Pi/Raspbian Linux
Node.js v20.18.0
Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
homebridge-govee v10.15.0
Did not have the scene while on previous version
Which Govee devices do you have that are causing issues? Please include product models if applicable.
What issue do you have? Please be as thorough and explicit as possible.
I have a scene with two lights. The plugin recognizes the scene and lists it for each of the two light devices. The scenes are exposed as accessory switches for each accessory, checks out fine both Home and Controller. So far so good.
The accessory switch is taking on the name of the parent light devices. I would have expected the name to be set to the scene name, which plugin knows as seen in the logs.
Am I missing some config to set the label, or is this expected behavior?
Details of your setup.
Please paste any relevant logs below.
The text was updated successfully, but these errors were encountered: