I understood all your explanations.
I changed it to Device and proceeded with the process you explained.
Now, no preferences defined for this device
I paired it again, and the picture below is the current state.
Now you need to switch back to the Heiman Zigbee Smoke Detector driver and press Configure or Initialize button.
1 Like
This is the picture after applying the new DTH and pairing it again.
Summary
dev:4252022-12-22 03:39:12.314 PMdebugBattery Attribute 0x0021 Received
dev:4252022-12-22 03:39:10.365 PMdebugModel is TS0205
dev:4252022-12-22 03:39:08.389 PMdebugManufacturer is _TYZB01_dsjszp0x
dev:4252022-12-22 03:39:06.317 PMdebugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x01, data: [0x33, 0x00, 0x86], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0x9742, isClusterSpecific: false, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x01, clusterId: 0x0001, destinationEndpoint: 0x01, options: 0x0040)
dev:4252022-12-22 03:39:04.301 PMdebugBattery level is 100% (3 Volts)
dev:4252022-12-22 03:39:02.275 PMdebugSmoke Detector is Battery Powered
dev:4252022-12-22 03:39:00.259 PMdebugSmartShield(text: null, manufacturerId: 0x0000, direction: 0x01, data: [0x00, 0x00, 0x86], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0x9742, isClusterSpecific: false, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x01, clusterId: 0x0502, destinationEndpoint: 0x01, options: 0x0040)
dev:4252022-12-22 03:38:58.232 PMdebugUnknown --> Cluster-> 0500 AttrInt-> 2 Value-> 0000
dev:4252022-12-22 03:38:56.209 PMdebugZone State is enrolled
dev:4252022-12-22 03:38:54.185 PMdebugZone Type is Fire Sensor
dev:4252022-12-22 03:38:42.073 PMdebugSmoke Detector all clear
dev:4252022-12-22 03:38:41.612 PMdebugRefreshing...
dev:4252022-12-22 03:38:41.609 PMdebugConfiguring...
dev:4252022-12-22 03:38:07.708 PMdebugRefreshing...
dev:4252022-12-22 03:38:03.300 PMdebugRefreshing...
dev:4252022-12-22 03:37:45.940 PMdebugRefreshing...
dev:4252022-12-22 03:37:42.044 PMdebugRefreshing...
dev:4252022-12-22 03:37:42.032 PMdebugSmoke Detector Setting Battery Last Replaced to Current date for newly paired sensor
dev:4252022-12-22 03:37:42.025 PMdebugConfiguring...
dev:4252022-12-22 03:31:28.646 PMinfoZigbee parsed:[raw:D60A01000108210020C8, dni:D60A, endpoint:01, cluster:0001, size:08, attrId:0021, encoding:20, command:0A, value:C8, clusterInt:1, attrInt:33]
dev:4252022-12-22 03:31:00.926 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0500", outClusters:"0003,0019", model:"TS0205", manufacturer:"_TYZB01_dsjszp0x"
dev:4252022-12-22 03:31:00.398 PMtraceZCL version:03
dev:4252022-12-22 03:31:00.376 PMtraceSoftware Build Id:unknown
dev:4252022-12-22 03:31:00.375 PMtraceModel:TS0205
dev:4252022-12-22 03:31:00.373 PMtraceManufacturer:_TYZB01_dsjszp0x
dev:4252022-12-22 03:31:00.113 PMdebuggetting info for unknown Zigbee device...
dev:4252022-12-22 03:30:58.393 PMinfoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:4252022-12-22 03:30:58.340 PMinfoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 D60A 00 00 0000 00 00 840AD692CFCCFEFF72025C80, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:D60A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[84, 0A, D6, 92, CF, CC, FE, FF, 72, 02, 5C, 80]]
1 Like
As you said, the previous driver seems to have been sorted out perfectly.
Thank you. I'm going to organize this and post it on the IOT Internet cafe.
By the way, I don't smoke. I think I'll have to wait for a customer to smoke.
1 Like
Hi, Can you please add support for manufakture _TZ3000_r6buo8ba?
Hi @user3186 ,
_TZ3000_r6buo8ba should be a power reporting smart plug, it is supported in this driver.
1 Like
does anyone know if there is a way I can test the alarm for Ts0601 please? it looks like this can be done if the alarm is connected through their own gateway?
there is no button on the body of the device to test either
If you have any details on how this is done using the Tuya gateway, please let me know. Do you have any PDFs or YouTube videos showing some details?
Have in mind, that there are at least 5-6 different 'TS0601' smoke alarms, so your device may be different.
I don't have a Tuya gateway. But in the instruction manual that was it says it can do through the app
my is
- endpointId: 01
- application: 48
- inClusters: 0004,0005,EF00,0000
- manufacturer: _TZE200_ntcy3xu1
- model: TS0601
- outClusters: 0019,000A
- softwareBuild:
What Tuya app ( SmartLife ) does is to simply show on the mobile phone screen 'Smoke Detected' when the button is pressed.
This is a real alarm test and will activate all of the notifications, sirens, alarms, etc.. that you may have configured in Hubitat.
What we need is probably a combination of an Hubitat app (or simply set of HE dashboard tiles?) that will put all the smoke detectors in a virtual testing mode for a time limited period. During this testing period, the driver will generate not a real 'smoke detected' event, but 'smoke tested' when the test button is activated or even better, when a real smoke test is performed. The testing mode should be terminated either from a button on the app or by timeout (10 minutes maximum time for testing, then the smoke detectors will be armed again).
Does anything like this exist already for other (non-Tuya) smoke/gas alarm sensors?
"Tuya Zigbee Smoke Detector" driver was updated to ver. 1.1.0 via HPM :
- extended tuyaMagic (hopefully activates check-in every 4 hours);
- added capability 'Health Check';
- added ping() command and rtt measurement;
The previously misused Presence capability is now removed and replaced with the healthStatus (online/offline) attribute.
1 Like
I would like to thank you for the tuya zigbee driver, the Tuya zigbee smoke detector works really well, only thing I had to do is when I paired the smoke detector, I had to put the smoke detector on top of the hubitat hub whiles it was pairing so it would pair properly, I had to do that with the Tuya zigbbe motion sensor as well, I have wrote a rule so when the smoke detector detects smoke my Danalock will unlock automatically if I'm home,
1 Like
The First Alert Smoke/CO detectors send a “test” message when pushing the test button.
2 Likes
Hi please can you help I have 2 AwoX bulbs and they have worked fine for 2 years on my Hubitat 5 hub, I have upgraded to Hubitat 8 2 days ago and worked fine but today both bulbs have stopped working, I've tried to repair them and they show up but they won't turn off or on. Thanks Tim
Hi Tim,
AwoX bulbs use Bluetooth communication... How were yours integrated to Hubitat?
As this thread is dedicated to Tuya Zigbee smoke detectors, it may be a good idea if you create a new thread for these bulbs, so there will be a better chance for more people to see it and respond.
Hi ,Thank you for you reply, the bulbs definitely are zigbee, they been working on the c5 hub, its only since I've upgraded to c8, I've just removed the bulbs from the hub and added them again but the bulbs will not come out of pairing mode.
There are still hiccups with some Zigbee devices pairing as a side effect of the new Zigbee 3.0 chip support in C-8 …
Hopefully these will be fixed in future HE platform updates.
1 Like
Yes hopefully, thank you again for your help, it is greatly appreciated.
1 Like
Hi @kkossev ,
Using your driver latest version 1.1.0 dated 7/4/23.
I am getting these error messages:
I am on the latest hub version 2.3.5.131
And the device details are:
I can not say the error message was not there before but I did not remember seeing them
1 Like
Thank you for the report, @amithalp !
You can try the fix in the version 1.1.1 and let me know if the error is gone.
Also, please check the Events history - is your Smoke Detector reported as offline periodically or not?
