I’ll have to get home to check, but I’m pretty sure you need the switch in the group for it to work properly…
I was having a similar issue. Updated to the newest Z2M (1.28.1) a few days ago and disabled relay click and that seemed to get it working, also make sure you have button delay to something other than 0. Still in the middle of testing it and verifying that it works correctly though.
I also have the switch as part of light group and had that working, but after playing with the bindings to solve the same issue I couldn’t get it to work so I binded the individual lights to the switch.
After a tad more testing, I believe this is the case. Tested with some Hue bulbs and they would not respond to commands if the switch was bound to a group that contained the bulbs but not the switch, and did respond when the switch was included.
Unfortunately, when included in a group with the Hue bulbs, multi-press actions still did not seem to work.
What bindings do you have set up? The below works for me to have multi-tap actions in the same sort of setup:
2 Likes
At present, just LevelCtrl with the lights group (which is what’s show in the setup video):
However, I’ve tried adding OnOff as well. That seemed to generate some error notifications with the Juno lights, but otherwise didn’t seem to change function.
Edit: I’ll try this setup with my Hue bulbs and see how that goes.
Edit 2: It seemed to work briefly. For a few minutes, actions seemed to come through. However, after that they didn’t seem to register. I’ve had that happen before, but haven’t been able to isolate it.
It may be worth noting that the switches seem to create a lot of traffic on the network (image related) compared to other devices. Not sure if possibly that’s an issue or not.
It seemed some of this traffic was electrical power/energy related. I’ve adjusted some of the power and energy report settings, which seemed to help some, but also needed to increase the Min rep interval for some of the items under the Reporting tab to help reduce this, but there’s still quite a lot.
Edit 3: May also be worth noting that I use Adaptive Lighting, which includes some long brightness/color transitions for lights every few minutes. The lights groups that the switch is included in is controlled by this. Could the long transition times possibly be interfering? Tried disabling it for these lights, but didn’t seem to immediately make a difference.
Edit 4: One other observation - when bound/grouped, even the up_single and down_single actions don’t come through (even though the bound lights do turn on/off and dim properly).
I have noticed an issue where the tap events stop registering if the switch hasn’t been interacted with in ~90 seconds. Not sure if something is going to sleep inside the switch or it’s some sort of signal issue or what. This thread seems like a similar issue to this one: Blue 2-1 "Wake" needed? - #29 by harjms
Could you provide the IEEE (first 6 digits) address of the device?
Assuming you’re asking me, 94:DE:B8.
Other than the tap actions in a Z2M group/binding, it’s been working great using the most recent Z2M version.
1 Like
You’re switch is part of the batch that has poor reception. That could be the cause. I have 17 switches installed and 3 of them won’t join. However the scenes and rules have been working fine.
Oh, have more potential IEEEs been identified? Last I heard it was IEEEs beginning with 38:5B:44 and 94:34:69 that seemed most likely affected.
I will say that in all other ways the switch seems quite responsive so far and has a LQI of 100+, just doesn’t seem to be transmitting “actions” when in a Z2M group/binding.
I believe 94:DE:B8 is fine, I have one from that that’s working perfectly for me.
1 Like
Those are currently the only ones that are affected. I believe the 04:0D:84 is a good batch.
1 Like
That’s a possibility, given the handful of times I noticed that actions seemed to register for a minute or two after grouping/binding. That said, it sounds like my switch is behaving a bit different in that it doesn’t seem to have a “wake” issue for actions when it’s not grouped and when it is grouped, actions don’t seem to “wake up” if I start interacting with the switch again. When it’s grouped/bound, I can attempt 5+ actions in the span of a minute and none seem to come through.
I am a novice when it comes to ZigBee groups/binding, but I do wonder if perhaps it’s an issue with the “action” message being sent to the Sonoff coordinator. When not grouped/bound and actions are properly received, I noticed the action data is part of a message in the “*/action” topic separate from the normal message used to report state changes or light controls. The “action” portion of the larger message does change, but it’s a change from null to “” rather than the action.
When grouped/bound, this separate smaller message with the action data does not seem to come through, even if the larger message does. Is it possible that when grouped/bound, something in the routing prevents this message from reaching the coordinator? I’m not knowledgeable enough about how messages are routed to know if that’s a possibility or not.
hey all,
I have a bunch blue switches in the listed out ieee’s that seem to be affected but I’ve got one that is 04:0d:84.
Using ZHA I’ve gotten it to pair via a sonoff hub. However I cannot get a single or group of lights to bind to the switch. When I click bind I get an indefinite scroll wheel.
Would this be related at all to the issues at hand or something different? the home assistant logs aren’t very fruitful on logging any issues for this.
thanks
It’s actually working in that case 
Bind just currently spins, should be fixed in a future update with ZHA (in HA).
1 Like
Got it! sorry if i missed that posted else where in the forms… appreciate your time.
No worries at all, it’s definitely a valid question!
1 Like
I tested out a setup similar to yours here with a blue switch bound to another blue switch in a three way setup and noticed a similar result.
The double tap up event does register but maybe only one out of every 10 or 20 attempts. As well, turning the switch on with a single tap doesn’t do anything to improve the situation which is contrary to the behavior I see on another switch I have with a similar setup but which is not part of a binding.
My switches are all part of the batch that have known signal issues so maybe that’s part of the issue. The odd thing is that commands sent from HA or an MQTT client work pretty flawlessly.
I have one grouped with 10 smart bulbs so will be following this thread. It’s IEE 0x943469 and the LQI in z2m will go from like 40 to 0. It still interacts with the smart bulbs. Interestingly I can dim it while it says LQI 0 and I see the LQI go from 40ish back to 0 in the z2m devices list. Almost right after I let go it says 0 again.
I cant imagine this is good for my mesh network because it still acts like a router.
Hey there. quick follow up…switched over zigbee2mqtt. a remote (different circuit) smart bulb can bind successfully to the switch but turning this switch state on/off does nothing to that smart bulb. The switch is in smart bulb mode.
any thoughts on debugging this? thank you!
edit: same result with bulbs on the same circuit as the switch. obviously works fine in this scenario if the switch is not in smart bulb mode.