I know there has been a lot of effort with community drivers for Leaksmart Moisture Sensors.
That is why I was so happy to see this in an official release 2.2.4. So I configured all of my Leaksmart Zigbee Moisture Sensors home with this new driver supplied with 2.2.4 firmware. I have both types of sensors, old version 1, and new version 2 as well.
It paired perfectly. Sensors themselves also work perfectly -- they detect leak just well and start noisy beeping.
However, no matter what I do, it never detects any leak inside Hubitat. Sensors never change state from dry to wet. All they do is report battery level, which seems to be working well (proper battery level is reported).
Did you click "Configure" after changing to the new drivers? This is usually a good idea to do, and for a Zigbee device usually affects when/what the device reports back to the hub, so it's worth a try if you haven't.
Visibly, no; it just sends Zigbee configuration commands to the device that may affect how it reports to the hub. If it doesn't help, then I'm not sure. Maybe try resetting the device and re-pairing? (No need to remove it from Hubitat; it will be recognized as the same device.)
You will see the "configure" in the logs. And maybe some output of the configure in the logs. But basically nothing shows in the device settings page. This is the log from a Zigbee switch with all logging turned on, and configure button pressed.
I have spent a couple hours trying to resolve issues. (Delete & re-pair). (don't delete and re-pair), (just change the driver from the community version to the now official driver).
The new driver doesn't work. (error attached). it doesn't update at all once newly paired. Also, the temperature is unavailable in the new driver. The only way I can get these sensors to work at all is with the community driver (used for months), which btw, seems that the battery reporting level has changed (now not accurate) during one of the past couple of firmware updates to the hub.
Is that error from the built-in driver or the community driver? If it's the built-in one, staff could probably use the logs you shared to figure out the problem. If it's a community driver, that would fall on that author (though if they aren't around anymore, someone could probably still take a look if you shared where it came from).
Yes, there is a bug in the temp reporting, it will be fixed in the next hot fix release.
Once we get that working, if moisture alerting is still not working, tag me and well dig into it some more.
I also ordered one of these, the priginal driver was written with a customer supplied sample...
Saw a hotfix come out today, but release notes didn't indicate Leaksmart. I upgraded; so just an FYI, the issue continues, maybe wasn't part of that release. thanks!
Thank you guys for confirming malfunctioning driver. This is helpful. It will save me a lot of time.
Question for @mike.maxwell: if I need to leave house for a longer time and Leaksmart sensors are paired and installed, would they start working (reporting moisture) automatically after next hot-fix update? Or they will have to be re-paired again?
Also since I live in the same city of Scottsdale, AZ where Hubitat HQ is, I can bring you one sensor for development. Actually you will need two sensors, because there is, as you surely know, version 1 (old) and version 2 (new). Just trying to help a bit
@nepto I have the label “sensor” on mine, but according to Hubitat I have version 2. But maybe thats the community driver identifying that. Is there another way to tell?
@todd.norman, honestly I do not know. I am new to Hubitat community and while I am good with programming, I prefer not to make my own drivers:)
Anyway I left my house already, so as for now I can only change drivers remotely and I am unable to do any kind of pairing anymore. So I will just wait couple of days for Hubitat update to come. If not, then I will just revert to community drivers. If that will ever happen (I hope not:) then I will be able to tell you more including all the details, since I will need to review and customize such drivers. Obviously, leak sensor is exactly that thing which you kind of want to work as much reliably as possible.
But let's at least hope we are on the right track with this.
Tried the included drivers for the first time, I had been using the community ones. It was time to replace the batteries, so it felt like a good time to try the new driver. I've got the older v1 style (with "sensor" on the top) and with the Hubitat driver, wet is never reported. With the community driver, it is.
