Just for your info:
https://bestow-regional.api.smartthings.com/invite/akMXvzDBLlb3
They include an appropriate drive for that device
edit At least sometimes it recognizes that device as smoke detector, just tested again and it shows a Z-Device. Seems, sometimes the model data is not transfered
Try installing this driver version and then
Uninstall device with app and reinstall device with app
───────────────────────────────────────────────────
Name Zigbee Smoke/CO Detector Mc
Version 2023-08-25T15:06:07.852034853
───────────────────────────────────────────────────
Are your device good metrics signals?
To see the fingerprints, Please post a screenshot from device data in my.smartthings.com, do not post the link
I got the solution (shame on me):
Just get closer to the hub and the devices are integrated without probs. The appropriate driver is found
under Samsung account (as I mentioned above)
Thanks anyway!
Hi Mariano,
It seems so, see picture
The only issue I have is, when testing the CO device it is not received by the hub and routines are not activated.
That is not what I understood in your previous post.
If the capability co detector is not activated in the app it is different.
If it does not activate and deactivate you will have to send me logs with the cli so that I can analyze it
Hi,
It paired directly. It has been going on/offline every 2 hours. I deleted the device and readded it, but it is still doing the same (online/offline every 2 h). Is it a just feature or can it be fixed?
What device is it, fingerprints?
I don’t know what is happening with the smoke detectors, that there are several new users that are marked offline, it gives the impression that they are not being configured correctly.
I would like someone who remains offline to send me some logs of the pairing of the device to see what happens in the configuration and to be able to analyze what is happening
It is the Nedis CO detector Heiman Smoke Sensor Only Being Detected as "Thing" - #49 by Ville_Rahkonen.
Where can I collect the log data? I could try to get it…
This is a tutorial to install CLI and capture logs
It would be interesting to capture the log when the device is being paired, leaving the CLI window ready for the see driver logs and pairing the device with the app, about 3 minutes of log.
Then, without touching anything, when the device stops sending information, it will send a health message every 30 sec and every 3 minutes a detector status message should arrive. Capture about 7 minutes
Hi Antoine,
I need the CLI logs when the device is paired.
Hi @KimNissen
Added to this driver version, try if it works.
I saw some problems in others platforms for this device
───────────────────────────────────────────────────
Name Zigbee Smoke/CO Detector Mc
Version 2023-08-28T19:51:21.264491082
───────────────────────────────────────────────────
- id: "Heiman/SMOK_YDLV10"
deviceLabel: HEIMAN Smoke Detector
manufacturer: Heiman
model: SMOK_YDLV10
deviceProfileName: smoke-battery
Thanks and all 5 smoke sensors are now discovered and paired perfectly with the the driver when scanning for new device in the app - uninstalled and installed the driver before device reset and scan. Seems like they all change to offline state, after approx. 2-3 hours. When testing smoke-activity manually (pressing test on devices), they wake up, get online, and activate controls in SmartThings as expected. Might be something related to the devices running ZigBee version 1.x - all 5 behaves in regards to offline / online the exact same way…The old IDE driver could “keep” them all in an online state, so the Home Security did not notice 5 x offline issues in the fire controls… They work and starts alarms, so the main purpose is fulfilled - if we can somehow manage the offline/online state, it would be great… otherwise a handful of newer devices might be the next step for me 
THANKS FOR ENABLING the smoke detection, because that works…
Try installing this driver version
Uninstall devices and reinstall devices with new driver version for devices configure
───────────────────────────────────────────────────
Name Zigbee Smoke/CO Detector Mc
Version 2023-08-29T10:40:47.14600191
───────────────────────────────────────────────────
Thanks a million - driver updated, devices removed and installed with the recent driver. I’ll slip a status later today… You’re a king and working perfectly or not, I appreciate your efforts…
All 5 discovered perfectly and all 5 is online as hoped for since 8 hours now. So, it looks like all works very well…
THANKS 
Hi Mariano,
Ofcourse, no problem. In the meantime I added 3 smoke detectors.
Best regards,
Antoine
? Select a driver. 12
connecting… connected
2023-08-30T12:42:07.958998999+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:42:35.892482003+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:42:35.893601669+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: a4e860e8-40ed-48c0-baca-cbc8611594ef [0x44AC] (Rookmelder hal)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x44AC, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCE, rssi: -58, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x42, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2023-08-30T12:42:35.918433003+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-30T12:42:35.919269336+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2023-08-30T12:42:35.922018003+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: a4e860e8-40ed-48c0-baca-cbc8611594ef [0x44AC] (Rookmelder hal)> emitting event: {“component_id”:“main”,“capability_id”:“smokeDetector”,“state”:{“value”:“clear”},“attribute_id”:“smoke”}
2023-08-30T12:42:35.924898003+00:00 DEBUG Zigbee Smoke/CO Detector Mc Rookmelder hal device thread event handled
2023-08-30T12:42:37.961420670+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:43:07.965802690+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:43:37.971036704+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:43:49.601665710+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:43:49.602854376+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: b4fe0d43-c9cb-4c50-89c2-c0736a676bda [0xA24C] (Rookmelder 2de verdieping)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xA24C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCE, rssi: -58, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x6A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2023-08-30T12:43:49.624647710+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-30T12:43:49.625477376+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2023-08-30T12:43:49.627173710+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: b4fe0d43-c9cb-4c50-89c2-c0736a676bda [0xA24C] (Rookmelder 2de verdieping)> emitting event: {“component_id”:“main”,“capability_id”:“smokeDetector”,“state”:{“value”:“clear”},“attribute_id”:“smoke”}
2023-08-30T12:43:49.677123376+00:00 DEBUG Zigbee Smoke/CO Detector Mc Rookmelder 2de verdieping device thread event handled
2023-08-30T12:43:57.089955713+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:43:57.099775380+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: 0e043bde-2d32-45a5-ae0b-4af519ac13a2 [0x6A43] (Trust CO Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A43, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD2, rssi: -61, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x5E, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0021, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
2023-08-30T12:43:57.221215380+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector → Co Detector
2023-08-30T12:43:57.222197380+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2023-08-30T12:43:57.227527713+00:00 PRINT Zigbee Smoke/CO Detector Mc <<< ias_zone_status_change_handler >>>>
2023-08-30T12:43:57.229811713+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: 0e043bde-2d32-45a5-ae0b-4af519ac13a2 [0x6A43] (Trust CO Detector)> emitting event: {“component_id”:“main”,“capability_id”:“carbonMonoxideDetector”,“state”:{“value”:“detected”},“attribute_id”:“carbonMonoxide”}
2023-08-30T12:43:57.253236380+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: 0e043bde-2d32-45a5-ae0b-4af519ac13a2 [0x6A43] (Trust CO Detector)> emitting event: {“component_id”:“main”,“capability_id”:“legendabsolute60149.signalMetrics”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/08/30 Time: 12:43
DNI: 0x6A43 LQI: 210 RSSI: -61dbm
”},“visibility”:{“displayed”:false},“attribute_id”:“signalMetrics”}
2023-08-30T12:43:57.269252380+00:00 DEBUG Zigbee Smoke/CO Detector Mc Trust CO Detector device thread event handled
2023-08-30T12:43:58.000026380+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:43:58.006539714+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: 0e043bde-2d32-45a5-ae0b-4af519ac13a2 [0x6A43] (Trust CO Detector)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A43, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0x76, rssi: -53, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x5F, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0020, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
2023-08-30T12:43:58.059173047+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector → Co Detector
2023-08-30T12:43:58.060029047+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2023-08-30T12:43:58.061747380+00:00 PRINT Zigbee Smoke/CO Detector Mc <<< ias_zone_status_change_handler >>>>
2023-08-30T12:43:58.066397714+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: 0e043bde-2d32-45a5-ae0b-4af519ac13a2 [0x6A43] (Trust CO Detector)> emitting event: {“component_id”:“main”,“capability_id”:“carbonMonoxideDetector”,“state”:{“value”:“clear”},“attribute_id”:“carbonMonoxide”}
2023-08-30T12:43:58.079878047+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: 0e043bde-2d32-45a5-ae0b-4af519ac13a2 [0x6A43] (Trust CO Detector)> emitting event: {“component_id”:“main”,“capability_id”:“legendabsolute60149.signalMetrics”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/08/30 Time: 12:43
DNI: 0x6A43 LQI: 118 RSSI: -53dbm
”},“visibility”:{“displayed”:false},“attribute_id”:“signalMetrics”}
2023-08-30T12:43:58.143556714+00:00 DEBUG Zigbee Smoke/CO Detector Mc Trust CO Detector device thread event handled
2023-08-30T12:44:07.979841718+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:44:14.230457055+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:44:14.231891055+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: cfa22fc5-65ec-49c4-8772-1d65df95496e [0x81CE] (Rookmelder 1ste verdieping)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x81CE, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD2, rssi: -57, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x13, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2023-08-30T12:44:14.266832388+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-30T12:44:14.267647721+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2023-08-30T12:44:14.269497055+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: cfa22fc5-65ec-49c4-8772-1d65df95496e [0x81CE] (Rookmelder 1ste verdieping)> emitting event: {“component_id”:“main”,“capability_id”:“smokeDetector”,“state”:{“value”:“clear”},“attribute_id”:“smoke”}
2023-08-30T12:44:14.318415722+00:00 DEBUG Zigbee Smoke/CO Detector Mc Rookmelder 1ste verdieping device thread event handled
2023-08-30T12:44:37.990030733+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:45:01.100260410+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:45:01.101375410+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: b4fe0d43-c9cb-4c50-89c2-c0736a676bda [0xA24C] (Rookmelder 2de verdieping)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xA24C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xD0, rssi: -58, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x6B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0021, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
2023-08-30T12:45:01.174698744+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-30T12:45:01.184266744+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2023-08-30T12:45:01.193485077+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: b4fe0d43-c9cb-4c50-89c2-c0736a676bda [0xA24C] (Rookmelder 2de verdieping)> emitting event: {“component_id”:“main”,“capability_id”:“legendabsolute60149.signalMetrics”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/08/30 Time: 12:45
DNI: 0xA24C LQI: 208 RSSI: -58dbm
”},“visibility”:{“displayed”:false},“attribute_id”:“signalMetrics”}
2023-08-30T12:45:01.224287077+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: b4fe0d43-c9cb-4c50-89c2-c0736a676bda [0xA24C] (Rookmelder 2de verdieping)> emitting event: {“component_id”:“main”,“capability_id”:“battery”,“state”:{“value”:100},“attribute_id”:“battery”}
2023-08-30T12:45:01.225799744+00:00 DEBUG Zigbee Smoke/CO Detector Mc Rookmelder 2de verdieping device thread event handled
2023-08-30T12:45:07.995020414+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-30T12:45:35.433491094+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-30T12:45:35.434888094+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: a4e860e8-40ed-48c0-baca-cbc8611594ef [0x44AC] (Rookmelder hal)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x44AC, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC6, rssi: -57, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x43, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0020 > > > >
2023-08-30T12:45:35.449647427+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-30T12:45:35.459020760+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2023-08-30T12:45:35.460784760+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: a4e860e8-40ed-48c0-baca-cbc8611594ef [0x44AC] (Rookmelder hal)> emitting event: {“component_id”:“main”,“capability_id”:“smokeDetector”,“state”:{“value”:“clear”},“attribute_id”:“smoke”}
2023-08-30T12:45:35.464672094+00:00 DEBUG Zigbee Smoke/CO Detector Mc Rookmelder hal device thread event handled
2023-08-30T12:45:38.003603761+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
I’m glad it works well