[RELEASE] Tuya Zigbee Smoke Detector

⚙️ Custom Apps and Drivers Custom Drivers
1

This driver adds support in Hubitat for these Tuya smoke detectors, that use the Tuya specific non-standard Zigbee cluster 0xEF00 messages.
Currently, it is being tested with manufacturer models "_TZE200_ntcy3xu1" and "_TZE200_uebojraa"

Please note, that none of these devices which are designed (not just manufactured) in China are known to have any UL, CSA, TÜV, AS/NZS or similar type certificates! Some models are listed as being EN14604 certified.

The recommended installation method is to use the community Hubitat Package Manager (HPM) app. Search for "Tuya Zigbee Smoke Detector" or by tag 'Zigbee'.
The driver can be also installed manually from this Github link

Please note that the links below are for reference only, not a purchase recommendation.

Tuya changes the electronics inside very frequently, so if the devices purchased from the same seller site a year ago have worked with this driver, there is absolutely no guarantee that what you will receive today will be the same device.

Supported models

Device Links
Tuya Smart Smoke Detector Sensor image AliExpress: (link)
Zigbee Smart Smoke Detector
image		 AliExpress: (link)

Compatibility

  • Tuya specific cluster 0xEF00 Smoke Detectors
    • model:"TS0601", manufacturer:"_TZE200_ntcy3xu1"
    • model:"TS0601", manufacturer:"_TZE200_uebojraa"
    • model:"TS0601", manufacturer:"_TZE200_t5p1vj8r" (not tested)
    • model:"TS0601", manufacturer:"_TZE200_yh7aoahi" (not tested)
    • model:"TS0601", manufacturer:"_TZE200_5d3vhjro" (not tested)
    • model:"TS0601", manufacturer:"_TZE200_aycxwiau" (not tested)
    • model:"TS0601", manufacturer:"_TZE200_vzekyi4c" (not tested)

Features

  • Standard "Smoke Detector" capability - ("detected","clear","tested")
  • Battery level capability
  • Health Check - will fire an healthStatus event 'offline' if there was no communication with the sensor for more than 13 hours
  • Tamper Alert" capability
  • PowerSource" capability
  • Debug/Info logging
8 Likes
2

REVISIONS HISTORY:

  • ver. 1.0.0 2022-10-29 - initial version for _TZE200_ntcy3xu1
  • ver. 1.0.1 2022-10-31 - added _TZE200_uebojraa
  • ver. 1.0.2 2022-11-17 - notPresentCounter set to 12 hours; states set to 'unknown' on device creation'; added Clear Detected Tested buttons; removed Configure button
  • ver. 1.0.3 2022-12-15 - added _TZE200_e2bedvo9
  • ver. 1.1.0 2023-04-07 - extended tuyaMagic (hopefully activates check-in every 4 hours); added capability 'Health Check'; added ping() command and rtt measurement;
  • ver. 1.1.2 2023-08-01 - added _TZE200_m9skfctm _TZE200_dq1mfjug _TZE200_ux5v4dbd _TZE200_ytibqbra _TZE200_dnz6yvl2
  • ver. 1.1.3 2023-11-19 - fixed _TZE200_m9skfctm battery reporting; fix RTT negative values bug
  • ver. 1.2.0 2024-02-20 - (dev. branch) Groovy lint; added TZE204_ntcy3xu1

The development branch version that contains the latest additions and bug fixes can be manually downloaded from here: https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya_Zigbee_Smoke_Detector/Tuya_Zigbee_Smoke_Detector.groovy

1 Like
3

I am wondering how the smoke detectors (but also leak sensors) are periodically tested, without triggering real fire alarms from all HE applications that are triggered by the "smoke detected" event?

The problem is that the cheap smoke detector from the first post does not make any difference between pressing the TEST button and sensing real smoke. The event that is sent to HE is one and the same...

Any ideas?

4

Hi
can confirm my Tuya Zigbee Smoke Detector
_TZE200_uebojraa
from this post

is working great with this driver! :slight_smile:

1 Like
5

In pretty much all smoke detectors I've tested, the TEST button produces a quick / rapid DETECTED and CLEAR signal within pretty much a split second... but testing with real smoke (smoke testing canisters) , the detection lingers longer and clear signal is sent after a longer period. I plan to create a condition where the detection must stay active for more than 3 seconds for it to be considered a real alert letting all sirens go off.

1 Like
6

With your device, when you press the TEST button the 'clear' event is sent 1.5 seconds after the 'detected' event. So creating a condition where the detection must stay active for more than 3 seconds for it to be considered a real alert will work!

