Danalock V3 ZWave och Aeotec Z-Stick Gen5

[ehallq]

Hi!

I just bought a Danalock V3 with Zwave support. As the topic specifies I am using a Aeotec Z-Stick Gen5.

I have tried to include the lock without success, I have done it manually by pressing the button on the stick, also tried both secure and unsecure inclusion in Domoticz but none has worked.

Usually when I have added unsupported devices (OpenZwave) it has been added but with no settings available, however now nothing happens it does only wait for the device for ever.

In the Android app nothing happens when I press connect, and on the iPhone it actually shows a loading window with the text "Connection device to Z-Wave gateway". However as in Domoticz, it just loads forever...

Have someone else successfully added this lock with Aeotec Z-Stick Gen 5?

[ehallq]

Actually solved it, the problem was the app.. So using a needle to push the small button in the case solved it, it was successfully put in inclusion mode and now I can toggle the lock with Domoticz

[havnegata]

Can you share more of your experiences with this lock and Domoticz?

[Lasermi]

Hi there! I also bought the v3 but I'm facing issues. I already found the App issue. I'm now using the button on the Smartlock with a clip. Connecting via domoticz doesn't work (neither include nor include secure). When I use the swith on the Gen5 stick, the lock pairs to the stick and it also shows up in Domoticz. However, device ID never shows up and after some minutes the lock is reported dead.
I still haven't edited manufacturer_specific.xml. Did you need to do so? What did you add?

Many thanks!
P.S: I'm generally satisfied with the lock, although it struggles to open the door (it's a very hard to open door, my girlfriend even sometimes can't open). On my Honor cellphone, bluetooth functionnality is just awsome. However, on my girlfriend's phone, the phone pairs and sees the lock status but for some reason the commands are not sent out so the lock doesn't open or close....

Enviado desde mi FRD-L19 mediante Tapatalk

[stutmich]

HI I'm new here,
an I do not know how to create an own topic, but my one fits into this.

I have the Danalock V3, I included it into the ZWave (Aeon Z-Stick Gen5). But if I check the configuration under hardware in Domoticz I only have an emtpy list. All other devices have a lot of config possibilities.
I can do everything with the danalock open/close/scripting/email - but no config.

I do not know what to do?

Any ideas.

Thx a lot.

[Lasermi]

HI I'm new here,
an I do not know how to create an own topic, but my one fits into this.

I have the Danalock V3, I included it into the ZWave (Aeon Z-Stick Gen5). But if I check the configuration under hardware in Domoticz I only have an emtpy list. All other devices have a lot of config possibilities.
I can do everything with the danalock open/close/scripting/email - but no config.

I do not know what to do?

Any ideas.

Thx a lot.

Hello to all,
Can you please detail hoe you included the device? I am still struggling to achieve that. Secure include will do nothing. I set the same password in options.xml and in domoticz, but secure inclusion doesn't seem to work on my aeon gen5 stick... any clues? Once I get the device included, I'm willing to help for the config issue.
Thanks!

Enviado desde mi FRD-L19 mediante Tapatalk

[stutmich]

Hi Lasermi

I had this problems also.
Than I installed domotics to my windows computer an put the stick into the USB port.
On my windows pc it was possible via domoticz to "add secure node".
Don't know why.

[bmhvanbenthum]

Is there any development in getting the danalock V3 working in domoticz?

I'm using the latest jadahl beta on synology (3.8687). My lock in initialized as unknown device. I'm unable to control it.

I would appreciate any kind of help.

Bram

[bmhvanbenthum]

My lock is working now.

There is firmware update:

https://danalock.com/dv3-faq.html#0401

First exclude your dana lock from domoticz.

Reset your lock by pressing the tiny button on the lock with a paperclip 10 times in 5 seconds. The lock starts flashing red. Wait unil the flashing is finished. Now remove the batteries and re-insert them after 10 seconds.

In domoticz soft reset controller. Restart domotoicz or your diskstion. Check if all other nodes are initialized after the restart.

Now in domoticz go to add node secure, and press the button on the danalock V3 1 time. Be patient, after 1 minute the lock is initialized as "polycontrol". You receive 5 new devices in domoticz:

295 Z-wave controler 00002634 6 Alarm Type: Access Control 6 (0x06) General Alarm Event: 0x03 (3)
294 Z-wave controler 00002634 1 Access Control Light/Switch Switch On - -
293 Z-wave controler 00002632 1 Alarm Level Light/Switch Switch Off - -
292 Z-wave controler 00002633 1 Alarm Type Light/Switch Switch Off - -
291 Z-wave controler 00002601 1 Locked Light/Switch Switch On - -

