-
-
Notifications
You must be signed in to change notification settings - Fork 50
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] Disable exposing groups #479
Comments
It appears that this issue did not have an update in quite some time. Please check if you can provide any additional information to help resolve this issue. If there isn't any activity in the next two weeks, this issue will be closed automatically. Thank you for your contributions! |
With regards to "disable exposing groups by default": I think for this, the easiest would be to add an additional configuration item where you can put in all the IDs or friendly names of the groups you do wish to expose. Can you elaborate on "be able to expose them by their group id instead of the friendly name (friendly name accept spaces and non English letters)"? |
That sounds like an nice way to make it work. The idea of using the id instead of the friendly name is, 1: you avoid troubles with misspelling and 2: if you rename the group, you don't have to update the config, as long as the group id is the same. |
But you can already use the group ID in the plugin configuration, so no change needed with regard to this? |
I was only thinking about the groups. if it could support both it would be nice too 😁 Just thought it would be easier to maintain on a daily basis, if one used the group id. So if I one day would like to expose group 17, I just put in that id, and not "Basement Gaming Room Second Row Spot" 😀 😀 |
I agree. That's why for the current configuration options, you can already use both. I think I'll be able to look at this request in more detail in the coming weeks. I'll keep you posted. |
Please use the template and fill in all the data requested below!
Problem description
Since exposing groups by default, people using IKEA's old firmware for buttons are experiencing all bulbs, blinds, etc exposed twice.
In the latest firmware for IKEA buttons, they have removed group cast. The old way of controlling lights, was to add bulbs to an group and then bind the button to the group. That way you avoided the infamous "popcorn effect".
The downside of this nice feature, was that even if you would control just one bulb, it has to be in an group. This way you end up with the bulb itself and also an group for that same one bulb.
It could be fixed just by updating the firmware, but that would kill this nice feature the firmware have.
The good thing about the old firmware is that the group cast don't need the controller to be online to function, so even if the controller crash, you can still control all your light, blinds, etc.
Suggested solution
Disable exposing groups by default, and be able to expose them by their group id instead of the friendly name (friendly name accept spaces and non English letters)
Describe alternatives you've considered
Downgrading to an release prior to group exposure was default.
Additional context
Are you willing to contribute to this feature?
Yes
The text was updated successfully, but these errors were encountered: