Tuya switch..what exactly isnt working?

[bkinmuc]

Hi
i ordered some of these switches
https://de.aliexpress.com/item/1005008821136233.html?spm=a2g0o.order_list.order_list_main.46.5c7a1802YEi0o3&gatewayAdapt=glo2deu
and wonder what exactly is wrong with them..

Application	93
Endpoint Id	01
Manufacturer	_TZ3000_bgtzm4ny
Model	TS0044
Tuya Version	2.1.3

they only seem to work 60% of the time, which led me to believe its a mechanical problem..
i tried some different drivers.. right now using
tuya scene switch ts004f
and they never behaved 100% reliable..

sometimes even the green led lights up when pushing a button, but no event is received by hubitat.. shouldnt it always send a commend when the light goes on?

i actually wanted to post some debug lines the switch normally produced until a few days ag, which seem to be gone like magic now that i use the button...
thought it had to do with the driver not working correctly..
so the log errors are gone, switch still unreliable though...

i have 4 in use now and all behave same..still- cant believe theyre ALL faulty..
also have a moes smart knob, which wont work at all..
https://de.aliexpress.com/item/1005006022656319.html?spm=a2g0o.order_list.order_list_main.40.5c7a1802YEi0o3&gatewayAdapt=glo2deu

are there brands, especially in the button / switch sector which are known to work great with hubitat, have decent quality and are supported?
i find some entries in the (un)official supported lists, but would like some more insight from the community.

---

c8

[chrisbvt]

I assume you are referring to this driver?

[RELEASE] Tuya Scene Switch TS004F driver (w/ healthStatus)

The recommended way to install the driver is Hubitat Package Manager (HPM). Search for "Tuya Scene Switch TS004F" or by tag "Zigbee". The latest driver code is availabe in Github: https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20TS004F/TS004F.groovy Important: Due to the Tuya specific initialization that these devices require, these scene switches must be obligatory re-paired to HE hub in order to work properly. Supported models Device Links Tuya Scene/Di…

I think many people are using that driver with these successfully.

This sounds more like a mesh issue. The scene switch may need more repeater paths for the location you have it in, if the hub is missing commands from it.

[chrisbvt]

Did you press configure on the command tab after changing the driver?

[kkossev]

I believe I have identified the problem and have a solution to fix it. Please wait until tomorrow for an update.

[kkossev]

@bkinmuc I am adding some additional code to the driver to prevent improper custom settings for this device, but if you haven't changed the default settings and you have paired the device again to your hub, it should be working properly already :

---

It is of critical importance to pair the device once again to your hub. Simply changing the drivers won't work for some wierd Tuya devices. This is written in the first post of the TS004F driver thread:

Could you please check your settings and confirm that the Tuya scene switch is paired again with your HE hub without deleting the device beforehand?

---

@chrisbvt

Did you press configure on the command tab after changing the driver?

Clicking on the 'Configure' button will NOT work for many Zigbee battery-powered sleepy devices... When I have the time, I can write a detailed explanation of why.

---

@bkinmuc

are there brands, especially in the button / switch sector which are known to work great with hubitat, have decent quality and are supported?

When you have a choice, avoid Tuya devices because of issues like this.

[bkinmuc]

Dude you're a godsend!
So I have a lot of learning to do this weekend..
Need to learn about the commands in the device settings page, device firmware, learn how to use RM properly and so on and on...

Will keep you updated how they behave!

I still could use some good switch recommendations (powered in wall socket and battery switches)..

I always read that the tuya are slow and hassle to write software for, but I need recommendations on GOOD switches..
If you put the money aspect aside-which are the top 5 brands which have proven reliable and easy to support/ companies close to the diy smart community?!?

That said I ordered a range of Moe's switches, which are a bit easier to support it seems?!
Quality might still be sub par, but I'm just starting out and can't find really good ones that are supported..
I'd love to have the wall and the battery switches in the same design.

@chrisbvt

This sounds more like a mesh issue. The scene switch may need more repeater paths for the location you have it in, if the hub is missing commands from it.

So I need to learn more about the technicals here.. I can only report they are very close to the hub, and I have 4 in different locations all behaving the same unreliable way..

I installed the zigbee mesh app that visualizes the network, but I don't yet know how to read that info/make a statement about my mesh quality.. how can I determine if it has a bad connection?

You're saying it should be able to connect through another powered device acting as a repeater??

I pressed configure here and there without knowing what it really does:)

