Well at least this give devs here an idea to work with.
Hans, @user4181, have you tried the generic driver that was mentioned as well?
Maybe its overkill to ask, but if the driver is not auto detected, did you manually assign the driver to the device?
Maybe usefull to go through this link (including the last post)
Hi @user4181 ,
Did you manage to make this contact sensor to work with Hubitat Elevation hub?
After you manually switch the driver to the one suggested above, you will need to pair it again to HE for a second time. The previously manually configured driver should remain and the contact sensor should start reporting open/close then.
Hi all,
sorry, I haven't been home over the last weekend. Just could try now.
I removed the contact switch from the 'device'-section and re.installled it by using Thomas' driver.
Hubitat didn't assign any name, just calls it 'device'. No entry under 'Current State' and 'State Variables'
2023-01-30 16:46:41.244[info]( -xxx- deviceId=47#)fingerprint profileId:"0104", endpointId:"01", inClusters:"0001,0003,0500,0000", outClusters:"0003,0004,0005,0006,0008,1000,0019,000A", model:"TS0203", manufacturer:"_TZ3000_oxslv1c9"
[dev:47]( -xxx- deviceId=47#)2023-01-30 16:46:41.137[trace]( -xxx- deviceId=47#)ZCL version:03
[dev:47]( -xxx- deviceId=47#)2023-01-30 16:46:41.135[trace]( -xxx- deviceId=47#)Software Build Id:unknown
[dev:47]( -xxx- deviceId=47#)2023-01-30 16:46:41.133[trace]( -xxx- deviceId=47#)Model:TS0203
[dev:47]( -xxx- deviceId=47#)2023-01-30 16:46:41.131[trace]( -xxx- deviceId=47#)Manufacturer:_TZ3000_oxslv1c9
[dev:47]( -xxx- deviceId=47#)2023-01-30 16:46:40.773[debug]( -xxx- deviceId=47#)getting info for unknown Zigbee device...
[dev:47]( -xxx- deviceId=47#)2023-01-30 16:46:38.750[debug]( -xxx- deviceId=47#)configure() called...
[Show more...]
Perhaps I am too stupid to change a driver manually, but now I honestly do not know HOW TO GET THESE SENSOR SWITCHES WORKING.
Hi @user4181 ,
You need to manually switch the driver for this device, as it is a relatively new one and will not be recognized automatically in HE from any built-in or custom driver.
do you have any other custom drivers installed?
Yes, of course. I already installed:
'Konke ZigBee Temperature Humidity Sensor' -> works
'Tuya Temperature Humidity Illuminance LCD Display with a Clock' -> works
'Tuya Zigbee Metering Plug driver for Hubitat Elevation - Power, Energy, Voltage, Amperage' -> works
'Tuya Zigbee Contact Sensor Version v1.0.0' -> doesn't work yet
Everytime when I installed a driver manually, I found a 'configure'-button in the device-section. But on the site of the contact sensor there is none, so I don't know, how to activate this driver.
Manually assign Thomas’s driver.
Then pair the sensor again to HE (without deleting the device)
I expect the contact sensor to start working after the second pairing.
The Configure button doesn’t work always for Tuya and Aqara battery-powered sensors. They stay in ‘deep sleep’ mode most of the time and do not receive the configuration commands.
However, the configuration is usually accepted during the pairing process, with the driver already assigned.
Hi,
I removed the device from my Hubitat, deleted the according custom driver, re-imported Thomas' driver from github.com again. Then re-installed the contact sensor using the freshly downloaded driver and afterwards I paired the sensor again. The sensor's 'Device'-site shows:
Initialize
Reset To Closed
Reset To Open
( empty )
( empty too )
The Logs say:
2023-02-02 13:38:28.232infomsgMap: [raw:catchall: 0000 0013 00 00 0040 00 3965 00 00 0000 00 00 4C653968F790629638C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:3965, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4C, 65, 39, 68, F7, 90, 62, 96, 38, C1, A4, 80]]
dev:592023-02-02 13:38:02.325warnGeneral catch all - description:catchall: 0000 0013 00 00 0040 00 391C 00 00 0000 00 00 461C3968F790629638C1A480 | msgMap:[raw:catchall: 0000 0013 00 00 0040 00 391C 00 00 0000 00 00 461C3968F790629638C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:391C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[46, 1C, 39, 68, F7, 90, 62, 96, 38, C1, A4, 80]]
dev:592023-02-02 13:37:36.641warnGeneral catch all - description:catchall: 0000 0013 00 00 0040 00 6E5E 00 00 0000 00 00 405E6E68F790629638C1A480 | msgMap:[raw:catchall: 0000 0013 00 00 0040 00 6E5E 00 00 0000 00 00 405E6E68F790629638C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:6E5E, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[40, 5E, 6E, 68, F7, 90, 62, 96, 38, C1, A4, 80]]
dev:592023-02-02 13:33:48.723infofingerprint profileId:"0104", endpointId:"01", inClusters:"0001,0003,0500,0000", outClusters:"0003,0004,0005,0006,0008,1000,0019,000A", model:"TS0203", manufacturer:"_TZ3000_oxslv1c9"
dev:592023-02-02 13:33:48.527traceZCL version:03
dev:592023-02-02 13:33:48.524traceSoftware Build Id:unknown
dev:592023-02-02 13:33:48.522traceModel:TS0203
dev:592023-02-02 13:33:48.520traceManufacturer:_TZ3000_oxslv1c9
dev:592023-02-02 13:33:48.170debuggetting info for unknown Zigbee device...
You should not do that - please follow what I proposed in this post:
After you manually assign Thomas's driver to the device as it is now already paired to the hub, just pair it again.
Manually assigning the custom driver is made this way :
Hi kkossev,
of course, I understood your suggestions. I just wanted to make a "clean install", therefore I tried to delete the existing and perhaps corrupted driver and re-load it from a secure source (and could only do so after having the sensor removed from the devices-section of my Hubitat). Well, now I have the sensor freshly installed with Thomas' driver and re-paired it again. This is EXACTLY the state you suggested. And to be sure that I do not face an individual issue of one special sensor, I took a second one, installed and re-paired it and got absolutely the same result:
( Status and Log please see in my last post.)
It seems to me that both sensors are not reporting. The only thing that I am allowed to do in the device-section is to manually "Reset (the sensor) To Open" and "Reset To Close". These are the only changes in Status that are shown. But I assume that it has nothing to do with the sensors itself.
Just to be sure - The sensors, we are talking about are: https://www.aliexpress.com/item/1005003186827400.html?spm=a2g0o.order_list.order_list_main.318.51a95c5fPUBw1b&gatewayAdapt=glo2deu
OK, I understand now...
I examined Thomas's driver, it may not be the appropriate one for your sensor.... It is missing the IAS zone enrollment configuration commands.
Last test: change the driver manually to HE inbuilt Generic Zigbee Contact Sensor (no temp) as suggested by @H_Local :
Make sure the debug logging is turned on.
Pair it again with this driver.
Please copy/paste the debug logs that start from the pairing time.
EDIT: I have one more idea to suggest to you to try if the above doesn't work.
.
BINGO !!!
That was it. Now the Status in the 'Device-Section' is updated in real-time.
THX a lot.
Hans
Thank you @kkossev for your explanations.
I got this contact sensor TS0203 (the one that uses 2 AA batteries).
The trick:
-Pair
-Assign the driver: Generic ZigBee Contact Sensor (no temp), then Save
-Press reset on the device (7s) & re-pair
Now works well.
Thanks for the information. I followed @stephane steps and was able to configure the sensor. Just FYI it is Moes Contact Sensor from Aliexpress.
dev:502023-04-01 01:51:53.046 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0001,0003,0500,0000", outClusters:"0003,0004,0005,0006,0008,1000,0019,000A", model:"TS0203", manufacturer:"_TZ3000_decxrtwa"
I also have a couple of Tuya door sensors that are not behaving, they have been fine on my C7 but after upgrading to the C8 they don't work! I have followed all steps above with no joy, 2 things I have noticed, if I pair with the C7 the light on the sensor stops flashing as soon as it is found whereas on the C8, it finds the device but the light continues to flash until it times out, tried the reset and repair as above, when I do this the device works for about 10 seconds then just stops, for the moment I am pairing these with my old C7 hub but would be interested if anyone has a fix for this, I have tried various drivers but the generic zigbee contact sensor works 100% on the C7, device data on both hubs is exactly the same.
If you can detach the sensors, try pairing them on C-8 away from the hub and very close to a Zigbee repeating device.
Can you post the device model and manufacturer from the Device Details Data section?
No difference with pairing next to a remote repeater, assuming it must be a C8 issue as I have these on multiple C7 hubs with no issues..
Thank you for the test!
Its really weird, as until now all the reported similar cases had a different effect - some Zigbee 3.0 only devices that didn’t work on C-7, worked for a short time with the early C-8 platform versions and now do not work again ( do not stay connected) on both C-7 and C-8.
For the moment have kept C7 hub and just used hub mesh to connect it to the C8 so have a C7 hub just for one sensor!
Download the Hubitat app
