[Wrong device]: iHseno "Z2M" temperature and humidity sensor mistaken as Tuya TS0203 door/window sensor

[jspiros]

Link

https://www.aliexpress.us/item/3256809207367334.html

Model

ZC-W1 (from manual included in product box) or IH-K009 (from AliExpress listing)

Description

Temperature and Humidity Sensor

Vendor

iHseno? Tuya?

Picture (link)

https://www.zigbee2mqtt.io/images/devices/IH-K009.png

Database entry

{"id":122,"type":"EndDevice","ieeeAddr":"0xa4c1381dc7bb4052","nwkAddr":4846,"manufId":4742,"manufName":"Zbeacon","powerSource":"Battery","modelId":"TS0203","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":770,"inClusterList":[0,3,1,32,1026,1029],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"modelId":"TS0203","manufacturerName":"Zbeacon","powerSource":3,"zclVersion":3,"appVersion":113,"stackVersion":2,"hwVersion":0,"swBuildId":"0122052017"}},"genPollCtrl":{"attributes":{"checkinInterval":6960}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":200,"batteryVoltage":30}}},"binds":[{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00124b002f8fa805","endpointID":1}],"configuredReportings":[{"cluster":1,"attrId":33,"minRepIntval":3600,"maxRepIntval":65000,"repChange":0},{"cluster":1,"attrId":32,"minRepIntval":3600,"maxRepIntval":65000,"repChange":0}],"meta":{}}},"appVersion":113,"stackVersion":2,"hwVersion":0,"swBuildId":"0122052017","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{"configured":1371223903},"lastSeen":1754290044048,"checkinInterval":1740}

Notes

I bought these from the "2pcs Z2M" variant on the AliExpress listing linked above. Somewhat ironic that they're specifically listed as working with Z2M.

The product box literally only has an image representation of the sensor, and the text "Temperature & Humidity Sensor", on one side. There are no other markings on the box. The item itself has no markings except for the thermometer icon. The small folded manual sheet specifies "ZC-W1" as the model.

[jspiros]

If anyone's curious, I took photos of the packaging and PCB compared to a nearly-identical temperature and humidity sensor that I have that reports as a TS0201/_TZ3000_fllyghyj and is identified as a Tuya TH02Z by Z2M (which works fine, though it looks different than the photo). The device this issue is about is the one on the left, with the green PCB.

[jspiros]

I'm currently using this external_converter and it seems to be working, though I'm not confident this is the best way to do it as it's only my first time creating a converter.

import {temperature, humidity, battery} from 'zigbee-herdsman-converters/lib/modernExtend';

export default {
	zigbeeModel: ['TS0203'],
	fingerprint: [{
		modelID: 'TS0203',
		manufacturerName: 'Zbeacon'
	}],
	model: 'ZC-W1',
	vendor: 'Zbeacon',
	description: 'ZC-W1 (or IH-K009) Temperature & Humidity Sensor',
	extend: [temperature(), humidity(), battery()],
};

[Koenkk]

Added!

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

Could you also submit a picture for the docs? This can be done by:

1. Create a fork by clicking here
2. Go to the public/images/devices directory, Add file -> Upload files
3. Upload the files and press Commit changes
4. Press Contribute -> Open pull request -> update title/description -> Create pull request

Make sure that:

• The filename is ZC-W1.png
• The size is 512x512
• The background is transparent (use e.g. Adobe remove background)

[jspiros]

@Koenkk Great, thanks!

Interestingly, I just received a new 2xAAA temperature & humidity sensor of the ZTH01/ZTH02 physical form factor, and my converter caught it, so it seems the TS0203/Zbeacon fingerprint is being used by more than just the original circular CR2450 device I opened this issue for.

The original CR2450 device, as you can see in the photos above, is identical to the IH-K009 and could use the same photo, so I assume I could just copy that in my pull request.

But, now that I'm aware of another form factor for the same fingerprint, I'm not sure which image makes the most sense; I have noticed this previously about the converters, it seems it's not uncommon for the same fingerprint to match for many different form factors sometimes. I could create a combination image, which would look fine on the device info page, but the image is sometimes used scaled down where that might be too busy. Is there any guidance on what to do, or do you not really care and just want something simple?

[brian-bh]

I have TS0203 door/window sensor and when I'm pairing this, this registered as this device iHseno ZC-W1. I think this issue is the reason. Is there any way to register as TS0203 door window sensor?

[brian-bh]

Not sure but https://a.aliexpress.com/_oBHJHU7 this product is the thing, and according to mapping, this is TS0203 and the manufacturerName is Zbeacon. (After pairing, manufacturer name became _TZ3000_bpkijo14 )
The problem is this is legit door contact sensor, and it paired as a humidity sensor because of this. Can't reconfigure and delete in normal way. Force delete and reset is always required.
Even though I made a custom external converters, but don't know why but this keeps paired as a humidity sensor.

