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
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.
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:
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!
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
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.
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 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
Remove your Door /WindowSensor 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.
Set your Z-Wave controller into unpair (exclusion) mode.
Triple-click the tamper switch on Door / Window Sensor 7 within 1.5 seconds.
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:
Remove the cover of Door / Window Sensor 7
Press and hold tamper switch for 5 seconds until the red LED blinks.
Release the tamper switch
Immediately press and hold the tamper switch again, the LED will flash red 5 times while holding.
A green LED will confirm reset, which you may release the tamper switch.
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.
To Terriās original post, I have an early Zooz ZSE40 Multisensor that gets āstuckā on āMotion.ā Swapping drivers and then back āfixesā it and āNo Motionā is reported. My hunch is that the general, generic SmartThings driver assumes no motion/water/whatever and, without bothering to poll the device status after the driver first initializesāperhaps when it wakes, if a āsleepyā deviceāafter the new driver is selected, doesnāt know the difference! Should someone walk into the room where my motion sensor resides (Iām not at that house right now and no one is home), it would report āMotionā and then āNo Motion,ā therefore reflecting the correct status.
It would be an interesting experiment, @Terri_Baker, if this is still an issue for you, to go stick that sensor in water, then remove it and let it report āDryā againājust to see if it is the same issue.