KSchex Posted May 27, 2017 Posted May 27, 2017 Just purchased an Aeotec Zw120 Door/Window Sensor. Included it in my network, battery level works, tamper alarm works but Binary Sensor does not. I have reset my dongle, reset the sensor to factory settings, and excluded before including. Still no action. So I purchased another from a different vender, same thing. This is the second type door/window sensor I have purchased (first was a Linear WADWAZ-1) that does not work as it should. At $30 a pop this gets expensive. Obviously the ISY994 Zwave version 4.5.5 is not compatible I would really appreciate it if someone could recommend some compatible sensors as there are many out there. Thanks...
Jimbo.Automates Posted May 27, 2017 Posted May 27, 2017 You have to change a param, this post should help http://forum.universal-devices.com/index.php?/topic/20581-Aeon-Labs-Recessed-Door-Sensor-work-around-5.0.7 Sent from my Nexus 6P using Tapatalk
KSchex Posted May 27, 2017 Author Posted May 27, 2017 You have to change a param, this post should help http://forum.universal-devices.com/index.php?/topic/20581-Aeon-Labs-Recessed-Door-Sensor-work-around-5.0.7 Sent from my Nexus 6P using Tapatalk Thanks for the reply. I will try your suggestion. What does changing those parameters do?
Jimbo.Automates Posted May 27, 2017 Posted May 27, 2017 The parameters are described here http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/405 Sent from my Pixel C using Tapatalk
KSchex Posted June 6, 2017 Author Posted June 6, 2017 With regard to the Aeotec ZW-120 Door/Window Sensor Gen 5, I was able to change the Configuration Parameter 121 to enable it to communicate properly and display the Binary Sensor status. The Parameter Size is 4, and Value is 16. If you look at the data sheet for this device, the message structure etc. is a bit ambiguous. It is subtle problems like this that makes one wonder how non-technical people can deal with today's technology. Thanks all..
Jimbo.Automates Posted June 6, 2017 Posted June 6, 2017 The issue should be resolved hopefully with 5.0.11 so you won't need to change the param. Sent from my Pixel C using Tapatalk
elJosho Posted July 7, 2017 Posted July 7, 2017 That worked great for my Aeotec sensor - is there something similar for the Wintop iDoorSensor (magnetic open/close sensor + temperature + battery)? I have a few, some badged MiCasaVerde but they're all the same WinTop sensor, and they're exhibiting the exact same behavior as the Aeotec sensor did. I've found a few parameters for it online but nothing seems to work correctly. Thanks! -Josh
Recommended Posts
Archived
This topic is now archived and is closed to further replies.