number 291 "291 Z-wave controler 00002601 1 Locked Light/Switch Switch On - - " will control your lock.

Off course the lock must be re-calibrated afterwards.

Good luck

Bram

[Lasermi]

Hi there! I also got it to work. Some additional notes (based on my mistakes):
Update domoticz to the latest beta as Danalock v3 support was added in openzwave after the last Domoticz release.
Of course, also uodate Danalock firmware.
Don't add the network key into options.xml file. Add into the Domoticz z-wave controller configuration and only there.
The network key in Domoticz contains no spaces (as opposed to options.xml).
After the secure inclusion, be patient. The device will eventually appear. If you restart Domoticz or the controller too soon, you may end up with the id 0000 and stay stuck there.

Enviado desde mi FRD-L19 mediante Tapatalk

[polo9222]

Hello, I am a newbee in domoticz on raspberry and I just bought a Danalock V3, a PI 3B, and an UZB1 usb key for Z-Wave.
Thanks to your help, I have updated my lock and my Pi is running well with ssl and domoticz realease Version 3.8153 (July 30h 2017) et Z-Wave 1.4.2501g5af6780 wich according to my reads should take into account my lock.
Despite of clear tutos , I am not able to pilot my lock from Domoticz ; I can see it as a device but nothing happen whzen i clic on it.

Capture.PNG (29.93 KiB) Viewed 7519 times

Is it a question of release all simply ? if yes how can I find the good one and how should I install it within domoticz

Thanks for your help.
Polo

[polo9222]

I forgot : do you think problem could come from the USB key : UZB1 ?

Polo

[at4500]

Lucky ones who made it working. Though, cant make it work. Controller adds node etc, but, isn't able to drive it.

I get timouts:
Jan 22 23:38:36 myRaspi domoticz[2057]: OpenZWave: Received timeout notification from HomeID: 3935312979, NodeID: 4 (0x04)
Seems like DomoticzV3 lock is sleeping and not answering.

