Can´t add Hue wall switch to Zigbee group

[thmnxo4]

What happened?

Adding switch to group fails

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.33.2

Adapter firmware version

6.10.3.0 build 297

Adapter

EZSP v8

Debug log

Error 2023-12-01 07:38:14Failed to add from group (Command 0x001788010b007ad4/1 genGroups.add({"groupid":1,"groupname":""}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 34097 - 1 - 134 - 4 - 0 after 10000ms))

[chrisvandiemen]

Experiencing the same problem.

zigbee2mqtt version: 1.34.0 adapter: SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P adapter firmware version: zstack 20210708 debug log: Failed to add from group (Command 0x001788010d9fb29c/1 genGroups.add({"groupid":1,"groupname":""}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 22193 - 1 - 214 - 4 - 0 after 10000ms))

[jamesonuk]

Have you toggle the switch before trying to add it to the group? You need to wake it up before trying to add it to a group (I normally press it a few times whilst Z2M is trying to send the join group command just to make sure)

[chrisvandiemen]

Thanks for the help!

Yep, did try that. Toggling before, during or after the add command doesn’t help. I did pair the Hue Wall via a router. Not sure if that is relevant but is worth trying pairing directly to the coordinator.

Op do 14 dec 2023 om 12:08 schreef jameson_uk @.***>

Have you toggle the switch before trying to add it to the group? You need to wake it up before trying to add it to a group (I normally press it a few times whilst Z2M is trying to send the join group command just to make sure)

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/19941#issuecomment-1855646441, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGK6WCOII2RUYLIV7NKCRE3YJLM2LAVCNFSM6AAAAABACLTT66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGY2DMNBUGE . You are receiving this because you commented.Message ID: @.***>

[thmnxo4]

Yes, I did so

jameson_uk @.***> schrieb am Do., 14. Dez. 2023, 12:08:

Have you toggle the switch before trying to add it to the group? You need to wake it up before trying to add it to a group (I normally press it a few times whilst Z2M is trying to send the join group command just to make sure)

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/19941#issuecomment-1855646441, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASJF77M4DFKSZO4GVWDSIFDYJLM2LAVCNFSM6AAAAABACLTT66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGY2DMNBUGE . You are receiving this because you authored the thread.Message ID: @.***>

[snurre0]

I'm having the same issue with my wall switch. I'm following the guide for directly controlling zigbee groups from here: https://www.zigbee2mqtt.io/devices/929003017102.html

But step 2 fails when trying to add it to a group, and I get the same error as above: Error 2024-01-13 18:23:09Failed to add from group (Command 0x001788010b031100/1 genGroups.add({"groupid":2,"groupname":""}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 15042 - 1 - 114 - 4 - 0 after 10000ms))

The thing is that after continuing with the binding, I get the wallswitch to control my lights, but in a super weird way. When I press my switch really quickly it works, but holding it for more than a split second makes the light go wither on or off again, depending on if I turned them off or on. Holding the button will dim them fully either way, but releasing the button makes them turn either on or off, depending on the state they're coming from.

Anyone else experiencing this with the wall switch? Is this related to the issue where I can't add the wallswitch to the group?

[thmnxo4]

Hi, will this be fixed in the near future?

[thmnxo4]

Seems to be fixed. Tried again with 1.37 and group binding worked.

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days

[mwerder]

Got the same issue, following the guide but cannot add the module to the group

[SkyhawkXava]

Same here. Can't add to a group and binding doesn't work.

z2m version: 1.42.0-2

zigbee-model: RDM004 firmware-Date: 20220510 firmware-Version: 2.60.16

Btw: This device is not listet in the ota section.

[SkyhawkXava]

I have now found a solution: First, the Cluster “Groups” must be bound to the coordinator. After that, the required steps can be carried out.

But: Dimming (hold button) is not working. (Push Button is activated.)

[fkuiper]

I've got the same issue with my switches. I create a zigee group and adding lights works perfectly, adding the switch will give:

error: z2m: Failed to add from group (ZCL command 0x001788010cc574da/1 genGroups.add({"groupid":4,"groupname":""}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 42216 - 1 - 178 - 4 - 0 after 10000ms))

z2m version: 1.42.0 coordinator: slzb-06p7 running firmware: 20240716 (radio) v2.3.6 (core) switch firmware: 1.0.5

Triggering the switch makes no difference. I've added this same switch and light to a group successfully on my previous coordinator (a Conbee II USB dongle).

[MfCrizz]

