Experiences with a Yale Assure Lock 2 (YRD420) and a 700 series Smart Module (AYR-MOD-ZW3)

[airdrummingfool]

This discussion is just to share some information and my current experience with a Yale Assure 2 lock and a Yale Z-Wave 700 series Smart Module (which are not available from Yale yet, but can be purchased on eBay).

Update 04/04/2024

I now have DoorSense via Z-Wave! The Integrator's Guide (2023 version, thanks @LSR19!) page 31 shows that DoorSense notifications can be enabled by writing 0xFF (255) to parameter 19 ("DPS Alarms") of the Configuration CC. After doing that, I started getting DoorSense updates via Z-Wave!

TL;DR

• The Yale Assure Lock 2 does not yet officially support the 700 series smart module
• Door open/close reporting (from DoorSense) does not work via Z-Wave (it works fine via BT)
• Lock/unlock functionality and reporting seems to work great via Z-Wave, and the lock has been solid and stable for over a week
• Yale is "working on a firmware update that will resolve the compatibility problems"

Details

I recently bought a Yale Assure Lock 2 (YRD420) and paired it with Yale's new Z-Wave 700 series module (AYR-MOD-ZW3), essentially making a YRD420-ZW3. It included to to my 500 series Zooz Z-Wave stick with S2 Access Control security without any issues. The device ID is 0x0129-0x8104-0x45d2.

Everything seems to work perfectly except for DoorSense door open/closed reporting - door status is always undefined, and it doesn't look like the module transmits any Z-Wave data when the door is opened or closed. My understanding is that this isn’t a Z-Wave-JS problem, but a limitation in the smart module itself.

Z-Wave JS doesn't have a config entry for this device yet, but since everything seems to work, it's not a big deal. Plus, there's no official entry in the Z-Wave Alliance DB (there is one for the YRD420-ZW2, which is the same lock with a previous-generation Z-Wave module). There is a (draft?) manual available.

I reached out to Yale support, and they replied with the following:

We regret to inform you that the AYR-MOD-ZW3 module is not fully compatible with the Yale Assure lock 2. However, we’re aware of the issue with the compatibility and working on a firmware update that will resolve the compatibility problems.

Unfortunately, we don’t have an estimated time for when the firmware update will be available. We apologize for any inconvenience this may cause and assure you that we’re doing everything we can to resolve the matter as soon as possible.

So I guess I'm holding tight and hoping that an update comes out soon(ish)!

[webmogul1]

Yale now offers a zwave version of the Assure Lock 2. But it seems it is sill the old version:
https://shopyalehome.com/products/yale-assure-lock-2-touchscreen-with-z-wave-plus?variant=41399131078788

Module only: https://shopyalehome.com/collections/accessories/products/yale-z-wave-plus-smart-module-for-assure-locks-yrd450430420410?variant=41397668970628
Description says: AYR-MOD-ZW2-USA

I have the YRD430 and the firmware was updated from 1.3.4 to 1.3.10.

@airdrummingfool Can you check which firmware you have and if DoorSense works?

[airdrummingfool]

@webmogul1 my lock's firmware is 1.3.10 and the Z-Wave module's firmware is 2.35.0. DoorSense is still not working.

I did notice one small (unhelpful) change after the lock's firmware updated to 1.3.10 last week: the "Current status of the door" sensor went from unknown to unavailable - it seems like that sensor doesn't exist anymore. There are other "door state" sensors (that are all unknown), so I'm not too concerned about it.

[rfg81]

@airdrummingfool could you please tell me what's the firmware printed on the label of the zw3 module?

[airdrummingfool]

Sure - the label says v2.35.0.

[rfg81]

Sure - the label says v2.35.0.

Thanks! It seems this is the newest one around. Do you have a link where you bought it?

[airdrummingfool]

I found it on eBay, but the listing I bought from is gone now (link is dead).

[webmogul1]

Too bad Yale announced the Zwave option for the Assure 2 locks without the latest generation Zwave module.

[tamorgen]

@airdrummingfool,
I have 2 of the YRD420 locks as well. I purchased them last October, and at the time, I thought I bought the z-wave modules for them (ZW2). One of them worked fine, the other didn’t. After 3 phone calls with Yale, they finally revealed that the particular firmware on that module wasn’t compatible with the 400 series, and that the new ones would be available by the end of year. I returned the two z-wave modules to Lowe’s

After waiting an additional 6 months, they finally released “new” versions of the ZW2, and I purchased two of them. I had problems pairing them into Home Assistant/Z-Wave JS UI, and I contacted their support. Their support is next to useless. Eventually I did get both modules included into Z-Wave JS UI, but DoorSense is buggy and doesn’t seem to report properly. One door says it’s open when it’s not, and the other says it’s closed. I’m also getting different sensors/entities between the two devices, which is totally strange. I’ve tried reaching back out to their support, but I’ve gotten zero response.

What I’ve discovered in regards to the new ZW2 modules.

Z-Wave Plus version 1
S0 Legacy security
Lock function does work
DoorSense iffy

This is hardly any different than what I had originally back in October.

Yesterday I ordered two ZW3 modules off of eBay. If the only thing that doesn’t work is DoorSense, I can live with that. Since the ZW3 modules are 700 series, in theory if there is a firmware update, they can be updated over the air. Since the DoorSense really isn’t working on the ZW2 modules, it seems to me that I’m better off with the ZW3 modules with Z-Wave Plus version 2, 700 series, and S2 security.

If you hear anything from your contacts within their support team, let everyone know.

[webmogul1]

@tamorgen same boat here. Got the lock in October and waited patiently for a zwave module just to learn a Zwave Plus v1 was now released.
Anyway, $100 for a module when the whole lock + module is $180 seems a lot.

[webmogul1]

@rfg81 It looks like a new ZW3 will be released later.
Take a look at this doc: https://products.z-wavealliance.org/ProductManual/File?folder=&filename=product_documents/4751/YRC612%20Manual.pdf
It lists all 400 series locks.

[tamorgen]

@rfg81 It looks like a new ZW3 will be released later. Take a look at this doc: https://products.z-wavealliance.org/ProductManual/File?folder=&filename=product_documents/4751/YRC612%20Manual.pdf It lists all 400 series locks.

According to the Yale website, the ZW3 is technically available now through "select dealers and wholesalers":

700 Series Z-Wave Plus Smart Modules only through select dealers and wholesalers.

We expect to roll this out to retail and ShopYaleHome.com in 2024

I find it a bit insulting that they made consumers wait 7 months after the release of the Assure Lock 2, only to get a outdated standard.

[rfg81]

In this link they are saying they will release officially just in 2024 https://support.shopyalehome.com/en_us/z-wave-smart-module-faq-BymsRfEI

