[ST EDGE] Z-Wave Lock PH

@h0ckeysk8er and @philh30

Thank you both !

Inputting the Code Length allowed the Toggle to stay put !

@philh30 I have several BE469ZPs and one older one I think.

1 Like

I’ll check tomorrow, but I still think if you issue a reloadCodes and other some other commands, the code names will reset on the non-ZP lock using your beta driver. Also, I think switching drivers will have the same result.

This makes sense, and I think would impact the ZP as well. The handlers should populate the driver’s name registry from the lockCodes capability, but I haven’t seen anywhere that that’s happening.

If so, grab logs so I can reproduce in a test script.

Lock code names are staying together with driver. When I do switching between beta and non-beta, names are updated each time. After switch is done, they stay as is.

So, I can’t seem to recreate the issues of all the codeNames being replaced with codeX like I could before. So whatever you did seems to have fixed it for my non-ZP lock. I’ll try with my ZP one if I can ever get it working with Edge drivers.

One thing that’s weird is that the unlockCodeName field is getting populated properly and yet the lockCodes array appears to be empty in my hub for the non-ZP lock. Could just be an error in how the default handler is presenting it in the CLI even though they really are populated. Will see if any of that changes once 45.11 is downloaded to my hub.

Attribute Value
codeLength 6
maxCodes 30
maxCodeLength
codeChanged “1 renamed”
lock
minCodeLength 8
scanCodes “Complete”
codeReport
lockCodes “{}”

? Select a capability. 4
──────────────────────────
Attribute Value
unlockCodeName “Bruce and Teri”

That is no longer happening on my BE469 (non-ZP) lock with the beta driver.

I’m also not seeing the issue with the empty lockCodes array in the CLI and I’ve been pushing the driver hard on both the BE469 and BE469ZP since last Friday trying to ensure nothing’s breaking.

Always possible there’s another hardware revision lurking out there somewhere, of course.

Yeah, I can’t recreate the issue either on my non-ZP now either.

You may not see the empty lockCodes array because you are on a different hub than I am with different firmware. I’m on the Wifi ST Hub running 43.5 waiting on 45.11 to be installed (which supposedly has some fixes for lockCodes though nothing specific is mentioned).

1 Like

Well, I spoke too soon. For some unknown reason, SLGA is getting Code 1 updated with name “Code 1” instead of the name that should be set. And it’s doing it continuously.

connecting... connected
2023-01-30T22:27:56.578970429+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:27:56.585725950+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Code 1\"}"},"visibility":{"displayed":false}}
2023-01-30T22:27:56.672687929+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:27:56.685992741+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(bda28c0c) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:27:56.694554970+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:27:56.701050554+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:27:58.054711927+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(bda28c0c) transmit status: TRANSMIT_COMPLETE_OK
2023-01-30T22:27:58.320374177+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler unnamed
2023-01-30T22:27:58.327570490+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received Z-Wave command: {args={user_code="**********", user_id_status="ENABLED_GRANT_ACCESS", user_identifier=1}, cmd_class="USER_CODE", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x01\x01\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A", src_channel=0, version=1}
2023-01-30T22:27:58.346094344+00:00 TRACE Z-Wave Lock PH BETA  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:27:58.351832406+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"codeChanged","capability_id":"lockCodes","component_id":"main","state":{"data":{"codeName":"Code 1"},"value":"1 changed"},"state_change":true}
2023-01-30T22:27:58.431303094+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:28:26.704390567+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:28:26.711030921+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Code 1\"}"},"visibility":{"displayed":false}}
2023-01-30T22:28:26.790659067+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:28:26.803473608+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(1eadbe3a) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:28:26.815777087+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:28:26.822627504+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:28:28.127318440+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(1eadbe3a) transmit status: TRANSMIT_COMPLETE_OK
2023-01-30T22:28:28.399493190+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler unnamed
2023-01-30T22:28:28.406290128+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received Z-Wave command: {args={user_code="**********", user_id_status="ENABLED_GRANT_ACCESS", user_identifier=1}, cmd_class="USER_CODE", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x01\x01\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A", src_channel=0, version=1}
2023-01-30T22:28:28.414981586+00:00 TRACE Z-Wave Lock PH BETA  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:28:28.421624044+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"codeChanged","capability_id":"lockCodes","component_id":"main","state":{"data":{"codeName":"Code 1"},"value":"1 changed"},"state_change":true}
2023-01-30T22:28:28.506584836+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:28:56.828299934+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:28:56.835491350+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Code 1\"}"},"visibility":{"displayed":false}}
2023-01-30T22:28:56.913217184+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:28:56.924553663+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(214a6718) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:28:56.931845975+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:28:56.937587163+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:28:58.415031516+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(214a6718) transmit status: TRANSMIT_COMPLETE_OK
2023-01-30T22:28:58.680224765+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler unnamed
2023-01-30T22:28:58.686999849+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received Z-Wave command: {args={user_code="**********", user_id_status="ENABLED_GRANT_ACCESS", user_identifier=1}, cmd_class="USER_CODE", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x01\x01\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A", src_channel=0, version=1}
2023-01-30T22:28:58.696732161+00:00 TRACE Z-Wave Lock PH BETA  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:28:58.702839328+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"codeChanged","capability_id":"lockCodes","component_id":"main","state":{"data":{"codeName":"Code 1"},"value":"1 changed"},"state_change":true}
2023-01-30T22:28:58.782645786+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:29:26.944762176+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:29:26.951590259+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Code 1\"}"},"visibility":{"displayed":false}}
2023-01-30T22:29:27.030481301+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:29:27.041921676+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(096d71a7) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:29:27.049467363+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:29:27.056166384+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:29:28.464498112+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(096d71a7) transmit status: TRANSMIT_COMPLETE_OK
2023-01-30T22:29:28.730085841+00:00 TRACE Z-Wave Lock PH BETA  Received event with handler unnamed
2023-01-30T22:29:28.736967653+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> received Z-Wave command: {args={user_code="**********", user_id_status="ENABLED_GRANT_ACCESS", user_identifier=1}, cmd_class="USER_CODE", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x01\x01\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A", src_channel=0, version=1}
2023-01-30T22:29:28.745561778+00:00 TRACE Z-Wave Lock PH BETA  Found ZwaveDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:29:28.751301487+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"codeChanged","capability_id":"lockCodes","component_id":"main","state":{"data":{"codeName":"Code 1"},"value":"1 changed"},"state_change":true}
2023-01-30T22:29:28.831206299+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled

What steps did you take with the lock prior to those logs?

About an hour ago (when I did the post about not being able to reproduce the name clearing), I did a requestCode codeSlot 1 and reloadAllCodes in that order from the CLI. Then the code 1 name resetting problem started about 50-55 mins after that and kept repeating. I then changed the name back to what I wanted it to be in SLGA, which changed the code name, and then it kept saying code 1 set to “Bruce and Teri” repeatedly until I unplugged the battery. However, the driver is still sending a request that is never replied to.

And apparently at some point during that hour, they pushed 45.11 to my hub. After the reboot, it has stopped…for now at least :slight_smile:

2023-01-30T22:52:02.522143133+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:52:02.529050654+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:52:11.414741895+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(5db934e7) transmit status: TRANSMIT_COMPLETE_NO_ACK
2023-01-30T22:52:32.538046188+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:52:32.546363625+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Bruce and Teri\"}"},"visibility":{"displayed":false}}
2023-01-30T22:52:32.636355625+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:52:32.656089542+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(48d2a78f) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:52:32.665665459+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:52:32.672615771+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:52:42.445089033+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(f16c66a5) transmit status: TRANSMIT_COMPLETE_NO_ACK
2023-01-30T22:53:02.676256534+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:53:02.682614513+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Bruce and Teri\"}"},"visibility":{"displayed":false}}
2023-01-30T22:53:02.768954013+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:53:02.783969680+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(c5af767d) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:53:02.794306763+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:53:02.802434451+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:53:19.325236914+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(48d2a78f) transmit status: TRANSMIT_COMPLETE_NO_ACK
2023-01-30T22:53:32.805132484+00:00 TRACE Z-Wave Lock PH BETA  Found CapabilityCommandDispatcher handler in zwave_lock -> Schlage Lock
2023-01-30T22:53:32.812719047+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> emitting event: {"attribute_id":"lockCodes","capability_id":"lockCodes","component_id":"main","state":{"value":"{\"1\":\"Bruce and Teri\"}"},"visibility":{"displayed":false}}
2023-01-30T22:53:32.894666276+00:00 INFO Z-Wave Lock PH BETA  <ZwaveDevice: 95130d4e-f4ee-4c39-b624-ad6013361692 [38] (Laundry Room Door Lock)> sending Z-Wave command: {args={user_identifier=1}, cmd_class="USER_CODE", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2023-01-30T22:53:32.906985505+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(6bc3dd8d) queued for radio transmission: CC:User Code, CID:0x02
2023-01-30T22:53:32.916163984+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:53:32.923910234+00:00 DEBUG Z-Wave Lock PH BETA  Laundry Room Door Lock device thread event handled
2023-01-30T22:53:50.725168030+00:00 TRACE Z-Wave Lock PH BETA  Z-Wave command(c5af767d) transmit status: TRANSMIT_COMPLETE_NO_ACK

2 Likes

Hopefully fixed in a new version dated 2023-01-30T23:11:55.938508123… They wrote these handlers so that sometimes codeId needs to be a string, other times a number. Changing it to a string fixed the renaming bug, but the handler that checks whether reloadAllCodes has finished running needs it passed as a number.

1 Like

Yikes. This is your driver on the new code.

2023-01-30T23:22:53.573929087+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:22:53.590524691+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:22:53.602167170+00:00 FATAL Z-Wave Lock PH BETA  Lua: callback error
stack traceback:
        [C]: in field 'st_json_decode'
        [string "json"]:17: in field 'decode'
        [string "st/capabilities/init.lua"]:56: in field 'build_cap_from_json_string'
        [string "st/capabilities/init.lua"]:142: in function <[string "st/capabilities/init.lua"]:134>
        [C]: in function 'pcall'
        [string "st/capabilities/init.lua"]:94: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
caused by: error converting Lua lightuserdata to String (expected string or number)
Traceback:
stack traceback:
        [C]: in function 'error'
        [string "st/capabilities/init.lua"]:98: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
2023-01-30T23:22:59.100349853+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:22:59.110129165+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:22:59.122350290+00:00 FATAL Z-Wave Lock PH BETA  Lua: callback error
stack traceback:
        [C]: in field 'st_json_decode'
        [string "json"]:17: in field 'decode'
        [string "st/capabilities/init.lua"]:56: in field 'build_cap_from_json_string'
        [string "st/capabilities/init.lua"]:142: in function <[string "st/capabilities/init.lua"]:134>
        [C]: in function 'copcall'
        [string "st/capabilities/init.lua"]:94: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
caused by: error converting Lua lightuserdata to String (expected string or number)
Traceback:
stack traceback:
        [C]: in function 'error'
        [string "st/capabilities/init.lua"]:98: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
2023-01-30T23:23:04.569126202+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:23:04.579777202+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:23:04.591998056+00:00 FATAL Z-Wave Lock PH BETA  Lua: callback error
stack traceback:
        [C]: in field 'st_json_decode'
        [string "json"]:17: in field 'decode'
        [string "st/capabilities/init.lua"]:56: in field 'build_cap_from_json_string'
        [string "st/capabilities/init.lua"]:142: in function <[string "st/capabilities/init.lua"]:134>
        [C]: in function 'copcall'
        [string "st/capabilities/init.lua"]:94: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
caused by: error converting Lua lightuserdata to String (expected string or number)
Traceback:
stack traceback:
        [C]: in function 'error'
        [string "st/capabilities/init.lua"]:98: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
2023-01-30T23:23:10.068651884+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:23:10.079282988+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:23:10.090148051+00:00 FATAL Z-Wave Lock PH BETA  Lua: callback error
stack traceback:
        [C]: in field 'st_json_decode'
        [string "json"]:17: in field 'decode'
        [string "st/capabilities/init.lua"]:56: in field 'build_cap_from_json_string'
        [string "st/capabilities/init.lua"]:142: in function <[string "st/capabilities/init.lua"]:134>
        [C]: in function 'copcall'
        [string "st/capabilities/init.lua"]:94: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
caused by: error converting Lua lightuserdata to String (expected string or number)
Traceback:
stack traceback:
        [C]: in function 'error'
        [string "st/capabilities/init.lua"]:98: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
2023-01-30T23:23:15.569699233+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:23:15.580840524+00:00 WARN Z-Wave Lock PH BETA  Unexpected filesystem lookup for capability platinummassive43262.lockCodeMaintenance
2023-01-30T23:23:15.593479712+00:00 FATAL Z-Wave Lock PH BETA  Lua: callback error
stack traceback:
        [C]: in field 'st_json_decode'
        [string "json"]:17: in field 'decode'
        [string "st/capabilities/init.lua"]:56: in field 'build_cap_from_json_string'
        [string "st/capabilities/init.lua"]:142: in function <[string "st/capabilities/init.lua"]:134>
        [C]: in function 'copcall'
        [string "st/capabilities/init.lua"]:94: in metamethod '__index'
        [string "init.lua"]:232: in main chunk
caused by: error converting Lua lightuserdata to String (expected string or number)
Traceback:
stack traceback:
        [C]: in function 'error'
        [string "st/capabilities/init.lua"]:98: in metamethod '__index'
        [string "init.lua"]:232: in main chunk

Yikes for sure. Experimental capability to add/delete lock codes via routine accidentally left in. Fully commented out in 2023-01-30T23:52:49.99918411.

1 Like

Ok, will give that a try. Both of the ZP locks that wouldn’t talk to the hub mysteriously working after new firmware…hmmmm

1 Like

Hmmmm … :wink:

1 Like

Where did you find this?

1 Like

Hi, did you get the Kwikset 912 lever working?
Thanks

Hi,

Yes, the Kwikset 912 works well.

Of course, it doesn’t have all of the capabilities of the Schlage 469, such as Alarm (tamper, activity, etc), but it definitely works with @philh30 's drivers !

image

1 Like

7 posts were split to a new topic: Kwikset 912 Lever Lock: Can’t Add Codes with Stock Edge Driver

Thanks for reply Bruce!
I will look stupid now but I have no idea what is SLGA , search only found
Saskatchewan Liquor and Gaming Authority
…I presume that ain’t it :rofl: