Any difficulty in getting them to pair?
Quite honestly, I consider this type of function to be absolutely critical for any Home Automation setup. So, if my sensors won't work reliably, I'll just swap them out with ones that are reliable.
(Although I have a good Zigbee mesh, I'd prefer to stick with Zwave).
Is anybody out there using the DMWS1 from Dome:
Dome Wireless Z-Wave Plus Leak Sensor with Remote Probe, Low Profile, Water Resistant (DMWS1)
No, both paired immediately.
I have to ask - did you try rebooting your hub and then attempt the pairing? This has worked in many scenarios - don't ask me why.
Yes, I did.
(I shutdown my Hub, and moved it close to the device, when I saw that it wasn't working.)
1 Like
What browser are you using?
I tried it using Brave (browser of choice), and when that didn't work, I tied using Chrome.
SOLVED: Issue with New Device Discovery/Pairing
I finally solved this issue,
I had been using the original AA alkaline batteries (which tested as good, in my battery tester).
I replaced the batteries with Energizer Ultimate Lithium batteries (the best battery, IMHO).
No problem - paired first time!
In conclusion, for the Everspring Water Sensor - use the best possible "AA" batteries!
(It doesn't matter if the original ones test as good...)
That hurt my head.... You know Energizer Lithium are NOT alkaline, right? Them being lithium is the whole point of why they last longer than their alkaline counterparts. 
Also note that the decay curve of voltage vs current is very different on lithium batteries, so any battery % reported from the end device will likely be wrong or stay ~100% until the battery just dies with no % in between 100% and dead.
I use lithium batteries in a lot of devices, since they often last longer. But the battery % reporting difference isn't something a lot of people understand.
1 Like
My apologies for hurting your head!
(Of course, you're right... I know that the're lithium, but they look like alkaline...)
I got introduced to these batteries, with my previous Kwikset Zwave Door lock. Regular AA's, lasted only 1-2 months! (freezing cold climate, and lack of proper insulation.) I changed to these batteries, and they lasted for 6-9 months! A winner!
(Of course, I then changed to a Zwave Plus Kwikset Door Lock, and the batteries have never needed replacement, so far...)
1 Like
No worries, I was just being sarcastic.
Back to the topic - fresh batteries = good. 
I'm in a situation like @Terk. We have the Everspring version here, and I can't get it to reset from the wet state without trying to unpair/re-pair it. Given that the pairing process is so onerous, what can we do? I tried switching the driver from Generic to the Utilitech one I found online -- a ST driver "Ported to Hubitat by cuboy29". It didn't make a difference in resetting from the wet state. Not sure whether to try resetting & re-pairing the device using the custom driver. Does anyone have any thoughts? Thanks for any & all feedback!
Lots of great tips below - and i had the same problem as you! Frustrating.
I over and over again tried the tips below - and after the 10th time of trying what i thought was the same thing - here is my recipe -
- unplug hubitat to reset it (just for insurance)
- in hubitat web app - go to add devices and do what you did above - that got us stuck on initializing... and it shows the ID # as in your example above 4a.. .
- click the exclude z wave devices in the web...
- on the utilitech - press that little button 5 times in 5 seconds then press it again once more. it will beep funny.. i think that when it is being removed /excluded the light in front goes out...
- then in the web app i got a message "unknown device excluded".
- then i click search for zwave device...
- i push that stupid button another 5 times.. wait a second then push it again... and the front red led comes on....
- interestingly i then get the found zwave device with a different ID# than when it was stuck.. in less than 2 minutes - it sync'd up and all was good.
Hope this helps someone, and i dont claim any original thought here - just repeating what people smarter than me said below with a few more details..
Thanks to all for the help!
Had a similar issue to everyone else. I tried a bunch of resets, and came up with what worked every time:
- Reboot the hub (guaranteed if you're reading this post, you likely have a bunch of renegade devices stuck on "Initializing", and this will clear them).
- (If your Utilitech/Everspring sensor is already blinking orange, and beeping once in a while, skip this step). Press the button on the back once, and tell Hubitat to exclude the device; you should get an "unknown device excluded", and now the led should be blinking orange and beeping once in a while.
- (this is my step that fixed everything) Take out a battery, wait a few seconds, put it back in; nothing will look like it changed, but if I skip this step, re-pairing NEVER works.
- Put Hubitat into pairing mode, and press the button on the back of the leak sensor (I only pressed it once); 3 beeps with a red led (which sounds to me like it failed), but it works now.
I see many people are frustrated with this thing, but it's the only cheap-ish sensor that I can use for my sump-well. Works great as a "water is higher than the sump-pump should allow, check it out" sensor.
2 Likes
DO NOT JUST "unplug Hubitat".
IF YOU DO, YOU RISK DATABASE CORRUPTION, AND YOU SHOULD GO THROUGH THE SOFT RESET PROCEDURE!
(please forgive the SHOUTING!)
2 Likes
thanks - that's good advice!
Thanks for the battery tip: that was key.
1 Like
I've had to revisit this thread again, since after a hard reset, I'm having to exclude/include everything. Included the 12-15 (I forget) Utilitech water sensors. The first one went relatively easy on my own. But I was on the second one for an hour before I got it. I followed these directions exactly, and it worked. I did go a little closer to the hub, but it had been paired before. Also, when I went to exclude, it would let me keep excluding one after the other-no limit: exclude unknown device, start excluding again...and there's another one.
Anyway, thanks again! Hopefully the next 10-13 will go smoother.
PS: I hate that little screw on the bottom too. If you don't use it, the switch doesn't get depressed.
I probably spoke too soon, but...
It kept getting hung up on Initializing until I went closer to the hub.
I don't recall having these problems last time.
Thing is, without a super-long LAN cable, I have to rip out the existing install.
