We are using on one door a door sensor. But it gives only correct results if the time between opening and closing the door is very long. If someone opens the door, leaves and then closes it the door sensor will only recognize the opening of the door but not the closing.
Basically at the moment it is more accurate to throw a coin to find out if a door is closed or open.
I experienced the same with Nuki 4 (non-pro), Bridge and Door Sensor and reported to Nuki.
It seems to be only a problem when the bridge is connected, then the closing of the door is only recognized when the door is open for some more seconds. Without bridge the opening and closing is recognized reliably.
(I don’t follow up this issue any longer as I switched from bridge to Matter over Thread which works as expected here)
pretty disappointing again. They must a) mention it in their product description b) support should know that and c) they should answer their paying customers.
If you have Home assistant you can put connect to the lock and one door sensor and do automatically actions to do things better than the original nuki door sensor… one big mistake of the original sensor is take 20 seconds in upgrade the status… also the price is to expensive fir what it does… i made some automatic actions with HA, such us: only fires when the door is closed, always lock when kids are alone. Allways lock when the door sensor detects that the door was close for x minutes and nobody is home… allways close the front and back door when i close the garage door, etc…
We will anyway throw out the Nuki products as soon as possible as too unreliable (as their support)
A door sensor which takes 20 seconds? That’s a joke. How can someone even consider to develop something like that? But its not that. It constantly displays wrong. like open when closed and closed when open. No updates after 20 seconds. not even after 20 minutes.
The smartlock works fine and report correctly? If your problem is with the door sensor, buy one raspberry and one door sensor if you don’t have one, install on HA and yo can make a lot of things also make automatization to lock when the last member leave the house… I can help you if you need any help .
I think the interesting point is, that the Nuki Door Sensor does work, even with remote access, but not if remote access is via Nuki Bridge but only if you use remote access via Matter/Thread (I do use Home Assistant now).
We are looking into this already. Obviously it is not the desired behavior. The door sensor should - if properly mounted and calibrated - report the closed state as fast as it reports the opened state.
Just one side note: The Nuki App is not a good means to monitor the door state in real time. The app requests the state every 20s when left open and does not receive pushed real time updates. The better indicator to judge if the door sensor did communicate its state to the lock is the LED on the Smart Lock itself as it lights up immediately, after the door sensor reported opened or closed states.
The problem are not the 20 seconds. We could accept those 20 seconds. The problem is hat if there are two events close together it reports a wrong state. For example someone opens the door and leaves and closes it. I will remain forever on open.
Dear all,
first of all, thanks for sharing your concerns regarding our Nuki Door Sensor product quality.
We are aware that we have still a few customer setups/installations with a Door Sensor status update issue. We just released a new Smart Lock 4 BETA firmware, which also solves communication issues between the Door Sensor and the Smart Lock 4. So please update your Smart Lock 4 to Beta FW 4.4.4
If you are still facing issues or are a owner of a Smart Lock 3, 2 or 1, please contact our customer support so that we can streamline the problems.
we have firmware 4.4.1. I thought that is the latest release firmware since the 4.3 firmware’s knock out the lock after 2 weeks.
As I said. The accuracy is comparable to a thrown coin and I pity the wasted money. Probably will send it back on your expense as it is not doing what promised.
Now „free features“ are being charged. See for example the Airbnb-implementation.
Features requested hasn’t been implemented. For example when the Airbnb code is being sent.
Or to be able to calibrate the maximum and minimum turns of the cylinder to save battery.
And we never understood why (finally/thanksfully) there was a usb-pack that had TWO usb-charging ports on the side instead of one in the front. Old or physically „restricted“ humans could have it way easier.
But Nuki does its business. It’s okay. One day we will move away too.
Any news? Yes, I know, this post will be deleted soon as “inappropriate”. You Austrians really have a strange classification for “inappropriate”
Dear all,
as mentioned here we have a solution for Smart Lock 4 users within the Beta FW 4.4.4.
The solution will be rolled out in one of the next public releases and we will inform you here and in the Smart Lock Release channel.
We do not provide specific release dates, as these could be subject to change. Rest assured, our team is committed to delivering the best possible product, and we will share updates as soon as more information becomes available. We appreciate your understanding and support.
I had the exact same door sensor behavior. It helped me to remove and put the batteries back in the lock. The sensor appeared to be disconnected for a while, but after a few minutes it appeared in the application and everything worked for a second. I have lock 4 not PRO with bridge connected.