In general: I am experiencing the same problem since the update to 2.0.6, although it worked with an earlier beta version 2.0.6-AU like a week ago.
I strongly advise anyone having these problems to enable their debug mode (Go to “Help” → “Debug Mode”) in your Nuki App, take screenshots of your “Last Auto Unlock” screen and send your Nuki-Debug-Log with as much and as detailed information as possible to contact@nuki.io
For example including the exact timestamps when you expected an AU that did not fire etc. is very helpfull for the dev team.
The more people we get to deliver their log and detailed input to the devs, the higher is the chance to get this fixed mid to long term as the AU feature is dependant from many circumstances.
@nirmalts : I believe since Android 8 every app is somewhat “suffering” from a very restrictive energy plan that limits the usage of certain Android services like GPS, Bluetooth etc.
The most common way to work around this restriction is to keep the app alive which also leads to this permanent notification you mentioned. So as the Nuki team of course is very eager to improve their service they now implemented this as a part of the solution to provide a reliable Auto-Unlock service on Android devices.
If they remove the permanent notification, the app will no longer be able to provide anything that comes even close to a reliable AU service.