Smart Home Scene Guide

Device TYPE

action.devices.types.SCENE In the case of scenes, the type maps 1:1 to the trait, as scenes don't combine with other traits to form composite devices.

Scenes should always have user-provided names, not default 'BobCo Scene' naming. Each scene is its own virtual device, with its own name(s). User-provided names may come in from SYNC.

action.devices.traits.Scene

These are our recommendations for traits on this type of device, however you are free to mix and match from all available traits to best match your existing product functionality.

Please see each individual trait document for implementation details like required attributes, EXECUTE and QUERY.

Sample SYNC Request and Response

This is an example using the device type and traits above. It is intended to give an idea of how to build a SYNC response. If you add or remove traits, this will need to be modified to reflect those changes.

Request
{
  "requestId": "ff36a3cc-ec34-11e6-b1a0-64510650abcf",
  "inputs": [{
    "intent": "action.devices.SYNC"
  }]
}
Response
{
  "requestId": "ff36a3cc-ec34-11e6-b1a0-64510650abcf",
  "payload": {
    "agentUserId": "1836.15267389",
    "devices": [{
      "id": "123",
      "type": "action.devices.types.SCENE",
      "traits": [
        "action.devices.traits.Scene"
      ],
      "name": {
        "defaultNames": [],
        "name": "Party Mode",
        "nicknames": []
      },
      "willReportState": false,     // should be false, as there's no state
      "attributes": {
        "sceneReversible": true
      },
      // Note -- probably no device info for virtual devices.
      "customData": {
        "fooValue": 74,
        "barValue": true,
        "bazValue": "lambtwirl"
      }
    }]
  }
}
Validator

Device ERRORS

See the full list of errors and exceptions.