Popp Electric Strike Lock Control: status misreported after automatic close #6557

dwmw2 · 2023-12-12T18:33:51Z

dwmw2
Dec 12, 2023

Checklist

I have read and followed the above instructions
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?

I have a Popp Electric Strike Lock Control: https://devices.zwave-js.io/?jumpTo=0x0154:0x0005:0x0001:0.0

Working:

In ZWave-JS-UI I set [3-98-0-targetMode] Target lock mode to [1] UnsecuredWithTimeout.
The relay clicks, the multimeter I put on the terminals of the relay beeps for ten seconds, then the relay clicks off again. Ten seconds is unsurprising since this is the value of [3-98-0-lockTimeoutConfiguration] Duration of timed mode in seconds
ZWave-JS-UI receives an update and sees that the lock is locked again:

2023-12-12T17:42:26.717Z SERIAL « 0x0123000400031b988176429ac3cdbe32a91eb0013ba7919d898b1c55e526455f6 (37 bytes)
                                  8cbca0098
2023-12-12T17:42:26.723Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:42:26.729Z CNTRLR   [Node 003] [~] [Door Lock] currentMode: 1 => 255                  [Endpoint 0]
2023-12-12T17:42:26.738Z CNTRLR   [Node 003] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2023-12-12T17:42:26.746Z CNTRLR   [Node 003] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2023-12-12T17:42:26.755Z CNTRLR   [Node 003] [~] [Door Lock] lockTimeout: 5 => 0                    [Endpoint 0]
2023-12-12T17:42:26.764Z CNTRLR   [Node 003] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2023-12-12T17:42:26.773Z CNTRLR   [Node 003] [~] [Door Lock] boltStatus: "unlocked" => "unlocked"   [Endpoint 0]
2023-12-12T17:42:26.781Z CNTRLR   [Node 003] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2023-12-12T17:42:26.788Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Secured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            unlocked
                                        door status:            open
                                        lock timeout:           0 seconds

An MQTT message is sent to report the locked status:

2023-12-12T17:42:26+0000 zwave/Strike_Lock/door_lock/endpoint_0/currentMode {"time":1702402946728,"value":255,"nodeName":"Strike Lock","nodeLocation":""}

Not working:

In ZWave-JS-UI I set [3-98-0-targetMode] Target lock mode to [0] Unsecured.


2023-12-12T17:51:07.848Z DRIVER   all queues busy
2023-12-12T17:51:07.860Z SERIAL » 0x0109001303029840252138                                            (11 bytes)
2023-12-12T17:51:07.862Z DRIVER » [Node 003] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      33
                                  └─[SecurityCCNonceGet]
2023-12-12T17:51:07.868Z SERIAL « [ACK]                                                                   (0x06)
2023-12-12T17:51:07.874Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-12-12T17:51:07.877Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:07.882Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-12-12T17:51:09.125Z SERIAL « 0x011800132100007e00ca7f7f7f7f000103000000004204000025              (26 bytes)
2023-12-12T17:51:09.128Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:09.134Z DRIVER « [REQ] [SendData]
                                    callback id:            33
                                    transmit status:        OK, took 1260 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -54 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         1
                                    beam:                   1000 ms
2023-12-12T17:51:09.156Z SERIAL « 0x0112000400030a98803d8bf4c96bac00e4ca009a                          (20 bytes)
2023-12-12T17:51:09.160Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:09.168Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceReport]
                                      nonce: 0x3d8bf4c96bac00e4
2023-12-12T17:51:09.183Z SERIAL » 0x011e0013031798818a10fe3c75457b998d9915b73dc2669170763481842522fb  (32 bytes)
2023-12-12T17:51:09.187Z DRIVER » [Node 003] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      34
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 61
                                    └─[DoorLockCCOperationSet]
                                        target mode: Unsecured
2023-12-12T17:51:09.193Z SERIAL « [ACK]                                                                   (0x06)
2023-12-12T17:51:09.202Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-12-12T17:51:09.204Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:09.207Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-12-12T17:51:09.225Z SERIAL « 0x011800132200000300cf7f7f7f7f00010300000000020100001b              (26 bytes)
2023-12-12T17:51:09.227Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:09.230Z DRIVER « [REQ] [SendData]
                                    callback id:            34
                                    transmit status:        OK, took 30 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -49 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         1
2023-12-12T17:51:09.253Z DRIVER   all queues idle

The relay clicks, the multimeter beeps for five seconds, then the relay clicks off again.
ZWave-JS-UI appears to receive an update saying the the lock is unlocked, which is no longer true.

2023-12-12T17:51:14.247Z DRIVER   all queues busy
2023-12-12T17:51:14.260Z SERIAL » 0x010900130302984025233a                                            (11 bytes)
2023-12-12T17:51:14.262Z DRIVER » [Node 003] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      35
                                  └─[SecurityCCNonceGet]
