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+magnetAfter 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.