Sciener bluetooth lock can't connect to the Internet by itself. If you want to manage the lock remotely via network, you need a gateway from Sciener, it's a gadget which can communicate with the lock and also can be connected to the network.
The gateway will automatically search locks nearby it, and notify the gateway server about the locks it found, the gateway server will create a many-to-many relationship between the gateways and locks if the lock and gateway belong to the same administrator account. The gateway server will choose the gateway with the best RSSI to communication with the lock when user want to operate the lock remotely. A gateway can connect to many locks and there is no limits on the lock number.
You can add the gateway with Sciener APP,please refer to :G2 gateway manual.
You may also develop your own APP base on our APP SDK to initialize the gateway,refer to: APP SDK gateway inerfaces for the details. Parameter uid is needed to identify which user account the gateway belongs to when initializing gateway, it will be returned when requesting for Access Token,you may also obtain the uid by Get user id API, following are the steps:
(1)Initialize the gateway with APP SDK, the gateway will automatically connect to the gateway server and registered itself to the cloud if it's successfully configured.
(2)Request cloud API Query the init status of the gateway to confirm gateway is successfully registered in the cloud,gatewayId will be returned if it's success.
(3)Request cloud API Upload detail info of gateway to upload gateway detail information to the cloud, you'll need these information for gateway firmware update.
You can query the gateway by cloud API Get the gateway list of an account.
The gateway will automatically search nearby locks, and if they belong to the same administrator they will connect each other, no need for manually bind from the end user. So if the gateway can't find the lock nearby, please make sure the lock and gateway is added by the same user account.
You can query the relationships of gateway and lock through these two cloud APIs: Get the lock list of a gateway and Get the gateway list of a lock, they will also return the RSSI between the gateway and lock.
The gateway server will choose the gateway with the best RSSI to communication with the lock when user want to operate the lock remotely.
You can send commands to the lock via gateway remotely, all the following operations can be done remotely: unlock the lock、lock the lock,query the lock state of the lock,manage(add, delete, update) passcodes,manage(add, delete, update) cards,manage(add, delete, update) fingerprints,query battery of the lock、query and calibrate the lock time.
And lock records will be automatically uploaded to cloud,administrator of the lock will receive unlocking notifications in the Sciener APP,developers can receive lock records notification by setting Callback URL in the application's detail page of open platform, refer to: Lock records notify for the detail.
The gateway communicate with the lock through bluetooth connection, it may take several seconds for the gateway to establish a bluetooth connection with the lock. So a remote operation will take longer time or even fail when the RSSI between the lock and gateway is too weak. Break of bluetooth connection(for example: touch the lock keypad) will also cause the failure of remote operation.
Remote operation may take a long time, our timeout for requests of remote operation is 30 seconds, if you set your request to timed out in shorter time (for example, you set your request to timed out in 10s) then you may not receive the response.
Gateway and lock can only establish a unique bluetooth connection at the same time, so remote operation should be requested one by one, if a remote operation is requested when the earlier operation is not finished, it is destined to fail.