Heiman (Nedis) Gas sensor Zigbee

Devices & Integrations
1

I bought this sensor which supports zigbee 3.0 and as I found the device in the list with available Edge drivers, I expected it to be recognized.
However after installing the driver and adding it to ST it is only recognized as ‘standard Zigbee device’.
I expect that Heiman has introduced a new version of this detector.
Model seems to be TS0204 and the presentation ID is bc813f60-efa1-3d89-896d-93ef64cf89c8
What should I do to get the device recognized as a working gas detector?

2

Did you check from device menu that it´s using the correct driver and not some random driver?

3

Yes. If I change the driver than I get the error message: “Error changing device driver to “Zigbee Smoke/CO Detector Mc”. Ensure that the driver you are trying to change to has a valid fingerprint match with this device”.

Other users seem to be using this Smoke/CO detector driver for the Heiman Gas detector…

4

Could you install Zigbee Thing Mc driver.
Using Zigbee Thing Mc driver is possible to read exact model and manufacturer.
Then it is possible to check which driver is supporting your device.

manufacturer:
model:
Server Cluster:
Client Cluster:

You can install Zigbee Thing Mc driver from Mariano’s Edge drivers Shared Channel
https://api.smartthings.com/invitation-web/accept?id=6b68563b-1905-4654-8d2b-e677a2997424

5

I have installed the Zigbee Thing MC driver.
When looking at the activity info I get the following:

DeviceInfo:

Manufacturer: _TYZB01_mfccmeio
Model: TS0204
FingerPrinted_EndPoint.Id: 0x01
App Version: 0x45
ZCL Version: 0x02
Network ID: 0xBF26
Zigbee EUI: 84FD27FFFEA6958F
Device ID: e1bd114c-d91e-4eaa-bbd6-1bd09df9a144

Server Cluster:
Ep: 0x01={ 0000,0003,0500 }

Client Clusters:
Ep: 0x01={ 0003,0019 }

Signal Metrics:
LQI: 94 … RSSI: -104 dbm

6

Hi @Arnout

Added to this driver version as Gas detector profile.
Is the first Gas detector added to this driver

───────────────────────────────────────────────────
 Name         Zigbee Smoke/CO Detector Mc
 Version      2023-08-15T11:03:19.684470003        
───────────────────────────────────────────────────
- id: "TS0204/_TYZB01_mfccmeio"
    deviceLabel: TS0204 Gas Sensor
    manufacturer: _TYZB01_mfccmeio
    model: TS0204
    deviceProfileName: gas-detector

Thanks @TapioX

7

That is fantastic Mariano! Many thanks!
I am currently travelling, but I will try it out tomorrow when I return back home.
What should I do to get this refreshed driver?

8

The driver will automatically update within 12 hours of release.

2 Likes
9

Hi Mariano, the updated driver “Zigbee Smoke/CO Detector Mc” is now active for my device, but it doesn’t work yet.
When selecting the device I get the message: “This device hasn’t updated all status information yet. Please try again later”. Same message if I wait 30 minutes.
I have also removed the device from the hub and included it again, but the behaviour is the same. I see no change in status when I press the test button on the gas detector.

IMG_1570
IMG_15701179×2300 105 KB

10

Hi @Arnout

Are you paired with driver or driver change from zigbee thing Mc?

It could need remove device and re-add as new device to it configure reporting.

11

It was initially paired with a “standard zigbee thing” driver, after that I manually changed it to the the “Zigbee thing Mc” and after that I set it to use the “Zigbee Smoke/CO Detector Mc”.
But I have already tried removing the device and adding it again. It then automatically uses the “Zigbee Smoke/CO Detector Mc” driver, but the problem remains.

12

It is the first device that I add as a gas detector and it has not been tested.

There may be a problem in the subdriver, it would be necessary you send me logs with the CLI to analyze the problem

Or I change it to a CO detector type as the previous ones were

13

Happy to support you with addional info, but then I would need some instruction.
Perhaps best to set it as CO detector again if that is easiest to do?

14

I’ll do it tomorrow, I’m out.

this is a tutorial on how to install the cli and capture the logs

When you answer, click on reply in the post you want to reply or tag me, otherwise I don’t know that you are writing to me

15

Hi Mariano,
I followed the CLI instruction and captured the log.
During logging, I pressed the test button on the Gas detector, so I guess this is the WARN in the log.
I hope it helps.