2023-12-12T17:51:14.274Z SERIAL « [ACK]                                                                   (0x06)
2023-12-12T17:51:14.278Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-12-12T17:51:14.281Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:14.286Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-12-12T17:51:15.539Z SERIAL « 0x011800132300007f00d07f7f7f7f00010300000000420400003c              (26 bytes)
2023-12-12T17:51:15.543Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.548Z DRIVER « [REQ] [SendData]
                                    callback id:            35
                                    transmit status:        OK, took 1270 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -48 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         1
                                    beam:                   1000 ms
2023-12-12T17:51:15.566Z SERIAL « 0x0112000400030a98803c8800cb4a3e3308ca0002                          (20 bytes)
2023-12-12T17:51:15.570Z SERIAL » [ACK]                                                                   (0x06)





2023-12-12T17:51:15.573Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceReport]
                                      nonce: 0x3c8800cb4a3e3308
2023-12-12T17:51:15.586Z SERIAL » 0x011d001303169881724d0552b8151663df3d793ca5d7b4ec6b5e2b9d252442    (31 bytes)
2023-12-12T17:51:15.589Z DRIVER » [Node 003] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      36
                                  └─[SecurityCCCommandEncapsulation]
                                    │ nonce id: 60
                                    └─[DoorLockCCOperationGet]
2023-12-12T17:51:15.601Z SERIAL « [ACK]                                                                   (0x06)
2023-12-12T17:51:15.605Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-12-12T17:51:15.607Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.609Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-12-12T17:51:15.627Z SERIAL « 0x011800132400000300d07f7f7f7f000103000000000201000002              (26 bytes)
2023-12-12T17:51:15.629Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.632Z DRIVER « [REQ] [SendData]
                                    callback id:            36
                                    transmit status:        OK, took 30 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -48 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         1
2023-12-12T17:51:15.649Z SERIAL « 0x010a00040003029840ca00e2                                          (12 bytes)
2023-12-12T17:51:15.652Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.656Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[SecurityCCNonceGet]
2023-12-12T17:51:15.675Z SERIAL » 0x01110013030a9880a62e4cedaf419ac9052558                            (19 bytes)
2023-12-12T17:51:15.678Z DRIVER » [Node 003] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      37
                                  └─[SecurityCCNonceReport]
                                      nonce: 0xa62e4cedaf419ac9
2023-12-12T17:51:15.684Z SERIAL « [ACK]                                                                   (0x06)
2023-12-12T17:51:15.696Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2023-12-12T17:51:15.698Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.701Z DRIVER « [RES] [SendData]
                                    was sent: true
2023-12-12T17:51:15.712Z SERIAL « 0x011800132500000300d07f7f7f7f000103000000000201000003              (26 bytes)
2023-12-12T17:51:15.714Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.718Z DRIVER « [REQ] [SendData]
                                    callback id:            37
                                    transmit status:        OK, took 30 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         LWR
                                    ACK RSSI:               -48 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         1
2023-12-12T17:51:15.744Z SERIAL « 0x0123000400031b98813bba50476635cea36b94afe9cea54038a6c8c554ea921cd (37 bytes)
                                  793ca00ce
2023-12-12T17:51:15.749Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:51:15.755Z CNTRLR   [Node 003] [~] [Door Lock] currentMode: 255 => 0                  [Endpoint 0]
2023-12-12T17:51:15.762Z CNTRLR   [Node 003] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2023-12-12T17:51:15.770Z CNTRLR   [Node 003] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2023-12-12T17:51:15.778Z CNTRLR   [Node 003] [~] [Door Lock] lockTimeout: 0 => 0                    [Endpoint 0]
2023-12-12T17:51:15.785Z CNTRLR   [Node 003] [~] [Door Lock] doorStatus: "closed" => "open"         [Endpoint 0]
2023-12-12T17:51:15.793Z CNTRLR   [Node 003] [~] [Door Lock] boltStatus: "locked" => "unlocked"     [Endpoint 0]
2023-12-12T17:51:15.802Z CNTRLR   [Node 003] [~] [Door Lock] latchStatus: "closed" => "open"        [Endpoint 0]
2023-12-12T17:51:15.810Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Unsecured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            unlocked
                                        door status:            open
                                        lock timeout:           0 seconds
2023-12-12T17:51:15.840Z DRIVER   all queues idle

Refreshing the status in ZWave-JS-UI appears to "confirm" the untrue Unlocked status:

2023-12-12T17:52:27.115Z SERIAL « 0x0123000400031b9881c41d165afdbacb26fdad71f0578c918fb86ca20bf75837f (37 bytes)
                                  bebd000d7
