Problems Setting Autolock with Z-Wave Lock PH Edge Driver

Is anyone else having problems with changing their “Auto lock” setting from the ST app? I’ve managed to turn off Auto Lock from the app recently and the lock has stopped unlocking. That was what I wanted for a week when we had workmen coming in and out, but the issue is now when I try to turn it back on.

First, the UI shows the state of Auto Lock as ON rather than OFF. I can try toggling the state to OFF and it seems to work, but then toggling back to ON, it just spins and gives a network error. If I refresh the screen, it once again says Auto Lock is ON (when it is still OFF). Looking at the CLI logs, it seems to only be sending OFF commands, but not ON.

2024-03-07T01:52:21.655499745+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-07T01:52:21.675936958+00:00 TRACE Z-Wave Lock PH  Z-Wave command(6f9ec7f6) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T01:52:21.681230604+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-07T01:52:21.716574600+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T01:52:21.721032495+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-07T01:52:21.725927941+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T01:52:23.201436994+00:00 TRACE Z-Wave Lock PH  Z-Wave command(6f9ec7f6) transmit status: TRANSMIT_COMPLETE_OK
2024-03-07T01:52:28.365032170+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-07T01:52:28.387794212+00:00 TRACE Z-Wave Lock PH  Z-Wave command(f6b3f7cb) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T01:52:28.390465214+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-07T01:52:28.405487721+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T01:52:28.409991972+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-07T01:52:28.415355653+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T01:52:29.881569727+00:00 TRACE Z-Wave Lock PH  Z-Wave command(f6b3f7cb) transmit status: TRANSMIT_COMPLETE_OK
2024-03-07T01:53:29.990420488+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-07T01:53:30.005650432+00:00 TRACE Z-Wave Lock PH  Z-Wave command(e13a8f20) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T01:53:30.008302424+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-07T01:53:30.020798002+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T01:53:30.035456328+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-07T01:53:30.041063797+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T01:53:31.501696749+00:00 TRACE Z-Wave Lock PH  Z-Wave command(e13a8f20) transmit status: TRANSMIT_COMPLETE_OK
2024-03-07T01:53:59.925509563+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-07T01:53:59.953930099+00:00 TRACE Z-Wave Lock PH  Z-Wave command(8ba1891d) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T01:53:59.956583759+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-07T01:53:59.961860396+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T01:54:00.023703635+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-07T01:54:00.035192377+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T01:54:01.381732644+00:00 TRACE Z-Wave Lock PH  Z-Wave command(8ba1891d) transmit status: TRANSMIT_COMPLETE_OK

Seems like the hub/driver is not receiving the ON command from the mobile app. I’d try changing the setting via either the CLI or via the ST Advanced Web App to see if it’s an app problem vs driver.

smartthings devices:commands
.....
? Select a device. 68

Laundry Room Door Lock

Components:
─────────────
 1  main     
 2  settings 
─────────────

? Enter component index or id 2

Capabilities:
───────────────────────────────────────────────
 1  platinummassive43262.schlageLockAlarm      
 2  platinummassive43262.autoLock              
 3  platinummassive43262.schlageInteriorButton 
 4  platinummassive43262.keypadBeep            
 5  platinummassive43262.lockAndLeave          
 6  platinummassive43262.vacationMode          
 7  platemusic11009.deviceNetworkId            
 8  refresh                                    
───────────────────────────────────────────────

? Enter capability index or id 2

Commands:
───────────────
 1  autolock() 
 2  off()      
───────────────

I was able to set the parameter back to Auto Lock using a routine. But the issue still stands that the app isn’t able to correctly toggle the state. I tried again to toggle it OFF and ON and it again gave a “network or server error” message.