[cybergrimes]

2024? Yeesh, they originally announced the 700 module way back in Sept 2021.

https://www.yalehome.com/us/en/stories/news/yale-upgrades-smart-lock-connectivity-with-new-z-wave-700-series-module

[jasonkelly214]

@airdrummingfool,

I have 2 of the YRD420 locks as well. I purchased them last October, and at the time, I thought I bought the z-wave modules for them (ZW2). One of them worked fine, the other didn’t. After 3 phone calls with Yale, they finally revealed that the particular firmware on that module wasn’t compatible with the 400 series, and that the new ones would be available by the end of year. I returned the two z-wave modules to Lowe’s

After waiting an additional 6 months, they finally released “new” versions of the ZW2, and I purchased two of them. I had problems pairing them into Home Assistant/Z-Wave JS UI, and I contacted their support. Their support is next to useless. Eventually I did get both modules included into Z-Wave JS UI, but DoorSense is buggy and doesn’t seem to report properly. One door says it’s open when it’s not, and the other says it’s closed. I’m also getting different sensors/entities between the two devices, which is totally strange. I’ve tried reaching back out to their support, but I’ve gotten zero response.

What I’ve discovered in regards to the new ZW2 modules.

Z-Wave Plus version 1

S0 Legacy security

Lock function does work

DoorSense iffy

This is hardly any different than what I had originally back in October.

Yesterday I ordered two ZW3 modules off of eBay. If the only thing that doesn’t work is DoorSense, I can live with that. Since the ZW3 modules are 700 series, in theory if there is a firmware update, they can be updated over the air. Since the DoorSense really isn’t working on the ZW2 modules, it seems to me that I’m better off with the ZW3 modules with Z-Wave Plus version 2, 700 series, and S2 security.

If you hear anything from your contacts within their support team, let everyone know.

Which firmware version do you have on the lock? I re-paired my lock with my zw3 module because I was having some trouble with it and now I can no longer get it to pair. I just get a pairing failed error. Somewhere in there I updated the lock firmware to 1.3.10. Hoping I can rule the firmware out as the culprit.

[tamorgen]

Which firmware version do you have on the lock? I re-paired my lock with my zw3 module because I was having some trouble with it and now I can no longer get it to pair. I just get a pairing failed error. Somewhere in there I updated the lock firmware to 1.3.10. Hoping I can rule the firmware out as the culprit.

I have the same version, currently paired with the ZW2 module. I was prompted for the firmware update when I paired the ZW2 module.

ZW3 modules are out for delivery today. Mail usually comes before 3 EST, so hopefully I have those modules in my hand soon and I’ll provide my results and device information. Crossing fingers.

[tamorgen]

I just got the two ZW3 modules in, and they added to Home Assistant relatively easily with Smart Start DSK. Home Assistant is showing Assa Abloy as the Manufacturer, vs Yale for the ZW2, and it's showing 0x8104 for Product, and Unknown product 0x45d2 for Product Code.

S2 Access Control completed successfully, and It does show as Zwave+ version 2. FW is showing as v2.17.0.

I am able to lock the deadbolt, and it is providing me the battery state. I am not yet getting the state of the door. I have a wired door sensor to my alarm system to determine if the door has been opened, so I'm not terribly concerned about that, but overall, I'd say it's better than the ZW2 version that I had a hard time pairing, and was running S0 Legacy, Zwave+ version 1, and a 500 series control chip.

I imagine I can get the manufacturer and product/product code updated if I submit a request the the Z-Wave JS UI group here on Github. I had the same sort of unknown stuff when I first tried to add this lock to my system back in October with the original ZW2 module.

[hecareth]

I have 4 of the YRD-450s so just ordered 4 AYR-MOD-ZW3 modules from the ebay guy. not going to lie the fact I only paid like 190 for these locks to have to spend an extra 100 for a ZWave module is nutty, but I'm sure I will make that up in buying batteries over the course of the year. Not sure if it makes a difference but I have a Zooz 800 LR controller as I heard the 700 controllers were buggy at some time.

Curious, what do you use to manage the keys?

[I1100]

Same experience - I have Yale Assure Levers and Assure 2 450s with the ZW3 module - the Assure Levers report correctly in Z-Wave JS UI but not the 450s. Functionality is same as you report. I had put in an issue with Z-Wave JS UI Git and provided the manual and they commented that the manual included all the variations including the Assure 2 with ZW3 in all the different models they have:
#5650

[d0u8l3m]

Hello everyone. Thanks for this wealth of information. I'm also in the same situation, bought the "new" Assure 2 compatible modules off yales site and realized that they were the older 500 series chipset (sending them back now).

I have two 410s (keyed, w/buttons) and just bought two ZW3 modules off ebay. Hopefully I can try to be of some help with setting up this config. The modules I got say they are FW version 2.35.0 on the box, I have the Zwave JS integration though. Do I need to switch to another add-on for this to work? Does anyone know if doorsense is fixed on 2.35 or does that have to do with the config?

[airdrummingfool]

@Narcopolypse ah, that is very helpful! That answers my question - it looks like command class 113 Notification, property AccessControl.DoorState. That's one of the ones in my screenshot that is showing undefined.

Z-Wave JS UI is just Z-Wave JS with a frontend, so that wouldn't make a difference. My guess is that since you're using a slightly different lock (YRD430?) it is slightly more compatible? It's also possible that since you set your lock up more recently, it had a more updated firmware when connecting to the ZW3? Neither of these are great guesses though 🤷‍♂️ I suppose it's time for me to re-setup my ZW3 from scratch and see if that helps!

Thanks for sharing that info - it gives me hope that my lock will get DoorSense over Z-Wave sometime!

[jasonkelly214]

I've been following along a little so apologies if this was touched on already but along with doorsense I'm also not seeing the most recent user code ID. I see it in the zwave log but I don't see anything in the notification tab of the device and of course it doesn't make its way to the home assistant configuration either. I'm guessing this is because it's not sure what to do with the property after an interview since (if I recall) it's more of an appended attribute than a direct CC.

[Narcopolypse]

@airdrummingfool
Glad I could help. I know what Z-Wave JS UI is, I just don't run it so I didn't know where to find those values right away.
My lock is a YRD450 (same as the 430, just a touchscreen rather than physical buttons). The reason I went with the YRD450 is it is the only lock in the Assure 2 line that has a ZW3 SKU listed on the Z-Wave Alliance DB. I figured it probably counts for something that it's the only certified combo package, even if you can't actually buy it that way yet.

[airdrummingfool]

@Narcopolypse

The reason I went with the YRD450 is it is the only lock in the Assure 2 line that has a ZW3 SKU listed on the Z-Wave Alliance DB. I figured it probably counts for something that it's the only certified combo package, even if you can't actually buy it that way yet.