I was thinking if the same logic can be implemented on a driver level - delay sending the smoke 'detected' event for 3 seconds. If within this 3-second window HE did not receive a 'clear' event - then fire the detected event which will activate the sirens.. However, if a 'clear' event was received within 3 seconds - then substitute the 'detected' event with the standard capability "tested" event value. So the tests will be still recorded in HE, but will not trigger alarm notifications.

3 Likes
7

Just ordered the Tuya Smart Smoke Detector Sensor (first link you sent). When it arrives I will test and share my results.
Thanks a lot for all your hard work @kkossev

1 Like
8

Hi @kkossev
Received my smoke detector today.
Paired it with the Tuya Smoke detector driver from HPM. Pairing went OK.
I tested the detector with real smoke but see no events in the log file.
Replaced the driver to the dev branch driver (version 1.0.2) but still no logs.
These are the details:

image
image1434×730 52.2 KB

image
image1002×154 4.54 KB

This is the log:
image
image1420×268 59.8 KB

9

The device does not send anything to the HE hub ...

Have you tried pairing it several times, and very close ( less than 1 meter ! ) to the hub?

10

I did pair it 3 or 4 times but never 1 meter from the hub.
As pairing seemed to go OK I didn't think I should pair closer to the hub. I will retry tonight again and report back.
Thanks

11

Check also whether the ‘powerSource” has changed to ‘unknown’ and the presence to ‘not present’

Keep the debug logs option enabled.

Please also update the driver to the new dev. branch version 1.0.2, time stamp 2022/11/17 1:13 PM
I have added Clear, Detected and Tested buttons (similar to HE inbuilt Smoke virtual driver). Clickng on these buttons generate 'digital' type smoke alarm events, its useful for testing your notification and alarm routines. The 'real' alarm events that come from the device are of a type 'physical'.

I have also removed the Configure button. It is a common misunderstanding that Zigbee battery-powered sleepy devices can be configured by clicking such 'Configure' buttons from the web page. Usually, they can't. (except if a complex logic is implemented inside the driver to buffer the configuration commands and to to send these buffered commands at the time when the device is awake... just a few drivers are actually doing that.).

You will have to pair the Tuya device again to HE hub (at a close distance).

12

Re-paired the device before seeing your last message.
So, re-pairing 1 meter from the hub did the trick. I can see events coming from the device. Great.
Now, changed the driver to latest dev branch:
image
I can see the 3 new buttons:

image
image930×217 4.04 KB

These are the logs when clicking Clear, Detected and Tested:

Summary

image

Edit - and in the events list:

Summary

image
image1557×222 17.7 KB

13

No, I didn’t see the smoke sensor working yet.

These events are not generated by the device itself, but are pure software events produced by the driver.

Remove the batteries for 1 minutes and put them back into the device.

Do you see any new logs?

14

My mistake. I did not show you the logs for the pairing process (that worked OK).
Have a look here for the first logs I got when I re-paired the device and then ran some smoke tests:

Summary

image
image1584×775 194 KB

image
image1600×817 208 KB

image
image1599×565 153 KB

1 Like
15

Great it works!

So the key was to pair it close to the hub.

Okay, I will push the latest version update via HPM then.

1 Like
16

Hello,
Thank you for developing those drivers. Can you please add support for my device _TZE200_e2bedvo9

Screenshot_1
Screenshot_1856×282 11.5 KB

1 Like
17

Hello,

I have added your device fingerprint to dev. branch version 1.0.3 (the link is in the second post).

You may need to pair the device once again to HE after manually updating the driver.

1 Like
18

I connected one sensor, which was sleeping in the warehouse, to HE.
It doesn't seem to work for my amortization.
--> Now it's working.

Current States

  • powerSource : battery

  • presence : present

  • endpointId: 01

  • application: 40

  • manufacturer: _TYZB01_dsjszp0x

  • model: TS0205

Summary

State Variables

  • packetID : 0
  • rxCounter : 2
  • hashStringPars : bdbdbdbdbdbdbdbdbdbdbd
  • isDigital : true
  • driverVersion : 1.0.3 2022/12/15 7:00 AM
  • txCounter : 2
  • notPresentCounter : 0
  • lastBattery : 0
  • motionStarted : 1671630879798
  • model : TS0205

dev:4252022-12-21 11:07:25.844 PMinfoSmoke Detector smoke is clear

dev:4252022-12-21 11:07:24.493 PMinfoSmoke Detector smoke is detected

dev:4252022-12-21 11:07:22.910 PMinfoSmoke Detector smoke is tested

