Driver code was updated with a correct fingerprint for the new Neo model;
Tuya check-in messages (usually received every 1 or 4 hours) are now shown in the device log page.
Yesterday I had my first REAL water leaking problem alert :
The leak sensor is the third one (the cheapest) shown in the first post. Tthe sensor box was mounted on the backside of the cabinet under the kitchen sink. The extension cord with the actual sensor at the end was simply thrown to the bottom, as I had not good visibility inside because... uhh.. of the many items that were put in the closet and I was too lazy to first remove and then rearrange all that stuff...
So in my case, the investment in these leak sensors has already paid off!
In my opinion, leak sensors are essential in North American homes, given that they often they are constructed as a wood frame with drywall, and wood floors.
To make things worse, my home has a 50 gallon water tank in the attic.
thanks for the awesome driver! that looks like a ton of work!
I don't see anything about battery status ...should there be?
I have the Model: TS0207
Manufacturer: _TZ3000_upgcbody
@tim.ocallag my _TZ3000_upgcbody sensor is reprting the battery percentage remaining every 4 hours. You can try to pair it again to HE and keep the debug logs for 24 hours to see if there are any battery reports.
You can also check the past logs ( you may need to press 'show more' several times
dev:31312022-07-10 18:20:32.105 infoSensor Water Leak Under Sink in the Kitchen battery is 24% (physical), water:dry
dev:31312022-07-10 14:22:15.774 infoSensor Water Leak Under Sink in the Kitchen battery is 24% (physical), water:dry
I notice that the battery level reported is suspiciously low, will check the code in the next days. Almost all sensors report the battery level in 0..100%, but some Tuya devices report in the 0..200 range, probably there is a bug here.
I am also planning to add a watchdog / offline timer so that we get an event 'powerSource unknown' if the device falls off the network. Also, the battery level will be forced to 0%, so that the HE apps that monitor battery levels are triggered to send an alarm.
Just got a slightly different water sensor ..looks like one of your pictures but has slightly different data...
the data is
endpointId: 01
model: TS0207
application: 41
manufacturer: _TZ3000_kyb656no
I thought I'd be smart and try and add the new device to your driver....but I can't tell what to put for the profileId, inClusters or outClusters
I thought I could google _TZ3000_kyb656no and find that info....but I don't see anywhere....how did you figure out what to put on the fingerprint lines?
Thanks again for your help !
Tim
p.s. cannot get it to register wet...i've checked the battery, removed the battery,etc
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?