Sure u added lock in save mode? Reset the lock by pressing the round button 10 seconds and pair again in save mode!
What device(s) did you get when it successfully included, @stiansoevik?
As I said earlier, I get a device called ‘lock.locked’, but can’t do anything with it. It has a toggle in the frontend, but when I click it, it reverts back to the former position (off) after a second or so. Nothing happens to the lock, and HA always assumes its state as ‘unlocked’, even though it is locked.
@thundergreen: I tried resetting the lock and pair in secure mode again, but that didn’t make a difference. Thanks for the tip, though.
Does anyone know if it is possible to update the OZW library on my Hass.io instance? Or at least know how I can find out if I have the latest version?
I suspect this being the issue, given that @stiansoevik got it working by compiling OZWCP himself. Also, it gets included, and recognised as a lock, but does not get a proper name/manufacturer/model. It also does not work, as stated earlier.
If you’re running 0.54 you’re at 0.4.0.31, and when 0.55 comes out you’ll be at 0.4.0.35, which is the most recent release of python_openzwave
Ok, thanks. What is the timeline for release of 0.55? Where can I see what version is newest and changelogs for each version?
Saturday - it’s every 2 weeks for releases.
Changelogs can be found on the blog for past releases, for future releases see Github.
Thank you.
I had a quick look at the change log for open-zwave (parent of python-openzwave), and can’t fand that the Danalock has been added to the library… I suspect @stiansoevik got it working but, not actually properly working with the manufacturer specifics. Could this ve the case?
Quite possibly, or he may have developed his own config file as explained here and not submitted it back to OpenZWave.
Update:
I set ‘assumed_state’ to ‘true’ for the lock, and was able to send ‘unlock’ command to the Danalock. However, ‘lock’ command did nothing, and the reported state in HA was still ‘unlocked’ all the time.
But that’s the least of my problems right now:
Yesterday, when I got home from work, the lock wouldn’t budge. The app gave me an error, and I could hear the lock trying to start the motor, but failed. Turns out the the batteries were completely drained! After less than a week…
I read somewhere that others had a battery drain issue when their Danalock (older gen.) was connected to a Z-Wave network. I wonder if this battery drain issue is related to my Z-Wave issue…?
I will contact the manufacturer. Sucks that I have to buy a new set of those expensive CR123A batteries.
Another update:
I just got a response from the manufacturer. Apparently, I am not the only one with the battery drain issue, and they are working ‘instesively’ on resolving it. They will also send me new batteries for free.
Just thought I’d write this up in case others come here with the same issue.
2 Likes
Sorry for the late reply. I did not need to do any customization myself - I just used secure add from ozwcp. zwcfg is shared between ozwcp and HA. Then, I opened HA (and probably restarted after a while), and the lock was shown with one device (Locked/Unlocked and a switch).
My battery also just went out after a week or so 
Does manufacturer and model show up in the node information?
Let’s hope the battery issue will be fixed by an OTA firmware update…
After replacing batteries, it seemed like the lock reset (had to reconfigure using BT, and could not control from HA anymore)
Anyway, here is what I can read from HA: product name
Unknown: type=0009, id=0001
I see…
I still have a feeling it is not actually added to the OZW device database, and that you only got it working as a generic lock. Better keep our fingers crossed this will all be resolved eventually. I’ve already had to mill out part of my doorframe to get it fitted…
I might look into adding it to OZW myself if I get the time.
BTW: Just out of curiosity, I measured the voltage of the depleted batteries. Three of them was at about 2.5V (3V is nominal), but the last one had switched polarity and was measuring -0.9V! This could mean there is a hardware error, but we’ll just have to wait and see what they come up with.
Just got another email from the manufacturer.
They had discovered that the battery drain issue is Z-Wave related, so if you just exclude it and not use Z-Wave temporarily, your batteries should not drain quickly.
Is it a problem if it works as a generic lock, as long as it works?
I also emailed them. For me, disabling Z-wave is not a good solution, as the app is not working very well (it did not unlock when I came home, but it did during the night…). How is the app working for you?
The app is working quite terribly for me as well. Auto unlock is a joke, I think it relies too much on GPS position. In my case, I park in a garage where there is no GPS reception, and then walk up the stairs in a concrete building, so even when I get to my door, the GPS reception will be poor.
Poly-control explained to me that when you are within 30 meters (GPS) of your lock, your phone starts pinging for the lock via Bluetooth. This obviously does not work if you don’t have a good reception…
I have also had the app crash on me a couple of times. I use iPhone, what do you use?
What is your solution for (auto?) unlocking via Z-Wave?
I have an Android phone. My plan is to use one of HA’s presence components together with push notifications, so I can open the door from my phone/watch when I get home. However, the Wifi detection seems a bit slow (I assume my phone doesn’t try to connect all the time)
Alternatively, it would be cool to open automatically if I find a safe (enough) way. Maybe some indication that I recently got in the area plus movement outside, or even face recognition 
Have been thinking about many of the same solutions for unlocking via Z-Wave. 
For me, the Wifi detection is fairly quick, and I have had the refresh interval at 15 seconds. I just set it down to 5 seconds, and will see how that works. I have set up a phone notification (automation) for when it is detected. I suppose I could also make a condition with a location component (iPhone app, Owntracks etc.) for added security.
Did you get it to work? After the battery change and reset, I am again having trouble, even with ozwcp and having the UZB very close to the lock.
The bad symptoms are:
2017-10-12 18:56:44.548 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-10-12 18:56:44.549 Detail, Node003, Removing current message
2017-10-12 18:56:44.549 Detail, Node003, Notification: Notification - TimeOut
Also, the twist assist does not work anymore