Phil’s channel is here: https://bestow-regional.api.smartthings.com/invite/1PlYENKbdNle
The latest version is Z-Wave Lock PH
@bthrock I was going to look at his drivers but I get a 403 forbidden message when I click the link you provided.
1 Like
Sorry, I was working from my phone and grabbed the wrong link. Should be good now.
1 Like
You can access the legacy driver migration using your legacy credentials which gives you access to all the lock features and bugs fixes in the stock driver (and any divers that use the stock driver code as the baseline). We’ve added a few more features to it last week related to routines and scenes.
I have the Universal enhanced Z wave lock beta driver installed now, but it looks like it’s dated from the beginning of June. Once installed do I need to continually download and re-apply the code similar to the old Groovy code updates?
I may have missed something pretty significant here… @RBoy do your new beta drivers allow any hub that still has your legacy SmartApps like RLA or others to continue to function in this new environment? Unfortunately, I already deleted RLA out of my test hub, but I do see RLA still picking up user events on my production hubs that I’ve been managing via SLGA in the interim.
Yes. It is just a driver. RLA is still dead. There will probably be a new RLA, which has no ETA.
The beta driver was released in June. Edge drivers update automatically when an author publishes a new version.
The production version of this driver is being released in a different channel and the author is charging to have access to it.
What I don’t like is it is now an annual fee and I saw someone mention a discount for legacy subscribers but never got any email or anything about this new driver coming out. Just happen to see some posts here. Didn’t get any discount for my first year payment either.
Seems like I can just pay for one year and then wait until I feel like I need an update to pay again? I hate annual fees for software.
2 Likes
What version are you referring to? I am subscribed and my driver hasn’t been updated in two weeks. It remains on 2023-06-23T19:12:54.891857241. As soon as I see an update, I’ll happily give it another go.
2 Likes
I also never got any email for a discount on the new driver after paying previously for a “Lifetime” license which is now a “Lifetime Usage” license and pay for 12 months of updates.
1 Like
second, never got a discount email for something that was promised as lifetime. i had missed this release to i just installed the beta drivers. Sadly the contact sensor seems to be afk and cant change the driver.
1 Like
The author said that there would be discounts offered on the SmartApps when they are released and not on the driver itself. Frankly, the driver should be provided at no cost as a loss leader to incentivize folks to be willing to pay for the apps.
4 Likes
Your version is newer than mine, I am stuck on 2023-06-02T03:43:11.800925743, I wonder why the driver is not updating accordingly.
Use case
When locking the house from the outside, activate the Tamper alarm.
Routine:
Copyright (c) RBOY APPS
Use case
When unlocking the door Manually from inside, activate alerts so that you know if your child knocks or opens the door.
Routine
Copyright (c) RBOY APPS
Use case
When the manager uses the keycard FOB to open the office for the day, disable Auto relock and the keypad to allow employees to freely access the day.
When the manager uses the FOB to lock the office at the end of the day, enable auto relock and the keypad to enforce security audits by having employees working later use their key code to operate the door.
Routine
Copyright (c) RBOY APPS
@RBoy - I am using the beta driver, v2023-06-02 and routines are not activating. I reduced a routine to a single condition, “user name = XXX“ but the routine does not run. I am receiving unlock notification via SLGA, so there is no connectivity/mesh issue. Another driver successfully runs the unlock routine.
As a side note, I am looking to run specific routines based on lock codes and that does not work either and SLGA only shows “locked” as opposed to “locked by XXX.” Is this a know issue with the beta driver?
Is there any way you can limit the time of when a code can be executed like with the smart app? I only want someone to be able to use the code between 9 am and 5 pm.
That’s WIP