2024-03-07T02:07:00.027481306+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-07T02:07:00.053929306+00:00 TRACE Z-Wave Lock PH  Z-Wave command(4bcfed6a) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T02:07:00.056589306+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"autolock","component":"settings","positional_args":{}}
2024-03-07T02:07:00.061894639+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T02:07:00.073945639+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=-1, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\xFF", src_channel=0, version=1}
2024-03-07T02:07:00.088348972+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T02:07:01.481479972+00:00 TRACE Z-Wave Lock PH  Z-Wave command(4bcfed6a) transmit status: TRANSMIT_COMPLETE_OK
2024-03-07T02:07:40.804599310+00:00 TRACE Z-Wave Lock PH  Received event with handler unnamed
2024-03-07T02:07:40.900737644+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (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="S2_ACCESS_CONTROL", payload="\x16\x01\x00\xFF\x06\x02\x00", src_channel=0, version=3}
2024-03-07T02:07:40.914791310+00:00 TRACE Z-Wave Lock PH  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T02:07:40.927506977+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"manual"},"value":"unlocked"}}
2024-03-07T02:07:40.932582977+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"unlockCodeName","capability_id":"platinummassive43262.unlockCodeName","component_id":"main","state":{"value":"manual"}}
2024-03-07T02:07:40.937443644+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T02:07:45.544976669+00:00 TRACE Z-Wave Lock PH  Received event with handler unnamed
2024-03-07T02:07:45.565516934+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received Z-Wave command: {args={door_condition=2, door_lock_mode="DOOR_UNSECURED", 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="S2_ACCESS_CONTROL", payload="\x00\x00\x02\xFE\xFE", src_channel=0, version=1}
2024-03-07T02:07:45.570685184+00:00 TRACE Z-Wave Lock PH  Found ZwaveDispatcher handler in zwave_lock
2024-03-07T02:07:45.584667171+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"unlocked"}}
2024-03-07T02:07:45.595008006+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T02:08:11.905069250+00:00 TRACE Z-Wave Lock PH  Received event with handler unnamed
2024-03-07T02:08:11.970337584+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received Z-Wave command: {args={alarm_level=1, alarm_type=27, event="AUTO_LOCK_LOCKED_OPERATION", event_parameter="", notification_status="ON", notification_type="ACCESS_CONTROL", v1_alarm_level=1, v1_alarm_type=27, z_wave_alarm_event=9, 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="S2_ACCESS_CONTROL", payload="\x1B\x01\x00\xFF\x06\x09\x00", src_channel=0, version=3}
2024-03-07T02:08:11.997510584+00:00 TRACE Z-Wave Lock PH  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T02:08:12.002358917+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"data":{"method":"auto"},"value":"locked"}}
2024-03-07T02:08:12.015107250+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"unlockCodeName","capability_id":"platinummassive43262.unlockCodeName","component_id":"main","state":{"value":"Locked"}}
2024-03-07T02:08:12.020673917+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T02:08:16.653983253+00:00 TRACE Z-Wave Lock PH  Received event with handler unnamed
2024-03-07T02:08:16.720394253+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (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="S2_ACCESS_CONTROL", payload="\xFF\x00\x00\xFE\xFE", src_channel=0, version=1}
2024-03-07T02:08:16.725490586+00:00 TRACE Z-Wave Lock PH  Found ZwaveDispatcher handler in zwave_lock
2024-03-07T02:08:16.729812253+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"lock","capability_id":"lock","component_id":"main","state":{"value":"locked"}}
2024-03-07T02:08:16.734992253+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T02:08:53.425429937+00:00 TRACE Z-Wave Lock PH  Received event with handler capability

One clue that may be relevant that when I was creating the routine, it showed all the parameters I could pick (including Auto Lock) but they all say “Not set”. So perhaps the underlying issue is the driver doesn’t seem to be refreshed with the latest lock settings. Is there something I can do to refresh them in the app?

The Actions in the Routine don’t reflect the state of the settings/capabilities only that, for the purposes of the Routine Actions, they have not been set. Again, we need to see if it’s the app or not. Check the state of the components/capabilities using the CLI or AWA. And try changing the Autolock setting as I suggested in my previous post.

Using the routine, the parameter did change to ON. But you’d like me to try using one of those other methods and see if the setting in the app will reflect that the parameter changed? I can do that. I’ll try OFF, check the app, then ON and check the app…

Btw, thanks for the help.

Update:
I used the AWA and clicked on the button for OFF and from the CLI log, it looks like the event was handled.

2024-03-07T03:07:36.494154391+00:00 TRACE Z-Wave Lock PH  Z-Wave command(eb869351) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T03:07:36.497176725+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-07T03:07:36.504994725+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T03:07:36.511102725+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-07T03:07:36.526565058+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T03:07:38.001608391+00:00 TRACE Z-Wave Lock PH  Z-Wave command(eb869351) transmit status: TRANSMIT_COMPLETE_OK

But in the app, it still shows the setting as Auto Lock = ON. Then I clicked on the button for “Auto lock” and the CLI log shows that it went through. I can’t tell anything from the app, because it always shows Auto Lock ON regardless.

