Aeotec Water Sensor 7pro issue

[Terri_Baker (TeBa)]

I have an aeotec water sensor 7pro that since switching to Smartthings z-wave sensor edge driver ocassionally gets stuck on wet.
I have been able to fix this by changing driver to the Smartthings z-wave switch and back.
Today the sensor is stuck as wet and a driver change did not fix it. I have cleared cache, force stopped app, restarted hub and phone with no luck. Any suggestions short of removing and readding the device?

ST V3 hub
Android OS
App version 1.7.98.21
ST version 47.03

[mean1979 (Justin Hyde)]

I have recently purchased this but not having much luck with the edge drivers. I have installed both the Water sensor 7 and Water sensor Pro 7 and they’re showing if I look in my hub, then ‘Driver’. I can see both ‘Aeotec Water Sensor 7 Pro’ and ‘Aeotec Water Sensor 7 Basic’ in the big list of drivers, but when I add the device (no matter how many times I remove it and re-add it) it just shows up as a Z-Wave switch and doesn’t allow me to change the driver (if I go into the device, click the 3 dots, there’s just ‘Edit’ and ‘Information’. Banging my head against a wall with this. Does anyone have any ideas what I need to do to get to the drivers I’ve installed? Had this with a couple of other new devices of late. With thanks in advance.

[JDRoberts]

Have you checked with Aeotec support? As SmartThings’ hardware partner, they are quite familiar with edge drivers, unlike some other manufacturers. You can start with the contact link on the following page:

https://aeotec.com/support/

[mean1979 (Justin Hyde)]

I’ve not tried yet to be honest. I wondered if it was something obvious that I have been missing, but will reach out to them to see what they say. Thanks!

[Terri_Baker (TeBa)]

Mine is using the smartthings z-wave sensor driver and works 98% of the time except when it gets stuck on occasion. Do you have that driver installed? If not, you can download it from the smartthings beta driver page.

SmartThings Edge Beta channel with this link:
Samsung account 8.9k

[HalD (Hal)]

@mean1979

click the 3 dots, there’s just ‘Edit’ and ‘Information’

No Driver option there means it has paired using a DTH. At this phase of the migration, I believe that custom DTHs are selected in preference to any Edge driver.

Pull up the API Browser to see what’s is being selected. That might give a needed clue.

SmartThings API Browser+ ... Now Available to All

GENERAL ANNOUNCEMENT I’m pleased to announce that we’ve found a more stable hosting solution for the API Browser+, with huge thanks to @h0ckeysk8er. He has very kindly volunteered to let me host this on his AWS server. In general, you should see no difference other than the new URL, which we no longer have to worry about it changing. It’s great to have a more robust server where this can run and I can finally stop worrying about my own internet or power disruptions knocking this offline . THANK YOU @h0ckeysk8er for your generousity and help in getting this all set up !!! New permanent URL is: https://api-browser-plus.pinsky.us/

[mean1979 (Justin Hyde)]

Thanks @HalD and @Terri_Baker
Here’s a few shots of the device using the new API+

If I try to change the Driver using the new API+ then I get this message,

despite having the aforementioned drivers for the Sensor 7 basic and Sensor 7 pro install (as well as the one that @Terri_Baker mentioned above from the Beta channel. very confused.

Additionally, here’s the drivers that are installed on the hub.

Thanks again for your support.

[Paul_Oliver (PCO)]

I see 2 problems in your 1st screen shot.

1. The fingerprint (Mfg. Code) is 0000-0000-0000 which means it it did not bind properly during pairing.

2. Type is listed as DTH which means it is using a Device Handler not an Edge Driver.

So you need to exclude the device and re-pair it. I would suggest doing it close to your hub to help ensure proper binding.

Also if you have a custom device handler it would need to be removed from the IDE before pairing.

[mean1979 (Justin Hyde)]

Thanks for the speedy response @Paul_Oliver . I’ve not got any Device Handlers installed so i don’t think it’s that. I’ll attempt to exclude it, however this didn’t work following the guidance I found for the device, so if anyone knows a work around in the API - holding down the pair button for 20 seconds didn’t do anything. I’ll re-pair close to the hub to bind better either way! thanks again

[Paul_Oliver (PCO)]

Remove your Door / Window Sensor 7 Pro from Z-Wave network.

Your sensor can be removed from your Z-Wave network at any time. You’ll need to use your Z-Wave network’s main controller/gateway. To do this, please refer to the part of your gateway’s respective manual that tells you how to remove devices from your network.

1. Set your Z-Wave controller into unpair (exclusion) mode.
2. Triple-click the tamper switch on Door / Window Sensor 7 within 1.5 seconds.
3. After a successful exclusion, it will green light up its LED for 2 seconds then deactivate.

Reset your Door / Windows Sensor 7 Pro.

This device also allows being reset without any involvement of a Z-Wave controller. This procedure should only be used when the primary controller is inoperable.

To manually factory reset:

1. Remove the cover of Door / Window Sensor 7
2. Press and hold tamper switch for 5 seconds until the red LED blinks.
3. Release the tamper switch
4. Immediately press and hold the tamper switch again, the LED will flash red 5 times while holding.
5. A green LED will confirm reset, which you may release the tamper switch.

[mean1979 (Justin Hyde)]

Amazingly thats worked. It installed as the Aeotec water sensor 7 Pro too so a great outcome! Having similar issues with some other devices so rinse and repeat…thank you.

[Paul_Oliver (PCO)]

You are welcome. Glad it worked.