WiFi lock can connect directly to WiFi network, gateway is no longer needed. After successfully configured the WiFi lock, you can manage the lock remotely via the cloud APIs, the request URL and parameters are the same with the "Gateway APIs".
You can add the WiFi lock with Sciener APP to try it.
You may also develop your own APP base on our APP SDK to initialize the WiFi lock，refer to: APP SDK lock inerfaces for the details.
（1）Initialize the WiFi lock with APP SDK, the lock will automatically connect to the server and registered itself to the cloud if it's successfully configured.
（2）Request cloud API Update WiFi lock network to upload network information to the cloud,
You may query the network information of WiFi lock via cloud API: Get the detailed info of a Wifi lock.
The sleep mode is off on default, the WiFi lock will maintain a persistent TCP connection with the WiFi lock server in this mode, and the lock is ready to receive commands from cloud server.
When sleep mode is turned on, the WiFi lock will only connect to the server when the lock having something to notify the cloud server, for example, when there are unlocking records to be uploaded. In this mode you can't issue commands from cloud server，for example: -3035 error code will be returned when you request Unlock API.
You can turn on or off the powering saving by our APP SDK, refer to APP SDK lock inerfaces, and synchronize the setting to cloud server by requesting Modify lock settings API.
When the WiFi lock is in sleep mode, it allows the user to asynchronously initiate a remote operation request, which will be placed in a cache queue and sent when the WiFi lock wakes up and connects to the server.
For example, when the WiFi lock is in sleep mode and asynchronous commands are issued to add a custom password, the request will be successful immediately and the corresponding password ID will be returned, but the status of the password is "Adding" and it has not been added to the lock yet.
When the WiFi lock wakes up and reconnects to the server, the server sends out the cached commands, if the password is successfully added ("4" for "addType"), the corresponding password status changes to "Normal", and if it fails to be added, the status changes to "Failed to be added", and when it fails to be added, the third-party application will be notified through the callback address if it has been configured. If the application has configured a callback notification address, it will notify the third-party application through the callback address.