Hi everybody,
I have just received my Nuki 4 Pro lock yesterday. Unfortunately, I was not able to connect it via Matter (something about that device requiring a Border Thread router – which I have, I configured my SkyConnect USB stick to act as one… but this isn’t about that).
Anyway… It was also not possible to follow the perquisites here because this lock has WiFi built in and there is no Nuki bridge.
Fortunately, the device natively supported mqtt, so I went that route.
It kept unlocking overnight. Nobody has been controlling it via Home Assistant, yet it states that I have been unlocking it. I marked in red what should not have happened and in green the changes that were actually meant to be.
22:25:47 – “wurde aufgeschlossen” > “was unlocked”
22:25:40 – “nicht mehr verfügbar” > “unavailable / not available any longer”
05:15:28 – this was actually triggered by an automation, not by the entity state, as logs state, but it is correct behaviour
05:15:31 – this is just the status change from a couple of seconds before, so also correct
05:12:39 – “wird abgeschlossen” > “being locked” and
05:12:43 – “wurde abgeschlossen” > “has been locked”
Why is it being locked at all? This is not caused by any automation; neither did I do it, even though it states that I did (05:12:39, “Ben”).
I thought that perhaps the lock becomes unavailable because of deep sleep or something like that; but this isn’t ping, it’s mqtt. It should not become unavailable at all, should it?
I guess, technically it could toggle to “being locked” / “has been locked” after it had become unavailable; this might just be because the state changed from unavailable to the locked state… however, then it ought to be “has been locked” right away, without “being locked” first, correct?
If this is just a status update issue due to mqtt, that’d be “fine”. It would not actually be fine, but I could live with that, I guess. But if the lock actually re-locked each time it became available again, the battery will likely last at week instead of the advertised few months.
But if the lock were to actually unlock and lock on it’s own at random times, then it would be pointless to have this lock.
I’ll try the Border Thread router way once more today, but this should work either way. It can be controlled via mqtt, so the functionality should work reliably, right?
Thanks in advance for your ideas 