Smart building integration and device hub

Abstract

Embodiments are generally directed to systems, devices, methods, and techniques to control devices via a mobile device platform in a smart building system. Embodiments further include techniques to determine a device of the smart building system and an action to perform by the device. The techniques include establishing, a connection with a smart lock of the smart system, and communicating a request to perform the action to the smart lock of the smart system.

What is claimed is: 
     
         1 . A method, comprising:
 receiving, by a server from an application on a mobile device, an initial request to unlock a smart lock that is not persistently connected to the Internet, wherein the initial request is in response to an initial connection between the mobile device and the smart lock;   transmitting, by the server to the application, a credential to unlock the smart lock, wherein the credential is subsequently used by the mobile device to unlock the smart lock without the mobile device communicating with the server;   receiving, by the server from the application, a request to perform an action on a smart device that is not manufactured to directly communicate with the server; and   transmitting, by the server to a third-party cloud server associated with the smart device, a request to perform the action on the smart device.   
     
     
         2 . The method of  claim 1 , further comprising:
 transmitting, by the server to the third-party cloud server, a device identifier associated with the smart device to authenticate the request to perform the action on the smart device.   
     
     
         3 . The method of  claim 2 , further comprising prior to the server transmitting the request to the third-party cloud server:
 determining, by the server based on the device identifier, that the application is permitted to cause the action to be performed on the smart device.   
     
     
         4 . The method of  claim 1 , wherein the request to perform the action received from the application is based on a first format, wherein the server formats the request to perform the action on the smart device according to a second format, wherein the first and second formats are different formats. 
     
     
         5 . The method of  claim 1 , wherein the third-party cloud server causes the smart device to perform the action based on the transmission of the request to perform the action on the smart device. 
     
     
         6 . The method of  claim 1 , wherein a link associates the smart device and the smart lock. 
     
     
         7 . The method of  claim 6 , further comprising prior to the server transmitting the request to the third-party cloud server:
 determining, by the server based on the link associating the smart device and the smart lock, that the application is permitted to cause the action to be performed on the smart device.   
     
     
         8 . A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor, cause the processor to:
 receive, from an application on a mobile device, an initial request to unlock a smart lock that is not persistently connected to the Internet, wherein the initial request is in response to an initial connection between the mobile device and the smart lock;   transmit, to the application, a credential to unlock the smart lock, wherein the credential is subsequently used by the mobile device to unlock the smart lock without the mobile device communicating with the processor;   receive, from the application, a request to perform an action on a smart device that is not manufactured to directly communicate with the processor; and   transmit, to a third-party cloud server associated with the smart device, a request to perform the action on the smart device.   
     
     
         9 . The computer-readable storage medium of  claim 8 , wherein the instructions further cause the processor to:
 transmit, to the third-party cloud server, a device identifier associated with the smart device to authenticate the request to perform the action on the smart device.   
     
     
         10 . The computer-readable storage medium of  claim 9 , wherein the instructions further cause the processor to, prior to the transmission of the request to the third-party cloud server:
 determine, based on the device identifier, that the application is permitted to cause the action to be performed on the smart device.   
     
     
         11 . The computer-readable storage medium of  claim 8 , wherein the request to perform the action received from the application is based on a first format, wherein the instructions cause the processor to format the request to perform the action on the smart device according to a second format, wherein the first and second formats are different formats. 
     
     
         12 . The computer-readable storage medium of  claim 8 , wherein the third-party cloud server causes the smart device to perform the action based on the transmission of the request to perform the action on the smart device. 
     
     
         13 . The computer-readable storage medium of  claim 8 , wherein a link associates the smart device and the smart lock. 
     
     
         14 . The computer-readable storage medium of  claim 13 , wherein the instructions further cause the processor to, prior to the transmission of the request to the third-party cloud server:
 determine, based on the link associating the smart device and the smart lock, that the application is permitted to cause the action to be performed on the smart device.   
     
     
         15 . A computing apparatus comprising:
 a processor; and   a memory storing instructions that, when executed by the processor, cause the processor to:
 receive, from an application on a mobile device, an initial request to unlock a smart lock that is not persistently connected to the Internet, wherein the initial request is in response to an initial connection between the mobile device and the smart lock; 
 transmit, to the application, a credential to unlock the smart lock, wherein the credential is subsequently used by the mobile device to unlock the smart lock without the mobile device communicating with the apparatus; 
 receive, from the application, a request to perform an action on a smart device that is not manufactured to directly communicate with the apparatus; and 
 transmit, to a third-party cloud server associated with the smart device, a request to perform the action on the smart device. 
   
     
     
         16 . The computing apparatus of  claim 15 , wherein the instructions further cause the processor to:
 transmit, to the third-party cloud server, a device identifier associated with the smart device to authenticate the request to perform the action on the smart device.   
     
     
         17 . The computing apparatus of  claim 16 , wherein the instructions further cause the processor to, prior to the transmission of the request to the third-party cloud server:
 determine, based on the device identifier, that the application is permitted to cause the action to be performed on the smart device.   
     
     
         18 . The computing apparatus of  claim 15 , wherein the request to perform the action received from the application is based on a first format, wherein the instructions cause the processor to format the request to perform the action on the smart device according to a second format, wherein the first and second formats are different formats. 
     
     
         19 . The computing apparatus of  claim 15 , wherein the third-party cloud server causes the smart device to perform the action based on the transmission of the request to perform the action on the smart device. 
     
     
         20 . The computing apparatus of  claim 15 , wherein a link associates the smart device and the smart lock.