Aeon Labs Z-wave Door / Window Sensor 6 ZW112-A

Other Devices & Integrations Door Locks & Sensors
1

I have a single door in my house that doesn’t lend itself to traditional door/window sensors, as there isn’t enough room along the frame to put half of the sensor component. Rather than go the route of the recessed center (I’d rather not drill into my door if I don’t have to), I finally found something that seems like it would work: the Aeon Labs ZW112-A [url=http://www.amazon.com/Z-wave-Window-Sensor-rechargeable-battery/dp/B01E0OMQR6/ref=sr_1_5?s=electronics&ie=UTF8&qid=1461940334&sr=1-5&keywords=aeon+labs]http://www.amazon.com/Z-wave-Window-Sensor-rechargeable-battery/dp/B01E0OMQR6/ref=sr_1_5?s=electronics&ie=UTF8&qid=1461940334&sr=1-5&keywords=aeon+labs[/url]...it requires only tiny little magnets, which I can fit on the frame, just barely. It’s a Z-wave Plus device, and on proper modern gateways, it can be enabled with a secure, encrypted connection.

Unfortunately, there isn’t a device profile for it in my Vera Plus. So I resorted to “Generic Z-Wave Device.” It finds the device and adds it just fine, but it shows up simply as a binary device, and gives me a simple “On/Off” toggle, rather than the “Armed/Disarmed” toggle I would expect of a sensor.

On top of that, it doesn’t appear to do anything. When I first register the device, I get a message in the log that says it changed “tripped” state, but I can’t get it to log or visibly demonstrate that it does anything beyond that. Whether set to “On” or “Off,” I see no registered changes when I connect or disconnect the proximity of the magnets.

I also tried adding it to Vera “disguised” as a different Aeon Labs D/W sensor, but that didn’t work. It appears to not accept the device (returning to the “Add device now…” prompt rather than completing), and then I end up with “Generic I/O device” cluttering my interface.

Anyone familar with this sensor, and how to get it into the Vera Plus (U17) as a sensor? I’m happy to hack away at Advanced Settings if I knew what I were doing…

2

I currently have two of these just got them from my distributor with an agreement to do a write up on the ease/diffuculty of getting these new devices to behave. have you found any solutions to this yet?

3

[quote=“ahsboy, post:1, topic:192191”]I have a single door in my house that doesn’t lend itself to traditional door/window sensors, as there isn’t enough room along the frame to put half of the sensor component. Rather than go the route of the recessed center (I’d rather not drill into my door if I don’t have to), I finally found something that seems like it would work: the Aeon Labs ZW112-A [url=http://www.amazon.com/Z-wave-Window-Sensor-rechargeable-battery/dp/B01E0OMQR6/ref=sr_1_5?s=electronics&ie=UTF8&qid=1461940334&sr=1-5&keywords=aeon+labs]http://www.amazon.com/Z-wave-Window-Sensor-rechargeable-battery/dp/B01E0OMQR6/ref=sr_1_5?s=electronics&ie=UTF8&qid=1461940334&sr=1-5&keywords=aeon+labs[/url]...it requires only tiny little magnets, which I can fit on the frame, just barely. It’s a Z-wave Plus device, and on proper modern gateways, it can be enabled with a secure, encrypted connection.

Unfortunately, there isn’t a device profile for it in my Vera Plus. So I resorted to “Generic Z-Wave Device.” It finds the device and adds it just fine, but it shows up simply as a binary device, and gives me a simple “On/Off” toggle, rather than the “Armed/Disarmed” toggle I would expect of a sensor.

On top of that, it doesn’t appear to do anything. When I first register the device, I get a message in the log that says it changed “tripped” state, but I can’t get it to log or visibly demonstrate that it does anything beyond that. Whether set to “On” or “Off,” I see no registered changes when I connect or disconnect the proximity of the magnets.

I also tried adding it to Vera “disguised” as a different Aeon Labs D/W sensor, but that didn’t work. It appears to not accept the device (returning to the “Add device now…” prompt rather than completing), and then I end up with “Generic I/O device” cluttering my interface.

Anyone familar with this sensor, and how to get it into the Vera Plus (U17) as a sensor? I’m happy to hack away at Advanced Settings if I knew what I were doing…[/quote]

Ok sorry for a double post, It seems to be working fine after my first try at editing the advanced settings to match one of my other door sensors

I went into advanced and changed:

device type - urn:schemas-micasaverde-com:device:DoorSensor:1
manufacturer - Aeon
Model - ZW112-B
device file - D_DoorSensor1.xml
device_json - D_DoorSensor1.json

and bam! appears the same as my other door sensors with the wireless symbol changing from red to grey on the UI appropriately.

Im not 100% but i believe this only worked for me as i already have a working door sensor installed so my vera has the required json and xml files to reference.
let me know if you have a different way of fixing this or if this does not work for you!

4

I had found similar instructions on the blog at The Smartest House (from whom I’d bought it), but that blog post was for the recessed door sensor. I figured I could make the same advanced settings changes that you describe. The blog post also mentions a specific “Device Options” setting, and I’ve tried the changes both with and without the special Device Options change.

In both cases, I do successfully get the “sensor” icon, and it does seem to arm/disarm initially, but then it gets a little red alert message (“Please wait! Getting the manufacturer…”) and it never gets beyond that point. I believe that it eventually shows up as “Not responding” after a while, but I’ll double check when I’m back home. I’ve also tried to contact The Smartest House people in hopes of getting an answer from them.

So you never encountered the “Getting the manufacturer…” stage?

I also notice that you refer to it as the ZW112-B, whereas mine is clearly labeled ZW112-A. Any idea what the difference is?

Later: I forgot to mention that using your technique doesn’t seem to be complete. Other users report (as can I) that the new sensor does NOT show up in the list of sensors that can be armed/disarmed during Mode changes. So for some reason Vera doesn’t fully recognize it as a sensor. Does anyone know enough about the magic “capabilities” and other advanced codes to know what else might need tweaking?

5

Iv had a look at the blog, seems quite similar to my suggestion other then the special device property.
I did a quick google and found a contradiction to the suggested device options change.

the aeon labs website device comparison page has a note added to the door/window sensor 6 section saying " #20 Parameter 121 [1 byte] must be set to 2 "
whereas the blog suggests " Variable: 121, Data Size: 4 byte dec, and Desired Value: 16."

heres the page i found for aeotec (not much useful info on there other then the note)
http://aeotec.com/z-wave-gateways#DoorWindowSensor6

i have absolutely no experience messing with these parameters maybe someone with some more experience could chime in, it may be nothing… or it may be something… haha

Re: the getting the manufacturer message, how long does it take for this to pop up for you?
I’ve had the device armed for 20 minutes now with no message.

Yes my device is clearly labeled ZW112-B, can’t find any info on this A/B difference, possibly a revised model? my distributor says he has only just got them in (hasn’t got them on his website yet they are that new to him)
In my device manual it does mention a secure pairing mode if your gateway supports it, I only mention this as after the recent UI7 firmware update all of my aeon led bulbs would not behave unless i removed them all and paired them in secure pairing mode ( after that all error messages went away and they are behaving normally)

lastly - you are right with the mode changing devices, I have just checked and my sensor too does not show up (not a problem for myself as i don’t use the built in modes)

just out of curiosity, do you have any other door sensors installed and working correctly at the moment?