2023-12-12T17:52:27.119Z SERIAL » [ACK]                                                                   (0x06)
2023-12-12T17:52:27.125Z CNTRLR   [Node 003] [~] [Door Lock] currentMode: 0 => 0                    [Endpoint 0]
2023-12-12T17:52:27.133Z CNTRLR   [Node 003] [~] [Door Lock] outsideHandlesCanOpenDoor: false,false [Endpoint 0]
                                  ,false,false => false,false,false,false
2023-12-12T17:52:27.142Z CNTRLR   [Node 003] [~] [Door Lock] insideHandlesCanOpenDoor: false,false, [Endpoint 0]
                                  false,false => false,false,false,false
2023-12-12T17:52:27.150Z CNTRLR   [Node 003] [~] [Door Lock] lockTimeout: 0 => 0                    [Endpoint 0]
2023-12-12T17:52:27.159Z CNTRLR   [Node 003] [~] [Door Lock] doorStatus: "open" => "open"           [Endpoint 0]
2023-12-12T17:52:27.168Z CNTRLR   [Node 003] [~] [Door Lock] boltStatus: "unlocked" => "unlocked"   [Endpoint 0]
2023-12-12T17:52:27.177Z CNTRLR   [Node 003] [~] [Door Lock] latchStatus: "open" => "open"          [Endpoint 0]
2023-12-12T17:52:27.184Z DRIVER « [Node 003] [REQ] [ApplicationCommand]
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockCCOperationReport]
                                        current mode:           Unsecured
                                        active outside handles: false, false, false, false
                                        active inside handles:  false, false, false, false
                                        latch status:           open
                                        bolt status:            unlocked
                                        door status:            open
                                        lock timeout:           0 seconds
2023-12-12T17:52:27.186Z CNTRLR « [Node 003] received lock status:
                                  current mode:       Unsecured
                                  lock timeout:       0 seconds
                                  door status:        open
                                  bolt status:        unlocked
                                  latch status:       open
2023-12-12T17:52:27.222Z DRIVER   all queues idle

I need to explicitly set the lock back to Locked status, despite it already being locked, before it reports itself as such.

Is this a firmware bug? Can it be worked around?

Software versions

Driver (node-zwave-js): 12.4.1
Z-Wave JS UI: 9.5.1

If you are using something non-standard, tell us here: ...

Running on OpenWrt, using a secondary controller (node 2).

Device information

Manufacturer: Popp
Model name: Electric Strike Lock Control
Node ID: 003

Checklist

I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).

Upload Logfile

interview-log.txt

zwave-js-bot · 2023-12-12T18:34:07Z

zwave-js-bot
Dec 12, 2023
Collaborator

👋 Hey @dwmw2!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

0 replies

dwmw2 · 2023-12-14T10:53:33Z

dwmw2
Dec 14, 2023
Author

This lock doesn't really support being permanently unlocked. You can either set it to UnsecuredWithTimeout and it'll obey the explicit timeout that you configured, or you can set it to Unsecured and it'll lock itself again anyway after five seconds, then lie to you.

Can we just stop exposing the Unsecured option? I note that's the only thing we expose in the MQTT AutoDiscovery, in ${mqtt_prefix}/homeassistant/lock/Strike_Lock/lock/config I see:

{
   "command_topic" : "zwave/Strike_Lock/door_lock/endpoint_0/targetMode/set",
   "device" : {
      "identifiers" : [
         "zwavejs2mqtt_0xcbd6ef3f_node3"
      ],
      "manufacturer" : "Popp & Co",
      "model" : "Electric Strike Lock Control (012501)",
      "name" : "Strike Lock",
      "sw_version" : "1.5"
   },
   "json_attributes_topic" : "zwave/Strike_Lock/door_lock/endpoint_0/currentMode",
   "name" : "Strike Lock_lock",
   "payload_lock" : 255,
   "payload_unlock" : 0,
   "state_locked" : 255,
   "state_topic" : "zwave/Strike_Lock/door_lock/endpoint_0/currentMode",
   "state_unlocked" : 0,
   "unique_id" : "zwavejs2mqtt_0xcbd6ef3f_3-98-0-currentMode",
   "value_template" : "{{ value_json.value }}"
}

If I manually publish a new config topic with "payload_unlock": 1 it now works in Domoticz as expected. I click 'Unlock', it unlocks for the configured amount of time and then shows itself as Locked again.

0 replies

AlCalzone · 2023-12-14T23:24:23Z

AlCalzone
Dec 14, 2023
Maintainer

I just checked the specs again. The Lock implements Door Lock CC v2, but querying the supported modes is only available in Door Lock CC v4. So there's no way to know that the lock doesn't support constant mode (no timeouts). And since the command to query supported modes isn't available in v2, we can't simply override it.