ha, smart thinking to check that. I just assumed they would all "just work" 😅 . Thanks again for sharing your info!

[Randall-Mann]

I have a NTB612 that I pair with an Alarm.com (Qolsys) panel. I installed a few months ago (older ZW2 module) and the batteries lasted only a few days. I was told by Yale (Assa Abloy) that I need the AYR-MOD-ZW3-USA module (but they didn't have info on firmware version for the module). I see the ones listed on Ebay are V 2.17.0 and I see a reference on this thread with V 2.35. Can anyone tell me if the firmware version will update once installed or do I need to find a V2.35 somewhere (or if the v2.17.0 will fix my battery drain issue)?

[hecareth]

Hey folks got my AYR-MOD-ZW3 modules today so wanted to let you know my experience installing them on all 4 of my Assure Lock 2s (YRD450).

Controller: Zooz Zwave 800 LR USB Stick on HAOS installed on Dell Optiplex 3050 USFF running the latest software.
Latest Firmware on each lock: 3.10 (I believe)

1. I am using the august app, so I went into the App and copied over all the programmer codes. I'm sure they might be in a manual somewhere but it was just easier to it this way
2. I pulled all the batteries out of the devices, and swapped out each module
3. Put the batteries back in and let the devices start.
4. Added each new module to ZWave JS using Smart Start to scan the code and set the security to S2
5. Then for each device I included it to my controller by Entering the A) Programmer Code then Gear B) Pressing 7 then Gear and C) Pressing 1 then Gear (Pressing 3 is for exclusion)
6. It took maybe 30 seconds for the device to pop up and start the interview. Interview took about 30 seconds to a minute for each device.

That was it everything I need seems to be working. It adds a shit ton of entities which I don't even know works. I do know the Door sense contact sensor is not working so I disabled it. I actually put ZWave Sensitive strips in my door cracks to handle opening and closing. Which are great because I don't see them when the door is closed.

I installed Key Master, mainly so I can sync my codes all from the front door, and that seems to work well also. I use Google Home as my main control interface so they got exposed perfectly with no issues.

Now one thing that I really love is how responsive these locks are. They are almost instantaneous compared to the maybe 4 - 5 second delay with the WiFi locks. I have an automation running in Node Red that Lights up the Relay LED in all the Zooz Scene controllers I have in the house (8 in total). It lights green when all doors are locked and red if one door is unlocked. The led changes happened immediately a change occurred. With Wifi it sometimes took anywhere from 1 minute to 20 minutes...and I had to run a side automation to reload the integration just to make sure it ran.

All in all I am happy. Yes these things cost $100 a pop, but they work sooo much better now.

[Hamish1066]

Is it possible to enroll them without using the Yale app when pairing with the YRD450? I know you could use z-wave without the app on the Assure 1, but I don’t think it’s possible on the Assure 2?

[hecareth]

Is it possible to enroll them without using the Yale app when pairing with the YRD450? I know you could use z-wave without the app on the Assure 1, but I don’t think it’s possible on the Assure 2?

Yes. you need to make sure you have the Program Code. I paired mine without the App.

[hecareth]

I got my modules installed last night, the lock/unlock is definitely way more responsive vs the wifi so I agree these are worth it with the anticipated battery savings too.

They show up differently than yours though.

I enrolled them with the yale app as I like using it to manage users and codes rather than having to spend time to set that up in HA. Not sure if that's why or what but they seem to be working fine. I don't have doorsense enabled yet, I need to get a drill bit to flush mount the magnet.

My issue with managing codes in the Yale app is that I have to manage each of my 4 locks separately. I ended using Key Manager in Home Assistant where I could sync all my lock codes to a single parent lock which is working great.

[Hamish1066]

Could you please let me know the steps for doing this? I was on the phone with multiple people at Yale for hours trying to do this and they told me there is no program code for the YRD450 - this was only on the Assure 1.

[hecareth]

Could you please let me know the steps for doing this? I was on the phone with multiple people at Yale for hours trying to do this and they told me there is no program code for the YRD450 - this was only on the Assure 1.

The Programming code is in the Yale app. Before putting in the Zwave module, I copied all the program codes from the app. I should mention I used the August app for my locks...as I felt it worked better. Also I am not sure if the new Yale App that came out recently shows the program codes like the old one. Anyway, it should appear if you connect to the lock using bluetooth.

[BradleyCampbell]

I can't seem to get mine to pair with my network. Every option i try within ZWave JS results in a dead node. I've done default secure, default secure force s0, and s0. Any suggestions

[tamorgen]

Install z-Wave js UI if you don’t have it. You may need to try excluding the lock first. I would also say completely reboot HA. Sometimes z-wave js just doesn’t want to pair properly, and reboot will often fix it

[BradleyCampbell]

I was able to move my controller to a better position and the lock paired relatively quickly.

Are you able to manage user codes through Home Assistant with these? Does anyone have any recommendations on how to do that?

[cybergrimes]

I don't use it personally but I've heard about keymaster

https://github.com/FutureTense/keymaster

[hecareth]

I was able to move my controller to a better position and the lock paired relatively quickly.

Are you able to manage user codes through Home Assistant with these? Does anyone have any recommendations on how to do that?

So you can manage the codes directly on the lock it use something like Keymaster. I have 4 locks so I wanted my codes to sync, so I used Keymaster. I just have 3 of my 4 locks parented to my front door lock and that keeps my codes in sync.

[BradleyCampbell]

Yeah. I installed that based on someone else's recommendation recently. It's a pretty slick integration :)

[BradleyCampbell]

Yes. The only thing I used the app for was the initial calibration (not sure if you can do that without the app or not) and to figure out my programming code. I was only able to find it in the app. But the pairing was done completely outside of the app.

[Hamish1066]

Are you using the YRD450? If so, what steps did you take to pair it with z-wave js? For me, the module wasn’t active until I used the set up module option in the Yale app, then I completed inclusion in HA.

[BradleyCampbell]

The initialization and calibration done in the app did mention the module. So maybe you have to go through that to activate it. But since then, I haven't used the app.

Haven't started to mess with the blueooth auto unlock using my phone or watch yet. Not sure if that requires the app or not

[y2kbugger]

you can set your programming code by holdingthe inside button and then pressing 1 followed by gear. then create the programming code

[BradleyCampbell]

I'm seriously considering returning my Assure 2's for the Ultra-loq Pros. I can't see a single advantage the Assures have. The ultra loq comes with a 700 series zwave module (the assure 2's only have a 500 series), fingerprint reader, and code obfuscation (numbers before and after your pin). Am I missing something? Should I not bother and just keep the Assures?

