Zwave - Yale YRD220 Lock

z-wave
Tags: #<Tag:0x00007f51ea7c4988>

(Chris Jackson) #41

Again, please provide the debug log - without this I’ve no way to see what is happening - sorry.


(Brent) #42

What kind of logs do you want? Is there a specific log file or are the logs from the openHAB 2 Log Viewer good enough.


(Chris Jackson) #43

The OH logs are exactly what I’m after - you just need to enable debug logging for the zwave binding.


(Brent) #44

Ok, so how do I enable debug logging for the z-wave binding?


(Chris Jackson) #45

Check out the docs here.


(Brent) #49

I rebooted the openHAB machine and then enabled debugging again. I then used a user code after the device said that it had updated.


(Chris Jackson) #52

So, the log is a restart, so it loads all the codes, and everything looks like it’s probably ok. Some codes have codes set, and others are unoccupied. This lock has 250 codes, which takes ages to download - I need to somehow restrict this as I’m sure most people aren’t using more than 10 or 20.

I’m not really sure what I’m looking for as you don’t appear to have changed anything in this log (although it’s a bit hard to tell due to the length so please correct me if that’s wrong). From the log, everything looks fine and I can’t really see how all codes and all configuration should be reset. Unless you have a log of that event (I guess not) I’m not sure I can say much - sorry.

One question though - are you using HABmin or PaperUI to configure the system?

Also, regarding the initial question, are you able to provide a short log showing the alarm message when the door is opened so I can code up this notification.


(Brent) #53

I’m using Paper UI to add the things and items, as well as to change any other configurations that are present within Paper UI. I have used habmin to modify some of the items to add tags so that they will work with Alexa.

The odd thing is, the alarm isn’t always updating either. I’m not exactly sure what’s causing that problem.

I will try to get you the relevant logs, but I’m currently fighting off a nasty cold, so I’m going to get some rest right now.


(Brent) #54

I was using a newer snapshot (2.3.0.201803171831) than the latest stable snapshot (2.3.0.201803161151). I am going to test with the latest stable snapshot from now on. I haven’t tested it yet though.


(Scott Rushworth) #55

If you don’t use the development version of the binding, then your lock will not work. The current version of the development binding is 2.3.0.201803171831.


(Brent) #56

Do you know where the best link to get the development version is?


(Scott Rushworth) #57

First post…


(Brent) #58

Ok, I have done a hard reset of all of my devices such as my lock, including my z-wave controller, and excluded everything. Then I added the z-wave devices back using Paper UI. I added one user code to the lock and then used it.

Here are the logs of me using a user code to unlock the lock:

2018-03-19 01:14:50.904 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 09 02 98 40 20 

2018-03-19 01:14:50.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 02 98 40 

==> /var/log/openhab2/events.log <==

2018-03-19 01:14:50.915 [vent.ItemStateChangedEvent] - zwave_serial_zstick_bbfdf75b_serial_sof changed from 3007 to 3008

==> /var/log/openhab2/openhab.log <==

2018-03-19 01:14:50.913 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 02 98 40 

2018-03-19 01:14:50.920 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 02 98 40 

2018-03-19 01:14:50.922 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2018-03-19 01:14:50.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Application Command Request (ALIVE:DONE)

2018-03-19 01:14:50.928 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false

2018-03-19 01:14:50.932 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Incoming command class COMMAND_CLASS_SECURITY, endpoint 0

2018-03-19 01:14:50.935 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: SECURITY check internal

2018-03-19 01:14:50.938 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 9: Received COMMAND_CLASS_SECURITY V1 SECURITY_NONCE_GET

2018-03-19 01:14:50.941 [DEBUG] [andclass.impl.CommandClassSecurityV1] - Creating command message SECURITY_NONCE_REPORT version 1

2018-03-19 01:14:50.944 [DEBUG] [ommandClassTransactionPayloadBuilder] - At build null

2018-03-19 01:14:50.948 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Added to secure queue - size 1

2018-03-19 01:14:50.951 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Commands processed 1.

2018-03-19 01:14:50.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1971f0e.

2018-03-19 01:14:50.956 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-03-19 01:14:50.959 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-03-19 01:14:50.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-03-19 01:14:50.965 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start