I read about and use the fact that I need to pair tuya devices twice to enable proper behaviour which worked already and isn't nice to have to remember:/

So is it correct that button reliability is mostly a driver problem and seldom faulty hardware, even with the cheap Chinese parts?
Hard to learn when I gaslight myself again and again:)))

Enjoy your weekends!!

[bkinmuc]

ok so i

-updated the driver by copying the code from the app github link and pasting in driver code-wonder if theres another method..tried hpm but didnt see an update

• readded the device twice

• clicked configure

first question is how to determine if i readded the device a sufficient amount of times? what indicates that the switch is bound properly now?
also how can i see if the configure commend has made an impact?

i can see your red text now, but get the following log with bugs again:

---

dev:552025-11-30 17:12:10.305

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 17:12:09.348

info

Button 4Way 1 switch is off null

dev:552025-11-30 17:12:09.346

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 17:12:09.344

debug

Button 4Way 1 description is read attr - raw: 73F00100060800001000, dni: 73F0, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 17:12:09.113

debug

Button 4Way 1 restarted debouncing timer 1200ms for button 1 (lastButtonNumber=1)

dev:552025-11-30 17:12:09.095

warn

Button 4Way 1 ignored event for button 1 - still in the debouncing time period!

dev:552025-11-30 17:12:09.094

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 17:12:09.092

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 01 01 0040 00 73F0 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:73F0, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 17:12:09.090

debug

Button 4Way 1 description is catchall: 0104 0006 01 01 0040 00 73F0 01 00 0000 00 00

dev:552025-11-30 17:12:08.844

info

Button 4Way 1 button 1 was pushed

dev:552025-11-30 17:12:08.842

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 01 01 0040 00 73F0 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:73F0, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 17:12:08.840

debug

Button 4Way 1 description is catchall: 0104 0006 01 01 0040 00 73F0 01 00 0000 FD 00 00

---

[bkinmuc]

also all the buttons report button 1..

dev:552025-11-30 17:22:54.451

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 17:22:53.494

info

Button 4Way 1 switch is off null

dev:552025-11-30 17:22:53.491

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 17:22:53.489

debug

Button 4Way 1 description is read attr - raw: 075B0400060800001000, dni: 075B, endpoint: 04, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 17:22:53.246

info

Button 4Way 1 button 1 was held

dev:552025-11-30 17:22:53.241

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 17:22:53.238

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:04, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 17:22:53.235

debug

Button 4Way 1 description is catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 17:22:52.992

info

Button 4Way 1 button 4 was pushed

dev:552025-11-30 17:22:52.990

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:04, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 17:22:52.987

debug

Button 4Way 1 description is catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 FD 00 00

dev:552025-11-30 17:22:49.218

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 17:22:48.259

info

Button 4Way 1 switch is off null

dev:552025-11-30 17:22:48.256

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 17:22:48.254

debug

Button 4Way 1 description is read attr - raw: 075B0300060800001000, dni: 075B, endpoint: 03, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 17:22:48.009

info

Button 4Way 1 button 1 was held

dev:552025-11-30 17:22:48.006

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 17:22:48.002

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 17:22:47.999

debug

Button 4Way 1 description is catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 17:22:47.754

info

Button 4Way 1 button 3 was pushed

dev:552025-11-30 17:22:47.751

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 17:22:47.749

debug

Button 4Way 1 description is catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 FD 00 00

dev:552025-11-30 17:22:44.162

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 17:22:43.202

info

Button 4Way 1 switch is off null

dev:552025-11-30 17:22:43.200

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 17:22:43.197

debug

Button 4Way 1 description is read attr - raw: 075B0200060800001000, dni: 075B, endpoint: 02, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 17:22:42.950

info

Button 4Way 1 button 1 was held

dev:552025-11-30 17:22:42.948

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 17:22:42.945

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 17:22:42.943

debug

Button 4Way 1 description is catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 17:22:42.697

info

Button 4Way 1 button 2 was pushed

dev:552025-11-30 17:22:42.695

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 17:22:42.692

debug

Button 4Way 1 description is catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 FD 00 00

dev:552025-11-30 17:22:38.427

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 17:22:37.469

info

Button 4Way 1 switch is off null

dev:552025-11-30 17:22:37.467

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 17:22:37.464

debug

Button 4Way 1 description is read attr - raw: 075B0100060800001000, dni: 075B, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 17:22:37.240