[hecareth]

I have 4 Assure Lock 2's 450s. I honestly bought them mainly for 1) Aesthetics and 2) Future Proofness. I have the 700 series ([AYR-MOD-ZW3) module on all my locks as I bought it from the eBay guy. The whole codes obfuscation feature is cool but it did not lessen the fact that the in my opinion the Ultra Loq is freaking ugly and would not pass the wife approval test, LOL. Also not sure if this is the case for the Pro but I watched a review where the guy said the Ultra Loq only does basic Zwave commands and does not have alarm level entities for things like door is jammed and knowing who unlocked the door. Maybe the pro has those features. I dunno.

[webmogul1]

Ultra-loq reminds me of....

[BradleyCampbell]

Unfortunately I bought the locks that came with the modules. I figured 6+ months after the lock was released, they would be using the current zwave hardware.

Is there any functional difference? I guess with zw3 you get firmware updates, s2 security, longer range, lower power, etc. is there anything different about the functionality of the lock?

[zipzagster]

A wholesaler told me that Yale is aiming for late fall to release ZW3. This perhaps indicates that they will have a fix for the door closed sensor. Although Yale may be just trying to sell out ZW2 inventory before a mainstream release of ZW3. I suspect the current ZW3 is for professional installers like Control4 who won't put up with Yale's turtle-like approach to technology.

Yale has always been slow. They were still selling gen 1 modules a year ago.

[tamorgen]

Which probably means next April/May in reality. They had been promising the ZW2 module by end of 2022, and it took until April for it to be released.

I’ll be curious if they ever release OTA firmware updates. Their support certainly won’t understand that OTA updates is a requirement of 700 series certification.

[Queuecumber]

I just put a ZW3 module from eBay into my YRD450 and I can confirm other reports that doorsense seems to work on this model.

HA is reporting firmware 2.17.0, does anyone know if we'll eventually get OTA updates for this?

[bubba925]

I’ve got 3 YRD652 all on 2.35.0. Door sensor does not work.

[Queuecumber]

Yes working doorsense seems to be a peculiarity of the YRD450

[tamorgen]

HA is reporting firmware 2.17.0, does anyone know if we'll eventually get OTA updates for this?

Good question. The ZW3 module is a 700 series module, which means for certification, they are required to have OTA firmware update capabilities. It does not however require the vendor to provide any updates to the public. My experience with Yale customer service has been poor at best. I'm not hopeful, unless they acknowledge some vulnerability or shortcoming that is actually fixed in a firmware release.

As it stands now, Door Sense and everything is working for me on my 2 YRD420-ZW3 locks. Even better, the lastest Z-Wave JS update in Home Assistant actually correctly identifies the manufacturer and model of the lock, so no more "Unidentified" items in my Z-wave home.

[Queuecumber]

Yes Yale support told me it's "not possible to update it" but I'm going to try to escalate it.

[tamorgen]

Yes Yale support told me it's "not possible to update it" but I'm going to try to escalate it.

My belief that is their phone support not knowing what they are talking about. Some of their support had no clue what Z-wave even was, yet had to support it.

[airdrummingfool]

Bluetooth is how the Yale app communicates with the lock for management/etc - I don't think they'd want to provide a way to disable that. As long as you're not connecting to the lock over BT (e.g. by using the Yale app, Apple HomeKit integration, or Home Assistant via ESPHome Bluetooth proxy) the lock is only advertising, which should not take much battery.

What kind of batteries are you using @jeremykeen ?

For the record I use rechargeable NiMH batteries in my YRD420. I have it connected to Z-Wave JS (ZW3 module), Apple HomeKit (via BLE), and an ESPHome Bluetooth Proxy (also BLE), and the batteries last over a month. I have read it is not recommended to use rechargeable batteries; my guess is that's because the battery level estimation logic expects each battery to start around 1.5v instead of 1.2v. Rechargeable is working fine for me, but they don't seem to last as long as disposable alkaline.

[Queuecumber]

There's no reason they couldn't have a way to enable/disable Bluetooth via the keypad settings but I agree that ble shouldn't be doing much if you're not using it

You're certainly doing a lot with your lock but a month of battery sounds incredibly annoying to me. On my first gen Yale Assure which had only zwave the batteries lasted over a year.

[jeremykeen]

I completely agree ble should not be the issue here. I'm baffled because my 2 older assure locks on z wave only last for several months. Same config, roughly the same usage patterns. I have used rechargeables and regular energizer alkaline batteries. Rechargeables are frowned upon for the reason you stated but I do use them sometimes. In this case, they die in a few days. Attaching screenshot of battery drain on this lock.

[antokara]

@jeremykeen maybe something is constantly interviewing your locks Bluetooth module or your zwave controller polls the lock too frequently?

[airdrummingfool]

@Queuecumber

There's no reason they couldn't have a way to enable/disable Bluetooth via the keypad settings

fair point, I didn't think about that.

a month of battery sounds incredibly annoying to me

I should have been more clear: I haven't really timed it well enough to know how long my batteries last, but I'm confident it's longer than a month (for comparative purposes). That being said, I'm sure it's not as long as I'd like it to be, and they definitely don't make it to 6 months.

[jeremykeen]

z - wave -> I doubt it is happening any differently than the other two that are not draining rapidly. They all use the same automations etc. bluetooth -> Maybe. Would home assistant do this? I ignore the lock in home assistant since I did not want to integrate it using bluetooth.

…

On Tue, Sep 12, 2023 at 4:31 PM Antonios Karagiannis < ***@***.***> wrote: @jeremykeen <https://github.com/jeremykeen> maybe something is constantly interviewing your locks Bluetooth module or your zwave controller polls the lock too frequently? — Reply to this email directly, view it on GitHub <#5391 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACOAWYLTFROEIGA5FDIVGLDX2DBDJANCNFSM6AAAAAAUNGET6U> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[antokara]

Maybe some apple homekit device? They use Bluetooth and those locks are compatible with homekit...

[jeremykeen]

I tried a factory reset followed by removing the z-wave module to see how long the battery lasted on bluetooth alone. The battery was fine for well over a month. I reinstalled the z-wave module and re-joined home assistant (new device). The battery was at 78% to start. Just 4 days later and the battery level is showing 27%. No z-wave automations. I joined with S2 security. Is that the problem? My other locks are S0_legacy. Firmware version of the z-wave module is 2.17.

Any advice on how to troubleshoot this? Yale support is not helpful and will not provide a firmware update.

[tamorgen]

I have two of the same model with deadbolt with the ZW3 module. I can't say I've had any battery issues. I replaced both locks batteries about 2 months ago or so, and they're at 80 and 85%, and both are using S2 security.

