Ok, so we have the definitive answer from Aeotec.
ZWA009 firmware version is V1.XX, there is a V12.01 custom firmware update available to try to improve the report time of the ZWA009 for those that have it (increase static threshold checks to 4 minutes per check, allow lower setting for parameter 4 timed reports). V12.01 can be found here as a .GBL file: https://help.aeotec.com/support/solutions/articles/6000253486-update-zwa009-aerq-sensor-v12-01
ZWA039 firmware version is V2.XX which utilizes the same identifiers, the main difference seen in firmware is this firmware identifier. There are a lot of differences with this version, the main reason the named model number is difference is because its hardware has been changed greatly:
- Additional and expanded parameter settings from ZWA009
- Updated Z-Wave SDK library used (i believe 7.15)
- Better pairing detection and LED activity (more clear when it pairs)
- Better sensors with better accuracy
- Better battery sensor design for improved voltage detection
- Improved hardware, button press detection, and casing design
So, based on this we would need to create a new version of ZWA009 with Version=12, change the current ZWA009 to V=1.000-1.255, and set the new ZWA039 to 2.000-2.255.
Most of this is easy - but as we don’t have an XML for the ZWA009 with version 12, that is more difficult. I propose for now to leave this since it seems to not be too common (based on the “for those that have the problem” statement in the above). When someone comes along with the new V12 we can create that entry - or if someone already has that, or possibly even another ZWA009 XML that we can use we could hack the versions to get this included.
I should also add that this still doesn’t tie up with the image above from ZWaveJS, but let’s ignore that as I’ve no idea where that info came from.