loss of doorlock state

[Tony270570 107]

Hi all,

With this last release, I'm losing the doorlock state. I can send lock , unlock command the device receives the command but don't update the state of the lock. 

A hub.getValue (id, "value") always return the same state independently of the real state of the device.

Please login or register to see this spoiler.

[m.roszak 763]

Hello,
Thanks for the report, we will look into it. 

Z-Wave engine 3.0 or 2.0?

[Tony270570 107]

Sorry ! I’m still in v2.

[Conteaza84 0]

Danalock v3 status is ok!

[Neo Andersson 230]

@m.roszak Michale, can you confirm us that this issue is under investiagtion?

We are having troubles with Danalock all the time. On engine 2 it is reporting bad states all the time.

We have been discussing this with you and with your colleagues many many times.

We did the installations as it is recommended, so Danalock added as the very first device..without this it is 0 chance that it will report states correctly, but now even this doesnt' help

Danalock never changes the status..So annoying and so sensitive part of a house..

I am just waiting when some day some customer calls me and says that his house was robbed, while his door never triggered some alarm or something that he had adjusted..

This is really dangerous and sensitive thing..

Regarding the engine 3..We also tried with engine 3, and it was even worse..it was a horror so we went back to engine 2.

 

May i ask to get some info?

 

 

[Tony270570 107]

Hi all, my title is a little bit confusing as the problem is not of losing the state in my case, but is that the state remains unchanged independently of the command that is sent.

@Neo Andersson What I did to avoid having bad status reported, i put a fibaro walli controller to commande the lock inside (the ring colore indicates if the doorlock is locked or unlocked..)   and a RFID reader (satel integra system...)  outside. I never lock/unclock the doorlock manually/by key, otherwise it loose the state very quickly. But you already knows it

 

Edited September 25, 2024 by Tony270570

[m.roszak 763]

So, we found out what is happening - it's fixed to the upcoming version.
Not all locks were affected by this, that's why it was missed. 

[Tony270570 107]

I had absolutely no doubt that you would find the problem, thank you for your update @m.roszak !

Ready to click on the next firmware update as soon as it lights up.

Edited October 3, 2024 by Tony270570

[Tony270570 107]

Issue fixed by 5.163.59.

@m.roszak,thank you for your reactivity !