When a message is sent to a specific ZigBee group, does the HUB (coordinator) also receive this message?
Edit.: After searching and learning a little bit, it seems that when a groupcast message is sent to a group, only the devices that are bound to the group handle the messages. So, i think that the HUB (coordinator) will only handle the message (and show it in the logcat) if is bound to the specific group. THAT’S CORRECT?
So, i saw that:
I´m interested in this part: “Allow drivers to add the hub to group id 0x0000 that may fix some Zigbee buttons”
How this can be made and how can i check if the hub is in the 0x0000 group?
Are there any impact in the zigbee network traffic when adding de hub to a group (let´s use the 0x0000 as example) that we need to be cautious?
Probably just a general increase in the number of messages being sent around the network. Problems can arise if zigbee networks get too congested, so the same general warning applies there.
Are there any impact in the functioning of another drivers?
For adding the hub itself to a new group? I can’t think of one or how it might happen, but I’ve been known to be wrong.
I wasn´t able to find a similar remove hub from group command. What if we need to remove the hub from a group or change to another group ID?
This is by design so that we don’t allow one device to interfere with the functioning of another. If a device relies on the hub being a part of the group for functionality, then if any driver can remove the hub from any group, any driver could break that device.
Do we even need to take account of some “cleaning” procedure and remove the hub from group (like when removing device or changing his driver)?
Not possible at the moment, so no nothing you can/should do, but we did discover a bug a while back (more info here) such that the hub, over its lifetime, is limited to joining 32 groups. You can factory reset the hub to reset this number, but beyond that once you hit the limit it’s non-recoverable. We’re currently reworking a lot around how we work with groups, so hopefully in the future we have a better answer here.
In summary, for the most part, we try to limit how much you can interfere with other devices with how we handle groups, but you can get into a situation where, if you use too many, fresh installs of devices that need groups to function may not work.
Thanks for all the information @nayelyz and @steven.green , this clarifies a lot of things.
This is great news! A default way to manage zigbee groups for all devices will be awesome.
If i can ask one more question, smartthings platform supports group binding? So you don’t need to add a controller device (let’s use a remote button as example) to group(s), you just bind specific clusters of the device to groups, so the device can send messages of that cluster to all bound groups but messages of other not bound clusters continue to be sent to the coordinator?