2024-03-07T03:07:50.975517060+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-07T03:07:50.994160726+00:00 TRACE Z-Wave Lock PH  Z-Wave command(efd3e11d) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-07T03:07:50.999431726+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"autolock","component":"settings","positional_args":{}}
2024-03-07T03:07:51.016649393+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-07T03:07:51.022696393+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=-1, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\xFF", src_channel=0, version=1}
2024-03-07T03:07:51.030482060+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-07T03:07:52.461666393+00:00 TRACE Z-Wave Lock PH  Z-Wave command(efd3e11d) transmit status: TRANSMIT_COMPLETE_OK

So is that an app issue or a driver issue?

Yes… I’ve been having problems setting the Auto Lock on 1 out of 8 locks on that hub.

See post back onSeptember 15th 2023:

So just to clarify, in my case, the app seems to be showing the wrong state for Auto Lock. It sees it as always enabled (set to Auto Lock) so no matter what, if I click on it, it sends the command to turn Auto Lock off.

I can change the state of the setting via the AWA or via routine, so that’s my current workaround. Can anyone else confirm if they are able to turn the setting off, see it off in the app, then turn it on and see it back on?

I think what you’re seeing are the parameters you can select in the Routine Screenshot below :slight_smile:

In contrast, what you see in the Device card are the current settings of the Lock.

Nope, as was pointed out previously, the values on the routine screen don’t reflect the current state of the lock parameters. That was a red herring and I’m sorry I muddied the waters by mentioning it.

I’m talking about the following screen:


This is the state of the screen after using the Advanced Web App to turn off Auto lock, Internal Schlage button and Keypad beep. As you can see the Auto lock setting on the screen still shows on when in reality it is off. The other two are correct.

Because it has the wrong state on the app screen, I can no longer get it back to the desired state of Auto lock being enabled. Because it shows as “on” whenever I click on it, it just sends the “off” commands, as noted in my CLI logs. The other two example settings (Internal Schlage button and Keypad beep) in my screenshot have the correct state. So I can set those accordingly from the app.

Could you try turning the setting off in your copy of the app to verify if it is a problem for everyone or not?

Additional information.
Here’s the log of the 3 events that were generated disabling the three features from AWA.

