100% agree with you. Every other hub device that I’ve dealt with has taken that approach and yeah, it’s not a good way to deal with it. Would it be possible to have the end user choose the group type? Perhaps something as simple as a light group and a generic group? The light group would mimic the light group integration and the generic group could just be a simple switch (binary) grouping. Given that (at least imho) most users are going to group basically two types of devices (lights and switches/dimmers), giving the option to be able to select a group type would be a benefit.
Ohhhh, I like that idea. Kind of like how button remotes work today when selecting “Device”?
To be fair, that probably covers 90% of use cases But I agree, I can see Shades/Covers, Switches and Thermostats be groupable as well. Another dilemma: how do you represent the state of the group? e.g. with a group of three lights,
light #1 is off
light #2 is on
light #3 is offline
What the “state” of the group should be? It almost like group should be “stateless” AKA a “remote”, only in this case HA itself being a “remote” Which I think we probably could do with a custom lovelace card which just calls zha.issue_zigbee_group_command service
When I add a remote with multiple endpoints, it seems to add duplicate devices, one for each endpoint. Is there a way to specify which endpoint of the device to bind to the group?
Has anyone got the King of Fans zigbee controllers fully working? Mine add and look like they will work but are stuck in a state showing incorrect status and command and status don’t work on light on fan.
I have three of these and they work well, they have terrible range though. I almost gave up on the first one for the same issues, then i added a router in the room and it solved my issues.
Thanks, I had them into Hassio via Wink and have moved everything off Wink except these. Tried a remote deConz with no success. Looking again, one controller is working properly via ZHA, it is just one that is giving problems. I may have a spare.
Dug out what I thought was a spare, but it is toast. Smells of smoke and stays invisible. I bought all three of the controllers at once and have one in service that reports it is a Hampton Bay controller and one that ZHA discovers that reports its a Home Decorators controller. Wink had entries for both. I have moved everything off Wink and also a Hue hub for good measure, but can’t get the home Decorators version to complete pairing. I’m using the Integration which does not have the option on quirks which may help. Really don’t want to remove the integration and try the config.yaml method but am out of choices.
I’ll grab logs tomorrow. Adding the device has a line where it is skipping initialization of existing device. I did remove device and then restarted hassio. I added device three times and got progressively more returns but it now doesn’t finish and expose a device. It’s like the permit is not long enough
Tried setting up a new zigbee group, and the UI never reported success (just spinning progress circle) and then the entities were added to my single existing group.
I saw someone else report the same thing, but now I can’t find the issue.
Can anyone else replicate the issue? Running 0.104.2
Make a new Zigbee group (so you have at least one)
Create a second group (see if UI reports success)
Check if second group was created
Check first zigbee group to see if it had the entities added from the second group
Is this a question on making a “Quirk” to get this device to work ? I’m not entirely new to Python, but I need possibly to learn how this i should be set up i Home Assitant
just in case this affects anyone else this bug can be reproduced if you delete a group with a lower ID number then an existing group. It will be fixed in 105.
No that isn’t what it was supposed to show as. It’s a button - not a switch. It has since been fixed with an applied quirk. It now shows taps - double taps - triple taps. I have since deleted it anyway as ST sensors are trash with batteries.
But I agree, I can see Shades/Covers, Switches and Thermostats be groupable as well. Another dilemma: how do you represent the state of the group? e.g. with a group of three lights,