I can't convey how little I think of Yale's support, but I'm hoping once they officially release the ZW3 module to the general public, they'll provide firmware update. Hoping.... Their Tier 1 support isn't going to understand, but to get the 700 series certification, devices are required to be able to receive OTA updates, so their claims that it can't be done are BS, as I've previously pointed out. That being said, I don't think there is a requirement for vendors to actually provide firmware updates, so who knows if Yale will ever provide them, unless they finally recognize issues in their current firmware.

[hecareth]

Hye folks I know its been a while, but just wanted to give an update on the 4 Assure Locks. I moved to ZWave back in May. Well for starters the batteries still seem to be going strong. It's been about 4 months since I replaced all of them with Lithium batteries, and things are working well. I will say I don't trust the battery level on the thing as 2 of my locks say 100% and the other 2 say 55%, but will continue to monitor. I have not had any issues. They function near flawlessly. I have mine programed to a button in each rooms scene controller that will show an LED of Red if any door is unlocked and Green if all doors are locked. If I push the button all the doors lock.

Anyway just thought I would give an update from my last 4 months.

[hecareth]

Ok so it seems there was a firmware update that seemed to get certain things enabled. I was recalibrating my door locks because....well California i.e earthquakes throwing stuff off and the August app basically said there is an update and immediately started installing. Damn thing didn't even ask me. The new firmware version is 1.3.16 upgraded from 1.3.10. There was no changes to the ZWave Module firmware.

Anyway after install I was hoping nothing got screwed, and to my surprise things got enabled. Let's list them

1. Door Sense is now working. Well working for Door Open and Door close. There is about a 3-4 second delay for it to register. Not as fast as my sensitive strips I have on my doors which are nearly instant but much better than what it was before, which was somewhere in the 30 seconds+ space using the Yale Wifi Module. There are 2 sensors which seem to be the same thing so I would just enable one.

2. There seems to be a new Alarm Type which is not documented anywhere. Alarm Type 43. In testing the Alarm Type seems to come on when the door is opened, so my assumption this Alarm Type corresponds with the door sensor being enabled

I got a list of the Yale Assure Lock SL Alarm Type codes from here: https://www.makeitwork-tech.com/best-smart-locks-for-home-assistant/

My plan is to create setup some YAML code to convert the AlarmType sensors into some useful statusing. This seems to be something doable based on what I read here: https://community.home-assistant.io/t/z-wave-yale-lock-issue-missing-alarmlevel-and-alarmtype/297343/11

Anyway thought I should share.

[caseyjhol]

Am I reading this correctly that DoorSense now works via Z-Wave? Which module are you using?

[claytonjn]

It is for me with the AYR-MOD-ZW3-US module on 2.17.0 firmware.

[airdrummingfool]