Danalock FW: 0.8.0 (basically, the latest)
Domoticz V3.8834 (after series of unsuccess, updated to beta.

Controller log:
2018-01-22 23:38:35.240 Always, End of queued log message dump
2018-01-22 23:38:35.240 Always,
2018-01-22 23:38:35.240 Detail, Node004, Removing current message
2018-01-22 23:38:35.240 Detail, Node004, Notification: Notification - TimeOut
2018-01-22 23:38:35.243 Detail,
2018-01-22 23:38:35.243 Info, Node004, Sending (Send) message (Callback ID=0xc7, Expected Reply=0x04) - DoorLockCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x62, 0x02, 0x25, 0xc7, 0x61
2018-01-22 23:38:36.243 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-01-22 23:38:36.243 Always,
2018-01-22 23:38:36.243 Always, Dumping queued log messages
2018-01-22 23:38:36.244 Always,
2018-01-22 23:38:36.244 Always,
2018-01-22 23:38:36.244 Always, End of queued log message dump

[at4500]

bizzare enough, after ten's of resets, excludes, includes etc, made it work. Dont have any confidence will stay that way..

Jan 23 16:25:08 xxx domoticz[2630]: User: admin initiated a switch command (101/Danalock v3/Off)
Jan 23 16:25:08 xxx domoticz[2630]: OpenZWave: Domoticz has send a Switch command! NodeID: 5 (0x05)
Jan 23 16:25:08 xxx domoticz[2630]: (zwave) Light/Switch (Danalock v3)
Jan 23 16:25:10 xxx domoticz[2630]: (zwave) Light/Switch (Alarm Type)
Jan 23 16:25:10 xxx domoticz[2630]: (zwave) Light/Switch (Alarm Level)
Jan 23 16:25:26 xxx domoticz[2630]: (zwave) Light/Switch (Alarm Type)
Jan 23 16:25:26 xxx domoticz[2630]: (zwave) Light/Switch (Alarm Level)
Jan 23 16:25:26 xxx domoticz[2630]: (zwave) Light/Switch (Danalock v3)

[paqpaq]

I've successfully added a V3 Z-wave version to a UZB01 stick.
however, after about 1,5 - 2 days, the lock stops responding in domoticz and displays a red ! at status.
I reset the pi with domoticz and all is back up again, until 1,5 - 2 days later it all repeats itself.



How can I isolate what is causing this issue? an/or is there a work around to automatically reboot (just Domoticz) evey night at say 03:00 AM?

[bramski]

@at4500

I'm also not able to get it to work. Get the same errors as you about timeouts and the command to lock/unlock is being dropped (see logs below). I have several non battery powered zwave devices very close to the lock, so connectivity should not be an issue.

Tried a lot of different things.
- Adding the lock with the app and adding by pushing the tiny button on the device.
- Add it with the Z-Stick controller, in domoticz (Add secure), and in OZW control panel.
- Excluded and included several times.
- Reset my lock (pushing the button 10 seconds)
- Upgraded firmware to 0.8
- Installing the latest beta of Domoticz Version: 3.8914
- Rebooting and restarting domoticz several times
- Soft reset Z-stick multiple times

Struggling for hours to get this working as advertised. Hope you guys have any suggestions how to resolve this issue.

Logs here:

Spoiler: show

2018-02-10 18:46:52.823 Info, Node026, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2018-02-10 18:46:52.823 Info, Node026, Value_Lock::Set - Requesting lock to be Unlocked
2018-02-10 18:46:52.823 Detail, Node026, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-02-10 18:46:52.824 Detail, Node026, Queuing (Send) DoorLockCmd_Set (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x62, 0x01, 0x00, 0x25, 0xe6, 0x5f
2018-02-10 18:46:52.824 Detail, Node026, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-02-10 18:46:52.824 Detail, Node026, Queuing (Send) DoorLockCmd_Get (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x62, 0x02, 0x25, 0xe7, 0x5f
2018-02-10 18:46:52.825 Info, Node026, Processing (Send) Nonce Request message (Callback ID=0xe6, Expected Reply=0x04)
2018-02-10 18:46:52.825 Info, Node026, Sending (Send) message (Callback ID=0xe6, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-02-10 18:46:52.833 Detail, Node026, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-02-10 18:46:52.834 Detail, Node026, ZW_SEND_DATA delivered to Z-Wave stack
2018-02-10 18:46:54.113 Detail, Node026, Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x81, 0x68
2018-02-10 18:46:54.114 Detail, Node026, ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-02-10 18:46:54.114 Info, Node026, Request RTT 1289 Average Request RTT 1305
2018-02-10 18:46:54.135 Detail, Node026, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x1a, 0x0a, 0x98, 0x80, 0x35, 0x02, 0x66, 0xc9, 0xab, 0xc0, 0xcd, 0x38, 0xe5
2018-02-10 18:46:54.136 Info, Node026, Received SecurityCmd_NonceReport from node 26
2018-02-10 18:46:54.136 Info, Node026, Sending (Send) message (Callback ID=0xe8, Expected Reply=0x04) - DoorLockCmd_Set (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x62, 0x01, 0x00, 0x25, 0xe8, 0x51
2018-02-10 18:46:54.148 Detail, Node026, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-02-10 18:46:54.148 Detail, Node026, ZW_SEND_DATA delivered to Z-Wave stack
2018-02-10 18:46:54.172 Detail, Node026, Received: 0x01, 0x07, 0x00, 0x13, 0xe8, 0x00, 0x00, 0x03, 0x00
2018-02-10 18:46:54.172 Detail, Node026, ZW_SEND_DATA Request with callback ID 0xe8 received (expected 0xe8)
2018-02-10 18:46:54.173 Info, Node026, Request RTT 1347 Average Request RTT 1326
2018-02-10 18:47:02.825 Error, Node026, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-10 18:47:02.827 Detail, Node026, Removing current message
2018-02-10 18:47:02.828 Detail, Node026, Notification: Notification - TimeOut

[paqpaq]

I had An iBeacon very close to the lock today, and Domoticz refused to connect. So it still could be an issue there.

[bramski]

Finally got it to work. Did the following:
- Delete lock from app
- Pull out batteries
- Delete the node from domoticz
- Add the lock in the app and walk the settings/calibration screen.
- Include secure in domoticz
- Push the small button

Now I have 5 devices in domoticz for the lock. Previously I had 2 devices.
I can now unlock/lock remotely with domoticz.

No idea why it is working now. Hope it stays this way.

[mjaqb]

What version of Domoticz do you have? Does anybody know is it working fine on 3.8314? (this is version that I have on my Qnap - unfortunately update doesn't work...).

[murat]

Hi Bramski
I also have the same issue, include is working fine, but cannot drive the danalock, whenever I include the switch, it cannot make any connection and then I get error messages like you mentioned.
IS it now stable and any update what the trick was to include in a good way?
thanks
Murat