Assistance with new button

🛎️ Get Help
1

I am running a recently updated c-7 hub.

I ordered a new SOS button for my bathroom.

1000016606
10000166061920×2550 141 KB

1000016605
10000166051920×2550 383 KB

Application 4D
Endpoint Id 01
Manufacturer _TZE284_2baujqot
Model TS0601
Power Cluster none
Tuya Version 1.0.13

It gets this driver on pairing:

Tuya Zigbee Tank Level Monitor

Device Profile
UNKNOWN
Driver Version
3.4.1 2025/07/27 6:13 PM (TS0601 _TZE284_2baujqot) (C-7 2.5.0.126)
Health
{"checkCtr3":0}
Last Rx
{"timeStamp":"2026-05-05 18:30:25.019","checkInTime":1778023820505}
Last Tx
{"cmdTime":1778023819476}
States
{}
Stats
{"cfgCtr":1,"rxCtr":6,"instCtr":1,"txCtr":2

Maybe @kkossev can help? If so, let me know if you need more info.

Thanks and God bless.

2

Can you post the clusters for this device? Chances are high it will work with one of the existing zigbee button drivers.

3

Hey @aaiyar , where can I find the clusters? Thanks.

4

They would have appeared in the logs during pairing. Post-pairing, you can change to the driver called "Device", and then click on Configure - the clusters will appear in the logs (so keep a live log window open). Cut and paste that section of the logs.

5

Ok, I hope this is it:

  1. Home
  2. Devices

dev:2822026-05-05 07:44:44.356 PM

info

Zigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 E870 00 00 0000 00 00 0070E805D869B32D38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E870, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 70, E8, 05, D8, 69, B3, 2D, 38, C1, A4, 80]]

dev:2822026-05-05 07:44:43.134 PM

debug

getting info for unknown Zigbee device...

dev:2822026-05-05 07:44:41.678 PM

info

Zigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 E870 01 00 0000 02 01 00470302000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E870, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 47, 03, 02, 00, 04, 00, 00, 00, 64]]

dev:2822026-05-05 07:44:40.999 PM

info

Zigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 E870 01 00 0000 02 01 00461701000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E870, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 46, 17, 01, 00, 01, 00]]

dev:2822026-05-05 07:44:33.668 PM

info

Zigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 E870 00 00 0000 00 00 1370E805D869B32D38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:E870, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[13, 70, E8, 05, D8, 69, B3, 2D, 38, C1, A4, 80]]

dev:2822026-05-05 07:44:33.099 PM

debug

getting device info in 10 seconds...

dev:2822026-05-05 07:44:01.827 PM

info

fingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000,ED00", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE284_2baujqot", controllerType: "ZGB"

dev:2822026-05-05 07:44:01.702 PM

trace

ZCL version:03

dev:2822026-05-05 07:44:01.700 PM

trace

Software Build Id:unknown

dev:2822026-05-05 07:44:01.698 PM

trace

Model:TS0601

dev:2822026-05-05 07:44:01.696 PM

trace

Manufacturer:_TZE284_2baujqot

dev:2822026-05-05 07:44:01.611 PM

debug

getting info for unknown Zigbee device...

dev:2822026-05-05 07:43:51.583 PM

debug

getting device info in 10 seconds...

dev:2822026-05-05 07:43:46.703 PM

info

Zigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 C963 00 00 0000 00 00 0D63C905D869B32D38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:C963, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0D, 63, C9, 05, D8, 69, B3, 2D, 38, C1, A4, 80]]

dev:2822026-05-05 07:43:00.802 PM

info

Tuya Zigbee Tank Level Monitor updated

dev:2822026-05-05 07:43:00.747 PM

info

scheduling health check every 240 minutes by Activity check method

dev:2822026-05-05 07:43:00.721 PM

info

Tuya Zigbee Tank Level Monitor driver version 3.4.1 2025/07/27 6:13 PM (TS0601 _TZE284_2baujqot) (C-7 2.5.0.126)

dev:2822026-05-05 07:43:00.715 PM

info

Tuya Zigbee Tank Level Monitor updated()...

dev:2822026-05-05 07:42:58.142 PM

info

Tuya Zigbee Tank Level Monitor is now online!

dev:2822026-05-05 07:42:58.141 PM

info

Tuya Zigbee Tank Level Monitor healthStatus changed to online

dev:2822026-05-05 07:42:58.127 PM

info

Tuya Zigbee Tank Level Monitor tuyaVersion set to 1.0.13

dev:2822026-05-05 07:42:58.121 PM

info

Tuya Zigbee Tank Level Monitor device model TS0601 manufacturer _TZE284_2baujqot was not found!

dev:2822026-05-05 07:42:58.119 PM

info

Tuya Zigbee Tank Level Monitor unknown model null manufacturer null

dev:2822026-05-05 07:42:58.011 PM

info

Tuya Zigbee Tank Level Monitor Updated to version 3.4.1 2025/07/27 6:13 PM (TS0601 _TZE284_2baujqot) (C-7 2.5.0.126)

dev:2822026-05-05 07:42:57.905 PM

info

