New paired/installed Z2M Push Button (Loginovo ZG-101ZL) switches Light without Automation

[temmyn (on a steep learning curve)]

Hi,

I added the mentioned Push Button in HA over Zigbee2MQTT addon, which worked fine (I have about 10 of those Push Buttons in my mesh).

In the automations I usually set how the Push Buttons should behave/which device to switch on/off.

On the newly added push button the single push action is already triggering one switch/light in my installation, which I haven’t defined in my automations.
I cannot figure out why and where I can see/change this behaviour.

Any hint would be highly appreaciated, thanks.

Tesa

[temmyn (on a steep learning curve)]

So it’s not so obvious it seems?

[LiQuid_cOOled (Not really a...)]

Did you check your Logbook to see what triggered the one switch/light in your installation?

[temmyn (on a steep learning curve)]

Yes I did. Unfortunately he Logbook only shows that the device has been turned on or of without any informatione regarding automations (which is the case when device are beeing actually turned on/off via an automation). So I assume the automations can be excluded in the troubleshooting?

What else can I do/check?

[francisp (Francis)]

See if it has bound itself to the light. Binding is a feature of Zigbee that allows a button (or other device) to control a light (or other device) without HA (or another coordinator/controller) being present.

[temmyn (on a steep learning curve)]

I had hope this is the issue, but unfortunately not.
There are no bindings for this device.

I have bound another one yesterday an it doesn’t trigger any device unwanted.

Even when I remove this “trouble” push button device and repair it with Z2M, it behaves in the same way (meaning it will switch the light when pushing the button). So it doesn’t seem to be a setting of the push button I would assume.

[francisp (Francis)]

Did you check the Zigbee2MQTT logs ?

[LiQuid_cOOled (Not really a...)]

What happens if you remove the non-trouble push button? Does the light still trigger with the trouble push button?

[temmyn (on a steep learning curve)]

Yes, but honestly I don’t know what to look for and the informations I get are pretty confusion to me. I will take a look later when I’m home again and If I spot something suspicious.

[temmyn (on a steep learning curve)]

Yes, it still triggers the light.

I have about 10 of those push buttons installed and 2 of them trigger light’s I haven’t defined in automations or in Z2M bindings.

[LiQuid_cOOled (Not really a...)]

I have you tried setting a different mode via 3 clicks?

Operation mode

You can switch between the “command” and “event” operation mode with a triple click

Command mode enables on/off mode : single click : on double click : off long press (>5s) and release : brightness_move_to_level

You can then use OnOff and LevelCtrl binding in this mode

Event mode enables click : single/double/hold

I think your are bound at OnOff and LevelCtrl because the button is in command mode

Your other button shows no clusters

Operation mode (enum)

Operation mode: “command” - for group control, “event” - for clicks.

Check the Expose tab to see you current mode

[temmyn (on a steep learning curve)]

Very interesting! I think we might be on the right route here.

Indeed on those two buttons which show the unwanted behaviour there is not
an operation mode explicitly set (command or event). See screenshot.

However, the other buttons which work as expected, they have the event operation mode explicitly set (black background).

Now when trying to change the operation mode over z2m I get an error:

2025-06-04 12:40:24z2m: Publish 'set' 'operation_mode' to 'Kaffeebar Monsi Push Button ' failed: 'Error: ZCL command 0xa4c138769fa756e8/1 genOnOff.write({"tuyaOperationMode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 53991 - 1 - 132 - 6 - 4 after 10000ms)'

Not sure what this means but apparently the mode change is unsucessful and the operation mode remains as shown in the screenshot. Any ideas why the operation mode fails and if there is anything I can do about it?

I have you tried setting a different mode via 3 clicks?

Do you mean by tapping the button 3 times in a row? I have tried this but nothing has changed.

[LiQuid_cOOled (Not really a...)]

Click on the Expose tab and click the button. You’ll see Action change real time. If nothing happens the binds most likely need adjusted.

For example, My Hue Dial removes the brightness when I Unbound the LevelCtrl

[temmyn (on a steep learning curve)]

@LiQuid_cOOled

Click on the Expose tab and click the button. You’ll see Action change real time.

Nothing happens or rather the prior posted z2m error message pops up after 10 seconds.

If nothing happens the binds most likely need adjusted.

In which way and why is this device different than the others? All report as " ZG-101ZL" model.

[LiQuid_cOOled (Not really a...)]

Not sure, all I know is this has been a issue for a while. I couldn’t even find a online vendor to purchase one other than direct from China. Expected delivery August

I’d at least try a hard reset, add the button back to Z2M and try the 3 click option one more time.

EDIT: Its actually a TUYA device rebranded.

[temmyn (on a steep learning curve)]

Thanks, will try a hard reset and report back.

[temmyn (on a steep learning curve)]

OK guys, I figured it out. Damn this is a hard to find error …

First of all I got suspicious when the push button still was turning the light on/off without beeing registered/paired with Z2M … even after a hard reset the problem remained!
So I don’t think it’s a Z2M issue, but cannot tell for sure.

However, it has something to do with the Wall Light switch which is a Aqara E1 (Model: QBKG41LM)!
Both rockers are operating in relais mode (not sure if this is relevant). For some reason the push button an the left rocker of the Aqara Wall switch get coupled/paired. I don’t understand why … is this a bug or maybe even a feature?

In the end I made a hard reset of the push button far away from the Aqara E1 and voila, the push button doesn’t trigger the light controlled by the Aqara E1 anymore.

With the other push button there is exactly the same scenario, again this type of push button in combination with the Aquara E1 Wall switch. Could solve the unwanted behvaiour here as well with the described procedure.

Thanks everyone for getting involved

[LiQuid_cOOled (Not really a...)]

@temmyn

In the end I made a hard reset of the push button far away from the Aqara E1 and voila, the push button doesn’t trigger the light controlled by the Aqara E1 anymore.

Can you do one last favor and post a pic of what Z2M Bind looks like now? I very curious.

[temmyn (on a steep learning curve)]

Sure

[LiQuid_cOOled (Not really a...)]

@LiQuid_cOOled

EDIT: Its actually a TUYA device rebranded.

Really appreciate it. I still believe something went haywire in the initial Z2M setup and bound it self to the wall switch. The device is registering as a Tuya device with no bindings. Aqara E1 are notoriously difficult .

Glad you got it working!