onyx galleon
There is a PR adding sensors to show which current scene is active for hue light groups. I don't know much about how the scenes in the hue ecosystem works, but if there is the concept of "active" then it should wither be a switch per scene or, as suggested in a comment, a select with the different scenes.
I don't think a scene entity + multiple sensor entites per scene is a good approach.
See https://github.com/home-assistant/core/pull/151883#issuecomment-3977454987
Thoughts?
Hue scenes that should not be scenes?
tulip pewter
A dropdown control would avoid the radio button effect you get with switches where activating one switch deactivates another switch (because only one scene can be active)
potential con: might be harder to query the history of indidiual scenes when you only have the combined history of all scenes in a room/zone
dire breach
In general we don't allow calculating state in integrations that integrate devices or services. The current scene sensors in the PR are calculated, which isn't allowed.
We're only allowed to express state that is already exposed by the API.
The only exception is time where we allow converting to a time that matches the entity design.
onyx galleon
@dire breach what about the suggestions (changing them to switch or select)?
From what I understood,SceneActiveStatus and SmartSceneState on the Hue API represent the scene state
dire breach
A select sounds good. As long as we're following the API it's fine.
tulip pewter
Ok didn't know about the rule against computed sensors, I will replace them with a select for regular scenes. For smart scenes, I need to have a think about how to handle those.