Tuya Zigbee Tank Level Monitor sent device configuration

dev:2822026-05-05 07:42:57.882 PM

info

Tuya Zigbee Tank Level Monitor configureDevice...

dev:2822026-05-05 07:42:57.880 PM

info

Tuya Zigbee Tank Level Monitor initializeDevice...

dev:2822026-05-05 07:42:57.874 PM

info

Tuya Zigbee Tank Level Monitor tuyaBlackMagic()...

dev:2822026-05-05 07:42:57.865 PM

info

Tuya Zigbee Tank Level Monitor configure()... cfgCtr=1

dev:2822026-05-05 07:42:57.639 PM

info

Tuya Zigbee Tank Level Monitor installed

dev:2822026-05-05 07:42:57.634 PM

info

Tuya Zigbee Tank Level Monitor installed()... instCtr=1

6

Oh, and I looked and this changed a little.

Application
4D
Endpoint Id
01
In Clusters
0004,0005,EF00,0000,ED00
Manufacturer
_TZE284_2baujqot
Model
TS0601
Out Clusters
0019,000A
Software Build
null
Tuya Version
1.0.13

Are those the clusters as reported in the logs?

Thanks.

7

Hi Paul,

Please change the driver to Tuya Scene Switch TS004F driver.

This is a new device and its fingerprint is not in the code yet, but before adding it we must be sure that it is successfuly paired to your HE hub and is sending Zigbee messages on a button press.

Enable the Debug logging in the TS004F driver, then push the button. Anything in the live logs?

8

Ok, I changed to that driver and saved it. Then I re-paired it to the hub and it paired. Then I pressed the button and clicked on logs,

Bath soa InitializeVars()... fullInit = false

dev:2862026-05-06 12:52:19.339 AM

debug

Bath soa updating the settings from the current driver version UNKNOWN to the new version 2.9.2 2026/03/30 9:57 PM

dev:2862026-05-06 12:52:19.289 AM

info

Bath soa sending Tuya Magic commands... Make sure the device is awake (a device button was pressed) before clicking on the Configure button!

dev:2862026-05-06 12:52:19.288 AM

info

Bath soa battery reporting interval not changed.

dev:2862026-05-06 12:51:26.280 AM

info

Bath soa InitializeVars()... fullInit = false

dev:2862026-05-06 12:51:26.273 AM

debug

Bath soa updating the settings from the current driver version UNKNOWN to the new version 2.9.2 2026/03/30 9:57 PM

dev:2862026-05-06 12:49:04.152 AM

info

Tuya Zigbee Tank Level Monitor updated

dev:2862026-05-06 12:49:04.118 AM

info

scheduling health check every 240 minutes by Activity check method

dev:2862026-05-06 12:49:04.081 AM

info

Tuya Zigbee Tank Level Monitor driver version 3.4.1 2025/07/27 6:13 PM (TS0601 _TZE284_2baujqot) (C-7 2.5.0.126)

dev:2862026-05-06 12:49:04.078 AM

info

Tuya Zigbee Tank Level Monitor updated()...

dev:2862026-05-06 12:49:01.634 AM

info

Tuya Zigbee Tank Level Monitor is now online!

dev:2862026-05-06 12:49:01.632 AM

info

Tuya Zigbee Tank Level Monitor healthStatus changed to online

dev:2862026-05-06 12:49:01.619 AM

info

Tuya Zigbee Tank Level Monitor tuyaVersion set to 1.0.13

dev:2862026-05-06 12:49:01.613 AM

info

Tuya Zigbee Tank Level Monitor device model TS0601 manufacturer _TZE284_2baujqot was not found!

dev:2862026-05-06 12:49:01.611 AM

info

Tuya Zigbee Tank Level Monitor unknown model null manufacturer null

dev:2862026-05-06 12:49:01.520 AM

info

Tuya Zigbee Tank Level Monitor Updated to version 3.4.1 2025/07/27 6:13 PM (TS0601 _TZE284_2baujqot) (C-7 2.5.0.126)

dev:2862026-05-06 12:49:01.180 AM

info

Tuya Zigbee Tank Level Monitor sent device configuration

dev:2862026-05-06 12:49:01.169 AM

info

Tuya Zigbee Tank Level Monitor configureDevice...

dev:2862026-05-06 12:49:01.167 AM

info

Tuya Zigbee Tank Level Monitor initializeDevice...

dev:2862026-05-06 12:49:01.163 AM

info

Tuya Zigbee Tank Level Monitor tuyaBlackMagic()...

dev:2862026-05-06 12:49:01.156 AM

info

Tuya Zigbee Tank Level Monitor configure()... cfgCtr=1

dev:2862026-05-06 12:49:01.021 AM

info

Tuya Zigbee Tank Level Monitor installed

dev:2862026-05-06 12:49:01.016 AM

info

Tuya Zigbee Tank Level Monitor installed()... instCtr=1

Is this good or bad?

10

You have changed the driver successfuly, but there are no events registered in the logs when you press a button.

Try pairing the device again to your hub at a close distance. Do NOT delete it - just pair it for a second time.

If you don't see anything in the Debug logs afterward, there is little if nothing that can be done to make it work directly paired to HE. Some of these Tuya SOS buttons are known to be very problematic and do not work even with Home Assistant ...

11

Ok. First, I forgot to enable debug but I have now. Here is the logs

manufacturerId:0000, command:11, direction:01, data:[00, 05, 40]]

dev:2862026-05-06 01:26:20.028 AM

debug

Bath soa unexpected catchall from cluster 61184 sourceEndpoint 01

12

Well, let me try that again.

ev:2862026-05-06 01:28:24.542 AM

debug

Bath soa UNHANDLED event for button 0, lastButtonNumber=0

dev:2862026-05-06 01:28:24.539 AM

debug

Bath soa catchall descMap: [raw:catchall: 0104 EF00 01 01 0040 00 0249 01 00 0000 02 01 00F60302000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0249, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, F6, 03, 02, 00, 04, 00, 00, 00, 64]]

dev:2862026-05-06 01:28:24.538 AM

debug

Bath soa unexpected catchall from cluster 61184 sourceEndpoint 01

dev:2862026-05-06 01:28:24.534 AM

debug

Bath soa catchall descMap: [raw:catchall: 0104 EF00 01 01 0040 00 0249 01 00 0000 02 01 00F60302000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0249, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, F6, 03, 02, 00, 04, 00, 00, 00, 64]]

dev:2862026-05-06 01:28:24.532 AM

debug

Bath soa description is catchall: 0104 EF00 01 01 0040 00 0249 01 00 0000 02 01 00F60302000400000064

dev:2862026-05-06 01:28:24.477 AM

debug

Bath soa UNHANDLED event for button 0, lastButtonNumber=0

dev:2862026-05-06 01:28:24.474 AM

debug

Bath soa catchall descMap: [raw:catchall: 0104 EF00 01 01 0040 00 0249 01 00 0000 02 01 00F51701000101, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0249, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, F5, 17, 01, 00, 01, 01]]

dev:2862026-05-06 01:28:24.473 AM

debug

Bath soa unexpected catchall from cluster 61184 sourceEndpoint 01

dev:2862026-05-06 01:28:24.470 AM

debug

Bath soa catchall descMap: [raw:catchall: 0104 EF00 01 01 0040 00 0249 01 00 0000 02 01 00F51701000101, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0249, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, F5, 17, 01, 00, 01, 01]]

dev:2862026-05-06 01:28:24.468 AM

debug

Bath soa description is catchall: 0104 EF00 01 01 0040 00 0249 01 00 0000 02 01 00F51701000101

dev:2862026-05-06 01:28:20.772 AM

debug

Bath soa (ZDO 0013) device announcement from dni 0249, data=[00, 49, 02, 05, D8, 69, B3, 2D, 38, C1, A4, 80

That's better.

13

Unfortunately, these are not the Zigbee message that follow a button press. So, most probably, this Tuya SOS button will not work when paired directly to HE.

14

Well crap. Thanks for checking on it for me. I guess it goes back to Amazon then.

15

I tried the button again and this showed up in the logs

dev:2862026-05-06 01:37:29.810 AM

debug

Bath soa (ZDO 0013) device announcement from dni 0249, data=[00, 49, 02, 05, D8, 69, B3, 2D, 38, C1, A4, 80]

dev:2862026-05-06 01:37:29.807 AM

debug

Bath soa catchall descMap: [raw:catchall: 0000 0013 00 00 0040 00 0249 00 00 0000 00 00 00490205D869B32D38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0249, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 49, 02, 05, D8, 69, B3, 2D, 38, C1, A4, 80]]

dev:2862026-05-06 01:37:29.804 AM

debug

Bath soa description is catchall: 0000 0013 00 00 0040 00 0249 00 00 0000 00 00 00490205D869B32D38C1A480

dev:2862026-05-06 01:31:31.854 AM

debug

Bath soa UNHANDLED event for button 0, lastButtonNumber=0

It's ok though. I understand. Have a good night

1 Like
16

C-7 is NOT Zigbee 3.0 compliant, don't use it with 2026 Tuya, Aqara, and Shelly devices... some will work, others will not.

17

Oh my. That is not good, but it does explain some things. Why haven't they (hubitat) fixed that with a firmware update? I hate to assume things buty is it a hardware issue instead of a firmware issue?

I had assumed it was fully compatible with the zigbee standards.

There is no way we can buy any device that will be old enough to be compatible except maybe used off eBay.

This is disappointing.

Well, being on a fixed budget I can't afford a new c-8 hub, let alone the best one.

Bummer. Thank you for all you do with these devices. Enjoy the rest of your day.

Paul

1 Like
18

Older hardware. The C-8 and later have zigbee chips that support zigbee 3.0 (and potentially Thread).

1 Like
19

Thanks. I understand, but still disappointed. Lol.

20

image
image812×650 88 KB

image

Not a firmware upgrade...

1 Like
21

Well that looks like a firmware upgrade to me. Lol

They saw a problem and fixed it.

I understand it is not the same. Different hardware. I had to go there though, if nothing else, just to match your joke. Hehehe

Thanks everyone.