You simply won’t see any channels until the database entry is active; there’s no way around that.
Thanks. I was hoping that since I got it to go online in a secure mode that there would be enough functionality to work. Alas, I miss the days of smacking the radio/tv on the top to make it work.
Eddie
The z-wave database entry for this lock has been approved now. Though the lock still shows up as online but it still says it is an unknown device. The device info says that it may take awhile for the device to do it’s discovery process and may need to be woken up several times. How might one wake up the device? I can change/add lock codes but don’t know how to make it do the rest of the discovery process. Any suggestions? Do I need to delete the lock and re-scan for it?
Eddie
I’m not sure about locks, but that is the normal procedure to pick up DB changes with other devices. (after of course either OH3 or the z-wave binding is updated to the snapshot version that includes the change)
Ok deleting and re adding didn’t help.
The data base entry says
Last Approval 2022-08-08 23:29:03 OH-SNAPSHOT
So how do I tell if OH has the mod rolled in? Where do I find instructions for updating my OH? I have not found my way around in OH or in the documentation. Though I’m a retired programmer and consider myself technically competent, this is a new world for me. I know a jar has something to do with Java but I’ve never been there.
Also, this is a new installation so it would not be a big deal to restart from another new install.
Thanks,
Eddie
I usually just install the snapshot zwave binding to minimize chances of picking up a bug from the other changes in the OH distribution. The latest zwave binding is here. The update procedure for that is
However, you should be able to check what zwave binding you have with
bundle:list |grep ZWave in the Openhab-cli console also. It looks like it needs to be dated Aug 9 something
Bob
edit: again still not sure about locks. May actually have to exclude then reinclude to get the security key correct, but try the easier way first.
Wow!
I finally figured out how to get to the openhab cli. I was expecting to be in a nice command line window but “Toto, I’ve a feeling we’re not in Kansas anymore.”
Anyway, I managed the feature:install step. Then using shell:ls and shell:cd I cannot find an openhab/addons directory. And I don’t know how to copy from the Jenkins zwave site to anywhere in this environment. I tried poking around in the other directories but don’t know what I’m looking for.
I tried doing the
bundle:list |grep zwave
Or is grep case sensitive. I just noticed i don’t have the same case as above.
Any pointers would be appreciated.
On a side note I was unable to simply connect my monitor and keyboard to the raspberry and login. It never gave me any command prompt. I think I remember logging in as admin on my previous installation attempt. Did I forget to enable something during installation?
Thanks,
Eddie
Sorry for being so dense but I do feel like I been dropped into Oz.
I’ll try, but there is documentation of openhabian 
Probably most helpful is if samba was setup by openhabian. I’m basically a windows person, so how to do some of this from the command line of the Rpi would be tough for me to explain since I don’t use that. Probably one of the linux people can help…
I have the key OH folders visible via the Samba setup on my windows machine and simply download the jar to my downloads folder and drop in the OH via file explorer
the folder is here(I believe this is a symlink location, but it should work.
edit: ZWave is case sensitive. I did it wrong the first time too
Oh. that is part of it. When I login to openhab it puts me in that home directory. I didn’t know I needed to be looking in /srv from the root dir.
I still need to figure out how to copy the file over there. I can ssh into the raspberry so that may be the easiest way. I’ll let you know.
As for documentation it is written clearly for someone who knows what they are doing. if one is unfamiliar with the software environment and/or tools and the usage environment (home automation, in this case) then things are not so clear. It could as well be written in another language. That has always been what I have always found when I move into something new. That’s why the newbies frustrate the Old-hands so. I try to read the docs because I’ve been on the other side but it is a slow process coming up to speed.
I really do appreciate your help.
Eddie
1 Like
I think I’m almost there…
I got the file copied over and deleted and reloaded the lock thing and zwave bridge and re-scanned but I’m seeing the same unknown device for the lock thing.
The bundle:list command gives:
266 │ Active │ 80 │ 3.3.0 │ openHAB Add-ons :: Bundles :: ZWave Binding
269 │ Active │ 80 │ 3.4.0.202208090348 │ openHAB Add-ons :: Bundles :: ZWave Binding
It looks like I have two zwave bindings? The second one has the date I’m looking for.
What did I miss deleting?
Eddie
Yes. Needed to uninstall zwave from the ui first. The safest is to remove the 3.4 snapshot and uninstall from the ui. Then readd the 3.4. You may need to restart oh if the zwave things do not come online. Then delete (Not exclude) the thing and scan again. See if that works.
I had just deleted the Things. I went back and deleted and reinstalled the things and the binding and now it recognizes the Device. I’m thinking all is good. I’m now going to try to add as equipment and see if I can control it.
baby steps…
Thanks again for all your help,
Eddie
Sounds good. If things go astray get to one zwave binding, if you still have both.
I now have the Lock thing recognized and I can see 6 channels available. On the channels page of the lock thing I select all and do Add Equipment To Model. An item for each channel is created for that channel.
I go to Pages Overview page and add a toggle card and on the toggle card edit page select the door lock Item that was created. When I go to run mode or go to that page it does not work. I don’t know how to tell what is not working.
I do have a wifi light switch working on this page. Though that is much simpler I think my process is right.
I haven’t found any documentation that is helpful here. Can anyone give me any insight into what to look for.
Thanks,
Eddie
Ok Back to the openhab-cli. This time log:set DEBUG org.openhab.binding.zwave. try the switch both from the toggle and from the list of items. Then set the log back to INFO. (I do not think these are case sensitive). You’ll see if the command is being sent and if the Node is responding.
Edit: could also try opening the lock
Ok. Thanks. I’ll give that a shot. I’m certain it is something dumb I’m doing but I can’t see it. One thing that puzzles me is that when it creates the lock channel item it is a point and not a switch.I’m not sure what that means.
The lock works manually from the keypad so it is “functioning” and I can set lock codes from the thing so their is some communication. But don’t see it responding to anything else remotely.
Eddie
As mentioned earlier, I don’t have a zwave lock How far away is the lock from the controller, How close is it to your nearest powered Zwave node? The zwave debug file will provide if communication is happening.
Actually I have not used the sematic model either, but I do not think “point” and “switch” are mutually exclusive. The channel is set up with the binding as ON_OFF
I recently moved and I’m adding a security system. I started to use openHab a year or so ago but got interrupted with the move.
The physical lock is sitting on the desk with the openHabian raspberry pi with z stick. Less than a foot separation.
This is my first zwave node. I’ve setup wifi nodes with no trouble. I’m am getting too many wifi devices so I decided to expand to zwave and add a couple of locks and some motion detectors. Next is a zigbee momentary switch for my driveway gate opener. It will use a 5 year old digi xstick for the coordinator which I used it on a old system so I’m expecting problems with it as well. But just one step at a time and those are apparently small steps.
I deleted the thing and items once again and also did a factory reset on the KS lock. Rebuilt the thing and item. No perceptible change.
I did notice that I still have two zwave bindings.
269 │ Active │ 80 │ 3.4.0.202208090348 │ openHAB Add-ons :: Bundles :: ZWave Binding
270 │ Active │ 80 │ 3.3.0 │ openHAB Add-ons :: Bundles :: ZWave Binding
Looks like one for version 3.4 and one for 3.3. The 3.4 is the new one I just added.
Here is the debug output from doing a couple of open/close from the item:
Nothing jumps out at me but then I don’t have any experience looking at this stuff.
==> /var/log/openhab/events.log <==
2022-08-13 18:57:52.489 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' received command OFF
2022-08-13 18:57:52.491 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' predicted to become OFF
2022-08-13 18:57:52.498 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' changed from ON to OFF
==> /var/log/openhab/openhab.log <==
2022-08-13 18:57:54.009 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling...
2022-08-13 18:57:54.010 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling deferred until initialisation complete
2022-08-13 18:57:54.505 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:cd2ff9fc7d:node4:lock_door --> ON [OnOffType]
2022-08-13 18:57:54.506 [DEBUG] [mmandclass.ZWaveDoorLockCommandClass] - NODE 4: Creating new message for application command DOORLOCK_SET, value 255
2022-08-13 18:57:54.507 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY required on COMMAND_CLASS_DOOR_LOCK
2022-08-13 18:57:54.508 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_DOOR_LOCK is required to be secured
2022-08-13 18:57:54.509 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 304 priority from Get to Immediate
2022-08-13 18:57:54.510 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2022-08-13 18:57:54.511 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original
2022-08-13 18:57:54.512 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 304 to queue - size 2
2022-08-13 18:57:54.513 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:54.514 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling initialised at 86400 seconds - start in 1500 milliseconds.
==> /var/log/openhab/events.log <==
2022-08-13 18:57:54.484 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' received command ON
2022-08-13 18:57:54.493 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' predicted to become ON
2022-08-13 18:57:54.496 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' changed from OFF to ON
==> /var/log/openhab/openhab.log <==
2022-08-13 18:57:56.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling...
2022-08-13 18:57:56.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling deferred until initialisation complete
2022-08-13 18:57:56.321 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:cd2ff9fc7d:node4:lock_door --> OFF [OnOffType]
2022-08-13 18:57:56.321 [DEBUG] [mmandclass.ZWaveDoorLockCommandClass] - NODE 4: Creating new message for application command DOORLOCK_SET, value 0
2022-08-13 18:57:56.322 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY required on COMMAND_CLASS_DOOR_LOCK
2022-08-13 18:57:56.323 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_DOOR_LOCK is required to be secured
2022-08-13 18:57:56.324 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 305 priority from Get to Immediate
2022-08-13 18:57:56.325 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue
2022-08-13 18:57:56.326 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original
2022-08-13 18:57:56.326 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 305 to queue - size 2
2022-08-13 18:57:56.327 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:56.328 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling initialised at 86400 seconds - start in 1500 milliseconds.
2022-08-13 18:57:56.944 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 4: TID 300: Timeout at state WAIT_DATA. 3 retries remaining.
2022-08-13 18:57:56.945 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 300: Transaction CANCELLED
2022-08-13 18:57:56.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2022-08-13 18:57:56.946 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: notifyTransactionResponse TID:300 CANCELLED
2022-08-13 18:57:56.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-08-13 18:57:56.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 300: Transaction event listener: DONE: CANCELLED -> WAIT_DATA
2022-08-13 18:57:56.949 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node Init response (1) org.openhab.binding.zwave.internal.protocol.ZWaveTransactionResponse@62f46b5b
2022-08-13 18:57:56.949 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: isNonceAvailable = null
2022-08-13 18:57:56.949 [DEBUG] [andclass.impl.CommandClassSecurityV1] - Creating command message SECURITY_NONCE_GET version 1
2022-08-13 18:57:56.949 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: No data from device, but it was ACK'd. Possibly not supported? (Try 1)
2022-08-13 18:57:56.950 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 04 02 98 40 25 27 39
2022-08-13 18:57:56.951 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 4: Sending REQUEST Message = 01 09 00 13 04 02 98 40 25 27 39
2022-08-13 18:57:56.951 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2022-08-13 18:57:56.952 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.952 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2022-08-13 18:57:56.953 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2022-08-13 18:57:56.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2022-08-13 18:57:56.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2022-08-13 18:57:56.955 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:56.955 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:56.959 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2022-08-13 18:57:56.960 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2022-08-13 18:57:56.961 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2022-08-13 18:57:56.961 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2022-08-13 18:57:56.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 306: [WAIT_RESPONSE] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:56.962 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01
2022-08-13 18:57:56.963 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: sentData successfully placed on stack.
2022-08-13 18:57:56.963 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 306: Advanced to WAIT_REQUEST
2022-08-13 18:57:56.963 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: TID 306: Transaction not completed
2022-08-13 18:57:56.964 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:56.964 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
==> /var/log/openhab/events.log <==
2022-08-13 18:57:56.308 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' received command OFF
2022-08-13 18:57:56.309 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' predicted to become OFF
2022-08-13 18:57:56.312 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode004Kwikset620Deadboltvariant_DoorLock' changed from ON to OFF
==> /var/log/openhab/openhab.log <==
2022-08-13 18:57:57.828 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling...
2022-08-13 18:57:57.829 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Polling deferred until initialisation complete
2022-08-13 18:57:58.190 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 27 00 00 7C B0
2022-08-13 18:57:58.191 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=39, payload=27 00 00 7C
2022-08-13 18:57:58.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=39, payload=27 00 00 7C
2022-08-13 18:57:58.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 306: [WAIT_REQUEST] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:58.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2022-08-13 18:57:58.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 306: [WAIT_REQUEST] priority=High, requiresResponse=true, callback: 39
2022-08-13 18:57:58.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 306: (Callback 39)
2022-08-13 18:57:58.194 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2022-08-13 18:57:58.194 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 306: callback 39
2022-08-13 18:57:58.195 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=39, payload=27 00 00 7C
2022-08-13 18:57:58.195 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: SendData Request. CallBack ID = 39, Status = Transmission complete and ACK received(0)
2022-08-13 18:57:58.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 306: Advanced to WAIT_DATA
2022-08-13 18:57:58.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: TID 306: Transaction not completed
2022-08-13 18:57:58.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:58.197 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2022-08-13 18:57:58.205 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 04 0A 98 80 A5 3C 22 E3 09 CC 83 B3 50
2022-08-13 18:57:58.206 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 98 80 A5 3C 22 E3 09 CC 83 B3
2022-08-13 18:57:58.207 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 0A 98 80 A5 3C 22 E3 09 CC 83 B3
2022-08-13 18:57:58.208 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-08-13 18:57:58.208 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DYNAMIC_VALUES)
2022-08-13 18:57:58.209 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SECURITY, endpoint 0
2022-08-13 18:57:58.209 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY check internal
2022-08-13 18:57:58.209 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SECURITY V1 SECURITY_NONCE_REPORT
2022-08-13 18:57:58.210 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: NONCE Received start...
2022-08-13 18:57:58.210 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: NONCE Received start null
2022-08-13 18:57:58.211 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: NONCE Received ZWaveNonce [nonceBytes=(A5 3C 22 E3 09 CC 83 B3 ), timer=146591, valid=true]
2022-08-13 18:57:58.211 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-08-13 18:57:58.211 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@18e5c2e6.
2022-08-13 18:57:58.212 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@18e5c2e6.
2022-08-13 18:57:58.212 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: notifyTransactionResponse TID:306 DONE
2022-08-13 18:57:58.213 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2022-08-13 18:57:58.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2022-08-13 18:57:58.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-08-13 18:57:58.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-13 18:57:58.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-08-13 18:57:58.216 [DEBUG] [andclass.impl.CommandClassSecurityV1] - Creating command message SECURITY_MESSAGE_ENCAPSULATION version 1
2022-08-13 18:57:58.218 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: SECURITY_TXD 62 01 FF
2022-08-13 18:57:58.220 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 1E 00 13 04 17 98 81 78 09 61 F5 59 51 E8 66 31 C8 8E C7 A5
Here are the thing properties: I think it says it is secure
zwave_class_basic BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic GENERIC_TYPE_ENTRY_CONTROL
zwave_frequent true
zwave_neighbours 1
modelId Kwikset 620
zwave_listening false
zwave_plus_devicetype NODE_TYPE_ZWAVEPLUS_NODE
zwave_version 7.20
manufacturerId 0090
manufacturerRef 0811:23A8
dbReference 1513
zwave_deviceid 9128
zwave_nodeid 4
defaultAssociations 1
vendor Black & Decker
zwave_routing true
zwave_plus_roletype ROLE_TYPE_SLAVE_SLEEPING_LISTENING
zwave_beaming true
zwave_secure true
zwave_class_specific SPECIFIC_TYPE_DOOR_LOCK
zwave_devicetype 2065
zwave_manufacturer 144
All help is appreciated…
Eddie
Having two binding processes cannot be good and you need to eliminate that variable. At this point I would delete the 3.4 from the addons, then use openhabian-config to update to the 3.4 milestone 1. That will have a zwave binding with the lock. IMO it is better to update to the milestones (after a few days) than wait for releases, despite the warnings. If something goes astray you can find the problem in the recent posts. If you wait 6 months for the release, the problems that happened in earlier months are harder to find.
You probably need to run the Debug longer, it seems like it was cut off. Also there is a zwave debug viewer here. It makes it easier to understand, at least at a high level. This is what I got from yours (events files are not really needed).
