New Device (I believe) Aeon Labs Door/Windows Sensor 7

Hi,

https://aeotec.com/z-wave-door-window-sensor/
https://aeotec.freshdesk.com/support/so ... user-guide

New Device definition (or perhaps model ID needed)

Aeotec Door/Window Sensor 7.
Syncs, reports battery - "Notification Sensor" but no on/of state change with magnet door/open close.

Details below:

Code: Select all

Indigo Z-Wave Version: 7.4.1
Node ID: 161
Model: Notification Sensor
Model ID: 02020007
Manufacturer: Aeon Labs
Manufacturer ID: 0371
Protocol Version: 6.02
Application Version: 1.00
Model Definition Version: 0
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 80v1 84v2 85v1 86v1 8Ev1 55v1 59v1 5Av1 5Bv1 5Ev1 9Fv1 20v1 70v1 6Cv1 30v1 71v1 72v1 73v1 7Av1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 5, 10, 29, 35, 44, 46, 47, 48, 51, 52, 55, 56, 93, 102
Associations: 1:[1] 2:[] 3:[] 4:[]
Config Values: - none -

Thanks

Glenn

Hi Glenn,

I think it's not a new device, but maybe the model ID is changed?

viewtopic.php?f=58&t=22581

Ours is working perfectly with Indigo since 9 months.

Regards,

John

[matt (support)]

John is correct – we'll get the model ID yours is using added to the next version of Indigo.

[matt (support)]

Indigo 7.5 is now available and includes the model ID for your Door/Window Sensor 7.

Hello.

Similar issue w/ some ZWA011 versions of Aeotec's Door/Window Sensor 7. I am only able to get them to join as "Notification Sensor" which, as far as I can tell, cannot do anything. At least the open-close functionality (w/ the magnet) does not work.

This is on Indigo 2021.1.0 running on macOS 10.15.7.

I've reported the sensor via the web form (from the device settings dialog, on the server), but here's the information anyway:

Indigo Z-Wave Version: 7.5.1
Node ID: 156
Model: Notification Sensor
Model ID: 0102000B
Manufacturer: Aeon Labs
Manufacturer ID: 0371
Protocol Version: 7.12
Application Version: 1.01
Model Definition Version: 0
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 80v1 84v2 85v1 86v1 87v1 8Ev1 55v1 59v1 5Av1 5Ev1 9Fv1 20v1 6Cv1 70v1 71v1 72v1 73v1 7Av1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: - none -
Associations: 1:[1] 2:[] 3:[] 4:[]
Config Values: - none -

