Search the Community

Hello I need help with the integration of a Danalock V3, this fail on a specific HC3, works on another. Fibaro support did a reprogram of the zwave chip but it was still failing... now they asked a factory reset of the HC3 (to reset the encryption key) and reconfigure manually everything, the backup is not an option as it contains the encryption key. Before going to this option (3 days work) I poll the community to see if similar problem was found and what are the alternatives to solve it without a complete manual reconfiguration. The integration in secure mode of a Danalock V3 (fw 0.16.1) on HC3 5.061.36 (beta) failed partially. The pairing with the HC3 is done at 1m. The device is recognized, see the log below. However the configuration didn't happen no parameter template loaded. I tried the exclude/include process several times without better results On another HC3 the inclusion is successfull with only one "Requesting neighbours, please wait..." ----------------------------- [25.02.2021] [09:36:09] [TRACE] [ZWAVE]: Home Center in learning mode [25.02.2021] [09:36:28] [TRACE] [ZWAVE]: Adding devices complete [25.02.2021] [09:36:33] [TRACE] [ZWAVE]: Home Center in learning mode [25.02.2021] [09:36:53] [TRACE] [ZWAVE]: Device added [25.02.2021] [09:36:53] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:36:58] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:03] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:08] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:13] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:18] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:23] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:28] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:33] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:38] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:43] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:48] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:53] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:37:58] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:38:03] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:38:08] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:38:13] [TRACE] [ZWAVE]: Requesting neighbours, please wait... [25.02.2021] [09:38:15] [TRACE] [ZWAVE]: Requesting neighbours done. [25.02.2021] [09:38:15] [TRACE] [ZWAVE]: Add node status protocol done [25.02.2021] [09:38:16] [TRACE] [ZWAVE]: Adding devices complete [25.02.2021] [09:39:28] [TRACE] [ZWAVE]: ID 273: Device configuration finished Thank you for your help

I have an issue with removing a Danalock from my HC3. I first tried to reconfigure the lock but it does not reconfigure, this is weeks ago. When trying to remove the lock nothing happens. when I try to force delete the lock I get the following Z-Wave trace: ”ID 1607: NOP sending succeeded. The device has not been removed. Please use Learning Mode to remove it.” Is there any other way to delete the device?

Hi I'd like to open/close the danalockv3 id541 using two triggers. Holding the light switch (the danalock status changes each time the key id553 is held down) or the alarm output (the ldanalock status changes depending on the alarmoutput id430 status on/off on=unsecure off=secured). In addition, the alarm output state should be synchronized with the lock state, because I can open the lock manually for example. How to modify the lua code below to add a second trigger to it (alarm out) and synchronize lock state? { conditions = { { id = 553, isTrigger = true, operator = "==", property = "centralSceneEvent", type = "device", value = { keyAttribute = "HeldDown", keyId = 1 } }, { id = 430, isTrigger = true, operator = "!=", property = "state", type = "device", value = {} } }, operator = "any" } local deviceValue1 = fibaro.get(541, "value") if deviceValue1 == true then fibaro.call(541, 'unsecure') else fibaro.call(541, 'secure') end

Hi All, I have been searching for a while now on the forum, but have not find the solution to my problem. We do have the danalockV3 and the Fibaro intercom. Both device can be found in the HC3. Now the problem is that when we try to open the Danalock trough the intercom or in a scene, the Danalock doesn't respond to it. If i look in the recent history of the HC3, i can see that the scene has run. As well there is a action that is called Action: Device polling. Does anybody know how i can fix this? Happy to hear your answers. I am new in this world so please be free to ask me if you need more information. Greetings, Thomas

Dear Users, I'm running version 4.140 and I've just installed a new Danalock v3. Seems like the Danalock v3 is working just fine, but I cannot select it while I'm making a block scene. Steps to reproduce: Make sure you have properly working Danalock v3. Add a new scene using blocks start your scene with an 'Days in week' at Anytime (I think it doesn't matter how you start your scene anyway). Add your device - Danalock v3 result: The Fibaro user interface scrolls or refreshes to the top of your browser and the device (danalock v3) is not added. Other devices seem to work fine... Hoping there is an explanation to this. With kind regards, Peter Seems to work in a LUA scene..

I have a Danalock which is situated on the edge of HC2 range and it receives commands maybe one time out of 10. But it stubbornly doesn’t want to do any hops via intermediary devices which there are plenty of between the lock and controller. Fibaro door-window sensor located on the same door for example easily hops via two devices and works reliably. so the question is if it’s possible to manually set its routing to make hops? Probably with UZB?