NAT64 worked perfectly fine on my V3…
… but on my V4 it’s gone. Nuki app shows that there’s no connection between the lock and the cloud:
The setting is also missing in the AWA:
Mentioned here and I can confirm that I had this setting before:
NAT64 worked perfectly fine on my V3…
… but on my V4 it’s gone. Nuki app shows that there’s no connection between the lock and the cloud:
The setting is also missing in the AWA:
Mentioned here and I can confirm that I had this setting before:
That’s definitely not good ![]()
As a minimum you’d expect everything to be the same if not better on v4 (excepting obviously zwave).
Other than this how is the v4 compared to v3?
Faster response times / lower latency for sure. On the V3 it was almost instant, now it’s what you could consider as instant.
Excellent, that’s good to hear.
And how easy was the hub swap/restore? I’m on soft limit with v3, do you know does the extra memory give more headroom in that respect? Thanks in advance
It took longer to open the box than to perform the Hub Replace itself. Data transfer took maybe 20 seconds, and the devices were back online a minute later. It’s comparable to a hub reboot - a very slick experience overall.
I don’t have many drivers installed anymore, thanks to Matter. I once hit the soft limit when I had an additional Matter sensor driver installed on my V3, but it’s OK now.
Sounds excellent ![]()
I found another user who owns both hubs - the V3 and the V4. He confirmed that the V4 is missing NAT64 support. Hopefully, this isn’t a fundamental issue, since NAT64 will become increasingly important in the near future.
Here are two screenshots he provided:
V4:
V3: