[ST EDGE] Z-Wave Lock PH

Devices & Integrations Community Created Device Types
209

I need turn off the lights when the door is locked by pressing the Schlange button on the keypad (not by entering a code)

210

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:

Clipboard01
Clipboard011150×947 54.6 KB

1 Like
211

I understand, Thank you

212

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

213

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?

214

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
215

So, I see the following:

  • The lock is manually locked and the driver emits the events
  • The driver receives a command (from App/CLI/API) to unlock the lock
  • Z-Wave command to unlock is sent
  • Driver receives a Z-Wave command of “Try Again Later” which seems to be indicate that the lock was not able to unlock
  • Driver sends a Z-Wave command to retrieve the state of the lock
  • Driver receives Z-Wave command with the status
  • Driver emits event indicating that the lock is locked

So, it looks like the unlock fails and then the locked is reported as locked. Is that what you are seeing?

2 Likes
216

I am manually locking the lock and then I receive an alert on my phone via SLGA that the lock was “unlocked”.

I’m not kicking off any command via the App or CLI… so I am now wondering if I have something using the API to react to the manual lock… or if this is SLGA

217

Next, I would look at a couple of other places:

  • Check the SLGA History to see what it thinks is happening
  • Check ST History (3 bar menu)->History to see what might be triggering the unlock
  • Check the lock’s device history to see what it thinks is happening
  • Check the Routines tab on the lock’s device panel to make sure there aren’t any Routines you’ve forgotten about

Do you have the Schlage Skill for Alexa installed? If so, make sure there aren’t any Alexa routines in play as well.

218

So it was a routine that was a bit too aggressive on triggering for presence - added a bit of a wait on a state and that did the trick.

Thank you again for the help

1 Like