Background:
Because there are many components in motion, we've compiled a list outlining requirements, clarifications, and areas of responsibility to ensure the seamless integration between Inlet and the lock system.
Read more about the security principles for Inlet and the connections to locks here.
Practical and Technical Requirements:
- Nuki locks and equipment is installed and fully commissioned in the usual manner by the installer.
- Make sure the bridge is installed and configured so the lock can communicate to the internet
- Enable Nuki WEB as described here: https://support.nuki.io/hc/en-us/articles/360016485718-How-to-activate-and-deactivate-your-Nuki-Web-account
- Add your individual locks to Nuki WEB as instructed here: https://support.nuki.io/hc/en-us/articles/360016485738-Add-your-Nuki-device-to-Nuki-Web
- Go to your Nuki WEB dashboard: https://web.nuki.io/
- Inside your Nuki WEB dashboard, click API on the left side.
- Give it a useful name, Inlet or similar, then make sure it has at least the right to "View devices","Operate devices" and "View anbd manage authorizations".
- Click "SAVE" in the top right corner, and then you will be presented with an access token.
- Inlet needs receive the following to email support@inlet.tech (using PrivateBin ):
- Customer Name
- Information on what locks and lock groups Inlet should set up.
- Nuki Api token
- Inlet retrieves IDs from the locks to configure Inlet with the locking system.
- Inlet provides information to the main system/booking system for testing.
- Inlet requires a minimum of 2 weeks of testing with the main system/booking system after Inlet has received everything.