We have published new documentation for Scenes, an ARTIK cloud services feature that allows you to use Actions in concert without writing complex Rules. Read about Scenes here.
A Scene is a group of Actions sent to one or more devices at the same time. The devices in a Scene can belong to different device types. For this reason, Scenes are perfect in real-world contexts that call for the activation of several kinds of devices, but not necessarily interactions between them. These might include:
- An “at home” Scene that unlocks the door, turns on several lights, and raises the thermostat temperature.
- An “away from home” Scene that locks all doors, turns off all lights, and turns down the thermostat.
- A “cooking” Scene that turns on the kitchen light and radio.
A Scene is unlike a device in that it does not have a state (such as on/off). A Scene is comparable to a switch that activates the corresponding state changes on devices in the Scene. To “reverse” the effects of a Scene, you would create a separate Scene to send the appropriate state changes.
Note that Actions in a Scene must conform to certain rate limits!
If you are familiar with how Rules are written, Scenes are easy to understand. A Scene includes a name, description, and list of Actions to send to devices. Actions in a Scene are formatted identically to Actions in a Rule body. An Action can be sent to a single destination device that you specify, or to all devices belonging to a certain device type.
Activating a Scene results in the Actions being sent. Deleting one of the destination devices causes a Scene to become invalid. To learn about an invalid Scene, you call one of the APIs to list Scenes and see the invalidation timestamp and error code that are returned.