[Z-Wave] Danalock V3 not recognized

Wawszczak · August 19, 2021, 8:13pm

Dear All,

I am using OpenHab version 3.1.
Z-Wave Stick is Aeotec Gen7.
I have done discovery and inclusion, but It has been detected as generic thing zwave:device:zwawe-hub:node2
Inclusion Mode : High Power
Secure Inclusion Mode: Entry Control Devices
Default Wakeup time: 3600
Network Security key is configured to proposed value.

Logs:
2021-08-19 21:38:16.839 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:zwawe-hub:node2’ to inbox.
2021-08-19 21:38:21.960 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-19 21:38:21.968 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-19 21:38:21.969 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2021-08-19 21:38:37.044 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: SECURITY_INC State=FAILED, Reason=GET_SCHEME
2021-08-19 21:38:37.172 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-19 21:38:37.202 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-19 21:38:37.203 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = – (0xa8)
2021-08-19 21:39:17.748 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.

Last three messages are repeating in the logs.

mstormi · August 19, 2021, 8:39pm

Start your post by providing comprehensive information please.
Minimum would be the OH version you run and how inclusion was done (secure?)

How to ask a good question / Help Us Help You - Tutorials & Examples - openHAB Community

apella12 · August 19, 2021, 10:12pm

As Marcus notes, could be anything. I did look up the lock in the Zwave database, so it is probably there (if your device numbers match). Might want to review that information vs the UI thing page. One quirk: looks like you need to pair with bluetooth first. Did you do that?. As battery device it is probably not fully included. As security device that needs to happen quickly, etc. etc. Need more info

Bob

edit: OpenSmartHouse Z-Wave Device Database

chris · August 19, 2021, 11:47pm

The log shows that the device failed to securely join. You must now reset the device and redo the secure inclusion. You also need to ensure that the inclusion is done with the stick in the PC and not by taking the stick to the device as that will not work for security enabled devices.

Wawszczak · August 20, 2021, 11:16am

Dear All, Thank you for your replies.

@mstormi - I am really sorry for violence of Posting Rules.
I have edited original post with addition of description of my environment.

@apella12 - how can I check my device numbers?
I have missed default label during thing addition and overwritten it with my own Label…

Wawszczak · August 20, 2021, 11:50am

@chris
I have done following:

Exclude device from network via OpenHab
Delete thing from openhab
reset device to factory settings (push button ten times, red diode has turned on)
init inclusion mode (push button for five seconds, green diode has turned on)
discover device in openhab
add device to open hab

Unfortunatelly it is still not working, but I know now, that device numbers are not visible to OpenHab.
Default Label is “Z-Wave Node 002”

Moreover, i have found additional entry in the logs:
2021-08-20 13:19:57.984 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.

Complete Logs:

2021-08-20 13:18:45.138 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:18:45.148 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:18:45.150 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:18:51.968 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:18:51.979 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:18:51.981 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:18:59.976 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:18:59.985 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:18:59.985 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:19:04.969 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: SECURITY_INC State=FAILED, Reason=SECURE_PING
2021-08-20 13:19:06.318 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:06.328 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:06.330 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:19:13.829 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:13.838 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:13.839 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:19:22.954 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:22.962 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:22.963 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:19:35.031 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:35.039 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:35.040 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:19:52.981 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:52.989 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:52.990 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:19:57.984 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.
2021-08-20 13:19:58.121 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:58.127 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:19:58.128 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:20:05.727 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:20:05.736 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:20:05.737 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:20:14.762 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:20:14.773 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:20:14.774 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:20:40.339 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:20:40.351 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:20:40.352 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:21:05.880 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:21:05.890 [WARN ] [.serialmessage.ZWaveCommandProcessor] - SerialMessage class null is not implemented!
2021-08-20 13:21:05.891 [WARN ] [ve.internal.protocol.ZWaveController] - TODO: Implement processing of Request Message = -- (0xa8)
2021-08-20 13:43:18.107 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! Manufacturer data not known.
2021-08-20 13:43:18.126 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:zwawe-hub:node2' to inbox.

apella12 · August 20, 2021, 1:53pm

Probably not the issue, but the device numbers I’m talking about are shown here

Sometimes there is a new version that needs to be added.

You need to look at the link I posted above for two reasons

Check the device numbers match
Your inclusion/exclusion description does not align with the instructions (Bluetooth app first?)

Bob

Wawszczak · August 20, 2021, 1:58pm

Dear @apella12 ,

Thank you for hint.
I have verified manufacturerId and manufacturerRef are not visible:

regarding app, i don’t want to have Bluetooth app, only control from OpenHab. Documentation states, that when I do pair with BT app, I will lost further access to Bluetooth.
Of course, I will retry with BT app, when I came back home.
Stanislaw

chris · August 20, 2021, 8:14pm

The problem is that the stick is a new stick and isn’t compatible with the binding.

Wawszczak · August 20, 2021, 8:25pm

@Chris,

Thank you for explanation.
I thought it is backward compatible, when I have bought it, there were no Gen5+ available with shipment to Poland unfortunatelly.
How can I help you with adding support for Gen7 ?
I have created previously binding for Modbus device, so I have some experience with OpenHab bindings.

Stanislaw