Wow @h0ckeysk8er ! That is what you call Peace of Mind! Great to know! Thank you!
Won’t help on the transition from DTH to Edge (obviously), but it is certainly useful for backing up your codes periodically if you have more than a few programmed.
1 Like
Hey guys, sorry for the noob question, but if i switch the driver from stock, to phils, will all of my routines associated to that lock be erased?
If you are running the stock Edge driver and switch to Phil’s, you will not lose your Routines. His driver is based on the stock driver and has all the capabilities of the stock plus more.
Your lock code names may be reset since the codeId to codeName relationship is maintained by the driver. Also, use his beta driver since it fixes an issue where lock code names are reset and exposes the code name used to unlock the lock as a trigger in Routines.
1 Like
Finally figured out how to get my Schlage BE469NX off the old Device Handler. Got this driver set up but my device screen only shows its status and battery power. I don’t even have a settings option in the three dot drop down in corner. I verified that I have the correct driver. Am I missing something?
Sounds like you are running the stock Edge driver not this one. Please go to the API Browser+, select the Device Details and post the output here. I’m guessing your specific fingerprint may not be included in the driver so you’re falling back to the stock driver.
So, while you’re using Phil’s driver, the fingerprint shows the device didn’t pair properly to your hub so it defaulted to the base-lock profile which only has lock status and battery. I’d suggest that you exclude the lock from your hub and then do a factory reset on it before re-adding it. Until it pairs with the proper fingerprint, you won’t get a profile that exposes the Schlage specific settings.
I also recommend that your install Phil’s beta driver as it fixes a bug with lock code names resetting periodically and exposes the unlock code name as a trigger in Routines.
Thanks. I got it working and love the features. One more thing, most of the features were grayed out, that is until I use them in a routine, then they became useable. This isnt a big deal as I just ran a few routines to make them useable but for others that may have this problem.
There are a lot of capabilities exposed in his driver and it takes a few refreshes on the device panel to get them all populated from the lock. Setting them in a Routine is another way of getting them populated.
Glad you got it working!
2 Likes
@Starsetter this may be more than what you’re looking for, but I had outlined a method of making the Schlage Alarm work in Home Monitor
@philh30 Would it be possible to add this Kwikset 910 to your driver?
type:4003
mfr:0090
prod:0003
model:0236
Thank You!
Hi
@philh30 With Edge Driver “Z-Wave Lock PH BETA”, is possible to create a routine that is activated when I locked with the keypad´s lock?
Yes, it’s possible. What specifically are you looking to do?
I need turn off the lights when the door is locked by pressing the Schlange button on the keypad (not by entering a code)
The driver doesn’t expose how or by what code or code name the lock is locked. Only the code name used to unlock is exposed. SLGA provides a notification of which lock code name is used to lock the door, however, there isn’t a way to write a Routine based on that notification in the ST app.
That said, you should be able to use the 3rd party tool sharptools.io to create a rule based on the event data emitted by the lock event to do what you want (requires their premium service). Here is an example:
1 Like
I understand, Thank you
Hi everyone - I briefly read through the thread but couldn’t find anything on this (if there is can you point me at it) but is anyone else getting “unlock” events when the locks are actually “locked”?
I get these via Smart Guest Lock Access, and I’m also getting it as events in SharpTools
Haven’t seen that. Which version of the driver are you using, the 1.0 or the Beta? What lock do you have? Can you please get driver logging from the ST CLI using the command “smartthings edge:drivers:logcat” and post here?
Hey there - I’m using the PH BETA driver, lock is a Schlage BE469
Here are the command line events for when I manually lock the lock
2023-05-24T16:16:14.460053779+00:00 TRACE Z-Wave Lock PH BETA Received event with handler unnamed
2023-05-24T16:16:14.462634820+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> received Z-Wave command: {args={alarm_level=1, alarm_type=21, event="MANUAL_LOCK_OPERATION", event_parameter="", notification_status="ON", notification_type="ACCESS_CONTROL", v1_alarm_level=1, v1_alarm_type=21, z_wave_alarm_event="MANUAL_LOCK_OPERATION", z_wave_alarm_status="ON", z_wave_alarm_type="ACCESS_CONTROL", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x15\x01\x00\xFF\x06\x01\x00", src_channel=0, version=3}
2023-05-24T16:16:14.555246737+00:00 TRACE Z-Wave Lock PH BETA Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2023-05-24T16:16:14.555975279+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> emitting event: {"state":{"value":"locked","data":{"method":"manual"}},"capability_id":"lock","attribute_id":"lock","component_id":"main"}
2023-05-24T16:16:14.566519570+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> emitting event: {"state":{"value":"Locked"},"capability_id":"platinummassive43262.unlockCodeName","attribute_id":"unlockCodeName","component_id":"main"}
2023-05-24T16:16:14.567366112+00:00 DEBUG Z-Wave Lock PH BETA Front Door Lock device thread event handled
2023-05-24T16:16:14.703078195+00:00 TRACE Z-Wave Lock PH BETA Received event with handler capability
2023-05-24T16:16:14.712671404+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(462cae7d) queued for radio transmission: CC:Door Lock, CID:0x01
2023-05-24T16:16:14.714323987+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> received command: {"component":"main","capability":"lock","command":"unlock","positional_args":{},"args":{}}
2023-05-24T16:16:14.716359987+00:00 TRACE Z-Wave Lock PH BETA Found CapabilityCommandDispatcher handler in zwave_lock
2023-05-24T16:16:14.717521654+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> sending Z-Wave command: {args={door_lock_mode="DOOR_UNSECURED"}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_SET", dst_channels={}, encap="AUTO", payload="\x00", src_channel=0, version=1}
2023-05-24T16:16:14.726422070+00:00 DEBUG Z-Wave Lock PH BETA Front Door Lock device thread event handled
2023-05-24T16:16:14.727107279+00:00 DEBUG Z-Wave Lock PH BETA driver device thread event handled
2023-05-24T16:16:16.148668654+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(462cae7d) transmit status: TRANSMIT_COMPLETE_OK
2023-05-24T16:16:16.466970487+00:00 TRACE Z-Wave Lock PH BETA Received event with handler unnamed
2023-05-24T16:16:16.467526571+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> received Z-Wave command: {args={status="TRY_AGAIN_LATER", wait_time=0}, cmd_class="APPLICATION_STATUS", cmd_id="APPLICATION_BUSY", dst_channels={}, encap="S0", payload="\x00\x00", src_channel=0, version=1}
2023-05-24T16:16:16.476326654+00:00 DEBUG Z-Wave Lock PH BETA Front Door Lock device thread event handled
2023-05-24T16:16:18.937091487+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(d2b826b4) queued for radio transmission: CC:Door Lock, CID:0x02
2023-05-24T16:16:18.938545612+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> sending Z-Wave command: {args={}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-05-24T16:16:18.941746071+00:00 DEBUG Z-Wave Lock PH BETA driver device thread event handled
2023-05-24T16:16:20.388771571+00:00 TRACE Z-Wave Lock PH BETA Z-Wave command(d2b826b4) transmit status: TRANSMIT_COMPLETE_OK
2023-05-24T16:16:20.656493988+00:00 TRACE Z-Wave Lock PH BETA Received event with handler unnamed
2023-05-24T16:16:20.657049613+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> received Z-Wave command: {args={door_condition=0, door_lock_mode="DOOR_SECURED", inside_door_handles_mode=0, lock_timeout_minutes=254, lock_timeout_seconds=254, outside_door_handles_mode=0}, cmd_class="DOOR_LOCK", cmd_id="OPERATION_REPORT", dst_channels={}, encap="S0", payload="\xFF\x00\x00\xFE\xFE", src_channel=0, version=1}
2023-05-24T16:16:20.676494946+00:00 TRACE Z-Wave Lock PH BETA Found ZwaveDispatcher handler in zwave_lock
2023-05-24T16:16:20.676927571+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> emitting event: {"state":{"value":"locked"},"capability_id":"lock","attribute_id":"lock","component_id":"main"}
2023-05-24T16:16:20.679668863+00:00 DEBUG Z-Wave Lock PH BETA Front Door Lock device thread event handled
when i manually unlock this is fired:
2023-05-24T16:17:32.190122539+00:00 TRACE Z-Wave Lock PH BETA Received event with handler unnamed
2023-05-24T16:17:32.193096539+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> received Z-Wave command: {args={alarm_level=1, alarm_type=22, event="MANUAL_UNLOCK_OPERATION", event_parameter="", notification_status="ON", notification_type="ACCESS_CONTROL", v1_alarm_level=1, v1_alarm_type=22, z_wave_alarm_event="MANUAL_UNLOCK_OPERATION", z_wave_alarm_status="ON", z_wave_alarm_type="ACCESS_CONTROL", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x16\x01\x00\xFF\x06\x02\x00", src_channel=0, version=3}
2023-05-24T16:17:32.252801330+00:00 TRACE Z-Wave Lock PH BETA Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2023-05-24T16:17:32.258336580+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> emitting event: {"state":{"value":"unlocked","data":{"method":"manual"}},"capability_id":"lock","attribute_id":"lock","component_id":"main"}
2023-05-24T16:17:32.259420289+00:00 INFO Z-Wave Lock PH BETA <ZwaveDevice: XXX-XXX [1E] (Front Door Lock)> emitting event: {"state":{"value":"manual"},"capability_id":"platinummassive43262.unlockCodeName","attribute_id":"unlockCodeName","component_id":"main"}
2023-05-24T16:17:32.261959705+00:00 DEBUG Z-Wave Lock PH BETA Front Door Lock device thread event handled