frient Intelligent Smoke Alarm | Wireless Fire Sensor | Instant Notification | EN 14604 | Battery-Powered | Consumer Electronics | Zigbee | Works with SmartThings and Homey

Product Information

Keep your family safe with this battery operated Zigbee smoke alarm. The detector is equipped with the latest Zigbee protocol to make you alerted of the danger via Smart Life app on your phone wherever you are. The sensor can also be used in Smart Life automation scenarios e.g. switching off your gas supply (using our WIFI Smart Shut-Off Valve) when the smoke is detected.

Zigbee is expecting to sell around 4 billion chipsets by the year 2023, expanding its presence in over 37 countries globally. So, it's pretty safe to say that Zigbee-enabled devices are quite widely used. dev:4252022-12-21 10:54:41.658 PM debugTuya 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]]

Specifications

dev:4252022-12-21 10:55:06.818 PM debugupdating 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 Upgrading your smoke detectors may seem like a daunting task. Because there aren’t very many options to choose from, the decision is even harder. Do you choose one that ties in directly with SmartThings or one that requires a subscription? Do you choose to bypass SmartThings altogether and choose a smart one through a popular brand? dev:4252022-12-21 11:06:33.338 PM debugSmoke Detector description is zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000 Accurate, Reliable & Highly Sensitive Alarm: Equipped with photoelectric smoke sensor; detects both fast and slow-burning fires, and instantly notifies you by sound and app message when dangerous smoke is detected while minimizing false alarms

Regarding the alarm when I’m not at home. I certainly aware that sometimes a room can burn down in a few minutes. Too many developers tend to implement features in custom clusters or attributes even though the equivalent feature exists in the standard Zigbee Cluster Library specification. dev:4252022-12-21 10:55:06.815 PM debugSmoke Detector description is read attr - raw: 038601000108210020C8, dni: 0386, endpoint: 01, cluster: 0001, size: 08, attrId: 0021, encoding: 20, command: 0A, value: C8Meanwhile there is a real situation, but you turned off the alarm in the low level state, and things get worse in a few minutes and alarm goes into a full blast smoke alarm state. That few minutes is enough to burn down a whole room. Or the CO to kill somebody in sleep. Smoke, CO alarm goes off, but the level is small, and the software would allow you to silence it being away, without seeing what is the real situation next to the smoke detector. Even worse, you would set an automation to turn it off automatically because you deem there are far too many false positives. dev:4252022-12-21 10:58:30.223 PM debugSmoke 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:59:29.133 PM debugSmoke 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]] An LED rings the middle of the alarm and changes color based on the alarm's status. Green and blue indicate that the alarm is starting up or in pairing mode. Yellow means there's a malfunction or a low battery, while red means there's a fire or smoke condition.In Z2M, it is identified as model HS1SA with different ZigBee IDs depending on which version you have: dev:4252022-12-21 10:54:41.670 PM debugTuya 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 11:06:32.926 PM debugSmoke 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])

My understanding is that the Satellite Units should still wirelessly trigger the Relay Modules via the Hard-wired Co-ordinator Pigtail. (just waiting for confirmation from Kidde Support to validate that, but intuitively appears to sound like the case)The EN14604 certificate it possesses further solidifies its case a solid product. This tells me that the Heiman Smoke Sensor is not some cheap Chinese junk, but a product that the company went out of it’s way to certify and prepare for western markets. I Intend to dig a little deeper about this company in a future article. dev:4252022-12-21 10:55:07.091 PM infoSmoke Detector Debug logging will be automatically switched off after 24 hours