I don’t know if anything has changed, but I just set up groups for the first time earlier today. Here’s an excerpt from my groups.yaml that worked for me:
This should work, just tested it with ‘light.toggle’.
Is it anything special you are doing? Do the lights have different features and are you using an unsupported feature for one of the lights?
@Jae_Oh Be aware of the fact that you are combining switches and lights. When you toggle a light, the switches will give an error in the log and will not be toggled. If you want to have a group with bothm for example to see if a switch ir light is turned on, you could create a 3rd group that contains the other two groups.
I get it, but I think that’s how it is designed.
If you toggle the group, all lights are toggled. If you toggle an individual light, you (indeed) need to build an automation if you want the others to follow.
You can do this with one automation by the way. Have the lights as a trigger and use ‘trigger.to_state.state’ as a choose condition to turn the lights off or on.
Its weired… A few days ago it was working different… when I toggled one light, the other toggled together…
anyway… the solution is the automation!!!
Thank you guys!!
I haven’t noticed anything going wrong. I haven’t checked the logs, but everything works as intended. Groups are toggled on and off and everything is happening as I expect it to. If you’re saying there might be issues with HA properly deciding what the state of the group is, that could be true, but if so it doesn’t seem to be affecting the functionality I want from it.
Good to read, maybe they made it more robust in the later versions. I don’t keep track of earlier experiences cause the behavior (toggle light doesn’t toggle a switch in the same group and visa versa) made sense and is no bug.