Danalock control stopped working

[marbe 23]

After last updates, the Danalock lock control stopped working.
I tested on a new block scene, LUA commands are still the same.
I also tried removing the lock and re-adding it to the system, but to no effect.

Danalock has last FW.
Does anyone have a similar problem?

 

hub.call(deviceID, 'secure')

hub.call(deviceID, 'unsecure')

[m.roszak 774]

Which version of ZW are you using?
 

[marbe 23]

Hi @m.roszak , old Z-WAVE version v. 4.33.

[m.roszak 774]

Is it Danalock V2 or V3 module?

[marbe 23]

Danalock V3

[Neo Andersson 230]

On 10/18/2022 at 8:34 AM, marbe said:

After last updates, the Danalock lock control stopped working.
I tested on a new block scene, LUA commands are still the same.
I also tried removing the lock and re-adding it to the system, but to no effect.

Danalock has last FW.
Does anyone have a similar problem?

 

hub.call(deviceID, 'secure')

hub.call(deviceID, 'unsecure')

Danalock needs a special topic in general. I have discussed its problem in several mails with Fibaro support, and with Danalock support either. The conclusion was, Danalock V3 can not work correctly with Fibaro zwave engine 2. The lock states are many times incorrectly reported or not reported at all. We figured out, that if we add Danalock as the very first device to the system, it can help the situation but not solve entirely.

Your problem however is a bit different, becuase commands were always applied correctly before and after update either. One thing we noticed after update too, that on YUBII, the icon (locked or unlocked) never update, so definitelly there is some bug either on Danalock or Fibaro side, which i think will not be solved ever, becuase as other say, it works in engine 3 perfectly. Maybe mr Roszak will ensure us, that even on engine 2 there will be some deeper investigation for Danalocks.

 

[marbe 23]

Hi Neo  @Neo Andersson , thank you for answer. I am only surprised that until now everything worked properly, and after the last upgrades there have been such serious changes, which, as you write, are due to a fundamental incompatibility earlier. I would ask Mr Rozsak @m.roszak for a more detailed analysis from Fibaro. Thank you

[marbe 23]

I found:

• Danalock is not possible to add in S0 mode
• After new adding of Danalock there is endpoint 0 missing and is not possible to add it manually. In my experience endpoint 0 must be on every Z-Wave device. Without this no changes are sent to controller.

This is Danalock device. No endpoint.

Please login or register to see this attachment.

[Eufi 4]

wich firmware version have your dana?

My have 0.20.2 and no problems!

[marbe 23]

0.20.2 too.

[Neo Andersson 230]

On 10/21/2022 at 8:27 AM, marbe said:

I found:

• Danalock is not possible to add in S0 mode
• After new adding of Danalock there is endpoint 0 missing and is not possible to add it manually. In my experience endpoint 0 must be on every Z-Wave device. Without this no changes are sent to controller.

This is Danalock device. No endpoint.

Please login or register to see this attachment.

Uncheck the two checkboxes...

Just now, Neo Andersson said:

Uncheck the two checkboxes for filtering. (Zarizeni stenje urovne a to druhe)

 

[marbe 23]

Yes, I tried right now, but no change

[m.roszak 774]

Access control devices must be added in secure mode to work correctly, as Danalock can't be added to large systems as explained in linked topic it will be an issue without solution for existing systems... 

[fuser99 16]

For me worked to move Danalock closer to HC3 (~50cm) when adding it (with S0 enabled and NWI disabled) in the past (1-2 year(s) ago I guess). I don't know which software version I had at that time but I know that I had at least 50 Z-wave devices already added to the system before adding Danalock.

[Sjakie 156]

My DanaLock is number 37/ 78 devices

[Neo Andersson 230]

On 10/24/2022 at 5:25 PM, m.roszak said:

Access control devices must be added in secure mode to work correctly, as Danalock can't be added to large systems as explained in linked topic it will be an issue without solution for existing systems... 

Dear Michael, this problem is lingering in the air more than 2 years, and making us a huge problem. As I mentioned in some earlier topics, Danalock is the only Zwave lock that is available for EU market, and after a lot of mails with Danalock support, we concluded, that Fibaro must have some bugs in the system.

When Danalock added in S0 security mode, Fibaro is not capable of getting its status properly. That was our main problem so far.. Now, with the latest update, not only statuses are not reported, but even locking and unlocking process is bugged. I have several installations, where we had to install Danalocks. Nowadays i am facing a lot of issues, that customers house is not locked anymore, when they press LOCK button, or when we call

