-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request]: Support effect / effect_list in groups exposed to Home Assistant #13438
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
not stale |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
not stale! |
not stale but closed! implemented 😄 Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
This is working well for me. I even have a group of Hue and non-Hue bulbs that don't support effects, and I can send an effect to the group and if the bulb supports it, it executes. Thank you! |
Is your feature request related to a problem? Please describe
I noticed that I was unable to trigger effects like "okay" and "blink" on my Philips Hue bulbs that are in a group. Targeting individual bulbs worked fine, and sending an effect to a group over MQTT worked as well.
The hint I was missing is that Home Assistant wasn't showing effects in the entity card to control the group:
When I manually added
effect
andeffect_list
to the device configuration topic, it showed up in the UI and effects worked as expected.Describe the solution you'd like
I think groups should be exposed to Home Assistant with the union of the capabilities of their underlying bulbs. I believe this is the behaviour for attributes like colour and temperature.
Describe alternatives you've considered
It looks like the topic has already reverted and I don't see a way to ensure it stays configured in the long term.
Additional context
Here's a working topic:
The text was updated successfully, but these errors were encountered: