Hi all,
i have got a problem, and i wrote an email to @chris, but he is busy an i need assistance to solve the issue.
So im using Danalock V3 with openhab and ZWAVE beginning with March. Everything was OK.
Now, i installed the new firmware for the lock, and after that i cant add it to Openhab2.
Lock is hard-reseted, Zwave controller is hard reseted, i installed a fresh Openhab2 (version snapshot 1725)
and i tried to add the lock .
i got all the time the same message in the log:
2019-10-16 16:14:53.843 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:CONTROLLER:node2’ to inbox.
2019-10-16 16:15:00.049 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 2: Using Scheme0 Network Key for Key Exchange since we are in inclusion mode.
2019-10-16 16:15:00.256 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: SECURITY_INC State=COMPLETE
2019-10-16 16:15:00.896 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 010E:0009:0001::1.2
2019-10-16 16:15:05.757 [INFO ] [mmandclass.ZWaveDoorLockCommandClass] - NODE 2: Door-Lock config report - timeoutEnabled=false timeoutMinutes=254, timeoutSeconds=254
2019-10-16 16:15:06.609 [INFO ] [mmandclass.ZWaveDoorLockCommandClass] - NODE 2: Door-Lock config report - timeoutEnabled=false timeoutMinutes=254, timeoutSeconds=254
is there a possibility, that we have got a database problem because of new firmware?
Build 1725 is a snapshot, correct? Z-Wave binding os broken in the latest snapshots for many people. Does Milestone 3 not contain all the entries you need?
I think there has been some GitHub activity troubleshooting the bining but I would expect it coud take a few days before a solution is verified.