[RELEASE] Tuya NEO Coolcam Zigbee Water Leak Sensor

Google search shows a few results - for example, this . The best is to search for the manufacturer ID inside Github.com - this

You can also get the fingerprint by temporarily switching to HE inbuilt driver named 'device'. Clicking on the 'Get Info' button from the device web page should show the device fingerprint in the logs. The sensor needs to be awake at that time - make it wet, or re-insert the batteries first and then click on the Get Info button.

Regardless that this device fingerprint is not in the driver, once you assign the driver manually and then pair the device again to HE, the same driver should be selected automatically during the second pairing process - does it work this way in your case?

thanks ! I appreciate all the details....I added
fingerprint profileId:"0104", endpointId:"01", inClusters:"0001,0003,0500,0000", outClusters:"0019,000A", model:"TS0207", manufacturer:"_TZ3000_kyb656no", deviceJoinName: "Aubess Water Sensor" // vendor: 'not sure

not sure if it was that or deleting the device and re-finding but the device now showed wet when stuck in water......BUT ..
its now stuck saying WET even though its been dried off for minutes.....is there any suggestions on that?
Thx!

1 Like

Make sure the Debug logging is on, then remove the battery for 1-2 minutes and put the cell back in.
Please send me the logs from the time when the sensor is powered on again and starts sending data to HE.

weird,nothing
dev:7472022-08-02 11:52:03.488 pm infoLaundry Water Sensor Debug logging will be turned off after 24 hours

dev:7472022-08-02 11:52:03.457 pm infoLaundry Water Sensor Debug logging is true; Description text logging is true

dev:7472022-08-02 11:52:03.456 pm infoLaundry Water Sensor Updating Laundry Water Sensor (Tuya NEO Coolcam Zigbee Water Leak Sensor) model TS0207 manufacturer _TZ3000_kyb656no

battery added at 11:53
I even put in water and nothing

Pair it again, close to the hub.

You can also try resetting it first, this is often achieved by holding the pair button pressed for 20-30 seconds or more.

when i pair it again...do you mean remove first ? if I dont then it just says found a device it already knew about ..if I delete it and it refinds it it has turned off debugging

No, do not delete the device from HE. Just pair it again, the debug logs should appear on the existing device logs page.

so just say dismiss
image

here is log
dev:7482022-08-03 12:11:26.714 am infoLaundry Sensor 2 is dry

dev:7482022-08-03 12:11:21.000 am traceLaundry Sensor 2 sendZigbeeCommands(cmd=[he raw 0xCF08 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0xCF08 0x01 0x0000 0xFFDE 0x20 {13} {}, delay 200])

dev:7482022-08-03 12:11:20.978 am infoLaundry Sensor 2 InitializeVars()... fullInit = true

dev:7482022-08-03 12:11:20.960 am infoLaundry Sensor 2 configure()..

putting in water gets no reaction in logs....i am right near hub

a different sensor exact same model
dev:7492022-08-03 12:18:08.607 am infoLaundry Sensor 1 battery is 100% (physical), water:dry

dev:7492022-08-03 12:18:06.491 am infoLaundry Sensor 1 is dry

dev:7492022-08-03 12:18:02.980 am traceLaundry Sensor 1 sendZigbeeCommands(cmd=[he raw 0x21A4 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x21A4 0x01 0x0000 0xFFDE 0x20 {13} {}, delay 200])

dev:7492022-08-03 12:18:02.962 am infoLaundry Sensor 1 InitializeVars()... fullInit = true

dev:7492022-08-03 12:18:02.947 am infoLaundry Sensor 1 configure()..

Okay, I will have to do some more things in-depth search if there are any specifics for this device.

Last thing that comes in my mind now is to advise you to change the battery cell with a new one. Often the batteries that come with the Tuya device are of a questionable quality, may be depleted or just make a bad contact.

thanks so much for your help..i can try another battery but both measured 3.1v

1 Like

DANG, you were right !!!!
new batteries (3.3v) and both work
so sorry to waste your time (although I appreciate the learning!)
Thx !!!

2 Likes

The problem with some bad quality battery cells is that they have a big internal resistance. This means that if you measure the battery voltage with a voltmeter, they will show 3V or higher. But when the device starts transmitting, it draws much more current than when in idle state. And at this time the voltage drops rapidly, causing device to be reset or hang.

4 Likes

@kkossev The one I ordered from WalMart is round with Neo logo (instead of water drop) external sensor like the old Dome sensor. It is like the first one pictured in post 1.

But its feetprint is

  • endpointId: 01
  • application: 41
  • softwareBuild:
  • inClusters: 0001,0003,0500,0000
  • outClusters: 0019,000A
  • model: TS0207
  • manufacturer: _TZ3000_5ynfoj1f

dev:3042022-08-06 01:41:27.751 pm infoWater Leak Under Hall Bathtub battery is 100% (physical), water:dry

dev:3042022-08-06 01:41:24.305 pm infoWater Leak Under Hall Bathtub is dry

dev:3042022-08-06 01:41:20.882 pm traceWater Leak Under Hall Bathtub sendZigbeeCommands(cmd=[he raw 0xEC0E 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0xEC0E 0x01 0x0000 0xFFDE 0x20 {13} {}, delay 200])

dev:3042022-08-06 01:41:20.835 pm infoWater Leak Under Hall Bathtub InitializeVars()... fullInit = true

dev:3042022-08-06 01:41:20.819 pm infoWater Leak Under Hall Bathtub configure()..

Your driver works fine. Thanks!

2 Likes

I recently installed the model described above as well as the round Walmart one. The Walmart model works perfectly.

The elongated modes pictured above doesn’t do anything. When I put the sensor in water, the light blinks for a bit, but nothing seems to make it to the hub. I tried your driver as well as a few generic drivers, but unfortunately, no go… Any recommendations?

1 Like

I had issues with mine as well. Rejoin close to the hub, within 6 inches. I left the sensor there overnight. Make sure you are getting regular batter reports. Then move to you final spot. Mine has worked flawlessly ever since.

2 Likes

I tried re-joining close, but not that close… Will try your recommendation and report back!

UPDATE: I removed the device, placed it next to the hub (within 6-inches) re-joined it. It worked perfectly from that point on.

Prior to that, I was re-joining it but not removing it.

2 Likes

I am glad it worked for you. The need to pair a device close to the hub after being first deleted from HE is probably due to the differences in HE pairing procedures for new and existing devices, I have never had the time to research more deeply what exactly happens and why, but as a rule of the thumb - the chance to successfully pair all these Zigbee devices (not just Tuya devices, but also Aqara and LIDL and other brands ) increases greatly when paired very close to HE hub as a new device only.

3 Likes

We all just appreciate all the hard work you've put in to making these devices work...

2 Likes