connecting… connected
2023-08-17T15:08:44.226621593+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:08:56.945726928+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-17T15:08:56.951354262+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: f9e08bb6-a0bf-4f90-9b92-6fc0427816bc [0xBF26] (TS0204 Gas Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBF26, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: Basic >, lqi: 0xC8, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x1A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0001, DataType: Uint8, ApplicationVersion: 0x45 > > > >
2023-08-17T15:08:56.972099262+00:00 DEBUG Zigbee Smoke/CO Detector Mc TS0204 Gas Sensor device thread event handled
2023-08-17T15:09:14.235930003+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:09:44.221153456+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:10:14.242746668+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:10:44.331173994+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:11:14.436920987+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:11:32.115941316+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-17T15:11:32.116906316+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: f9e08bb6-a0bf-4f90-9b92-6fc0427816bc [0xBF26] (TS0204 Gas Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBF26, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: Basic >, lqi: 0xBA, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x1B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0001, DataType: Uint8, ApplicationVersion: 0x45 > > > >
2023-08-17T15:11:32.135190649+00:00 DEBUG Zigbee Smoke/CO Detector Mc TS0204 Gas Sensor device thread event handled
2023-08-17T15:11:44.624823979+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:12:14.653987305+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:12:40.437731633+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-17T15:12:40.452509633+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: f9e08bb6-a0bf-4f90-9b92-6fc0427816bc [0xBF26] (TS0204 Gas Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBF26, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC8, rssi: -72, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x1C, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0001, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
2023-08-17T15:12:40.454639299+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-17T15:12:40.455899633+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2023-08-17T15:12:40.457577966+00:00 WARN Zigbee Smoke/CO Detector Mc Attempted to generate event for f9e08bb6-a0bf-4f90-9b92-6fc0427816bc.main but it does not support capability Smoke Detector
2023-08-17T15:12:40.459409299+00:00 DEBUG Zigbee Smoke/CO Detector Mc TS0204 Gas Sensor device thread event handled
2023-08-17T15:12:41.806432632+00:00 TRACE Zigbee Smoke/CO Detector Mc Received event with handler zigbee
2023-08-17T15:12:41.811161966+00:00 INFO Zigbee Smoke/CO Detector Mc <ZigbeeDevice: f9e08bb6-a0bf-4f90-9b92-6fc0427816bc [0xBF26] (TS0204 Gas Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBF26, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC4, rssi: -65, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x1D, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0000, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
2023-08-17T15:12:41.834520299+00:00 TRACE Zigbee Smoke/CO Detector Mc Found ZigbeeMessageDispatcher handler in zigbee-smoke-detector
2023-08-17T15:12:41.837538966+00:00 INFO Zigbee Smoke/CO Detector Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2023-08-17T15:12:41.843203966+00:00 WARN Zigbee Smoke/CO Detector Mc Attempted to generate event for f9e08bb6-a0bf-4f90-9b92-6fc0427816bc.main but it does not support capability Smoke Detector
2023-08-17T15:12:41.851430966+00:00 DEBUG Zigbee Smoke/CO Detector Mc TS0204 Gas Sensor device thread event handled
2023-08-17T15:12:44.538196632+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled
2023-08-17T15:13:14.690482632+00:00 DEBUG Zigbee Smoke/CO Detector Mc driver device thread event handled

16

Hi @Arnout

Sorry, I forgot add de subdriver in template.
Fixed in this driver version

You can install this new version with CLI execute this command smartthings edge:drivers:install and follow the prompt screen steps

After installing wait about 1 min to driver install

───────────────────────────────────────────────────
 Name         Zigbee Smoke/CO Detector Mc
 Version      2023-08-17T16:42:43.491547864        
───────────────────────────────────────────────────
17

It works!
After updating the driver according to the procedure you provided it didn’t work at first, but after removing and re-adding the device all looks fine!
Here’s a screenshot:

ST-Nedis Gassensor
ST-Nedis Gassensor2048×2048 198 KB

Thank you for the great work! I also learned something in terms of drivers and CLI so I am planning to read more about how this all works.

1 Like
18

Hi @Mariano_Colmenarejo

Followed your instructions for the Heiman gas sensor today, and it worked. Thank you for the awesome drivers as well as all the support you provide!

1 Like
19

@Mariano_Colmenarejo Hello Mariano, I have the Heiman Z-wave gas sensor, before the last firmware update it was working, now the sensor monitor has not been added and it does not send notifications. You could verify what happens. thank you so much.