dev:4252022-12-21 11:07:11.379 PMdebugSmoke Detector sendZigbeeCommands (cmd=[he raw 0xDBF9 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200])

dev:4252022-12-21 11:07:11.320 PMinfoSmoke Detector configure()..

dev:4252022-12-21 11:07:11.319 PMinfoupdated()...

dev:4252022-12-21 11:07:11.318 PMinfoSmoke Detector Debug logging will be automatically switched off after 24 hours

dev:4252022-12-21 11:07:11.270 PMinfoSmoke Detector Debug logging is true Description text logging is true

dev:4252022-12-21 11:07:11.269 PMinfoUpdating Smoke Detector (Smoke Detector) model TS0205

dev:4252022-12-21 11:07:03.574 PMwarnSmoke Detector received unhandled event battery = 100.0

dev:4252022-12-21 11:07:03.570 PMdebugSmoke Detector description is read attr - raw: DBF901000108210020C8, dni: DBF9, endpoint: 01, cluster: 0001, size: 08, attrId: 0021, encoding: 20, command: 0A, value: C8

dev:4252022-12-21 11:06:33.342 PMwarnSmoke Detector Unprocesed unknown command: cluster=null command=null attrId=null value=null data=null

dev:4252022-12-21 11:06:33.341 PMdebugSmoke Detector Desc Map: [:]

dev:4252022-12-21 11:06:33.338 PMdebugSmoke Detector description is zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000

dev:4252022-12-21 11:06:33.331 PMinfoSmoke Detector Received device announcement, data=[85, F9, DB, 92, CF, CC, FE, FF, 72, 02, 5C, 80] (Sequence Number:85, Device network ID: DBF9, Capability Information: 80)

dev:4252022-12-21 11:06:33.328 PMdebugSmoke Detector Desc Map: [raw:catchall: 0000 0013 00 00 0040 00 DBF9 00 00 0000 00 00 85F9DB92CFCCFEFF72025C80, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:DBF9, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[85, F9, DB, 92, CF, CC, FE, FF, 72, 02, 5C, 80]]

dev:4252022-12-21 11:06:33.326 PMdebugSmoke Detector description is catchall: 0000 0013 00 00 0040 00 DBF9 00 00 0000 00 00 85F9DB92CFCCFEFF72025C80

dev:4252022-12-21 11:06:32.926 PMdebugSmoke Detector sendZigbeeCommands (cmd=[he raw 0xDBF9 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200])

dev:4252022-12-21 11:06:32.876 PMinfoSmoke Detector configure()..

dev:4252022-12-21 11:05:23.333 PMinfoSmoke Detector smoke is clear

dev:4252022-12-21 11:05:19.517 PMinfoSmoke Detector smoke is detected

dev:4252022-12-21 11:05:15.710 PMinfoSmoke Detector smoke is tested

dev:4252022-12-21 11:01:28.789 PMinfoSmoke Detector smoke is clear

dev:4252022-12-21 11:00:30.001 PMwarnSmoke Detector Unprocesed unknown command: cluster=null command=null attrId=null value=null data=null

dev:4252022-12-21 11:00:30.000 PMdebugSmoke Detector Desc Map: [:]

dev:4252022-12-21 11:00:29.997 PMdebugSmoke Detector description is zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000

dev:4252022-12-21 10:59:59.395 PMwarnSmoke Detector received unhandled event battery = 100.0

dev:4252022-12-21 10:59:59.391 PMdebugSmoke Detector description is read attr - raw: 310A01000108210020C8, dni: 310A, endpoint: 01, cluster: 0001, size: 08, attrId: 0021, encoding: 20, command: 0A, value: C8

dev:4252022-12-21 10:59:29.146 PMwarnSmoke Detector Unprocesed unknown command: cluster=null command=null attrId=null value=null data=null

dev:4252022-12-21 10:59:29.145 PMdebugSmoke Detector Desc Map: [:]

dev:4252022-12-21 10:59:29.143 PMdebugSmoke Detector description is zone status 0x0004 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000

dev:4252022-12-21 10:59:29.136 PMinfoSmoke Detector Received device announcement, data=[84, 0A, 31, 92, CF, CC, FE, FF, 72, 02, 5C, 80] (Sequence Number:84, Device network ID: 310A, Capability Information: 80)

dev:4252022-12-21 10:59:29.133 PMdebugSmoke Detector Desc Map: [raw:catchall: 0000 0013 00 00 0040 00 310A 00 00 0000 00 00 840A3192CFCCFEFF72025C80, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:310A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[84, 0A, 31, 92, CF, CC, FE, FF, 72, 02, 5C, 80]]