I have the same problem with my switches. I cannot add them to groups. However, I am wondering if this is necessary because if I skip this step in the instructions, I can still bind the on/off cluster of the group to the switch.

The switch can then also turn the group on and off, but then I have the problem that if I control the group in a different way than with the switch (e.g. sending a mqtt message), I have to press the switch twice to control the group again.

z2m version: 1.42.0 Coordinator type: zStack3x0 Coordinator revision: 20240710

zigbee-model: RDM004 firmware-Date: 20220510 firmware-Version: 2.60.16

[hatti75]

Same problem here.

[fkuiper]

After a lot of try-and-error I found out that:

• You do need to add the switch to the group! Trigger the switch right after you added it to the group, but it will still give a time-out error. You can ignore this error and you won't see it in the UI but some how something is changed somewhere (sorry, I don't have any idea what or where).
• After this you need to unbind the OnOff Cluster from the coordinator. Of course you need to trigger the switch right after you click unbind so it wakes up.
• Now you can bind the OnOff Cluster to the group (again you need to trigger to wake up the switch).

For me this worked like a charm. My groups now toggle on and off without any automation in home assistant; it works for both lights as well as smart plugs; and it even works if zigbee2mqtt or home assistant is down (this will greatly improve your wife acceptance factor!). If your lights support dimming, you can also unbind and bind manuSpecificPhilips together with OnOff so the lights will dimm up or down if you hold a puls switch for longer than a second.

If you still whish to trigger some automation when you switch the lights on or off you can do on of two things:

1. Use the device as tirgger and make sure you select the device that is coupled to the group. I noticed the light does not always get triggered somehow (it does switch on or off thou).
2. You can rebind the OnOff Cluster to the coordinator (make sure this is the last step!) and trigger on the switch device again... Make sure the device action is 'toggle'. I had to do this in the yml-code because home assistant UI didn't detect the change in actions correctly.

IMO the time-out after you add the switch to the group and it not showing as a group member is a bug in zigbee2mqtt and is related to the zStack. I didn't have these issues when I used my Conbee II stick and somehow in the zigbee devices themself it does get registered correctly if you follow these steps.

[hatti75]

The binding works indeed. But if the bound lamp is triggered by something else, I have to push the switch twice.

[SkyhawkXava]

fkuiper wrote:

After a lot of try-and-error I found out that:

• You do need to add the switch to the group! Trigger the switch right after you added it to the group, but it will still give a time-out error. You can ignore this error and you won't see it in the UI but some how something is changed somewhere (sorry, I don't have any idea what or where).
• After this you need to unbind the OnOff Cluster from the coordinator. Of course you need to trigger the switch right after you click unbind so it wakes up.
• Now you can bind the OnOff Cluster to the group (again you need to trigger to wake up the switch).

For me this worked like a charm. My groups now toggle on and off without any automation in home assistant; it works for both lights as well as smart plugs; and it even works if zigbee2mqtt or home assistant is down (this will greatly improve your wife acceptance factor!). If your lights support dimming, you can also unbind and bind manuSpecificPhilips together with OnOff so the lights will dimm up or down if you hold a puls switch for longer than a second.

If you still whish to trigger some automation when you switch the lights on or off you can do on of two things:

1. Use the device as tirgger and make sure you select the device that is coupled to the group. I noticed the light does not always get triggered somehow (it does switch on or off thou).
2. You can rebind the OnOff Cluster to the coordinator (make sure this is the last step!) and trigger on the switch device again... Make sure the device action is 'toggle'. I had to do this in the yml-code because home assistant UI didn't detect the change in actions correctly.

IMO the time-out after you add the switch to the group and it not showing as a group member is a bug in zigbee2mqtt and is related to the zStack. I didn't have these issues when I used my Conbee II stick and somehow in the zigbee devices themself it does get registered correctly if you follow these steps.

@fkuiper: Which zigbee-model? RDM001 or RDM004?

[hatti75]

If have both, RDM001 and RDM004. Both don't work.

z2m version: 2.1.1 Coordinator type: zStack3x0 Coordinator revision: 20210708

zigbee-model 1: RDM004 firmware-Date: 20240618 firmware-Version: 2.77.35

zigbee-model 2: RDM001 firmware-Date: 20240618 firmware-Version: 2.77.35

[SkyhawkXava]

hatti75 wrote:

The binding works indeed. But if the bound lamp is triggered by something else, I have to push the switch twice.

The RDM001 and RDM004 behave differently, as far as I have been able to research:

RDM001:

• Group binding is possible.
• The switch sends a “toggle” command to the device.
• Dimming works on long press if the “Level Control” cluster has been bound to the group.

RDM004:

• Group binding is possible, but only if the “Groups” cluster has also been bound to the coordinator.
• The switch sends “on/off” commands to the device.
• Dimming does not work on long press, even if the “Level Control” cluster has been bound to the group.

Since the RDM004 version only sends “on/off” commands and not the “toggle” command, the behavior described by you, hatti75, is correct. The Hue wall switch internally stores the last status (on or off). If the group is switched by another switch, the Hue wall switch does not receive this information.

As a battery-powered switch, it quickly returns to standby mode after each activation, during which it no longer receives messages or actively listens. As a result, the last stored group status in the Hue wall switch may be outdated. This can lead to situations where, for example, the Hue wall switch sends an “on” command even though the group has already been turned on by another switch.

[fkuiper]

I have them both in my network and didn't notice any difference between them. In fact, I didn't know I've had two different versions up until now :)

I also use automations to switch on and off lights which I can also toggle using the switches. I've never noticed any odd behavior like needing to toggle my switches twice after an automation changed the state. I only modify via the groups, not an individual light btw, maybe that is something?

Do you use pulse or rocker switches? Mine are all pulse...

-------- Oorspronkelijk bericht -------- Op 23-02-2025 22:03, schreef SkyhawkXava :

fkuiper wrote:

After a lot of try-and-error I found out that:

• You do need to add the switch to the group! Trigger the switch right after you added it to the group, but it will still give a time-out error. You can ignore this error and you won't see it in the UI but some how something is changed somewhere (sorry, I don't have any idea what or where).
• After this you need to unbind the OnOff Cluster from the coordinator. Of course you need to trigger the switch right after you click unbind so it wakes up.
• Now you can bind the OnOff Cluster to the group (again you need to trigger to wake up the switch).

For me this worked like a charm. My groups now toggle on and off without any automation in home assistant; it works for both lights as well as smart plugs; and it even works if zigbee2mqtt or home assistant is down (this will greatly improve your wife acceptance factor!). If your lights support dimming, you can also unbind and bind manuSpecificPhilips together with OnOff so the lights will dimm up or down if you hold a puls switch for longer than a second.

If you still whish to trigger some automation when you switch the lights on or off you can do on of two things:

• Use the device as tirgger and make sure you select the device that is coupled to the group. I noticed the light does not always get triggered somehow (it does switch on or off thou).
• You can rebind the OnOff Cluster to the coordinator (make sure this is the last step!) and trigger on the switch device again... Make sure the device action is 'toggle'. I had to do this in the yml-code because home assistant UI didn't detect the change in actions correctly.

IMO the time-out after you add the switch to the group and it not showing as a group member is a bug in zigbee2mqtt and is related to the zStack. I didn't have these issues when I used my Conbee II stick and somehow in the zigbee devices themself it does get registered correctly if you follow these steps.

@.***(https://github.com/fkuiper): Which zigbee-model? RDM001 or RDM004?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[SkyhawkXava]SkyhawkXava left a comment (Koenkk/zigbee2mqtt#19941)

fkuiper wrote:

After a lot of try-and-error I found out that:

• You do need to add the switch to the group! Trigger the switch right after you added it to the group, but it will still give a time-out error. You can ignore this error and you won't see it in the UI but some how something is changed somewhere (sorry, I don't have any idea what or where).
• After this you need to unbind the OnOff Cluster from the coordinator. Of course you need to trigger the switch right after you click unbind so it wakes up.
• Now you can bind the OnOff Cluster to the group (again you need to trigger to wake up the switch).

For me this worked like a charm. My groups now toggle on and off without any automation in home assistant; it works for both lights as well as smart plugs; and it even works if zigbee2mqtt or home assistant is down (this will greatly improve your wife acceptance factor!). If your lights support dimming, you can also unbind and bind manuSpecificPhilips together with OnOff so the lights will dimm up or down if you hold a puls switch for longer than a second.

If you still whish to trigger some automation when you switch the lights on or off you can do on of two things:

• Use the device as tirgger and make sure you select the device that is coupled to the group. I noticed the light does not always get triggered somehow (it does switch on or off thou).
• You can rebind the OnOff Cluster to the coordinator (make sure this is the last step!) and trigger on the switch device again... Make sure the device action is 'toggle'. I had to do this in the yml-code because home assistant UI didn't detect the change in actions correctly.

