@apella12 I have now followed all the steps. Enclosed is the log file.
openhab.log (120.6 KB)
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
Sorry
Yes, I removed the lock from the app and then pressed the PIN 10 times to reset the lock.
Yes, after pressing the PIN, the lock lights up green for a short time and then starts flashing green for about 30 seconds.
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 have now tried it again several times, unfortunately always without success. I hate to say it, but I give up.
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.
I assume that you mean this paragraph? I’m just wondering how the exclusion is supposed to take place if the stick is no longer connected, so how is a signal supposed to arrive at the lock?
Exclusion: Delete the lock from the app before you exclude. Otherwise it won’t work. Exclusion is successful when the green light stops lightning immediately. If you use the Aeotec Z-Stick Gen5 it is easier to exclude with the USB stick detached. Inclusion of course with the stick attached to the PC. You can use any kind of controller to exclude - no matter with which controller it has been paired before.
I don’t think that will help, because I also tried to include the lock without the app, which didn’t work either.
Yes. Up above you said you had an Aeotec stick. They all have internal battery to send exclusion signals without being connected to a server/power. I’m still stuck on the idea that the zwave info (from previous attempts with the app or with OH) has not been cleared from the lock
edit: As a side note you can generally include any device with a detached Aeotec zstick except for devices that include security (like your lock). It is not recommended because it is better to have OH perform the inclusion (sometimes using a detached Aeotec Zstick has problems with inclusion)
Ok, I didn’t know that the stick has a battery. But where do I start the exclusion? In OH it makes no sense if the stick is no longer connected.
By the way, this is the stick I have. Does this one actually have a battery as well? It doesn’t say anything about it in the description. Is there another stick that you can recommend?
Maybe you have a different model, but there should be a button (that flashes color) hit once to get flashing blue (include) hit again to get flashing yellow (exclude). Do you have that? If yes get to the flashing yellow and poke the switch on the lock. If this works, there should be a solid yellow for a few seconds
Nevermind I thought you had the actual aeotec zstick. Your does not have a battery
Unfortunately, the stick has no button 
Sorry. That feature comes in handy from time to time, but I would not bother buying one. All controllers are basically the same otherwise.
This leaves excluding through OH. I know you are at the end of your rope, but i’ll suggest this anyway.
- remove from App (if not already)
- Set the binding to Debug in karaf, keep OH running
- on the controller UI page, click exclude devices, then yes
- Poke the switch on the lock
- wait 30 seconds
- post Debug log
This should confirm something or not 
PS: I’m going to have to step out for a bit
It might be a timing problem, possibly specific to your ZMEEUZB1:
Advice from @chris in Openhab3 with I'd lock 150 zwave might be relevant (narrow time window, OH should not be busy during inclusion).
Replacing the Z-Wave controller with another brand could be the last resort, e. g.
I had all the problems described here. The danalock just didn’t want to connect “securely”. It was indeed a timing problem. The button on the danalock must be pressed in the same second as the scan button in the OH GUI.
yes, it works good. It has sometimes a delay of some seconds, but yes, it works like expected. It needs a lot of battery, I’m already at 75% after heavily testing. I think about to connect it to a 12V power supply as permanent solution.