dev:4252022-12-21 10:59:29.129 PMdebugSmoke Detector description is catchall: 0000 0013 00 00 0040 00 310A 00 00 0000 00 00 840A3192CFCCFEFF72025C80

dev:4252022-12-21 10:59:28.756 PMdebugSmoke Detector sendZigbeeCommands (cmd=[he raw 0x310A 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200])

dev:4252022-12-21 10:59:28.696 PMinfoSmoke Detector configure()..

dev:4252022-12-21 10:59:00.423 PMwarnSmoke Detector received unhandled event battery = 100.0

dev:4252022-12-21 10:59:00.419 PMdebugSmoke Detector description is read attr - raw: CC2E01000108210020C8, dni: CC2E, endpoint: 01, cluster: 0001, size: 08, attrId: 0021, encoding: 20, command: 0A, value: C8

dev:4252022-12-21 10:58:30.241 PMdebugSmoke Detector Model is : TS0205

dev:4252022-12-21 10:58:30.240 PMdebugSmoke Detector Tuya check-in message (attribute 0001 reported: 40)

dev:4252022-12-21 10:58:30.239 PMdebugSmoke Detector zclVersion is : 03

dev:4252022-12-21 10:58:30.238 PMdebugSmoke Detector Manufacturer is : _TYZB01_dsjszp0x