IMO the time-out after you add the switch to the group and it not showing as a group member is a bug in zigbee2mqtt and is related to the zStack. I didn't have these issues when I used my Conbee II stick and somehow in the zigbee devices themself it does get registered correctly if you follow these steps.

@.***(https://github.com/fkuiper): Which zigbee-model? RDM001 or RDM004?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[SkyhawkXava]

I modify only via groups, as well. I use only push switches.

@fkuiper: On which firmware-date and -version are your RDM001- and RDM004- Switches?

[hatti75]

It doesn‘t work for me. I tried different bindings to the coordinator (with/without Groups cluster). I anyway get the error message when adding it to the group. I tried it at least 20 times. Binding to the group works, but both switches do not toogle. They send on/off commands to the bound group and so the command can be wrong if trigged by other sources.

z2m version: 2.1.1 Coordinator type: zStack3x0 Coordinator revision: 20210708

zigbee-model 1: RDM004 firmware-Date: 20240618 firmware-Version: 2.77.35

zigbee-model 2: RDM001 firmware-Date: 20240618 firmware-Version: 2.77.35

[fkuiper]

I've got two versions running:

RDM001 - 20210504 RDM004 - 20220510

I've never noticed any difference between them. As I said before: up until now I didn't even know they were different:).

Verzonden met Proton Mail Android

-------- Oorspronkelijk bericht -------- Op 23-02-2025 23:03, schreef SkyhawkXava :

I modify only via groups, as well. I use only push switches.

@.***(https://github.com/fkuiper): On which firmware-date and -version are your RDM001- and RDM004- Switches?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[SkyhawkXava]SkyhawkXava left a comment (Koenkk/zigbee2mqtt#19941)

I modify only via groups, as well. I use only push switches.

@.***(https://github.com/fkuiper): On which firmware-date and -version are your RDM001- and RDM004- Switches?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[Pferdebockwurst]

I can confirm the description at the zigbee2mqtt devices page works perfectly fine for two of my switches, which are both RDM001, on of them being on firmware 1.0.3 and one on 1.0.5. Will try my RDM004 later.

The response of my lamps is super snappy now. Great work @Koenkk. But maybe the error message, saying that adding the switch to a group was not successful, and the switch not showing up in the group as displayed in the GUI should indeed be fixed.

[hatti75]

Seems to be a problem with newer firmware... Mine are on the latest.

[fkuiper]

Hmm... maybe the never switch firmware has a bug in it. Mine is pretty old I see now. Apparently the OTA doesn't work on my switches... which could maybe be a good thing :)

-------- Oorspronkelijk bericht -------- Op 24-02-2025 19:01, schreef hatti75 :

It doesn‘t work for me. I tried different bindings to the coordinator (with/without Groups cluster). I anyway get the error message when adding it to the group. I tried it at least 20 times. Binding to the group works, but both switches do not toogle. They send on/off commands to the bound group and so the command can be wrong if trigged by other sources.

z2m version: 2.1.1 Coordinator type: zStack3x0 Coordinator revision: 20210708

zigbee-model 1: RDM004 firmware-Date: 20240618 firmware-Version: 2.77.35

zigbee-model 2: RDM001 firmware-Date: 20240618 firmware-Version: 2.77.35

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[hatti75]hatti75 left a comment (Koenkk/zigbee2mqtt#19941)

It doesn‘t work for me. I tried different bindings to the coordinator (with/without Groups cluster). I anyway get the error message when adding it to the group. I tried it at least 20 times. Binding to the group works, but both switches do not toogle. They send on/off commands to the bound group and so the command can be wrong if trigged by other sources.

z2m version: 2.1.1 Coordinator type: zStack3x0 Coordinator revision: 20210708

zigbee-model 1: RDM004 firmware-Date: 20240618 firmware-Version: 2.77.35

zigbee-model 2: RDM001 firmware-Date: 20240618 firmware-Version: 2.77.35

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

[Pferdebockwurst]

@Koenkk if you want to investigate this, I could send you one of these switches with a recent firmware. I am very interested in getting them to work when bound to a group too.

[Pferdebockwurst]

I have found this discussion and indeed the RDM004 is reported to behave very different. But is this really dependent on the new firmware?

[SkyhawkXava]

I do think it’s due to the newer firmware version. @hatti75 has the latest 2024 firmware version on both revisions and obviously, both revisions (RDM001 and RDM004) have the issues.

[Pferdebockwurst]

So then the RDM001 must have been manually updated by him. Because as far as I know the RDM001 has never been shipped with a new firmware 2.x.x. But where does this firmware file come from and how did he update?