I have an Aeotec Door Sensor 7 (model ZWA008, z-wave), which I need to run in “dry contact sensor” mode. Does anyone know of an Edge driver that works with this sensor? I have installed the original driver from Aeotec, but it does not work properly. The simple “magnet sensor” mode and the tamper alarm works, but neither does the “dry contact” nor the “sensor reversal” setting. Before Edge, it worked well with a DTH, so the device itself is ok.
Was the driver you tried from this link?
Aeotec Edge Drivers : Aeotec Help Desk (freshdesk.com)
I have the same sensor and in dry contact mode it chewed through batteries in no time making it unusable that way. Others on the forum have reported the same. That was using the old DTH so would be interesting to know if an edge driver makes any difference (if one exists that allows setting change).
Yes, I have noticed that with the old DTH, too. I guess this would also apply to the edge driver, but only time will tell. I need this to work for me even if it eats through batteries quickly.
I have not found any other “dry sensor” device on the market that would open/close depending on the presence or absence of current on a sensor contact. If someone knows of a device, please let me know!
Regarding my problem with changing the device parameters in the edge driver, the Aeotec support team was very helpful and told me how to make it work. The point is that for the edge driver they cannot tell the driver to wait for a wakeup report and then push the new setting to the device. The old DTH could do that. So, to make changes in the parameters, it is necessary to IMMEDIATELY after saving the new setting to press the tamper button to send a wakeup call to the device. This worked for me the first time I tried it. It may be necessary to do it several times to get the timing right, but it does work. The same applies for changing the “sensor reversal” setting.
Finally got mine working with the Edge driver thanks to the instructions above.
Never had battery problems using it as a doorbell sensor. I did read a while back that when the dry sensor is closed the device trickles a current through the sensor to be able to detect when it opens. So I run mine with default open, then the doorbell relay closes the dry contact and the sensor sends the signal to the other doorbells around the house.
Hope that helps, though it may not be possible with your specific application.
Perhaps, using a n/o contact instead of n/c contact would solve the early depletion of the battery. I’m planning to purchase a few of the n/o contacts for my door contacts. The edge driver seem seems to work much better after the sensor got its head straight.
There is a community FAQ for this. It has been updated to say which ones have edge drivers, and there are a number of candidate devices. The selection does vary by region.
I want to connect a standalone keypad to the window sensor to trigger a scene in my home automation. I guess this is not too different from what you are doing.
Would you mind sharing how you set up the sensor?
Many thanks, Christian
Sorry, didn’t see this until now. I suspect you’ve figured it out by now.
Chris. I am a new member to this Smart Things group, but I too want to use the Aeotec Door Window Sensor Pro 7 as a door bell slave. My problem is that it all connects ok via a relay to operate the sensor, BUT the problem is that it takes one door bell pulse to wake up the sensor where upon it responds ok to all subsequent pulses. After about 30 seconds, it seems to go to sleep again and will need another wakeup pulse before it cand send forward other pulses to my Fibaro HC3. Have you had this problem? Perhaps if you could state your Sensor Parameter settings. I have simply set P1 = 1
Best Regards RonH
This forum was set up a number of years ago so that customers could help other customers with the Samsung SmartThings ™ Home automation platform, so all of the questions and answers are assumed to be in that context.
It sounds like you may be using the Fibaro home center platform instead, which is a competing brand. It is possible to use some of the same end devices with both platforms, but the way you set them up and configure them is quite a different process. And the way the devices act may be somewhat different from platform to platform.
For example, the post you are responding to discusses edge drivers, which are used with the SmartThings platform, but are not used with the Fibaro home center.
So you might get more helpful answers if you post in the fibaro community instead.
Hello. I’ve not come across that problem. I operate the sensor in ‘Dry Contact Sensor Mode’ and ‘Reverse state’ of sensor reversal. It also has a setting for Association Group 1: Lifeline, which is blank. These are all settings in the Edge driver for Smartthings. I haven’t had to do anything else. I just kind of works, most of the time.