FYI) I was using latest-dev Docker image, rollbacking to 2.6.0 fixed the problem.

[JakubMadro]

Hi, I have the same Device as @brian-bh, and same issue.
My device is discovered as TS0203 (window/door sensor) instead of temperature sensor

[Koenkk]

Could you both provide the data/database.db entry of your device?

[JakubMadro]

{ "id": 5, "type": "EndDevice", "ieeeAddr": "0xa4c1380639e421a4", "nwkAddr": 12360, "manufId": 4742, "manufName": "Zbeacon", "powerSource": "Battery", "modelId": "TS0203", "epList": [ 1 ], "endpoints": { "1": { "profId": 260, "epId": 1, "devId": 770, "inClusterList": [ 0, 3, 1, 32, 1026, 1029 ], "outClusterList": [ 25 ], "clusters": { "genBasic": { "attributes": { "hwVersion": 0 } }, "msRelativeHumidity": { "attributes": { "measuredValue": 6672 } }, "genPollCtrl": { "attributes": { "checkinInterval": 6960 } }, "genPowerCfg": { "attributes": { "batteryPercentageRemaining": 200, "batteryVoltage": 30 } } }, "binds": [ { "cluster": 1, "type": "endpoint", "deviceIeeeAddress": "0x00124b0030e6ab46", "endpointID": 1 } ], "configuredReportings": [ { "cluster": 1, "attrId": 33, "minRepIntval": 3600, "maxRepIntval": 65000, "repChange": 0 }, { "cluster": 1, "attrId": 32, "minRepIntval": 3600, "maxRepIntval": 65000, "repChange": 0 } ], "meta": {} } }, "appVersion": 113, "stackVersion": 2, "hwVersion": 0, "swBuildId": "0122052017", "zclVersion": 3, "interviewCompleted": true, "interviewState": "SUCCESSFUL", "meta": { "configured": 1371223903 }, "lastSeen": 1756395699179, "checkinInterval": 1740 }
Funny thing, it's working in Smartlife and its discovered as Temperature and humidity sensor :(

And here working Temperature sensor:
{ "id": 11, "type": "EndDevice", "ieeeAddr": "0xa4c138842c1efe7a", "nwkAddr": 34523, "manufId": 4742, "manufName": "eWeLink", "powerSource": "Battery", "modelId": "TH01", "epList": [ 1 ], "endpoints": { "1": { "profId": 260, "epId": 1, "devId": 770, "inClusterList": [ 0, 3, 1, 32, 1026, 1029 ], "outClusterList": [ 25 ], "clusters": { "genBasic": { "attributes": { "modelId": "TH01", "manufacturerName": "eWeLink", "powerSource": 3, "zclVersion": 3, "appVersion": 113, "stackVersion": 2, "hwVersion": 0, "swBuildId": "0122052017" } }, "genPollCtrl": { "attributes": { "checkinInterval": 6960 } }, "genPowerCfg": { "attributes": { "batteryVoltage": 30, "batteryPercentageRemaining": 200 } }, "msTemperatureMeasurement": { "attributes": { "measuredValue": 2338 } }, "msRelativeHumidity": { "attributes": { "measuredValue": 5612 } } }, "binds": [ { "cluster": 32, "type": "endpoint", "deviceIeeeAddress": "0x00124b0030e6ab46", "endpointID": 1 }, { "cluster": 1026, "type": "endpoint", "deviceIeeeAddress": "0x00124b0030e6ab46", "endpointID": 1 }, { "cluster": 1029, "type": "endpoint", "deviceIeeeAddress": "0x00124b0030e6ab46", "endpointID": 1 }, { "cluster": 1, "type": "endpoint", "deviceIeeeAddress": "0x00124b0030e6ab46", "endpointID": 1 } ], "configuredReportings": [ { "cluster": 1026, "attrId": 0, "minRepIntval": 30, "maxRepIntval": 300, "repChange": 20 }, { "cluster": 1029, "attrId": 0, "minRepIntval": 30, "maxRepIntval": 300, "repChange": 100 }, { "cluster": 1, "attrId": 32, "minRepIntval": 3600, "maxRepIntval": 7200, "repChange": 0 }, { "cluster": 1, "attrId": 33, "minRepIntval": 3600, "maxRepIntval": 7200, "repChange": 0 } ], "meta": {} } }, "appVersion": 113, "stackVersion": 2, "hwVersion": 0, "swBuildId": "0122052017", "zclVersion": 3, "interviewCompleted": true, "interviewState": "SUCCESSFUL", "meta": { "configured": -2085432827 }, "lastSeen": 1756394755798, "checkinInterval": 1740 }

[Koenkk]

@JakubMadro this one should be detected correctly in the dev branch.

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

[JakubMadro]

Hi,
Works perfectly in version 2.6.1 👍
Thank you @Koenkk