SMARTTHINGS SMARTAPP EXAMPLE CODE

For example, burglars can target a connected door lock to plant hidden access codes 1.Įarly smart-home systems had steep learning curves and complicated device setup procedures and thus were limited to do-it-yourself enthusiasts. However, attackers can manipulate smart devices to cause users physical, financial, and psychological harm. IP-enabled cameras, motion sensors, and connected door locks offer better control of home security. For instance, water flow sensors and smart meters facilitate energy efficiency. Smart-home technology has evolved beyond basic convenience functionality, such as automatically controlled lights and door openers, to provide tangible benefits. Improve productivity and collaboration with unparalleled speed, scale, and resilience. Also we (the community not me I think APIs are cool like bow ties) may come out with some really cool things to work with.Camunda Platform 8: The Universal Process Orchestrator. That will be a great way to test out some of the new APIs see what areas are missing/lacking etc. My challenge out to everyone, if you think this layer of abstraction is limiting to some experimenters build a new way to tinker with the APIs. I also strongly think it will help the development community but once again I’m biased I like this type of programming.Īs for the average experimenter I think we already assume a lot of programming knowledge there are other offerings built on the system right now that give more experimentation around home automation and less need to get into the services. So there will be the ability to build more levels of abstraction on top of this but moving down a layer I think will help us in the long run. This layer of abstraction will expect more understanding of REST and general programming. Instead of having a sandboxed quick dev web ide be the main integration point we are moving down a layer of abstraction. The way I look at it (I’m super biased so take this with a grain of salt.) is we are moving to open the core building blocks of the system and have that be the API. That pretty much takes development for the average experimeter off the table unless you’re familiar with creating webservices.

SMARTTHINGS SMARTAPP EXAMPLE CODE

I guess one of the big changes in the now the code will be written and executing on non smartthings servers, the ST platform is just going to provide hooks. In the future world with continuing advances in network technology and computing power advances and overhead optimization, it may be reduced to a fraction of that!

In the current world, it adds a few hundred milliseconds. ActionTiles already uses an intermediary cloud layer and it has not detracted from our customer’s experience. For apps with a UI, this possibly eliminates one hop, thus no increase in net latency.įinally, note that Samsung is “playing the long game” here, and likely making the assumption that cloud-cloud latencies are going to be increasingly trivial. The new API also allows callback definitions on subscriptions to be targeted directly to the developer’s front-end application. And if the 3rd party developer runs in AWS too, then with the new API, there isn’t even any significant extra network latency! So currently it is actually (I think!): HUB ST Device Handlers in AWS SmartApps in AWS … Therefore, it’s the same number of hops. You see, this already happens in the SmartThings Cloud… Device servers (even the physical hardware) are not likely to be the same servers running SmartApps! And, BTW, they already both run in AWS. I think you may be over estimating the real world impact of this distinction, actually… Instead of HUB ST CLOUD we will get HUB ST CLOUD AWS CLOUD (or private server, etc)

Smartthings smartapp example