Check if your device has the complete model number (including the frequency letter) printed on it, or on the retail box, and that will tell you which frequency it uses.
Regarding the Danalock, I’m pretty sure they also have a few variants for different country regions.
it states that lock in inclusion mode will be flashing green for 30 secs. Also you should not try again after a this because inclusion may still be processing for next 30 secs or more.
@mjeshurun I have now checked the frequency of the stick as well as the Danalock lock. Both devices transmit on the same frequency and are EU models. So the problem does not seem to lie here.
I give up. I have now tried everything possible, the Danalock lock is not found.
Here are the facts again. Both devices (Z-Wave stick and lock) operate on the same frequency and are EU models.
I have reset the lock completely = no success.
I have set the lock to inclusion mode via the app and the other time via the pin = no success.
I have tried various settings (Secure Inclusion Mode, Inclusion Mode, etc.) in openHAB = no success.
I have tried different versions of openHAB (3.4.0 M3, 3.4.0 M4, 3.4.0 snapshot) = no success.
By the way, other devices like a water detector are found by the Z-Wave stick, so the basic function seems to be there.
@apella12 The only Z-Wave controller entry I can find in the log is this one:
2022-11-16 14:46:58.237 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 2: Device discovery could not resolve to a thingType! 010F:0B01:1003::0.0
@apella12 No, there is no pop-up, etc. After the scan, no new device appears in the list and no error message appears. The search simply finds nothing.
Well… Mostly bad news. The Debug shows no message from the lock while inclusion was active. So it is a defective device, bad batteries or is somehow jammed up from previous tries. Is there any green light indication while pressing with pin/paper clip? Only suggestion I have (short of giving up) is to really poke around aggressively with a paper clip while the zwave is in scan mode & Debug. Scan mode lasts 1 minute, so there is time for several tries at various angles and force.
On step 1 did first remove the device from the app before pairing again?
Other observations
It looks like you set Debug and restarted OH. That is not really needed and fills up the log. It does however help me to conclude your zwave controller is starting ok and the Fibaro water sensor is also there. You can just set Debug on a working system, then inbox–>zwave–>scan
Your zwave XML files indicate you have created the controller 4 times. I don’t know if that is related. Only the f7daa5c7 version is working
I thought I read that is the expected behavior while being included, so surprising no radio wave that the controller is picking up. In my experience even if not an understood message Debug says something lkie “unknown message”
Edit: While resetting I’m assuming you saw these additional hints in the Zwave DB
I can’t say I don’t agree. You have given it the old college try (so to speak).
Did you try the idea on the DB page to remove from the app, then use your disconnected (from OH) zstick button to exclude? The plus side of that is you get a visual (IIRC a solid yellow for a few seconds) -no Debug required ! The hint also seems to imply the green light will go dark suddenly
edit: I also had the thought to delete and reinstall a fresh copy of the app. It might have some memory of the earlier attempts to use it for inclusion.