hub.call(id,'secure) command to lock the door. It is not like a light doesn't turn on or off, that the customer can live with for a while, this is a major problem. Its about safety of their houses. Back than, Danalock has confirmed me, that Fibaro doesn't comunicate its statues, and that it is in Fibaro system, that makes these problems. Then I recieved a suggestion from some Fibaro developer, that we can try to add Danalock as the very first device into the system, and it might help. It looked that it really helped. But now, at this moment, Danalock is absolutelly out of order in Fibaro systems. It sometimes works, sometimes not, and reporting of statuses is just zero. We tried to use Danalock in other zwave systems, and it works fine. Hubitat, Homey, we didn find any problem...i am wondering, what can we do with these installations. I am deeply afraid, that it is only matter of time, that we will face some real trouble, when someone steals something from customer's houses, then we can find ourselves sued and blamed from the losses. We just cant go back and tell all the people, that sorry, we need to uninstall the locks, becuase it doesnt work..I have never seen any information, or warning from Fibaro, that its not capable of working with Danalocks ever. We also heard, that Danalock is working when we run engine 3 on Home centers, but everyone told us, to not use engine 3 yet, as it is full of bugs, and not reliable yet. What to do now, which way to go? Is there any hope, that in S0 mode Danalock will work with Fibaro?? Should we really remove all the Danalock devices from all the installations?

Please try to instruct us, what tot do.

Thanks

 

[fingusio 12]

Just bought Danalock V3 and after few days will add to clear HC3 (knowing the problem I thought it over and that's why I'm doing it first)  - will inform how it work

[marbe 23]

Hi, I have tested repeatedly removing and adding the lock to the system, and finally successfully.
Functional configuration of add parameters: disable remote adding, force adding only in S0 mode, allow adding only near controller. And of course the lock must be close to the controller. Then the lock was added in S0 mode and association endpoint 0 was added too. Now everything seems to work as it should.

[m.roszak 774]

On 10/28/2022 at 4:56 PM, Neo Andersson said:

Dear Michael, this problem is lingering in the air more than 2 years, and making us a huge problem. As I mentioned in some earlier topics, Danalock is the only Zwave lock that is available for EU market, and after a lot of mails with Danalock support, we concluded, that Fibaro must have some bugs in the system.

When Danalock added in S0 security mode, Fibaro is not capable of getting its status properly. That was our main problem so far.. Now, with the latest update, not only statuses are not reported, but even locking and unlocking process is bugged. I have several installations, where we had to install Danalocks. Nowadays i am facing a lot of issues, that customers house is not locked anymore, when they press LOCK button, or when we call

hub.call(id,'secure) command to lock the door. It is not like a light doesn't turn on or off, that the customer can live with for a while, this is a major problem. Its about safety of their houses. Back than, Danalock has confirmed me, that Fibaro doesn't comunicate its statues, and that it is in Fibaro system, that makes these problems. Then I recieved a suggestion from some Fibaro developer, that we can try to add Danalock as the very first device into the system, and it might help. It looked that it really helped. But now, at this moment, Danalock is absolutelly out of order in Fibaro systems. It sometimes works, sometimes not, and reporting of statuses is just zero. We tried to use Danalock in other zwave systems, and it works fine. Hubitat, Homey, we didn find any problem...i am wondering, what can we do with these installations. I am deeply afraid, that it is only matter of time, that we will face some real trouble, when someone steals something from customer's houses, then we can find ourselves sued and blamed from the losses. We just cant go back and tell all the people, that sorry, we need to uninstall the locks, becuase it doesnt work..I have never seen any information, or warning from Fibaro, that its not capable of working with Danalocks ever. We also heard, that Danalock is working when we run engine 3 on Home centers, but everyone told us, to not use engine 3 yet, as it is full of bugs, and not reliable yet. What to do now, which way to go? Is there any hope, that in S0 mode Danalock will work with Fibaro?? Should we really remove all the Danalock devices from all the installations?

Please try to instruct us, what tot do.

Thanks

 

I have got an e-mail from Danalock last week, I will keep you informed.

[fingusio 12]

Today added to clear HC3 (5.110.15 firmware) new Danalock V3 (newest firmware 0.20.2) without any problems

 

Edited November 2, 2022 by fingusio