Same. It’s the only place I could find it. Only one seller too.
Hi! Would you mind to share who was the seller? If you could provide a link would be even better 
Stuff2SellThree
I finally got my hands on the “new” version that is supposed to be compatible with the Yale Assure Lock 2 smartlocks. It appears to be the old version (ZW2) in green, not the ZW3 (black) version. It does not have SmartStart ability, and the security is S0 Legacy. DoorSense doesn’t appear to work. Their support is next to useless. I got a response today from them:
We’ve researched the compatibility of this Z-Module and it only works with Samsung Smarthings, Ring, and Avatar.
We recommend that you contact Home assistance to see if this Z-Wave module can be enrolled.
They’re idiots. Ring doesn’t have Z-Wave, and Avatar is a lighting product from what I can tell.
I’m half tempted to return these and get the ZW3 modules listed on eBay, so at least I’ll have SmartStart and S2 security.
I found this article over on the Hubitat forums, and it links to a Yale FAQ page regarding the ZW3 modules. It would appear the ZW3 modules are only sold to wholesalers and won’t be available until 2024 to the general public. The ZW2 modules they are shipping now for the Assure Lock 2 are 500 series with S0 legacy only, and the DoorSense is buggy at best.
I just ordered two ZW3 modules off of eBay. I’d rather have the 700 series chipset and S2 security, even if it isn’t officially supported by Yale. At least the 700 series have to have OTA firmware updates in order to get the 700 series certification. If it doesn’t work for me, I’ll return it. If it does, I’ll return the ZW2 modules to Yale.
Either way, they have the worst support on the planet. I tried calling them up again, and the woman I spoke with said that they didn’t have any agents that were really familiar with Z-Wave, and that she was going to give me a phone number to call, which was going to be to the Z-wave alliance.
And I thought Comcast was bad….
@migbot, did you find a way to update your firmware? I just got the ZW3 modules in off of eBay, and I’m on the same version as you.
Also, has anyone requested on the zwave-js github page to define the device?
No. Yale doesn’t provide any firmware. They won’t officially own up to supporting the module with assure 2 either, so attempts with level 1 support are short. Hopefully that will change. For this reason, I have not requested device support at zwave-js yet.
Yale’s Tier 1’s are terrible. I tried to get support for the ZW2 (official supported with Assure Lock 2), and I can’t get them to call me back or respond to my emails. They basically are telling me this is a problem with Home “assistance” and to ask them. After emailing them twice in response, the only thing I’ve gotten from them is a request to close the ticket because I haven’t responded to their email (like I said, I emailed them twice).
As for the ZW3, this is what I’m seeing in my controller
One of them does show the door state, the other does not.
I am seeing events in the logbook for the one that is showing the state.
I can live with this. I might try and learn how to write the config file for Z-wave JS so all the values fill in correctly. I’m not really sure how difficult it is, but it’ll give me a project for a while.
Hello everyone. Thanks for posting this information, I also ended up getting the zw2 modules from yales site thinking they were newer. I returned them and got two ZW3 modules off ebay. The box says they are version 2.35.0, I won’t know if doorsense works because I haven’t installed the magnets in the door frame yet. Does anyone have this FW version and know if it still has issues? Is there a way to dump the FW off these?
I ordered a ZW3 and it unfortunately came with firmware version 2.17, not 2.35 that others are seeing. It paired successfully with s2. I do not, however see a way to program codes and the “lock” command is not available. Is there something I did wrong? Has anyone had any success getting newer firmwares from Yale?
Reinterview the lock.
I tried re-interview. I am going to attempt to exclude and include again to see if that fixes things.
Edit: Excluding and including again got the lock to show up correctly. All looks good now.