You need to add it to your automations or buttons to Call A Service, select Scene Presets: Start dynamic scene and then set the preset ID of the scene you like and any other config you like.
I have mine setup on Hue Switches and the HUE Button activates the Scene. An important piece to note it does not work with Light Groups. You need to select each Light Entity.
@Hypfer Another thing as a feature request is to be able to use Light Groups instead of individual light entities. If I wanted to setup all my house with a scene that would involve adding over 100 light entities.
You mean Zigbee groups? Thatās not possible.
Essentially, Zigbee groups are a single light. They all listen to the same address/have the same shared group identity on top of their individual one and thus behave as one. Because of that, you canāt resolve a zigbee level group to its individual lights from Home Assistant.
The hue bridge can do that because it has insight into the zigbee layer but that canāt be replicated by this custom_component.
What you can do though is use group entities or areas and devices in Home Assistant. The integration can resolve those three and fetch the individual light entities from them.
Not Zigbee Groups but standard Helper - Group - Lights. I was thinking that it should work with them but when selecting a light group and running a dynamic scene they are all to be the same colour cycling through the dynamic scene. If you set the entities individually then each light will be different which is similar to the way the Hue app does it.
Well I know for a fact that it works with Home Assistant groups because I specifically built it like that since I use it exactly like that.
Maybe your group accidentally contains a zigbee group light entity that then sets all the lights to the same color?
Whatever it is itās user error so please refrain from making bold claims like āyou have to use it like thisā without the knowledge to back them up. That is just going to confuse other people.
So what am I doing wrong? This is repeatable in my situation. And as for making bold claims, not making any claims at all, just adding my experience in setting it up with the documentation provided through trial and error on how I got it all working.
Iāve also noticed that it is possible to build loops with groups.
The new resolver should be resilient against that but Home Assistant itself and its core services donāt seem to be so donāt do that.
@Hypfer Many thanks for the quick update of the code! I have tested it and it works perfectly.
I made one change on my end to my Helper Groups. I had Helper Light Groups inside of Helper Light Groups (Kitchen All Group and inside that the light groups Kitchen Bench, Kitchen Sink, Kitchen Galley) and that didnāt work but once I added each individual light entity to Kitchen All and then called the helper groups it worked fantastic!
Also I will write up later on how I have it working with the Philips Hue Switch and the buttons with Scene Presets.
Again, many thanks for this Custom Component. Itās brilliant!
Sorry, that shouldāve worked. But I didnāt test it, again , because I donāt have a dev setup with a debugger and printf debugging is annoying. Oh well.
My bad. Fixed with 1.1.4
You should now be able to use that helper group structure.
Thank you @Hypfer. Iāve been wanting to ditch my hub and the scenes were the only things keeping me attached to it.
Also, this is the final piece needed for āHA Wife Approvalā, as she loved the Hue Scenes and I had been manually integrating them (also to work with other brands of bulbs). This is seamless and elegant. Much appreciated!!
Has anybody had any luck using the available service calls in Node Red, for which they could share examples? I have not had any luck, and Iām not even sure where to look. For example, when I try to call scene_presets.start_dynamic_scene, and use the helper in Node Red to load example data, it loads examples for everything except ātargetsā and I cannot figure out the expected syntax for a single light entity, let alone a list of entities. (Also, I do realize that the presets are called by an ID and not a name anymore, I just left the example data as-is for the screenshot.)
Oh, sorry for being unclear. I meant exporting the style you have for the presets into a card which can be used in the Lovelace dashboard. With a dropdown for the specific preset id so that the name and especially the image are shown.
Thank you for this set of presets, Iāve been waiting for something like to this finally move away from the Hue Bridge and utilise dynamic scenes
A couple of questions which I donāt know if the integration caters for or not right now?
If you have multiple light entities running a dynamic scene, there doesnāt seem to be a way to control the individual brightness per light right now. Is that correct?
e.g. x4 lights added to a dynamic scene, set up via an automation. Service call toggles the dynamic scene, but only a master brightness level for all lights in that scene?
Is there functionality to fade in the start of the dynamic scene or not? I can only use an automation to fade out the dynamic scene right now, using a time based toggle service to set the brightness to 0 over xxx number of seconds via a transition
Keep up the good work, and hopefully someone can answer the above when possible