To enable the online option via thread how we have to proceed?
I have the following configuration:
[LOCK] ----> [thread using Nest hub as border router] ----> [Home Assistant with matter addon]
Thanks!
I’m very well aware of this. I think the support article was created after I asked about it: Smart Lock 4.0 Pro + WPA3. I just hoped that “improving the WiFi implementation” would incorporate the feature request, but thank you for confirming that it doesn’t.
Hi there,
im using a Nuki 4.0 non Pro Lock in combination with a Nuki Keypad, an Nuki Opener and a Nuki Bridge.
As [Stefan Reiterer] mentioned …
“If you install this Beta on a Smart Lock (4th generation, Standard variant) you might experience that the Bridge connection is lost and that the app asks you to purchase an upgrade to receive the full remote access. In this particular case please write me a DM for further assistance.”
It is better not to install the Smart Lock Beta 4.1.2 Version, and keep disabled the “Auto Firmware update function” to avoid further surprises ?
Currently im on Smart Lock Beta 4.1.1
Some thread enabled Apple devices are in use.
Original post has been updated with release notes for the Smart Lock Beta 4.1.3
This Beta is adding bugfixes and stability improvements on the recently changed connection handling implementation (including optimizations for the Thread uplink).
The new feature can now be also tested in combination with the iOS version of the Nuki App: APP UPDATE: Nuki iOS App 2024.2.1-Beta (Improved Shortcuts) - #5 by Stefan_A
Please install this beta and provide your feedback via this channel - thank you!
Hi,
you can install the Beta without any issue, since you are using Apple devices (supposedly Home Pod?) you could actually bring your Smart Lock online without the Nuki Bridge.
So - if you are going for the Beta please send me your Nuki ID via private message upfront so that I can enable the Remote Access via Thread for you.
Please refer to this description on how to properly set up the Home Assistant to get the Remote Access working:
1 Like
Thanks Stefan,
There are 3 HomePods mini and an AppleTV as possible Thread Boarder Routers.
Is it possible to go back to Nuki Bridge as Remote Access Device if I install the 4.1.3 firmware and use Thread for Remote Access?
Is the paired Keypad still working as normal via Bluetooth ?
Will i am forced to pay the planned fee for thread remote access when the feature becomes official or can I return to Nuki bridge access then?
You can pair the Bridge again after the update and everything will work as before.
Keypad is not affected.
Since I have my new Smart Lock Pro (4) I have an instable WLAN connection to my Fritz Box 7590AX.
After 1 or 2 days the Smart Lock will lose the connection and I have to disconnect the batterie to get WLAN again. Reset the Router or only disable the WLAN of the Smart Lock will not help.
Support told me to try the Beta Firmware, but same problem here. Am I the only one with this Problem?
Original post has been updated with the additional information on using the compatible App beta versions:
Note:
Please use this firmware in combination with the most recent App beta versions:
Please install the App beta as well to get the full experience in utilizing the new remote access capabilities of your Smart Lock (4th Generation).
1 Like
Since the current beta update the lock looses the WiFi connection. Even a restart of the lock does not help.
Only if I restart the fritzbox 7580 it connects to the WiFi.
1 Like
I am trying to enable the debug mode on my SmartLock 4 Pro with door sensor. The lock is running Beta 4.1.3 and I am using TestFlight iOS app 2024.2.1 (2506), but when I click 6 times on the Functions and Configuration header it tells me I need to run the latest software on the SmartLock. What to do?
BTW the reason I need to run Debug mode is that I can use the lock with the front door in our small theater that has a “panic” handle on the inside that unlocks the door at all times, whereas the outer handle only opens the door when it is unlocked (either by key or by somebody using the inside handle before.), see Notification or Auto-Calication for cylinders with panic function
1 Like
1 Like
I was only able to activate remote access via Thread for one of my two Smart Lock 4.0 Pro. On the second device, “activating remote access…” spins for a few seconds, then disappears and the switch remains disabled.
1 Like
Original post has been updated with release notes for the Smart Lock Beta 4.1.4 and Smart Lock Beta 4.1.5.
These Beta versions include several stability improvements for the remote access connection via Thread as well as for the WiFi connection.
We kindly ask all of you to update your Smart Locks manually with the Nuki App to version 4.1.4 and let the update to the version 4.1.5 then happen automatically over night.
As usual please provide your feedback via this channel - thank you!
Additional information on the new Smart Lock firmware and the remote access capabilities
With the new firmware the Smart Lock implements the ability to provide the full remote access capabilities via the Nuki app by using the Thread uplink from a Matter pairing if it is supported by your Matter hub*. There are several ways on how this feature can be enabled, depending on the Smart Lock variant and its surroundings:
Option 1 - Smart Lock with Nuki Bridge
If your Smart Lock is paired to a Nuki Bridge you can cut this connection by opening the Matter settings in the Nuki App and clicking onto the button Delete Bridge connection, after that the remote access via Matter is automatically established. If you have a non Pro Smart Lock a one-time payment is necessary to activate it.
Option 2 - Smart Lock with activated WiFi
If your Smart Lock is connected to WiFi it will automatically close this connection and establish the remote access connection via Thread. If the Thread network does not provide an internet connection or becomes unavailable it will continue to use WiFi.
Option 3 - Smart Lock is connected via Thread, but shall be changed to WiFi
If you want to change the remote access connection from Thread to WiFi you have to simply disable the Remote Access in the Matter settings. After that ensure that WiFi is correctly set up.
Option 4 - Smart Lock is connected via Thread, but shall be changed to Nuki Bridge
If you want to change the remote access connection from Thread to a Nuki Bridge you have to simply pair the Nuki Bridge using the Nuki app. This will automatically turn off the remote access via Thread
*Please keep in mind that the remote access via Thread is for now only supported by Apple devices (HomePod, HomePod Mini, Apple TV) and Home Assistant.
I still cannot enable debug mode after upgrading Smart Lock Pro 4 to 4.1.5, get the same message that I should upgrade it first.
Would it possibly be different when I try from an Android device instead of iOS?
Hi, with version 4.1.4 lock disconnects randomly from matter. HA matter addon shows:
2024-02-10 15:22:45 core-matter-server matter_server.server.device_controller[131] INFO Attempting to resolve node 8… (attempt 2 of 2)
2024-02-10 15:23:16 core-matter-server chip.DIS[131] ERROR Timeout waiting for mDNS resolution.
2024-02-10 15:23:30 core-matter-server chip.DIS[131] ERROR OperationalSessionSetup[1:0000000000000008]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout
2024-02-10 15:23:30 core-matter-server matter_server.server.device_controller[131] WARNING Unable to subscribe to Node 8 as it is unavailable, will retry later in the background.
2024-02-10 15:24:10 core-matter-server matter_server.server.device_controller.[node 8][131] INFO Setting up attributes and events subscription.
2024-02-10 15:24:20 core-matter-server matter_server.server.device_controller.[node 8][131] INFO Subscription succeeded
After removing and inserting the batteries it connects again (done at 15:24h).
Randomly online stops working but it is available with matter.
Same here.
Thread remote connection is sometimes lost. Firmware 4,1.5. Reconnection only works by removing the Locks battery for some seconds.
Don’t know exactly if this would happen in FW 4.1.3 too…. as this version runs only for 3-4 days. But during this testing period it never happened in 4.1.3.
In 4.1.5 it happened 2 times in one day.