2018-03-19 01:14:51.017 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from secureQueue

2018-03-19 01:14:51.021 [DEBUG] [nal.protocol.ZWaveTransactionManager] - getTransactionToSend 6

2018-03-19 01:14:51.026 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 13 09 0A 98 80 FE 25 5D EF CA C0 80 06 25 F3 D5 

2018-03-19 01:14:51.030 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 9: Sending REQUEST Message = 01 11 00 13 09 0A 98 80 FE 25 5D EF CA C0 80 06 25 F3 D5 

2018-03-19 01:14:51.033 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT

2018-03-19 01:14:51.037 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: Transaction Start type SendData 

2018-03-19 01:14:51.039 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 1028: [WAIT_RESPONSE] requiresResponse=true callback: 243

2018-03-19 01:14:51.041 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd class: null

2018-03-19 01:14:51.039 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06

2018-03-19 01:14:51.044 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: expected cmd: 0

2018-03-19 01:14:51.045 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-03-19 01:14:51.045 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage Transactions outstanding: 1

2018-03-19 01:14:51.046 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-03-19 01:14:51.048 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Mon Mar 19 01:14:53 EDT 2018 - 2000ms

==> /var/log/openhab2/events.log <==

2018-03-19 01:14:51.047 [vent.ItemStateChangedEvent] - zwave_serial_zstick_bbfdf75b_serial_ack changed from 1019 to 1020

==> /var/log/openhab2/openhab.log <==

2018-03-19 01:14:51.049 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage lastTransaction: TID 1028: [WAIT_RESPONSE] requiresResponse=true callback: 243

2018-03-19 01:14:51.049 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 

2018-03-19 01:14:51.054 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 1<>127 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-03-19 01:14:51.056 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-03-19 01:14:51.050 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer

==> /var/log/openhab2/events.log <==

2018-03-19 01:14:51.059 [vent.ItemStateChangedEvent] - zwave_serial_zstick_bbfdf75b_serial_sof changed from 3008 to 3009

==> /var/log/openhab2/openhab.log <==

2018-03-19 01:14:51.062 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Start transaction timer to Mon Mar 19 01:14:53 EDT 2018 - 1986ms

2018-03-19 01:14:51.063 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (1): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-03-19 01:14:51.065 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1028: [WAIT_RESPONSE] requiresResponse=true callback: 243

2018-03-19 01:14:51.066 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 F3 00 00 02 1A 

2018-03-19 01:14:51.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK

2018-03-19 01:14:51.068 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 1<>127 : Message: class=SendData[19], type=Request[0], dest=0, callback=243, payload=F3 00 00 02 

2018-03-19 01:14:51.071 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=SendData[19], type=Request[0], dest=0, callback=243, payload=F3 00 00 02 

2018-03-19 01:14:51.072 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

==> /var/log/openhab2/events.log <==

2018-03-19 01:14:51.077 [vent.ItemStateChangedEvent] - zwave_serial_zstick_bbfdf75b_serial_sof changed from 3009 to 3010

==> /var/log/openhab2/openhab.log <==

2018-03-19 01:14:51.081 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1028: [WAIT_RESPONSE] requiresResponse=true callback: 243

2018-03-19 01:14:51.083 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-03-19 01:14:51.085 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1028: [WAIT_RESPONSE] requiresResponse=true callback: 243

2018-03-19 01:14:51.087 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-03-19 01:14:51.089 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: sentData successfully placed on stack.

2018-03-19 01:14:51.093 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 28 00 04 00 09 22 98 81 D9 9B 2C A9 F1 A4 A5 18 30 55 F5 75 66 17 BB 98 A8 39 81 F0 D6 99 29 FE 49 E2 EE 8D A3 E7 C9 3B 7F 

==> /var/log/openhab2/events.log <==

2018-03-19 01:14:51.096 [vent.ItemStateChangedEvent] - zwave_serial_zstick_bbfdf75b_serial_sof changed from 3010 to 3011

==> /var/log/openhab2/openhab.log <==

2018-03-19 01:14:51.098 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance ST: WAIT_RESPONSE

2018-03-19 01:14:51.100 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance WT: null {}

