I had tried the Modify Configuration Parameter... but did again, after a factory reset of the sensor (exclude, reset, add), making sure to wake the device, etc.
Here are the device details (written to the log) prior to attempting to change parameter 3:
Indigo Z-Wave Version: 2023.2.0
Node ID: 148
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, 56, 112, 115, 128, 156, 199, 200, 201, 205, 206, 209, 210, 213, 214, 215, 216, 218, 219, 220, 221
Associations: 1:[1] 2:[] 4:[] 5:[]
Config Values: 2:1 13:1 14:1 15:1
Parameter 3 is not listed among the Config Values, but that doesn't surprise me as presumably it is in its default state after the reset.
Then ... here is the result (log) when I used Modify Configuration Parameter... to read the value of parameter 3 (prior to attempting to change it):
Z-Wave retrieved parameter 3 value: 0 (size 1)
Here is the result (log) when I used Modify Configuration Parameter... to write a value of 1 to parameter 3:
Z-Wave device " TEST - Door/Window" parameter 3 changed to 1
Finally, here are the device details (written to the log) after attempting to change parameter 3 to 1:
Indigo Z-Wave Version: 2023.2.0
Node ID: 148
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, 56, 112, 115, 128, 156, 199, 200, 201, 205, 206, 209, 210, 213, 214, 215, 216, 218, 219, 220, 221
Associations: 1:[1] 2:[] 4:[] 5:[]
Config Values: 2:1 13:1 14:1 15:1
Note that the Config Values have not changed — parameter 3 is still not listed.
And then ... as I indicated above, the unit actually seems to stop working — the log shows "on" every time I move the magnet close — as if the reverse worked, but then nothing appears in the log when I move the magnet away; in addition the state remains "on" all the time in the main Indigo window (under DEVICES), no matter what I do with the magnet.
I've been in touch w/ an Aeotec support person (he has been very responsive and helpful in the past) but no luck there yet — he wanted to know whether I could tell if the parameter was changing, so I reported the same (above) to him.
When I can do so I will try to use a Windows laptop and the Aeotec diagnostic software (whatever it's called) to see if I can see and difference there.