I've only seen reports of DoorSense via Z-Wave working for YRD450 locks (which is what @hecareth has). I don't think other Assure Lock 2s support it yet (e.g. it's not working yet on my YRD420).

@claytonjn what model lock do you have?

[caseyjhol]

Ah ha. Good to know. I have the YRD430. Thanks for the heads up.

[claytonjn]

I also have a YRD450, technically the YRD450-N-BLE-BSP (Yale Assure Lock 2 Plus with Apple Home Keys). I'll note for anyone else considering that model that Z-Wave does NOT report HomeKit status, which means that as of now Home Key is a bit useless if you depend on Z-Wave status being correct.

[Doughboy68]

You can set user codes manually in Z-Wave JS UI.
I just noticed today that there is schedule for my lock.
I have had this for years, using on different system than HA, and it was not a known feature of the lock for me.
I can enable the scheduling setting and even query it back from lock. I just am not sure if it works... will test later when home.
Not sure how the lock knows what time it is and how to set the time/date. This scheduling seems a feature self-contained in the lock itself.
I found this in the manual however...
"When batteries are replaced, Smart Module locks have a real time clock that will be set through the User Interface (UI);
it is recommended to verify correct date and time particularly those locks operating under Daylight Saving Time (DST)."
I have no idea where this can be set, I have looked everywhere.
Maybe this is not supported and the integration is pulling info/values that sorta work but are not really functioning on this lock.

I have not found a way to access the schedules in HA directly (but not sure if they even work)

For user codes:
Can also call service in HA to update user codes.
So one could make an automation that just changes the code at certain time of day to simulate a schedule.

I have tried keymaster from HACS a while ago and didn't work, maybe I will try again now that I have more experience with HA.

Edit in advanced I see this...

Will test and see how this works.
Update... works! A feature in my 4+ year old lock that didn't know of!

[claytonjn]

Has anyone tried using the ZW3 module with the Assure Lock 2 Touch or Plus (YRD420-F / YRD450-F / YRD450-N)? I've tried both, and in both cases the Z-Wave status does not reflect any changes when the lock is controlled by Bluetooth, Fingerprint, or HomeKit. When controlling the lock by the keypad Z-Wave states update as expected but when controlling by any of those three mechanisms the lock state does not update to reflect locked/unlocked and alarmType/alarmLevel do not update either (I see no changes at all reflected in Z-Wave). Based on the file posted previously for the YRC612 alarmType and alarmLevel should indicate Bluetooth or HomeKit unlock, I don't see anything in there for Fingerprint.

My RW3 module is on firmware 2.17.0, no idea if that's the latest or if any updates have been made available. I'm also curious if anyone is using the ZW2 module with the Touch/Plus models and if Bluetooth/Fingerprint/HomeKit control is reflected in Z-Wave.

[jfroy]

I thought the HomeKit version ("Plus") was not compatible with any of the zwave modules, and the touch version ("Touch") was not compatible right now. Maybe they'll fix that with firmware updates in the future?

[claytonjn]

Support told me that neither were compatible with the Z-Wave module, but the YRC612 doc explicitly calls out expected Z-Wave status for HomeKit lock/unlock. As far as I know, all YRD420/450 models have BLE and HomeKit, and the Plus model only adds NFC for Home Key. So there shouldn't be any reason that those models don't support the Z-Wave module, but it seems that Yale/August simply haven't considered or don't care about that use-case.

[wellsi]

The ZW3 module also works on YRD256, with S2. Firmware is 2.35

[lazy-pete]

Hi - I’ve been reading this with interest. I’m trying to find a smart lock solution for my front door in the UK, that allows local control via HA. I’ve managed that in one door with a Danalock in Zigbee (only one that would fit my Swedish barrel multipoint door), but need another solution for two exterior doors. Yale and Z-Wave seem to be the most reliable for local control but unfortunately the UK version ‘Keyless connected smart lock’ won’t fit my door due to the framing details (ancient wooden door). I think the slightly longer backseat of the US versions discussed here would fit. I realise I’d have to somehow download a US only Yale app to set it up, but am hoping thereafter that Z-Wave and HA would allow daily use. I’m wondering if someone could point me to a list of the features that do work over HA (assuming correct ZW3 module etc) - ideally I’d like a touchscreen version with fingerprint/NFC/physical key but am a bit bewildered by the range descriptions - and be able to lock / unlock remotely, create access codes remotely and monitor door state and notifications when the kids come home etc.

A bit of an ask I know, but there is perhaps a Z-Wave spec for these somewhere ?

[hecareth]

I am no expert here and do not know how things are changed between Europe, GB, or the US in regards to ZWave specs. For me, once on ZWave the locks will function without the need for the App. The App is really only needed to pull the master codes and update firmware. I did not use the Yale app to do this I actually had my locks on the August App. Just make sure you do this first before switching it to ZWave.

Once I pulled and stored the codes adding the devices to my ZWave controller was all done thorough the physical lock (No App Required and Fully local to HA). I have a Zooz Zwave 800 LR controller so that probablly helped for the more far away doors as my house is 4300 sqft. I enrolled 4 doors into my system since maybe May and have changed the batteries once. In regards to the app, I only opened the app back in September to update the firmware. All my lock settings are run through Key Master.

I am really impressed with the ZWave functionality compared to WiFi. For example I have a HA automation that changes the color of my Scene controller (Zooz) LED if any of the door are unlocked. It works instantly as soon as I turn the knob the LED changes. That one little things has impressed me by far as the response time is insane.

I do not use the Bluetooth unlock feature my lock. Mainly because it is kind of wonky and I refuse to use that app. I have been thinking of creating an ESP Presence sensor I can plug into a hidden outlet by my door so I can write an automation for when it detects presence from my phones to unlock the door. I can get a lot more specific with rules on this one.

[claytonjn]

One thing I want to clarify because @lazy-pete specifically noted

ideally I’d like a touchscreen version with fingerprint/NFC/physical key

I'm not aware of a US model that supports NFC, other than HomeKit's Home Key. Also, in my experience with both the fingerprint model and HomeKit model, both fingerprint lock/unlock and HomeKit lock/unlock are not reflected in K-Wave status. That means that if you use either of those HA will not get the correct status. I have a pretty unreliable hack in place comparing Bluetooth-reported status to Z-Wave reported status to surmise if the lock was unlocked using one of those mechanisms. Documentation seems to indicate that HomeKit status should reflect in Z-Wave but with my module running FW 2.17.0 that is not the case.

[lazy-pete]

That’s really helpful- thanks. Sounds as if the physical dimensions work I should be able to make it all work ! Cheers, Pete

…

On Tue, 2 Jan 2024 at 23:09, hecareth ***@***.***> wrote: I am no expert here and do not know how things are changed between Europe, GB, or the US in regards to ZWave specs. For me, once on ZWave the locks will function without the need for the App. The App is really only needed to pull the master codes and update firmware. I did not use the Yale app to do this I actually had my locks on the August App. Just make sure you do this first before switching it to ZWave. Once I pulled and stored the codes adding the devices to my ZWave controller was all done thorough the physical lock (No App Required and Fully local to HA). I have a Zooz Zwave 800 LR controller so that probablly helped for the more far away doors as my house is 4300 sqft. I enrolled 4 doors into my system since maybe May and have changed the batteries once. In regards to the app, I only opened the app back in September to update the firmware. All my lock settings are run through Key Master. I am really impressed with the ZWave functionality compared to WiFi. For example I have a HA automation that changes the color of my Scene controller (Zooz) LED if any of the door are unlocked. It works instantly as soon as I turn the knob the LED changes. That one little things has impressed me by far as the response time is insane. I do not use the Bluetooth unlock feature my lock. Mainly because it is kind of wonky and I refuse to use that app. I have been thinking of creating an ESP Presence sensor I can plug into a hidden outlet by my door so I can write an automation for when it detects presence from my phones to unlock the door. I can get a lot more specific with rules on this one. — Reply to this email directly, view it on GitHub <#5391 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHMEIQ3DPXLCIUID3P5TKS3YMSHTRAVCNFSM6AAAAAAUNGET6WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TSOJXG43DE> . You are receiving this because you commented.Message ID: ***@***.***>

[lazy-pete]

I’ve found a new issue ! My Aeotec Z-Stick 7 | Z-Wave Plus V2 | ZWA010 | 700 series stick is set to EU region, where it needs to remain. I understand 700 a series controllers region can be adjusted, however I’m unsure whether the region of the eBay ZW3 module https://www.ebay.co.uk/itm/285530632873?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=vfmPdkJbQ2i&sssrc=4429486&ssuid=xZjAfUceSzW&var=&widget_ver=artemis&media=COPY
can also be adjusted to match the EU frequencies. This would be necessary to keep the system legal here and allow use of any other UK Z-Wave devices I have (like the Yale multipoint lock I’m also considering for the back door). Any thoughts ?

[drizuid]

I just wanted to provide some info. I've been using this lock since early november, I am still on my first set of batteries (amazon basics brand, so nothing special). zwavejsui reports my % at 77 still and we use this door fairly often. My specific model is the YRD420-ZW3. Doorsense is working fine for me, 94-113-0-Access Control-Door state and 94-113-0-Access Control-Door state (simple) both accurately reflect the state of the door (open or closed) and update quickly. I am using this with a zooz 700 zst10 stick, admittedly, i yolo flashed a firmware on it when i first got it due to some odd issues and now I can no longer flash firmware directly from zwavejs to it, but i imagine if i install windows and use the studio app i could.

it's worth noting that my bluetooth control and zwave controls both work without issue. I am able to create user codes (but not fingerprints) directly from zwave and i can also edit user codes created by the yale access app from within zwavejsui. (small note: zwavejsui does display the codes in plaintext, it would be nice to have that obfuscated in some way)

some info on my module

I am using the device files (in my case im using yrd430-zw3 and the updated template which i provided to the OP of that PR) from this pr #6503

I have another yale assure 2 lock and use the wifi module (didnt want the super old zwave module available for sale) and it's HORRIBLE compared to my zwave lock. burns through batteries and constantly loses connection to wifi. I've tried two wifi modules without any improvement. The zw3 module should become available for sale sometimes this year.

[airdrummingfool]

I actually emailed Yale Support last night asking if I can get any new firmware that might be available. The response I got back was not very encouraging (perhaps the support person was unaware of the beta, or just didn't understand what I was asking):

The DoorSense does not work for the Z-Wave application. Will only work for the Yale Access application. Also, we do not handle the firmware for the Z-Wave module. All of this will be updated via the Z-Wave hub so you have the module connected.

The DoorSense is the only feature of the Yale Access app. You won't be able to see this on a 3rd party application. The locks firmware 1.3.16 is for the Yale Access application not for Z-Wave.

You can use Yale Access to open\close, auto lock, auto unlock, and DoorSense via Bluetooth. Guest codes, open and close will be under the Z-Wave app. We do not have any Beta modules available for the Z-Wave module.

I'll push back once and see if I can get anywhere, but I don't have high expectations. We might have to continue waiting until this is officially released.

[drizuid]

Realized I didn't show doorsense, so I thought I would share just to keep you all excited.

because there is Door state AND Door state (simple) it does show up in HA twice, both work and can be used in automations

I still have no info on buying the module, trust me I want another as well, I'd really like to replace my wifi module in the other lock, it's trash.

[airdrummingfool]

@drizuid it's working... I'm excited. Though my conversation with Yale Support went so very very poorly, I'm wondering if a firmware update is ever going to be released. I couldn't even convince them that Yale has the firmware for their own module; they told me to ask my "Z-Wave system provider" (i.e. Z-Wave JS) for the firmware file 🤦‍♂️ .

Question: it looks like you're using a custom config file - was that required to get DoorSense working with your module? Z-Wave JS already has a config file for the YRD420-ZW3, but if yours is different would you be willing to share it?

[drizuid]

Question: it looks like you're using a custom config file - was that required to get DoorSense working with your module? Z-Wave JS already has a config file for the YRD420-ZW3, but if yours is different would you be willing to share it?

I'm using what was linked in the PR in my OP. If there is something now, there wasn't originally or is wasn't using the proper device codes

[drizuid]

saw a bunch of posts recently about doorsense, thought I'd share more shots of mine. It shows twice in HA because there are two sensors, like you see in the zwavejsui shots, one for door state (simple) and one for door state. That said, HA sees them as door open in regular position and door open in tilt position , which is a bit odd.

[LSR19]

I just purchased a ZW3 module (firmware 2.35) for a YRD430 Yale Lock 2, and I'm underwhelmed. The z-wave module lacks much of the helpful functionality of the Wi-Fi module working through the app. For instance, among other missing features, the lock with the ZW3 module: (1) does not identify the operator of the lock, which I use in some automations; and (2) does not identify whether the lock was operated manually vs the keypad. which I also use in some automations.

Does anyone know whether these very helpful features are or can be exposed by the ZW3 module? If not, I'm going to have to return to the slow and battery-draining Wi-Fi module until (hopefully) some additional features are made available via z-wave.

[y2kbugger]

Even the Z-Wave 2 module can do this. There's a blueprint that can make it extra easy, but you can also do it yourself with the info gets sent in a z-wave notification. I think the blueprint is called Yale user code automatic or something like.

…

On Mon, Apr 1, 2024, 21:07 LSR19 ***@***.***> wrote: I just purchased a ZW3 module (firmware 2.35) for a YRD430 Yale Lock 2, and I'm underwhelmed. The z-wave module lacks all of the helpful functionality of the Wi-Fi module working through the app. For instance, among other missing features, the lock with the ZW3 module: (1) does not identify the operator of the lock, which I use in some automations; and (2) does not identify whether the lock was operated manually vs the keypad. which I also use in some automations. Does anyone know whether these very helpful features are or can be exposed by the ZW3 module? If not, I'm going to have to return to the slow and battery-draining Wi-Fi module until (hopefully) some additional features are made available via z-wave. — Reply to this email directly, view it on GitHub <#5391 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABORVLIJDVT5Z4HKQPH6KPLY3IADZAVCNFSM6AAAAAAUNGET6WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNZYGAYTE> . You are receiving this because you commented.Message ID: ***@***.***>

[claytonjn]

This is what I have in Z-Wave JS UI

[LSR19]

It's possible the add-on Z-Wave JS UI 3.4.1 works with DoorSense but the built-in JS Z-Wave doesn't. If switching from my built-in JS Z-Wave implementation to the add-on implementation doesn't screw up all of my automations, I'll try to find out by installing the add-on version.

[airdrummingfool]

I think I figured it out, thanks to the updated Integrator's Guide posted by @LSR19. It states that DoorSense can be enabled(!) by setting the Configuration CC, parameter 19, to value 255 (decimal version of 0xFF).

Once I enabled DPS Alarms and opened/closed the door, two new Door State entities appeared and I now get DoorSense updates via Z-Wave! Updates seem to be delayed about 5 - 10 seconds, but it's a lot better than nothing!

[LSR19]

What model lock do you have? I do not see a DPS Alarms configuration parameter for my YRD430 lock (using the built-in JS Z-Wave integration).

[airdrummingfool]

YRD420 with firmware 1.3.16. My ZW3 module has firmware 2.35.0. I'm using Z-Wave JS UI via Docker, version 9.10.2 (which ships with Z-Wave JS 12.5.2).

[airdrummingfool]

I was able to get DoorSense notifications over Z-Wave working on my YRD420 (FW 1.3.16) with ZW3 module (FW 2.35.0) by setting the "DPS Alarms" parameter (19) of the Configuration CC to 255 (0xFF).

Here's the relevant documentation from the Integrator's Guide:

Note the following subscript in the documentation:

⁷ Only supported by YRD410/420/430/450. This requires additional Hardware and calibration within the Yale Access App.

And a screenshot from Z-Wave JS UI with my updated setting:

Now, two of the parameters in the Notifications CC update whenever the door is opened/closed:

And the lock device in HA has 4(!) entities that correctly show door status now.

[hlarsen]

Nice!

I tried this with my YRD450/ZW3 on firwmare 2.20.0 with no luck. I think the issue is my firmware version because in Z-Wave JS I have Door state and Door state (simple) entries, but I do not have an existing DPS Alarms entry. Trying to add the CC "succeeds" and adds the entry, but the entry name shows up as [16-112-0-19] param019 (property) (not DPS Alarms, no default text below the input) and the value ends up being -1:

2024-04-04 15:45:49.399 INFO Z-WAVE: Calling api sendCommand with args: [{nodeId: 16, commandClass: 112}, 'set', [{ parameter: 19, value: 255, valueSize: 1, valueFormat: 1}, [length]: 1], [length]: 3]
2024-04-04 15:45:50.791 INFO Z-WAVE: Success zwave api call sendCommand {status: 255}
2024-04-04 15:45:50.926 INFO Z-WAVE: [Node 016] Metadata updated: 112-0-19
2024-04-04 15:45:50.927 INFO Z-WAVE: [Node 016] Value updated: 112-0-19 0 => -1

Has anyone had any luck obtaining or applying firmware updates?

[airdrummingfool]

Has anyone had any luck obtaining or applying firmware updates?

I begged Yale support for a ZW3 module firmware update file and it was one of the most frustrating and ridiculous conversations I've ever had in my life. If you can get through to Tier 2 support then maybe you have a chance, but Tier 1 repeatedly told me that I have to get the firmware from Z-Wave JS because Yale doesn't have it 🙄. Eventually I gave up on trying to get them to give me an update.

I don't know how long the "DPS Alarms" config parameter has been available to me, but it's possible it showed up after a lock firmware update (via the Yale app) or, more likely, after an update to Z-Wave JS. If you haven't done so recently, you could try connecting with the Yale app to see if it prompts for a firmware update, and then updating Z-Wave JS and performing a re-interview of the lock to see if it shows up.

[jeremykeen]

@airdrummingfool are you saying you got the firmware update? Able to share? I had the same frustrating back and forth with support.

[airdrummingfool]

@jeremykeen unfortunately not - I never got anything useful from support. After 2 weeks of back-and-forth I requested a supervisor and never heard back; after that I stopped following up.

[LSR19]

While trying to resolve the DoorSense issue with my YRD430, I stumbled upon a problem about which I have not seen any posts and I cannot figure out the cause or how to fix things. The problem is my lock, after a period of inactivity, fails to transmit when the door auto-unlocks upon my return home. The door does auto-unlock when I approach it and the Yale app correctly reports the door was unlocked, but the ZW3 doesn't transmit. As a result, the expected automation doesn't run. When I looked at the alarm_type and alarm_level codes to see what went wrong, the alarm_type code shows the door was locked when I left 2 hours previously and that's the last thing it reports. It seems the lock isn't waking up the ZW3 to transmit anything when the door is unlocked after a period of inactivity. It doesn't make sense.

Has anyone seen this type of aberrant behavior or have any thoughts about what might be the cause? My ZW3 has firmware v, 2.35, and I'm using the official JS Z-Wave add-on (not the UI add-on).

[claytonjn]

I think this is similar to what I've observed with HomeKit BLE Lock/Unlock. I don't think it's a matter of not reporting after a period of inactivity, I think certain actions never trigger the ZW3 module to update status at all. For example, HomeKit Unlock should set alarmType 0xE5 (229) and alarmLevel 0x00 (0), however not only do neither change at all on HomeKit Unlock, the state of the lock itself also doesn't update from locked to unlocked.

This does not occur only after some time, I can lock/unlock manually and see immediate status updates in Zwave, then try HomeKit and get nothing, then lock/unlock manually again and get immediate updates again. Also, if I use HomeKit and then re-interview the node or rebuild the mesh, either of which I would expect to trigger a status update from Zwave if the device were just in some sleep state, however the status never changes from HomeKit actions. I've never tested with the Wi-Fi module so I don't know if this would work with that module and is a ZW3 specific issue, or if the issue is simply that the ZW3 (based on documentation) should reflect these actions but the lock itself doesn't send the events for these actions to the smart module.

[LSR19]

That's interesting. One thing in common between what you've seen with HomeKit and what I'm now seeing with Auto Unlock is BLE. In both cases, a lock/unlock state change caused by BLE seems not to be noticed by the ZW3 (either because the lock isn't sending the information to the ZW3 or it is but the ZW3 isn't responding). I was hoping there was a Configuration Parameter that needed to be set to enable BLE-based events (like DoorSense needs to be enabled), but I don't see any such setting in the May 2023 Integrator's Guide.

Perhaps BLE-caused state changes are not yet enabled for ZW3 modules. If so, that could be one reason why Yale hasn't yet generally released the ZW3.

[airdrummingfool]

I'm seeing similar behavior on my YRD420 - any Bluetooth interaction (from the Yale app or via HomeKit) does not trigger a status update in Z-Wave.

However, if I do a "Refresh Values" in Z-Wave JS, the lock status updates to the correct value.

[LSR19]

I have disabled Auto Unlock until this issue with BLE is sorted out or I can devise a reliable work around. With Auto Unlock enabled, the lock’s actual state (unlocked) loses sync with the state as seen by Home Assistant (locked) when I come home. That makes a mess of every automation that relies on the state of the lock.

[claytonjn]

For my case I "upgraded" from a YRD110 specifically for Home Key. To work around the issue with BLE based actions not updating in Z-Wave I'm using a combination of Z-Wave entities and Bluetooth entities to determine the state of the lock (I have an automation that updates Z-Wave entity state on Bluetooth entity updates so I still have a single source of truth). It's not at all ideal because BT is much slower and less reliable for me than Z-Wave, but it's working for now.

[webmogul1]

Finally we have an official release with the 700 chip. Now just a few more years for the 800 chip.
https://amzn.to/3UBMDqY

[LSR19]

Good question! The product number is "‎YRD450-F-ZW3-0BP", suggesting it has the new z-wave 700 series ZW3 module. But, when you look at this product on the Yale site and download the product instructions, that talks about a 500-series z-wave module. See here, p. 19 - https://images.salsify.com/image/upload/s--vOazn9-x--/fjcfiasy7fozabpzbivy.pdf. So .... ???

[webmogul1]

well, it shows a black module and the lock part number is YRD450-F-ZW3-0BP. The ZW3 means that it is a 700 chip.
https://products.z-wavealliance.org/products/4913?selectedFrequencyId=2 Zwave Plus version 2 means 700 chip

[Hamish1066]

Wow good eye LSR19 and webmogul1! I'm still apprehensive about the 700 series chip. The YRD450 is by far the worst z-wave device on my network because it is so unreliable in it's state reporting, and occasional unavailability. I still find myself checking the physical lock every night before bed because I can't trust it.

[drizuid]

I've been on the 700 chip for some time and found it to be quite reliable. That said, i do still check for the blinking light to indicate lock status.. better safe than sorry,.

[LSR19]

My YRD430 with a ZW3 module has been rock-solid, with very low battery drain and fast response times. It does not, however, detect auto-unlock via BLE. I cannot find where to update the ZW3's firmware. My firmware is v. 2.35. Others have reported different firmware versions. You'd think Yale would provide firmware updates, but I can't find where. Anyone know?

[maxballenger]

I am buying an old house and I need to replace locks. I like the Yale assure appearance the best. I am thinking of going with YRD420-F-ZW3-0BP because it's the only model Yale seems to sell right now with the 700 series module. Any thoughts on buying the lock with the 500 vs 700 series right now?

[drizuid]

i think it's a bit of a toss up on the 700; you're only going to have what i would consider the best firmware if you were in the beta, otherwise, it appears you end up with some wild range of firmware versions. that said, battery life in 700 is better than 500

[webmogul1]

I see no reason to get any device with a 500 chip.