Aeotec Door Window Sensor 7 Pro - won't recognise open state

@bravenel I got some brand new Aeotec Door/Window Sensor 7 Pro's in the mail today, but no matter what I try (include with or without security, both work just fine), I cant get them to recognise when the magnet moves away from the Sensor area.

I got these after the ZWJS upgrade, so I cant say if they would have worked in legacy mode.

The Tamper sensor state and battery both report without issues - any ideas?

C-8 Pro FW ver 2.4.1.151
ZW Radio/SDK 7.18.1 / 7.18.3
ZWJS = Yes



EDIT: it came from the factory with the current FW installed:

Close state is recognised, but not Open:

Extra data point:

I tried using the external contact config, and I get the same behaviour - I see the LED on the sensor activate, but only "Contact Closed" states are registered.

I have one of these, though possibly on an earlier firmware version if there are multiple, and it works on Z-Wave JS for me. But I see what is happening from your logs: it's using one of the more specialized values for the open state (that's the log entry with the "5632" value you should see generated when you open the sensor if you're watching in real time). Maybe that is something Aeotec changed in newer firmware.

The driver can be adapted to handle this (EDIT: nevermind, Bryan sees what JS is really doing with the value reported like this and it's being addressed in the class instead, but either way, a fix is coming). Likely in the next build.

4 Likes

Will be fixed in the next build.

5 Likes

Thanks Bryan, much appreciated. :+1:

2 Likes

Thank you @bcopeland this is now working perfectly in .153.

1 Like