2018-03-19 01:14:51.101 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 1<>127 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 22 98 81 D9 9B 2C A9 F1 A4 A5 18 30 55 F5 75 66 17 BB 98 A8 39 81 F0 D6 99 29 FE 49 E2 EE 8D A3 E7 C9 3B 

2018-03-19 01:14:51.102 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance RX: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-03-19 01:14:51.103 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 22 98 81 D9 9B 2C A9 F1 A4 A5 18 30 55 F5 75 66 17 BB 98 A8 39 81 F0 D6 99 29 FE 49 E2 EE 8D A3 E7 C9 3B 

2018-03-19 01:14:51.105 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance TO: WAIT_REQUEST

2018-03-19 01:14:51.108 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 1028: Advanced to WAIT_REQUEST

2018-03-19 01:14:51.109 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: TID 1028: Transaction not completed

2018-03-19 01:14:51.111 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (1): Message: class=SendData[19], type=Request[0], dest=0, callback=243, payload=F3 00 00 02 

2018-03-19 01:14:51.113 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 1028: [WAIT_REQUEST] requiresResponse=true callback: 243

2018-03-19 01:14:51.115 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-03-19 01:14:51.118 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 1028: [WAIT_REQUEST] requiresResponse=true callback: 243

2018-03-19 01:14:51.120 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 1028: (Callback 243)

2018-03-19 01:14:51.122 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!

2018-03-19 01:14:51.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 1028: callback 243

2018-03-19 01:14:51.125 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=243, payload=F3 00 00 02 

2018-03-19 01:14:51.127 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 9: SendData Request. CallBack ID = 243, Status = Transmission complete and ACK received(0)

2018-03-19 01:14:51.129 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false

2018-03-19 01:14:51.131 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: Transaction COMPLETED

2018-03-19 01:14:51.132 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance ST: DONE

2018-03-19 01:14:51.134 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance WT: null {}

2018-03-19 01:14:51.136 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance RX: Message: class=SendData[19], type=Request[0], dest=0, callback=243, payload=F3 00 00 02 

2018-03-19 01:14:51.138 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 1028: TransactionAdvance TO: DONE

2018-03-19 01:14:51.140 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Response processed after 103ms

2018-03-19 01:14:51.141 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: TID 1028: Transaction completed

2018-03-19 01:14:51.143 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: notifyTransactionResponse TID:1028 DONE

2018-03-19 01:14:51.145 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent

2018-03-19 01:14:51.147 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2018-03-19 01:14:51.150 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 22 98 81 D9 9B 2C A9 F1 A4 A5 18 30 55 F5 75 66 17 BB 98 A8 39 81 F0 D6 99 29 FE 49 E2 EE 8D A3 E7 C9 3B 

2018-03-19 01:14:51.151 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2018-03-19 01:14:51.153 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Application Command Request (ALIVE:DONE)

2018-03-19 01:14:51.155 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false

2018-03-19 01:14:51.157 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Decapsulating COMMAND_CLASS_SECURITY

2018-03-19 01:14:51.162 [DEBUG] [mmandclass.ZWaveSecurityCommandClass] - NODE 9: SECURITY_RXD 71 05 13 01 00 FF 06 06 04 63 03 01 01 00 

2018-03-19 01:14:51.163 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Incoming command class COMMAND_CLASS_ALARM, endpoint 0

2018-03-19 01:14:51.165 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 9: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT

2018-03-19 01:14:51.166 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: NOTIFICATION report - 19 = 1, event=6, status=255, plen=4

2018-03-19 01:14:51.167 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Alarm Type = ACCESS_CONTROL (19)

2018-03-19 01:14:51.169 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent

2018-03-19 01:14:51.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveAlarmValueEvent

2018-03-19 01:14:51.172 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255

2018-03-19 01:14:51.176 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

2018-03-19 01:14:51.178 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 6, type OnOffType

2018-03-19 01:14:51.180 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 6, channel alarm_access is not implemented.

2018-03-19 01:14:51.182 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

2018-03-19 01:14:51.183 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 6, type OnOffType

2018-03-19 01:14:51.185 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

2018-03-19 01:14:51.187 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 6, type StringType