As I indicated when I submitted it, I guess this is the "not Pro" (amateur?) ZWA011 version of their Door/Window Sensor 7. I did not even know that there was a "Pro" and "not Pro" version of the sensor, and accidentally ordered some "not Pro" versions from Amazon. (At first I thought they were defective because they don't have the terminal block inside...then I found out that the missing terminal block was intentional....)

I'm holding out hope that supporting them in Indigo won't be involved....

Thanks.

[matt (support)]

Indigo supports both versions of the Door/Window Sensor 7, so I think we just need to add the model ID for particular one you have. Is the specific model on the module itself ZWA008?

We'll get it added to the next version. In the mean time, try using a Trigger on the raw command shown on this post to see if that works.

The label inside the device says

Model: ZWA011-A (908.42MHz)
FCCID: 2AOGIZW011

The raw command triggers appear to work, although I seem to get both open and close messages/triggers every time I bring the magnet close OR move it away. (I would expect either an open or close when I bring it close or far, but not both.)

Thanks Matt.

Unless I'm dreaming I think this now works in 2021.1 (.1). I was able to add two, of them, they were identified properly (it seems) and work as expected. Thank you Matt!

[matt (support)]

Yep, the ZWA011 was one of several modules we added support for to 2021.1.1. I'm glad it is working for you now!

I have multiple brand new Aeotec / Aeon Labs Door / Window Sensor 7 Pro units (note the "Pro"), model ZWA012-A02, and Indigo appears to be reporting the open-closed state for magnet use backwards. Specifically Indigo reports OFF when the magnet is near, and ON when the magnet is far, i.e. a normally-closed behavior. I have seen this in five new units, out of the box and after resetting the units

I am wondering whether Matt or Jay can confirm that this specific version, which Aeotec refers to as ZWA012 V2, is supported. I ask because the parameters seem to be different than in the first version of the "Basic" and "Pro" versions of the Door / Window 7. For example, in the first versions the "Door/Window State" was parameter 2, whereas in V2 (ZWA012-A02) it is parameter 3.

https://aeotec.freshdesk.com/support/solutions/articles/6000230465-door-window-sensor-7-pro-user-guide-zwa012-

The documentation for both the previous and new devices that for the "Door/Window State" (parameter 2 in the previous, parameter 3 in the new), a parameter of 0 is "closed when the magnet is near." and 1 is "opened when the magnet is near," and both say 0 is the default.

I have also been unable to change the near-far magnet behavior through various means, including using "Modify Configuration Parameter ..." and "Send Raw Z-Wave Command ...." as we discussed in a previous thread for the Door / Window Sensor 6 (previous model).

https://forums.indigodomo.com/viewtopic.php?f=58&t=24071&hilit=reverse+magnet

After resetting one of the units, the device info is

Indigo Z-Wave Version: 2023.2.0
Node ID: 147
Model: Door/Window Sensor 7 Pro (ZWA012)
Model ID: 0102000C
Manufacturer: Aeon Labs
Manufacturer ID: 0371
Protocol Version: 7.15
Application Version: 2.02
Model Definition Version: 1
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 5Ev1 85v1 8Ev1 59v1 55v1 86v1 72v1 5Av1 87v1 73v1 80v1 9Fv1 30v1 71v1 70v1 84v2 5Bv1 6Cv1 7Av1
Encryption Status: Not Supported
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, waking
Neighbors: 38, 41, 112, 128, 156, 186, 199, 200, 201, 205, 206, 210, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 223
Associations: 1:[1] 2:[] 3:[] 4:[] 5:[]
Config Values: 1:0 2:0 13:1 14:1 15:1

I then used Indigo's Z-Wave command Received trigger mechanisms and attempted to gather the Z-Wave packets for when the magnet is near and far (not near), and I saw the following:

Magnet NEAR (moved close to unit)

5.4 seconds ago from 147 - TEST - Door/Window:
raw packet bytes: 0x01 0x0F 0x00 0x04 0x00 0x93 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x17 0x00 0xF4
suggested match bytes: ? ? ? ? ? ? 0x09 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x17 0x00 ?

Magnet FAR (moved away from unit)

5.0 seconds ago from 147 - TEST - Door/Window:
raw packet bytes: 0x01 0x10 0x00 0x04 0x00 0x93 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x16 0x01 0x00 0xE8
suggested match bytes: ? ? ? ? ? ? 0x0A 0x71 0x05 0x00 0x00 0x00 0xFF 0x06 0x16 0x01 0x00 ?

This is clearly not a show stopper — I can reverse trigger logic, etc. but it would be nice to have it right, and I'm wondering whether I'm missing something.

Thanks.

I have multiple brand new Aeotec / Aeon Labs Door / Window Sensor 7 Pro units (note the "Pro"), model ZWA012-A02, and Indigo appears to be reporting the open-closed state for magnet use backwards. Specifically Indigo reports OFF when the magnet is near, and ON when the magnet is far, i.e. a normally-closed behavior. I have seen this in five new units, out of the box and after resetting the units

Off when magnet is near should be the correct status. Off is Closed, On is Open. That's how my Insteon door sensors work, and I would expect the Z-wave ones to work the same.

Oh boy, of course you are correct. While posting my brain flipped. I'd love to retract my post but ....

The actual issue I am seeing is buried further in my post:

I have also been unable to change the near-far magnet behavior through various means, including using "Modify Configuration Parameter ..." and "Send Raw Z-Wave Command ...." as we discussed in a previous thread for the Door / Window Sensor 6 (previous model).

For example, I have tried sending 0x70 0x04 0x03 0x01 0x00 (or 0x01) but no luck.

Strangely when I use either the config or raw commands to set parameter 3 to 1 (which should reverse the behavior), it actually stops functioning.

It's certainly possible it's a device issue, but I'm wondering whether any Indigo users have successfully reversed the magnet behavior, and how.

Also wondering whether the ZWA012-A02 version should work (is fully supported).

Thanks.

[jay (support)]

Also wondering whether the ZWA012-A02 version should work (is fully supported).

I don't have one so I can't confirm the other stuff, but unless they changed the behavior it should work correctly. Aeotec doesn't often change behavior (on purpose) so I would be surprised if it didn't work the same.

Jay (and Matt), if I have a unit sent to you (Amazon or Aeotec) would you be able to look at / play with it? If so please send me a shipping address etc. via private message if you like.

I am surprised too. The other version 6 and earlier 7 all work as expected — it's only ZWA012-A02 that does not, for me. I've tested five.

Another surely related thing is that in "Edit Device Settings..." the "Operation mode:" pop-up is grayed out, but it should offer "Use Internal Magnet Sensor" and "Use External Terminal Connection" as the "Pro" units have a terminal block for wiring dry contacts, power, etc. All of my other 7 Pro units have a working (not grayed out) popup.

Thanks.

[matt (support)]

The documentation for both the previous and new devices that for the "Door/Window State" (parameter 2 in the previous, parameter 3 in the new), a parameter of 0 is "closed when the magnet is near." and 1 is "opened when the magnet is near," and both say 0 is the default.

Argh. It is most unfortunate they changed the configuration parameters around for a newer version of the module using the same model ID. That makes our device definitions impossible to define (for both module versions).

Anyhow, you should be able to use the Modify Configuration Parameter... menu item to manually change parameter #3. using Param Size of 1. Try waking up the module (normally via press holding its button for a bit) immediately before you press the button in Indigo to modify the config parameter. If it doesn't work, then copy/paste the Event Log window results into a reply for us.