There's one requirement that's not correctly handled by Z-Wave JS, but it would cause an issue in the opposite case:

A controlling node MUST NOT specify modes using timeout-based fall back if the Operation Type
of the supporting device is set to Constant operation (set by Door Lock Configuration Set).

And one requirement that's not correctly handled by the device:

A supporting node MUST apply the constant modes without any timeout even if it is set to Timed
Operation Type.

This one is causing your issue and the way I see it, it's a firmware bug.

6 replies

AlCalzone Dec 18, 2023
Maintainer

HA has an open issue to expose the other modes except lock/unlock. Not sure about Domotics, but AFAIK it should have access to the raw Z-Wave values, so unless it has built its own discovery scheme on top, those should be available.

dwmw2 Dec 18, 2023
Author

These days, Domoticz does the same autodiscovery in MQTT as HomeAssistant does. It used to use OpenZWave directly but has finally deprecated that in favour of ZWave-JS-UI (which is why I'm finally getting round to making it work with OpenWrt, qv).

As far as I could tell, the config that ZWave-JS-UI exposes doesn't include anything but the constant modes (255 and 0):

{
   "command_topic" : "zwave/Strike_Lock/door_lock/endpoint_0/targetMode/set",
   "device" : {
      "identifiers" : [
         "zwavejs2mqtt_0xcbd6ef3f_node3"
      ],
      "manufacturer" : "Popp & Co",
      "model" : "Electric Strike Lock Control (012501)",
      "name" : "Strike Lock",
      "sw_version" : "1.5"
   },
   "json_attributes_topic" : "zwave/Strike_Lock/door_lock/endpoint_0/currentMode",
   "name" : "Strike Lock_lock",
   "payload_lock" : 255,
   "payload_unlock" : 0,
   "state_locked" : 255,
   "state_topic" : "zwave/Strike_Lock/door_lock/endpoint_0/currentMode",
   "state_unlocked" : 0,
   "unique_id" : "zwavejs2mqtt_0xcbd6ef3f_3-98-0-currentMode",
   "value_template" : "{{ value_json.value }}"
}

As noted in #6557 (comment) if I tweak that to advertise 1 as the payload_unlock, it all works fine.

AlCalzone Dec 18, 2023
Maintainer

I see, this needs to be solved in https://github.com/zwave-js/zwave-js-ui though. MQTT is handled over there.
FWIW, Home Assistant does not use MQTT discovery anymore by default, but rather builds a Z-Wave specific discovery scheme on top of the websocket API.

dwmw2 Dec 20, 2023
Author

FWIW, Home Assistant does not use MQTT discovery anymore by default, but rather builds a Z-Wave specific discovery scheme on top of the websocket API.

Hm, would that allow us to run a smaller 'server' than the full ZWave-JS-UI? Perhaps we can make Domoticz do the same. Moving from the tiny libopenzwave library to ZWave-JS-UI is a problem for a lot of embedded machines, which is why we've been trying to cut down the footprint, but it's still taking 200MiB of RAM.

AlCalzone Dec 20, 2023
Maintainer

If you don't need the UI, https://github.com/zwave-js/zwave-js-server is what the "official" HA addon uses. This is just a translation layer from the Node.js world to Websockets.
You'll still have to deal with Node.js's RAM usage, but in my recent tests this was around 40-50 MB for just the driver. With the server wrapper it might be a bit more.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Popp Electric Strike Lock Control: status misreported after automatic close #6557

{{title}}

Replies: 3 comments 6 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Popp Electric Strike Lock Control: status misreported after automatic close #6557

dwmw2 Dec 12, 2023

Checklist

Describe the issue

Working:

Not working:

Software versions

Device information

Checklist

Upload Logfile

Replies: 3 comments · 6 replies

zwave-js-bot Dec 12, 2023 Collaborator

dwmw2 Dec 14, 2023 Author

AlCalzone Dec 14, 2023 Maintainer

AlCalzone Dec 18, 2023 Maintainer

dwmw2 Dec 18, 2023 Author

AlCalzone Dec 18, 2023 Maintainer

dwmw2 Dec 20, 2023 Author

AlCalzone Dec 20, 2023 Maintainer

dwmw2
Dec 12, 2023

Replies: 3 comments 6 replies

zwave-js-bot
Dec 12, 2023
Collaborator

dwmw2
Dec 14, 2023
Author

AlCalzone
Dec 14, 2023
Maintainer

AlCalzone Dec 18, 2023
Maintainer

dwmw2 Dec 18, 2023
Author

AlCalzone Dec 18, 2023
Maintainer

dwmw2 Dec 20, 2023
Author

AlCalzone Dec 20, 2023
Maintainer