Generic Zigbee 3.0 Valve not getting fingerprint

⚙️ Custom Apps and Drivers
1

I bought these valves on alibaba and there's no manufacturer or model number to speak of. When I try to pair with hubitat I can get position info, open or closed, but I cannot command it. Log shows: dev:4822022-04-19 06:25:33.428 pm infoINCOMPLETE - DO NOT SUBMIT THIS - TRY AGAIN: fingerprint model:"null", manufacturer:"null", profileId:"A1E0", endpointId:"F2", inClusters:"", outClusters:"0021"

dev:4822022-04-19 06:25:33.425 pm traceApplication: null

dev:4822022-04-19 06:25:33.423 pm infoNOT IMPORTANT: Application ID is missing for the fingerprint. Try again.

dev:4822022-04-19 06:25:33.421 pm traceModel: null

dev:4822022-04-19 06:25:33.419 pm traceManufacturer: null

dev:4822022-04-19 06:25:33.416 pm warnManufacturer name is missing for the fingerprint. Try again.

dev:4822022-04-19 06:25:33.414 pm debugGetting info for Zigbee device...

dev:4822022-04-19 06:25:33.383 pm traceSimple Descriptor Information Received - description:catchall: 0000 8004 00 00 0040 00 4BCF 00 00 0000 00 00 9300CF4B0AF2E0A161000000012100 | parseMap:[raw:catchall: 0000 8004 00 00 0040 00 4BCF 00 00 0000 00 00 9300CF4B0AF2E0A161000000012100, profileId:0000, clusterId:8004, clusterInt:32772, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:4BCF, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[93, 00, CF, 4B, 0A, F2, E0, A1, 61, 00, 00, 00, 01, 21, 00]]

dev:4822022-04-19 06:25:33.292 pm infoINCOMPLETE - DO NOT SUBMIT THIS - TRY AGAIN: fingerprint model:"null", manufacturer:"null", profileId:"0104", endpointId:"F2", inClusters:"null", outClusters:"null"

dev:4822022-04-19 06:25:33.285 pm warnOne or multiple pieces of data needed for the fingerprint is missing, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.

dev:4822022-04-19 06:25:33.282 pm traceApplication: null

dev:4822022-04-19 06:25:33.280 pm infoNOT IMPORTANT: Application ID is missing for the fingerprint, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.

dev:4822022-04-19 06:25:33.277 pm traceModel: null

dev:4822022-04-19 06:25:33.275 pm traceManufacturer: null

dev:4822022-04-19 06:25:33.262 pm warnManufacturer name is missing for the fingerprint, requesting it from the device. If it is a sleepy device you may have to wake it up and run this command again. Run this command again to get the new fingerprint.

dev:4822022-04-19 06:25:33.259 pm debugGetting info for Zigbee device...

I've tried several different drivers, that capture was using Zigbee - Generic Device Toolbox but I get similar results with other drivers. The valves pair and work with smartthings and an echo plus which identifies the valve as _TZ3000_iedbgyxt smart device.

1 Like
2

@mike.maxwell

3

If its not falling back to ZHA 1.2 properly theres nothing i can do for it. Tuya devices are flakey. We met with Tuya recently and they were not interested in sharing their cluster implementation so we wont be supporting their devices natively any time soon.

4 Likes
4

So is this a problem at the platform level that couldn't be fixed with a driver or app? I'm relatively new to the hubitat platform and by no means a coder, just a tinkerer. I'm just wondering if this is a lost cause and I need to fall back to smartthings for these devices?

5

I am interpreting what Mike says as to this is Tuya's fault for not using standard Zigbee clusters. And it isn't worth the limited staff to work on these as they will take significant time to support each device beyond the fact they have issues. So blame Tuya for that part of things. It is often best to stay away from Ali Express and the like, they often have some very non-standard devices on there.

As for the other part of your question, many devices have community drivers that aren't stock Zigbee, or use unconventional methods. The Aqara stuff is one example of this, but there are others. So maybe there is hope, but you are probably better off using devices that are known to work and known to be reliable.

4 Likes
6

Possibly with a driver. Check with @kkossev. He has written drivers for several TuYa devices.

5 Likes
7

@Bucket seems like your device has not paired successfully to the hub for some reason...

Please first REMOVE it from the device web page, then remove the power supply for a few minutes, then power it and then pair it to HE again. When discovered, there will be a link displayed. Press it and post the device data here. Device first endpoint data should be exactly like this.

In the same thread, @Juan is saying that he had success with the inbuilt Sinope Water Valve driver.

1 Like
8

I deleted and repaired using sinope water valve and this is what is shows:

  • endpointId: F2
  • model: null
  • application:
  • driver: v1.0.1.1123
  • manufacturer:

The device looks identical to the one Juan was posting about but for some reason hubitat isn't getting the correct data from it. The log shows:

dev:4832022-04-20 05:16:58.659 am warnconfigure...

dev:4832022-04-20 05:11:19.896 am errorjava.lang.StringIndexOutOfBoundsException: String index out of range: -2 on line 233 (method parse)

dev:4832022-04-20 05:11:19.856 am errorjava.lang.StringIndexOutOfBoundsException: String index out of range: -2 on line 233 (method parse)

dev:4832022-04-20 05:11:16.882 am warnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: A1FA01E0011010D0300030D03000, dni: A1FA, endpoint: 01, cluster: E001, size: 10, attrId: D010, encoding: 30, command: 0A, value: 0030D03000 | msgMap:[raw:A1FA01E0011010D0300030D03000, dni:A1FA, endpoint:01, cluster:E001, size:10, attrId:D010, encoding:30, command:0A, value:00, clusterInt:57345, attrInt:53264, additionalAttrs:[[value:00, encoding:30, attrId:D030, consumedBytes:4, attrInt:53296]], valueParsed:0]

dev:4832022-04-20 05:11:16.879 am infomsgMap: [raw:A1FA01E0011010D0300030D03000, dni:A1FA, endpoint:01, cluster:E001, size:10, attrId:D010, encoding:30, command:0A, value:00, clusterInt:57345, attrInt:53264, additionalAttrs:[[value:00, encoding:30, attrId:D030, consumedBytes:4, attrInt:53296]], valueParsed:0]

dev:4832022-04-20 05:11:16.866 am warnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: A1FA0100063C000010000140210000024021000001803001028030000050300100801000, dni: A1FA, endpoint: 01, cluster: 0006, size: 3C, attrId: 0000, encoding: 10, command: 0A, value: 000140210000024021000001803001028030000050300100801000 | msgMap:[raw:A1FA0100063C000010000140210000024021000001803001028030000050300100801000, dni:A1FA, endpoint:01, cluster:0006, size:3C, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, additionalAttrs:[[value:0000, encoding:21, attrId:4001, consumedBytes:5, attrInt:16385], [value:0000, encoding:21, attrId:4002, consumedBytes:5, attrInt:16386], [value:01, encoding:30, attrId:8001, consumedBytes:4, attrInt:32769], [value:00, encoding:30, attrId:8002, consumedBytes:4, attrInt:32770], [value:01, encoding:30, attrId:5000, consumedBytes:4, attrInt:20480], [value:00, encoding:10, attrId:8000, consumedBytes:4, attrInt:32768]], valueParsed:false]

dev:4832022-04-20 05:11:16.856 am infomsgMap: [raw:A1FA0100063C000010000140210000024021000001803001028030000050300100801000, dni:A1FA, endpoint:01, cluster:0006, size:3C, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, additionalAttrs:[[value:0000, encoding:21, attrId:4001, consumedBytes:5, attrInt:16385], [value:0000, encoding:21, attrId:4002, consumedBytes:5, attrInt:16386], [value:01, encoding:30, attrId:8001, consumedBytes:4, attrInt:32769], [value:00, encoding:30, attrId:8002, consumedBytes:4, attrInt:32770], [value:01, encoding:30, attrId:5000, consumedBytes:4, attrInt:20480], [value:00, encoding:10, attrId:8000, consumedBytes:4, attrInt:32768]], valueParsed:false]

dev:4832022-04-20 05:11:16.795 am errorjava.lang.StringIndexOutOfBoundsException: String index out of range: -2 on line 233 (method parse)

dev:4832022-04-20 05:11:16.780 am errorjava.lang.StringIndexOutOfBoundsException: String index out of range: -2 on line 233 (method parse)

dev:4832022-04-20 05:11:16.717 am warnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: A1FA01E0001003D0420441414141, dni: A1FA, endpoint: 01, cluster: E000, size: 10, attrId: D003, encoding: 42, command: 0A, value: 0441414141 | msgMap:[raw:A1FA01E0001003D0420441414141, dni:A1FA, endpoint:01, cluster:E000, size:10, attrId:D003, encoding:42, command:0A, value:AAAA, clusterInt:57344, attrInt:53251]

dev:4832022-04-20 05:11:16.713 am infomsgMap: [raw:A1FA01E0001003D0420441414141, dni:A1FA, endpoint:01, cluster:E000, size:10, attrId:D003, encoding:42, command:0A, value:AAAA, clusterInt:57344, attrInt:53251]

dev:4832022-04-20 05:11:14.241 am infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 A1FA 00 00 0000 00 00 5F00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A1FA, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[5F, 00]]

dev:4832022-04-20 05:11:12.346 am infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 A1FA 00 00 0000 00 00 6182, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A1FA, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[61, 82]]

dev:4832022-04-20 05:11:12.237 am infoRecovery feature ENABLED

dev:4832022-04-20 05:11:12.207 am infoNo VALID lastCheckin event available! This should be resolved by itself within 1 or 2 hours and is perfectly NORMAL as long as the same device don't get this multiple times per day...

dev:4832022-04-20 05:11:12.198 am infomsgMap: [raw:catchall: 0000 8021 00 00 0040 00 A1FA 00 00 0000 00 00 5F00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A1FA, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[5F, 00]]

dev:4832022-04-20 05:11:12.091 am infogetDriverVersion() = v1.0.1.1123

dev:4832022-04-20 05:11:12.084 am infoinstalled()

When pairing it by default matches it to the driver Zigbee - Xiaomi/Aqara Motion Sensor

1 Like
9

Did you try manually changing to the Sinope Water Valve driver and hitting Configure

4 Likes
10

Yes I have tried the Sinope Water valve, Zigbee Tuya Valve by Markus and several generic zigbee drivers but all fail to get a valid fingerprint. I've used the configure or initialize button and even let it sit for 24hours just to see if anything changed but alas it has not.

11

is this not it?

12

sure, all that looks standard for this device type, however it refuses to respond with the implemented clusters (aka fingerprint), so we are never going to be able to identify it and assign the correct driver.

13

Ive look and looked through that and can't fathom how they implement anything in the EF00 cluster.

Just trial and error

14

yeah, exactly, and they will not give out that info, we tried, they declined...

3 Likes
15

They probably just care about ZigBee 3.0.
Maybe HE C8?

16

Not even close, all they care about is their cloud and your data...

8 Likes
17

I have the same valve and the same experience as @Bucket . Anyone found working driver for this?

18

@kkossev fixed it for me. See this thread Water Shutoff valve that works with Hubitat - #64 by kkossev

3 Likes