2024-03-10T14:15:23.323056226+00:00 TRACE Z-Wave Lock PH  Z-Wave command(1c0f17e3) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-10T14:15:23.328447892+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-10T14:15:23.333438226+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T14:15:23.338070893+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-10T14:15:23.343554893+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-10T14:15:24.831487560+00:00 TRACE Z-Wave Lock PH  Z-Wave command(1c0f17e3) transmit status: TRANSMIT_COMPLETE_OK
2024-03-10T14:15:29.675584562+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-10T14:15:29.698123562+00:00 TRACE Z-Wave Lock PH  Z-Wave command(658aab3c) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-10T14:15:29.700802562+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.keypadBeep","command":"off","component":"settings","positional_args":{}}
2024-03-10T14:15:29.706274562+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T14:15:29.715706896+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=3, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x03\x01\x00", src_channel=0, version=1}
2024-03-10T14:15:29.723395229+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-10T14:15:31.181465896+00:00 TRACE Z-Wave Lock PH  Z-Wave command(658aab3c) transmit status: TRANSMIT_COMPLETE_OK
2024-03-10T14:15:31.355737896+00:00 TRACE Z-Wave Lock PH  Received event with handler unnamed
2024-03-10T14:15:31.371133896+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received Z-Wave command: {args={configuration_value=0, parameter_number=3, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x03\x01\x00", src_channel=0, version=1}
2024-03-10T14:15:31.376096230+00:00 TRACE Z-Wave Lock PH  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T14:15:31.380458563+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"keypadBeep","capability_id":"platinummassive43262.keypadBeep","component_id":"settings","state":{"value":"off"}}
2024-03-10T14:15:31.385401563+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-10T14:15:36.905104566+00:00 TRACE Z-Wave Lock PH  Received event with handler capability
2024-03-10T14:15:37.007891899+00:00 TRACE Z-Wave Lock PH  Z-Wave command(4dd002a2) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-10T14:15:37.031053566+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received command: {"args":{},"capability":"platinummassive43262.schlageInteriorButton","command":"disable","component":"settings","positional_args":{}}
2024-03-10T14:15:37.115666566+00:00 TRACE Z-Wave Lock PH  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T14:15:37.187222232+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=11, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0B\x01\x00", src_channel=0, version=1}
2024-03-10T14:15:37.243450232+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled
2024-03-10T14:15:38.451473233+00:00 TRACE Z-Wave Lock PH  Z-Wave command(4dd002a2) transmit status: TRANSMIT_COMPLETE_OK
2024-03-10T14:15:38.590602900+00:00 TRACE Z-Wave Lock PH  Received event with handler unnamed
2024-03-10T14:15:38.632580233+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> received Z-Wave command: {args={configuration_value=0, parameter_number=11, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S2_ACCESS_CONTROL", payload="\x0B\x01\x00", src_channel=0, version=1}
2024-03-10T14:15:38.667080566+00:00 TRACE Z-Wave Lock PH  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T14:15:38.671467566+00:00 INFO Z-Wave Lock PH  <ZwaveDevice: 4b1015f2-7483-44b5-a899-f05602334881 [2F] (Front Door Lock)> emitting event: {"attribute_id":"interiorButton","capability_id":"platinummassive43262.schlageInteriorButton","component_id":"settings","state":{"value":"disable"}}
2024-03-10T14:15:38.686519566+00:00 DEBUG Z-Wave Lock PH  Front Door Lock device thread event handled

As you can see parameter 15 (Auto lock) was sent the value of 0 (disabled) and indeed if I check the door, it will no longer auto lock after 30 seconds.

But even in the AWA, the setting of Auto lock shows as “auto lock” which means it thinks it is still enabled. This would explain why the UI shows the state of auto lock as still enabled. I think this points to a driver issue.

I’d like someone else to confirm the behavior please, so I don’t think I’m going crazy. :crazy_face:

1 Like

(I’ve moved this discussion to its own thread both because I think you may get more responses from people who see a more specific thread title, and because it was starting to overwhelm the base thread for that custom driver. Carry on. :sunglasses:)

2 Likes

Hi @Puzzling

Not at all… I may have got lost in the thread a bit :wink:

I tried some A/B Tests… operating from the Android App vs from SmartThings Advanced.

In SmartThings Advanced
Auto Lock was Off

In Android App
Auto Lock was Off
Toggled to On
“circled” for 25± seconds, resulted in pop up: “A network or server error occurred. Try again later.
Toggle remained Off (after refreshing card)
SmartThings Advanced Remained Off (after refreshing web page)

In SmartThings Advanced
Auto Lock was Off
Clicked “autolock” command button & refresh command button
Auto Lock was set to “autolock” in SmartThings Advanced
AND to “On” in Android App Device Card

Repeated “In Android App” steps above again, trying to turn OFF from Android App.
Same result… “network error…”
Android App Device Card Toggle remained On (after refreshing card)
SmartThings Advanced Remained autolock (after refreshing web page)

In SmartThings Advanced
Auto Lock was autolock
Clicked autolock “off” command button & refresh command button
Auto Lock was set to “Off” in SmartThings Advanced
AND to “Off” in Android App Device Card

Summary:

  1. The Android App Auto Lock Toggle does NOT work.
  2. All OTHER Commands sent from the Android App DO work.
  3. Sending AutoLock (and other commands) from SmartThings Advance DOES work.
  4. In my case, changes made on SmartThings Advance ARE reflected on the Android App Device Card

@philh30 Hope you’re doing well !!! Can you review my prior post on the “one” out of eight Schlage Locks not updating the AutoLock Status on the Device Card? I wonder if that, along with the behavior I outlined above and what @Puzzling is experiencing, might point to some kind of coding issue specifically related the AutoLock field ??? :thinking:

2 Likes

I am not seeing any signs of the events being emitted to set the autoLock attribute to either off or autolock as a result of the off or autolock commands.

The would be enough to confuse the mobile app as those commands are explicitly defined as enum commands that will result in the attribute being changed as specified.

I am also not seeing the autoLock attribute being updated when the preferences are changed.

A possible reason for the autoLock attribute not being updated in SmartThings is that there doesn’t seem to be a report from the lock to confirm it has happened. The ‘normal’ sequence in SmartThings is to send the Z-Wave command to the device, and then when the new state is reported back by the device to emit the event to update the attribute in SmartThings. That doesn’t seem to be happening here.

3 Likes

I see that too now. Changing the other two settings is followed by an emit action, but the autoLock is not.

I’m looking in the Github repository for the Schlage Z-Wave Lock PH and I see this code:

    local cap = paramMap[param].cap
    local evt = paramMap[param].attr(paramMap[param].map[value])
    if device:supports_capability_by_id(cap,comp.id) then
      device:emit_component_event(comp,evt)
    end

In the capabilities of the Schlage BE469 platinummassive43262.autoLock is listed.

So as far as I can tell, either the configuration report routine isn’t being called, or when it is, it is somehow skipping the emit call. That’s the extent of my noob knowledge, so hopefully someone else can narrow this down further.

1 Like

That’s exactly what I see when I log changing the auto lock setting:

Enable

2024-03-10T23:37:58.670371192+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler capability
2024-03-10T23:37:58.719894900+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(27ddbe90) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-10T23:37:58.731652775+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"autolock","component":"settings","positional_args":{}}
2024-03-10T23:37:58.734980942+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T23:37:58.736890921+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={configuration_value=-1, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\xFF", src_channel=0, version=1}
2024-03-10T23:37:58.740901754+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2024-03-10T23:38:00.554257732+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(27ddbe90) transmit status: TRANSMIT_COMPLETE_OK
2024-03-10T23:38:00.919101315+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler unnamed
2024-03-10T23:38:00.923091190+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received Z-Wave command: {args={configuration_value=-1, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x0F\x01\xFF", src_channel=0, version=1}
2024-03-10T23:38:00.940401148+00:00 TRACE Z-Wave Lock PH BETA  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T23:38:00.942801065+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"autoLock","capability_id":"platinummassive43262.autoLock","component_id":"settings","state":{"value":"autolock"}}
2024-03-10T23:38:00.950729065+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled

Disable

2024-03-10T23:38:06.957045809+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler capability
2024-03-10T23:38:07.421667559+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(023a2d83) queued for radio transmission: CC:Configuration, CID:0x04
2024-03-10T23:38:07.424546454+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received command: {"args":{},"capability":"platinummassive43262.autoLock","command":"off","component":"settings","positional_args":{}}
2024-03-10T23:38:07.560226642+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T23:38:07.671315767+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={configuration_value=0, default=false, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-10T23:38:07.707072329+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2024-03-10T23:38:09.218784119+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(023a2d83) transmit status: TRANSMIT_COMPLETE_OK
2024-03-10T23:38:11.268308784+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler unnamed
2024-03-10T23:38:11.274495326+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received Z-Wave command: {args={configuration_value=0, parameter_number=15, size=1}, cmd_class="CONFIGURATION", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x0F\x01\x00", src_channel=0, version=1}
2024-03-10T23:38:11.294000367+00:00 TRACE Z-Wave Lock PH BETA  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock -> Schlage BE469
2024-03-10T23:38:11.294950034+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"autoLock","capability_id":"platinummassive43262.autoLock","component_id":"settings","state":{"value":"off"}}

The Lock driver will only get called when a Z-Wave command is received by the default Z-Wave handler in the Lua library. Since we see no indication that a Z-Wave command is being passed to the Lock driver in the OP case, either 1) the transmitted command is not being received by the lock; 2) the lock fails to process the transmitted command properly; 3) the lock receives and processes it and fails to generate a configuration report; or 4) the report is generated, but not received by the hub.

Since the OP has 7 other locks that are working correctly, I don’t think we are looking at an issue with the driver but probably some kind of a hardware issue.

That section of code is part of the Configuration Report handler that gets called when the hub receives a Z-Wave command from the lock. Since we don’t see any indication in the logging that the driver receives a Z-Wave command of that command class, there would be no reason to expect an event to be generated.

Coming in late, but have the OP check the security levels of the misbehaving lock in the device profile at the advanced settings page of the official web UI.

My.smartthings.com/advanced

It is not uncommon in zwave to see different commandset profiles for different security levels.

1 Like

I only have one lock, I think you might be referring to @JohnRichard who is also having problems.

1 Like

Yeah, it got a little confusing when the topic was split.

1 Like

Where in the AWA can I find the security levels of the device?

Update: If it helps, using ST API Browser+ from @TAustin, I see NW Security Level is ZWAVE_S2_ACCESS_CONTROL

At this point, I’m willing to exclude and readd my Front door lock if that will possibly fix this.