debug

Button 4Way 1 restarted debouncing timer 1200ms for button 1 (lastButtonNumber=1)

dev:552025-11-30 17:22:37.219

warn

Button 4Way 1 ignored event for button 1 - still in the debouncing time period!

dev:552025-11-30 17:22:37.216

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 17:22:37.214

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 17:22:37.211

debug

Button 4Way 1 description is catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 17:22:36.966

info

Button 4Way 1 button 1 was pushed

dev:552025-11-30 17:22:36.963

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 17:22:36.961

debug

Button 4Way 1 description is catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 FD 00 00

[kkossev]

What device is this?

The previous device was TS0044 _TZ3000_bgtzm4ny

Is it working now without flashing theLEDs every hour ?

———

The logs are for another device TS0041 that is very different… typically these are single button ones. What is yours?
(I need both the Zigbee model and the manufacturer the info is shown at the bottom of the device Info web page).

[bkinmuc]

same device type/model, just i have 6 of them and now use only 1 and 1 light for error checking

now the buttons are reported correctly, still with bug msgs

dev:552025-11-30 18:25:16.352

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 18:25:15.392

info

Button 4Way 1 switch is off null

dev:552025-11-30 18:25:15.390

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 18:25:15.388

debug

Button 4Way 1 description is read attr - raw: 075B0400060800001000, dni: 075B, endpoint: 04, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 18:25:15.143

info

Button 4Way 1 button 1 was held

dev:552025-11-30 18:25:15.140

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 18:25:15.138

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:04, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 18:25:15.135

debug

Button 4Way 1 description is catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 18:25:14.887

info

Button 4Way 1 button 4 was pushed

dev:552025-11-30 18:25:14.885

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:04, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 18:25:14.882

debug

Button 4Way 1 description is catchall: 0104 0006 04 01 0040 00 075B 01 00 0000 FD 00 00

dev:552025-11-30 18:25:10.577

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 18:25:09.622

info

Button 4Way 1 switch is off null

dev:552025-11-30 18:25:09.620

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 18:25:09.617

debug

Button 4Way 1 description is read attr - raw: 075B0300060800001000, dni: 075B, endpoint: 03, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 18:25:09.370

info

Button 4Way 1 button 1 was held

dev:552025-11-30 18:25:09.367

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 18:25:09.365

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 18:25:09.362

debug

Button 4Way 1 description is catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 18:25:09.115

info

Button 4Way 1 button 3 was pushed

dev:552025-11-30 18:25:09.112

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 18:25:09.110

debug

Button 4Way 1 description is catchall: 0104 0006 03 01 0040 00 075B 01 00 0000 FD 00 00

dev:552025-11-30 18:25:05.066

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 18:25:04.106

info

Button 4Way 1 switch is off null

dev:552025-11-30 18:25:04.103

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 18:25:04.101

debug

Button 4Way 1 description is read attr - raw: 075B0200060800001000, dni: 075B, endpoint: 02, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 18:25:03.854

info

Button 4Way 1 button 1 was held

dev:552025-11-30 18:25:03.852

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 18:25:03.850

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 18:25:03.847

debug

Button 4Way 1 description is catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 18:25:03.634

info

Button 4Way 1 button 2 was pushed

dev:552025-11-30 18:25:03.632

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 18:25:03.596

debug

Button 4Way 1 description is catchall: 0104 0006 02 01 0040 00 075B 01 00 0000 FD 00 00

dev:552025-11-30 18:25:01.883

debug

Button 4Way 1 debouncing timer for button 1 expired.

dev:552025-11-30 18:25:00.927

info

Button 4Way 1 switch is off null

dev:552025-11-30 18:25:00.924

debug

Button 4Way 1 Event enter: [name:switch, value:off]

dev:552025-11-30 18:25:00.918

debug

Button 4Way 1 description is read attr - raw: 075B0100060800001000, dni: 075B, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:552025-11-30 18:25:00.696

debug

Button 4Way 1 restarted debouncing timer 1200ms for button 1 (lastButtonNumber=1)

dev:552025-11-30 18:25:00.673

warn

Button 4Way 1 ignored event for button 1 - still in the debouncing time period!

dev:552025-11-30 18:25:00.670

debug

Button 4Way 1 TS0041 Held via Cluster 0006/Command 00

dev:552025-11-30 18:25:00.668

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:]

dev:552025-11-30 18:25:00.665

