How to expose action_group for Tint remoteMLI-404011/MLI-404049?

[duckbert]

My recently purchased tint remote work nicely with ZHA except for the action_group which defines which light group is controlled by the remote. I was hoping to see the action group exposed as a parameter when an event is fired but it seems this is not (yet) implemented in the quirks. Unfortunately, I have no experience with quirks.
Can anyone tell me if it is even possible to create a custom quirk in order to expose additional parameters and maybe even provide me with some direction how to achieve that? For Zigbee2MQTT it seems to be possible. https://www.zigbee2mqtt.io/devices/MLI-404011_MLI-404049.html

[MattWestb]

Pleas post diagnostic / signature for the device so can see how the end points is configurated.

I think the device is default (after being resetted) is using group ID 16388/16389/16390 as action groups.
Try making this groups in ZHA configure - groups and adding at least 2 lights to them and then restart HA so its automatically adding the coordinator in them.
Then testing if you is getting events from the "action groups" in the log / device card log.

If the device is well behaving it shall being possible binding one group you self have made by from the device card - three dots . . . and manage Zigbee device and on the bindings tab. Select your self made group and adding the cluster you like to bind (need logs and device endpoints config for knowing witch is needed).
The device is automatically assigning the other 3 groups with ID of your self made bonded group + 1-3 as ID of the action groups if i have understanding Z2M right.

[duckbert]

Hi,
Thank you for your help. Please find the signature of the remote below. I am actually not trying to bin a light-group or multiple light groups directly with the remote but was rather hoping that the action_group is exposed to HA so that I can use it for my automation logic. It seems to be possible for Z2M but I am not considering migrating to Z2M because I am very happy with ZHA.
{
"node_descriptor": {
"logical_type": 2,
"complex_descriptor_available": 0,
"user_descriptor_available": 0,
"reserved": 0,
"aps_flags": 0,
"frequency_band": 8,
"mac_capability_flags": 128,
"manufacturer_code": 4635,
"maximum_buffer_size": 127,
"maximum_incoming_transfer_size": 100,
"server_mask": 11264,
"maximum_outgoing_transfer_size": 100,
"descriptor_capability_field": 0
},
"endpoints": {
"1": {
"profile_id": "0x0104",
"device_type": "0x0800",
"input_clusters": [
"0x0000",
"0x0003",
"0x1000"
],
"output_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0008",
"0x0019",
"0x0300",
"0x1000"
]
}
},
"manufacturer": "MLI",
"model": "ZBT-Remote-ALL-RGBW",
"class": "zhaquirks.mli.tint.TintRemote"
}

This is is an example of the zha_event for the power button:

event_type: zha_event
data:
device_ieee: 00:15:8d:00:03:8c:2e:1c
device_id: 82d704ba9d002bdae5838413459669ff
unique_id: 00:15:8d:00:03:8c:2e:1c:1:0x0006
endpoint_id: 1
cluster_id: 6
command: "on"
args: []
params: {}
origin: LOCAL
time_fired: "2025-06-15T18:17:03.738095+00:00"
context:
id: 01JXTCYAZTFMY1FYCWQ94CD8K3
parent_id: null
user_id: null

[MattWestb]

OK i see they was doing one quirk for it 2021 #1074 for getting the scene function working but nit mush more information.

One more question with coordinator type is you using ?
IT is listening to all broadcasts = all groups and EZSP must being configurated for getting events from them and also need 2 devices for getting it working (the coordinator is added as event listener).

So if TI the Default tint action groups (16388/16389/16390) shall working out of the box and dont need bindings and new groups and with other coordinator you must do Zigbee groups for the remote (default or new one as Z2M is writing) or the coordinator is not getting the commands the remotes is sending.

Ping @TheJulianJES Do you have some experience of Müller remotes or how to getting the commands from the default or new groups to ZHA events ??
The quirk looks only translating attributes sent and piping them to one virtual scene cluster and nothing with group handling.

Also can ZHA tagging commands with the group ID so can being used in automatons (light commands set to different groups but from the same EP / Cluster) ?

PS: I was hoping to see the action group exposed as a parameter when an event
This is not possible then the group buttons is changing where / group the commands is sent to (the commands from the other buttons) and is not sending "group button X pressed" then pressing them.

[duckbert]

Thank you again for looking into this my coordinator is a Deconz conbee II. Sorry, I am not sure what you mean with: "_getting it working (the coordinator is added as event listener)."
I agree the group button is not firing an event by itself. That is okay. It would however be helpful if the other buttons, e.g. on/off, would list the active_group as an attribute.

[duckbert]

I found some additional information which might be helpful. I just don't know how to translate to ZHA

The addresses for the pre-configured light groups are: 0x4004, 0x4005, 0x4006
On Tasmota you can listen to the addresses by: backlog zblisten1 0x4004; zblisten2 0x04005; zblisten3 0x4006
With Zigbee2MQTT the Action group (numeric) is exposed.
Value can be found in the published state on the action_group property

[MattWestb]

Yes i was writing that for some post ago.
Hex / decimal:
0x4004 = 16388
0x4005 = 16389
0x4006 = 16290

In ZHA you shall having one default in the system like this:
Group information, Name: Default Lightlink Group. Group Id: 0x0000.
So only adding your customer groups and ZHA (with the hex group number) is adding the coordinator to them on the net restart if you have at least 2 devices in the group and the coordinator is getting all events being sent to the groups.