![]() ![]() The installed device interacts with this event node. Whenever a user installs a SmartApp, they typically will select the devices to be used on the SmartApp. This node is registered as a subscriber through the Automation Node. Endpoint (Required)Īn Endpoint that should be invoked during execution. Properties - Name (Required)Ī Name for the WebHook endpoint. A WebHook endpoint in this context is a web services application which can receive incoming HTTP POST requests. The Automation node handles lifecycles of SmartApp. This node represents the WebHook Endpoint of SmartApp. The List of Capabilities provided by this Device.ĭetermines if this Device supports the specified capability name. Properties - Name (Required)Ī label of the Name assigned by the user. Find more information about the Capabilities of SmartThings. This node has a capability that represents a device feature. Event, Condition and Action nodes need to know which devices will subscribe to the SmartThings Cloud or commands. In this flow, You need to choose a device for automation. This node represents an installed device. You can extend the experience using external APIs.You can command the Device by placing an Command node.You can read the state of the device through the Status node.After that, implement the logic that corresponds to the autorun rule.Enter the web-hook URL through the Automation node.Place the Device Profile node and determine the required capability.In general, the SmartThings Automation is designed in the following order. Event nodes for device subscriptions, Status nodes for device status checks, and Command nodes for device commands are provided. Or simply deploying an Automation node that implements the SmartApp lifecycle without coding. The SmartThings nodes provided in the Automation Studio allows you to wire installed devices to implement autorun rules without any code. Integrating SmartThing's automation requires an understanding of the SmartApp lifecycles and implementing its protocol.
0 Comments
Leave a Reply. |