Core: ZHA Zigbee groups naming

[MattWestb]

The problem

Zigbee Lightlink groups.

Zigbee LL devices is assigning one random group to itself then being reseted / paired.
ZHA is pulling the group ID from the device then pairing it and making one "No name group" for it.

(IKEAs motion sensor E1525 = Old LL)

That's good but if having more LL groups being done by ZHA its not easy knowing for what device they is being made (in this case the E1525).
It would being good having the group named after the device model / ZHA name so being easier to identifying it, and also missing the possibility to renaming it in ZHA level (in HA Entities it can being renamed but its only for displaying in HA and still not updating in for displaying in ZHA).
Also more controlling devices can being bounded to one group by user (also by ZHA as 0x0000 for default binding group for ZB3 devices) and changing its purposes and ned being renamed for working well with the user.

Default binding group.

I think its should not being possible deleting this one and its being good assigning one better name then ZHA is making it (then pairing the first groupe controlling device without LL groupe and having group cluster).

(the trash symbol is not in the screenshot but is upper right corner on the same line as large "No name group 0x0000")

Also I think from the system view its should not being possible deleting the coordinator from the 0x0000 groupe as it is used by the coordinator to catching broadcast messages in the network.

I don't know if it should being blocked to deleting the coordinator in LL-groups (its auto assigned then ZHA is kreating them) and if then its should also being auto assigned to new user made groups i think (without knowing).

Greetings to the developers for making one great system and waiting for our beloved Bellows 2 to making the next large move from dev to master branch.

Environment

• Home Assistant Core release with the issue: Home Assistant 0.114.4 + bellows dev
• Last working Home Assistant Core release (if known): Probably never
• Operating environment (OS/Container/Supervised/Core): Docker on windows 10 homeassistant/home-assistant:stable, HW: EZSP v8 on "IKEA Billy EZSP"
• Integration causing this issue: ZHA
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

[dmulcahey]

This is great feedback. I'll see what we can do here but I am not too sure what is possible. We don't create these groups we just add the coordinator to them. I'm not sure what the devices will do if we modify the groups that they transmit to. Definitely worth trying it all out and seeing what is possible. Thanks for the report.

[MattWestb]

Thanks for feedback !!
The possibility of renaming groups (also user made ones) should not making any thing with the NCP, the "group id" is the index used for the system and the name is only "internal" for ZHA and HA for displaying.
The important things for the NCP like coordinator bonded to it should being read only so the user cant messing with it.
I'm very sure @Adminiuga have strictly thinking what shall or not being ;-))
Keep coding strong devs !!!

[Adminiuga]

@dmulcahey I think ability to rename the groups for starters should do it.
For automatically created ZLL groups, like in https://github.com/zigpy/zha-device-handlers/blob/408b14accfcb4dd4c447fcf24f63cf9847b790a5/zhaquirks/ikea/__init__.py#L33 should we try something like status = await coordinator.add_to_group(group_id, name=f"{str(self.endpoint.device.ieee) - {self.endpoint.manufacturer} {self.endpoint.model}") ?

[dmulcahey]

That’s along the lines of what I was gonna try. Will try it and see how it works.

[MattWestb]

For those that dont like waiting for implanting something in ZHA GUI its possible patching the zigbee.db.
First stop HA and going in the config folder and open the zigbee.db with one SQLite editor.
In table groups is all the groups stored with "group_id" and "name".
Changing the name off the groupe name and saving it and exiting.
Start HA and your groupes is renamed ;-))