debug

Button 4Way 1 description is catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 00 00

dev:552025-11-30 18:25:00.446

info

Button 4Way 1 button 1 was pushed

dev:552025-11-30 18:25:00.443

debug

Button 4Way 1 catchall descMap: [raw:catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 FD 00 00, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:075B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:FD, direction:00, data:[00]]

dev:552025-11-30 18:25:00.436

debug

Button 4Way 1 description is catchall: 0104 0006 01 01 0040 00 075B 01 00 0000 FD 00 00

[bkinmuc]

Application	93
Endpoint Id	01
Manufacturer	_TZ3000_bgtzm4ny
Model	TS0044
Tuya Version	2.1.3

[kkossev]

@bkinmuc Thank you for providing the logs!

Yes, you've discovered a bug . It was introduced on October 7, 2025, and it exists in the last three versions of this driver. I am currently working on a fix.

[kkossev]

Please update the driver manually to the new version ver. 2.8.6 2025-11-30 :

• bug fix: wierd TS0041 _TZ3000_rsqqkdxv switch event handling was affecting other devices;
• debug logs are automatically disabled after 24 hours;
• all Tuya buttons and scene switches now have the debounce function enabled by default.

[bkinmuc]

ok so it seems much more reliable now, but still not 100%..sometimes it just doesnt seems to send a signal..will monitor..
all the bug msgs in logs are gone

i guess its a mechanical thing..have another 6way switch which works a lot better than those 4ways, but i need to find something really reliable..

[kkossev]

I would recommend troubleshooting the devices one by one. Start with the one that is close to your hub, and make sure all button presses are registered reliably. Then move it to the final destination and test it the next day (it may take time to choose the best Zigbee router/repeater).

The latest driver version 2.8.6 enforces the built-in debouncing logic by default. This means that the driver will ignore two presses of one and the same button if they are registered in a period of less than 1.2 seconds.

Your device falls into the 'Tuya weird behaviour' category - it sends a Zigbee message when a button is pressed three times (in three different formats). This is the first time I have seen such a non-standard implementation for a button... For a test, you can try disabling the " Force debounce" option (it is visible when the 'Advanced Options' is toggled and the web page is refreshed). Without the debouncing algorithm, the scene switch will be more responsive when one and the same button is pressed in a short time period, but not quickly enough to register a 'doubleTapped' event.

[bkinmuc]

very interesting
isit pssible to control the debounce time?

i was wondering what determines the timings of switches..like this 1.2 sec period, or amount of time needed to register as a hold..
is this set by the device hardware (built in)? or isit only software side that determines these values?

so i want to use tap, double, and hold, for sth like this...
the hold example which first dims up, then down..

An idiot's guide for "push", "double-tap", "hold-release" vs "toggle on/off" (and making "on" always start at max dimmer level)

On the note of being unable to dim up if you dim too far, this is what I've got on one of my button controllers: [1000001551] That is, holding triggers a dim down, but a second one within ten seconds dims up, and it continues to flip-flop directions until you leave it alone for ten seconds. (And then because these bulbs are stupid and turn off if you dim too far, I turn them on at the end if they got turned off.)

here the "timeouts" of the button presses get really important i guess.

could this be programmed to not only have 2 hold functions, but as many as i want?
eg 1st hold dim up. 2nd hold dim down, 3rd hold change WW up, 4th hold change WW down, 5th hold start cycling through RGB, 6th hold as 5, other direction
wouldnt be convenient, but just want to know if it would be possible..

also want to add a variable to override a motion automation..
cannot think of more functions to put onto 1 button...or did i miss sth?

also im wondering.. already asked in another thread...
possibilities for an "AUX Channel":
so right now i want to replicate a scene cycler, like the hue buttons can do...1 press scene 1, 2nd scene 2 and so on...dont really know how to do that in HE..
BUT: i only want this functionality enaled after a double tap.
so normally button 1 has its normal functionality (toggle lights) but when button 1 (or another one setup) is double tapped, i come into scene cycle mode... after a certain timeout, button 1 goes back to normal behaviour

can i control these timeouts?

are there apps for the above? or do i need to do all this in RM?
or maybe first question...is this possible in HE?

anyway all my 4way buttons now work very well..only had 1 unregged push yesterday..will monitor..also more access points will be installed later this week..

sry if the questions are in the wrong place..theres so many and i dont want to clutter the forum with 50new threads..
thx again!