FAQ

404s from the Connected Products Web API

If the Connected Products Web API returns a 404 on any of the endpoints, please ensure that the device is activated. You will need to activate a device before the API returns any information about your lock.

Why do I get 404 Not Found InvalidActivationCode when I call the Connected Products API to activate my lock?

First, verify that you have the correct Device ID and Activation Code. If you do, this problem is likely occurring because the lock is already activated in another platform. If it is active in a Vault Enterprise account, you will need to delete it from that account and contact Master Lock to clear the provisioning on that lock.

When locks are activated, they are provisioned to only be used within the platform associated with that license. It is likely the lock you have has already been provisioned to another platform, such as Vault Enterprise. You will need to delete the lock from the other platform and contact Master Lock to release it to be moved into your platform.

My Temporary Code Isn't Working

• Ensure that the time on the lock is correct. This can be corrected by communicating with the lock via the SDK (with an access profile with the WriteTime permission).
• Ensure that the KeyNumber is correct.

Can I register and use a lock with the SDK and other Master Lock Vault platforms?

Once a lock is registered in either an App or the SDK, it cannot be registered again in another platform. This is a security design to prevent security gaps that could be exploited as the lock changes platforms and accounts.

In unique circumstances we can facilitate different SDK models for channel partners, please contact us to learn more.

Can our app communicate directly with the locks using direct Bluetooth commands?

No direct Bluetooth communication commands are supported; all lock communications must be executed using the included SDK libraries. This is required to ensure the security of all communications, which are encrypted using proprietary methods, and simplifies your experience interacting with locks.

Does application have any control over sending location data to the Master Lock platform?

Location data transmission to Master Lock is done automatically within the SDK. We transmit and store all SDK lock location data anonymously and do not share the data with anyone. If a customer has a preference to have this turned off it can be disabled through the SDK license Master Lock provides.

What is the basic workflow to register and communicate with a lock via SDK?

Call the Connected Products API to activate the lock (one-time), then create an Access Profile. With the Access Profile you can open a session with the lock through the mobile SDK and start executing commands as needed, such as unlock.

How are users created and managed?

Users should be created and managed in your own app. In the SDK, access profiles will be created and linked to your users with unique IDs.

Can Xamarin or similar cross-platform app development platforms be used with the SDK?

Yes. However, you will need to wrap the iOS and Android SDKs in a parent class that will choose the appropriate framework to use based on the device the app is running on.

See the Xamarin binding documentation.