dev:4252022-12-21 10:58:30.235 PMdebugSmoke Detector Desc Map: [raw:CC2E01000064040042105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86, dni:CC2E, endpoint:01, cluster:0000, size:64, attrId:0004, encoding:42, command:01, value:_TYZB01_dsjszp0x, clusterInt:0, attrInt:4, additionalAttrs:[[value:03, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:40, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:TS0205, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]]

dev:4252022-12-21 10:58:30.229 PMwarnexception caught while parsing description: read attr - raw: CC2E01000064040042105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86, dni: CC2E, endpoint: 01, cluster: 0000, size: 64, attrId: 0004, encoding: 42, command: 01, value: 105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86

dev:4252022-12-21 10:58:30.223 PMdebugSmoke Detector description is read attr - raw: CC2E01000064040042105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86, dni: CC2E, endpoint: 01, cluster: 0000, size: 64, attrId: 0004, encoding: 42, command: 01, value: 105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86

dev:4252022-12-21 10:58:30.211 PMwarnSmoke Detector Unprocesed unknown command: cluster=null command=null attrId=null value=null data=null

dev:4252022-12-21 10:58:30.209 PMdebugSmoke Detector Desc Map: [:]

dev:4252022-12-21 10:58:30.207 PMdebugSmoke Detector description is zone status 0x0004 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000

dev:4252022-12-21 10:58:30.173 PMinfoSmoke Detector Received device announcement, data=[83, 2E, CC, 92, CF, CC, FE, FF, 72, 02, 5C, 80] (Sequence Number:83, Device network ID: CC2E, Capability Information: 80)

dev:4252022-12-21 10:58:30.166 PMdebugSmoke Detector Desc Map: [raw:catchall: 0000 0013 00 00 0040 00 CC2E 00 00 0000 00 00 832ECC92CFCCFEFF72025C80, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:CC2E, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[83, 2E, CC, 92, CF, CC, FE, FF, 72, 02, 5C, 80]]

dev:4252022-12-21 10:58:30.163 PMdebugSmoke Detector description is catchall: 0000 0013 00 00 0040 00 CC2E 00 00 0000 00 00 832ECC92CFCCFEFF72025C80

dev:4252022-12-21 10:58:29.974 PMdebugSmoke Detector sendZigbeeCommands (cmd=[he raw 0xCC2E 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200])

dev:4252022-12-21 10:58:29.936 PMinfoSmoke Detector configure()..

dev:4252022-12-21 10:55:07.905 PMdebugSmoke Detector Model is : TS0205

dev:4252022-12-21 10:55:07.903 PMdebugSmoke Detector Tuya check-in message (attribute 0001 reported: 40)

dev:4252022-12-21 10:55:07.902 PMdebugSmoke Detector zclVersion is : 03

dev:4252022-12-21 10:55:07.900 PMdebugSmoke Detector Manufacturer is : _TYZB01_dsjszp0x

dev:4252022-12-21 10:55:07.886 PMdebugSmoke Detector Desc Map: [raw:038601000064040042105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86, dni:0386, endpoint:01, cluster:0000, size:64, attrId:0004, encoding:42, command:01, value:_TYZB01_dsjszp0x, clusterInt:0, attrInt:4, additionalAttrs:[[value:03, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:40, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:TS0205, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]]

dev:4252022-12-21 10:55:07.879 PMwarnexception caught while parsing description: read attr - raw: 038601000064040042105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86, dni: 0386, endpoint: 01, cluster: 0000, size: 64, attrId: 0004, encoding: 42, command: 01, value: 105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86

dev:4252022-12-21 10:55:07.868 PMdebugSmoke Detector description is read attr - raw: 038601000064040042105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86, dni: 0386, endpoint: 01, cluster: 0000, size: 64, attrId: 0004, encoding: 42, command: 01, value: 105F54595A4230315F64736A737A7030780000002003010000204005000042065453303230350700003003FEFF86

dev:4252022-12-21 10:55:07.158 PMdebugSmoke Detector sendZigbeeCommands (cmd=[he raw 0x0386 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200])

dev:4252022-12-21 10:55:07.094 PMinfoSmoke Detector configure()..

dev:4252022-12-21 10:55:07.093 PMinfoupdated()...

dev:4252022-12-21 10:55:07.091 PMinfoSmoke Detector Debug logging will be automatically switched off after 24 hours

dev:4252022-12-21 10:55:07.062 PMinfoSmoke Detector Debug logging is true Description text logging is true

dev:4252022-12-21 10:55:07.061 PMinfoUpdating Smoke Detector (Tuya Multi Sensor 4 In 1) model TS0205

dev:4252022-12-21 10:55:06.849 PMwarnSmoke Detector received unhandled event battery = 100.0

dev:4252022-12-21 10:55:06.840 PMtrace destinationEP = 01

dev:4252022-12-21 10:55:06.838 PMtrace model = TS0205

dev:4252022-12-21 10:55:06.824 PMinfoSmoke Detector InitializeVars()... fullInit = false

dev:4252022-12-21 10:55:06.818 PMdebugupdating the settings from the current driver version 1.0.15 2022/11/28 7:48 AM to the new version 1.0.3 2022/12/15 7:00 AM

dev:4252022-12-21 10:55:06.815 PMdebugSmoke Detector description is read attr - raw: 038601000108210020C8, dni: 0386, endpoint: 01, cluster: 0001, size: 08, attrId: 0021, encoding: 20, command: 0A, value: C8

dev:4252022-12-21 10:54:41.673 PMinfoTuya Multi Sensor 4 In 1 Received bind response, data=[4F, 00] (Sequence Number:4F, Status: Success)

dev:4252022-12-21 10:54:41.670 PMdebugTuya Multi Sensor 4 In 1 parse(_TYZB01_dsjszp0x) descMap = [raw:catchall: 0000 8021 00 00 0040 00 0386 00 00 0000 00 00 4F00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0386, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4F, 00]]

dev:4252022-12-21 10:54:41.661 PMinfoTuya Multi Sensor 4 In 1 Received bind response, data=[53, 8C] (Sequence Number:53, Status: Failure)

dev:4252022-12-21 10:54:41.658 PMdebugTuya Multi Sensor 4 In 1 parse(_TYZB01_dsjszp0x) descMap = [raw:catchall: 0000 8021 00 00 0040 00 0386 00 00 0000 00 00 538C, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0386, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[53, 8C]]

dev:4252022-12-21 10:54:41.649 PMinfoTuya Multi Sensor 4 In 1 Received bind response, data=[50, 00] (Sequence Number:50, Status: Success)

dev:4252022-12-21 10:54:41.641 PMdebugTuya Multi Sensor 4 In 1 parse(_TYZB01_dsjszp0x) descMap = [raw:catchall: 0000 8021 00 00 0040 00 0386 00 00 0000 00 00 5000, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0386, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[50, 00]]

dev:4252022-12-21 10:54:40.318 PMdebugTuya Multi Sensor 4 In 1 write attribute response is FAILURE

dev:4252022-12-21 10:54:40.314 PMdebugTuya Multi Sensor 4 In 1 parse(_TYZB01_dsjszp0x) descMap = [raw:catchall: 0104 0000 01 01 0040 00 0386 00 00 0000 04 01 86DEFF, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0386, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[86, DE, FF]]

dev:4252022-12-21 10:54:39.721 PMinfoTuya Multi Sensor 4 In 1 installed()

Show more...

1 Like
19

It shouldn't! :slight_smile:
This driver does not have any code to support the standard IAS zone smoke detectors... It is made for Tua specific cluster 0xEF00 only.

You can try the HE built-in driver, or search of HEIMAN smoke detector driver.

1 Like
20

Oh! That's amazing. I remember that there was a notification from the speaker when PC Devices tested. I'll try again, and I'll have to apply another dth.