Tuya Zigbee Button Stopped Working Correctly

General Discussion
1

Hi

I have a Tuya wireless button set up with smart things to trigger a routine when it is pressed. The routine is set to toggle on or off a set of smart plugs together.

It was all working fine but then a few weeks ago it started switching on some of the plugs and then switching them back off straight away leaving some of them on and some of them off.

The button is only linked to the routine not to switching the plugs directly.

When I trigger the routine directly from the Smartthings app this issue doesnā€™t happen. Even when I go into the switch page on the app and use the ā€˜test the routineā€™ option its fine.

Does anyone have any ideas which might help?

Thanks

2

Zigbee plugs?

3

Hi @plantyman

Could you please provide the name of the device?
Also, could you provide support access to your account, please?

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  3. Go to the SmartThings Web (my.smartthings.com )
  4. Log in to your Samsung Account
  5. Select Menu (ā‹®) and choose Settings
  6. Toggle on Account Data Access
  7. Select the time period and confirm - In this step, please select ā€œUntil turned offā€, once the team finishes, weā€™ll let you know so you can disable it again.
4

The plugs are zigbee plugs. BSD48.
The switch I canā€™t see the model number because Iā€™ve stuck it down and literally canā€™t get it back off but it is a round scene button like this:
https://www.aliexpress.com/item/1005005941325665.html?pdp_npi=4%40dis!GBP!6.82!3.14!!!60.82!27.98!%402141155017409934008848987d1091!12000034951268564!affd!!!&dp=Cj0KCQiAz6q-BhCfARIsAOezPxlgGr05bYHPpbARLlV-pASbki34isme8LUZ42iuIw6i6MHxj4IfVW8aApYyEALw_wcB&gad_source=1&gbraid=0AAAAADihhqXfrghCw24xQt_v-Bss4Ee9-&gclid=Cj0KCQiAz6q-BhCfARIsAOezPxlgGr05bYHPpbARLlV-pASbki34isme8LUZ42iuIw6i6MHxj4IfVW8aApYyEALw_wcB&aff_fcid=797f8126f4a44428b99eda3f59e9fd7c-1741372933518-01303&aff_fsk&aff_platform=api-new-product-query&sk&aff_trace_key=797f8126f4a44428b99eda3f59e9fd7c-1741372933518-01303&terminal_id=41c8269e031642618cebce38f28e4cae&afSmartRedirect=y#nav-specification

Same email as here and I have enabled data.

Thanks for the quick replies!

5

Sounds like Zigbee binding.

Delete the button in the SmartThings app and then add it back. Go through the routines to fix them and then try it again.

6

Just gave this a go but its still doing the same.

7

Hi @plantyman

We reviewed your routine settings and would like to verify if the button is sending a double event. To do so, we need your support in sending the Hub logs.

Note: Please send logs for all drivers, do not select a specific one.

Please repeat the routine and send the Hub logs through the my.smartthings.com:

  1. In the my.smartthings, enter ā€œyour hubsā€
  2. Enter the corresponding Hub
  3. Click on ā€œDump Hub Logsā€
  4. Change the reason for requesting hub logs if needed
  5. Click on ā€œDump Hub Logsā€
  6. Confirm that the request is submitted
    Note: If you have more than one Hub, the name of the one involved in the issue.
8

Hi, Iā€™ve submitted the request now. Thanks!

9

@plantyman Thank you for the information. Could you also support us by sending the driver logs, please?

To ensure we capture the correct events, please follow these steps:

:one: Enable logs:

  • Set up the ST CLI if you havenā€™t already.
  • Run the following command:
    smartthings edge:drivers:logcat
  • When prompted, select all drivers to capture all relevant events.

:two: Trigger the routine:

  • Press the button

:three: Monitor device behavior:

  • Pay attention to the physical response of the devices.

  • This will help identify at what point the state changes stop or behave unexpectedly.

:four: Save and share the logs:

  • Once you have completed the actions, close the logs in the CLI.
  • Copy the logs into a file and send them to build@smartthings.com.
10

Hi, thanks for putting me on the right track and looking into the fact that the button was sending 2 events. Ive found a different driver and installed it and it seems to be working again for now.

For anyone else reading, this is the driver I used:

1 Like
11

Hi, glad to hear you found a solution and that the new driver is working for now! Thanks for sharing your findings

1 Like
12

@plantyman, was you using the zigbee_tuya_button from ā€œObmazā€ driver channel before? @zambobmaz made some updates in his driver recently to support a tuya knob. I wonder if some of the changes are causing the press event of the other tuya buttons to be fired twice.
I also have one _TZ3000_ja5osu5g that are sending the press event twice in a row.

@zambobmaz, can you take a look at this?

13

@marcos.scheffler Yes, Iā€™m here

It doesnā€™t seem to be related to the addition of the knob function, but I canā€™t be sure until I see the log.If you could send the log for _TZ3000_ja5osu5g, it would be helpful. (github)

14

Yes that is the driver I was using previously. I thought it might have been a driver update too because it was working fine until about a few weeks ago and suddenly started doing this.

15

Hi @zambobmaz
Iā€™ve open an issue in your github and sent to you the log.

Tuya Zigbee Button Stopped Working Correctly Ā· Issue #55 Ā· obmaz/smartthings_edge_driver

thanks in advance

Log shows a toggle event ā€œbutton_handler_Knob_Scene_Toggle 1ā€ been fired right after the first button press. Wonder if this device exposes ā€œtoggle upā€ event after button release?

16

@plantyman , can you test now? @zambobmaz updated the driver.

17

Doesnā€™t seem to respond to the button at all now

18

Thatā€™s strange, mine works well!

Please, see if you have this driver version: 2025-03-14T11:30:03.143778274

If yes, try to put button in pair mode again and recommission the device (without deleting)

If this not work, try to delete and repair the device again directly with @zambobmaz driver, donā€™t perform a driver change (you may have to delete erickā€™s drive for this)

19

I deleted the driver and device and added them back. Seems to be ok again now. Thanks for the help coordinating and @zambobmaz for fixing the driver!

1 Like