2018-03-19 01:14:51.189 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:bbfdf75b:node9:alarm_raw to {"notification":"ACCESS_CONTROL__KEYPAD_UNLOCK","code":"99","type":"ACCESS_CONTROL","event":"6","status":"255"} [StringType]

2018-03-19 01:14:51.196 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

==> /var/log/openhab2/events.log <==

2018-03-19 01:14:51.199 [vent.ItemStateChangedEvent] - zwave_device_bbfdf75b_node9_alarm_raw changed from {"notification":"ACCESS_CONTROL__MANUAL_LOCK","type":"ACCESS_CONTROL","event":"1","status":"255"} to {"notification":"ACCESS_CONTROL__KEYPAD_UNLOCK","code":"99","type":"ACCESS_CONTROL","event":"6","status":"255"}

==> /var/log/openhab2/openhab.log <==

2018-03-19 01:14:51.199 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 6, type OnOffType

2018-03-19 01:14:51.201 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 6, channel alarm_general is not implemented.

2018-03-19 01:14:51.203 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Commands processed 1.

2018-03-19 01:14:51.204 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@de4324.

2018-03-19 01:14:51.206 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-03-19 01:14:51.207 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-03-19 01:14:51.209 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-03-19 01:14:51.210 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start

2018-03-19 01:14:51.211 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.213 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.214 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.216 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.217 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.218 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.220 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.221 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.223 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.224 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.225 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.227 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.228 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.230 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.231 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.232 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.234 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false

2018-03-19 01:14:51.235 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!

2018-03-19 01:14:51.237 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue

2018-03-19 01:14:51.238 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing

2018-03-19 01:14:51.239 [DEBUG] [nal.protocol.ZWaveTransactionManager] - STOP transaction timer

It seems to only show: “code”:“99” for all user codes, instead of the code slot that was actually used.


(Brent) #59

I’m not going to try to configure the lock with openHAB anymore. It just seems to screw everything up. I will just manually configure it at the door itself from now on.

I would really like to be able to have it report the user code slots that are used though.


(Chris Jackson) #60

There shouldn’t be any issue viewing, or setting the user codes as far as I know. I would suggest to use HABmin though rather than PaperUI.

If you have problems, then please provide a log - otherwise it wont get fixed.


(omatzyo) #61

@chris, he is having the same problem that we were discussing last month where “alarm level” is reporting the user code number in version 4. When we spoke last you were considering adding the .level to the alarm_raw report.


(Chris Jackson) #62

Yes - that’s what I am doing, but I just wanted to get a log of the event so that I can use this to produce a test case. Your logs that were provided previously were redacted.


(Brent) #63

I have finally converted all of my scripts away from SmartThings over to openHAB. They always seem to take about 10 seconds to run the first time they run after they are refreshed, but after the first time they seem to run immediately.

If you are able to update this to allow me to see the user code slot number that is being used when unlocking my lock from the keypad: when I update the z-wave addon file and restart the service, will I have to reinstall my z-wave items? I only ask because, when I added the z-wave addon the first time, none of my z-wave things would work until I removed them and added them back. I guess that would not be too terrible even if I have to do that, but I am just curious if it is supposed to be like that or not.

Also, where would you say is the best place to look to see the current changes to the z-wave binding?

I am sorry if these questions are off topic. I just want to keep up to date on this particular issue. And if you need anything else from me for this issue, please let me know.


(Misha Hill) #64

Just an FYI for others, I have had three of these locks (the 220) for five years, and two have had their touchscreens fail. They still work when activated from openHAB, and even light up for the remote state-change animations, but they don’t respond to being touched. Both that failed are on the same door – when the first one went out about a year ago, I replaced it with one that had been taken out of service a year earlier, and now it has failed in the same way. The door in question is an outer door, and gets little use. It does get direct sunlight. The one that remains working is inside a vestibule.


(Scott Rushworth) #65

This is a known issue.

When changing to the development binding, you would only have needed to delete the Things to get the updated thingTypes. Depending on what gets changed to correct the codes, you may need to delete the Thing for the lock, but that’s unlikely. Have you tried with the latest version of the dev binding?

It’s currently in the development branch here… https://github.com/openhab/org.openhab.binding.zwave/tree/development.