{"_id":"582789abbe5c080f00a5a81a","user":"568bdbc4fe6fcc0d006dc970","version":{"_id":"582789aabe5c080f00a5a7fe","__v":10,"project":"568bdc1483d2061900d86cdc","createdAt":"2016-11-12T21:29:14.915Z","releaseDate":"2016-11-12T21:29:14.915Z","categories":["582789abbe5c080f00a5a7ff","582789abbe5c080f00a5a800","582789abbe5c080f00a5a801","582789abbe5c080f00a5a802","582789abbe5c080f00a5a803","582789abbe5c080f00a5a804","582789abbe5c080f00a5a805","582789abbe5c080f00a5a806","582789abbe5c080f00a5a807","582789abbe5c080f00a5a808","5827ea984ca29e0f00137a9e","583df597887db62f00644283","583df5d9c622791900e78da5","5845cd8763c11b250037967d","5845d13063c11b2500379681","5859e859e3306d1900126725","587aeb9a01cf3a0f008359eb","587c422af45e2d0f005e200d","587d84dc82f6f30f004ceee5"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"beta2","version_clean":"0.0.0","version":"0"},"__v":0,"parentDoc":null,"category":{"_id":"5845d13063c11b2500379681","__v":0,"version":"582789aabe5c080f00a5a7fe","project":"568bdc1483d2061900d86cdc","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-12-05T20:42:24.315Z","from_sync":false,"order":1,"slug":"platform-overview","title":"Platform Overview"},"project":"568bdc1483d2061900d86cdc","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-02-19T02:45:32.457Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"A **device** is the digital representation of a connected thing.\n\nA device is something like a switch or a smart bulb that can be controlled remotely.\n\nThe capabilities of a device are defined using services. See [Service Classes](doc:services)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Defining Capabilities\"\n}\n[/block]\nDevice capabilities are modeled using Services. A device’s capabilities may be represented using multiple services and also multiple instances of those services.\n\nSee [Service Classes](doc:services) for a detailed explanation.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Using meta-data\"\n}\n[/block]\nA device can have custom meta-data associated with it. The meta-data API is a powerful tool for storing additional information about devices that is useful when presenting the information to your users.\n\nSee [Meta data](doc:metadata) for a detailed explanation.","excerpt":"Lightbulb, Coffee Maker, Toaster, Microverse Battery and more…","slug":"devices","type":"basic","title":"Devices"}

Devices

Lightbulb, Coffee Maker, Toaster, Microverse Battery and more…

A **device** is the digital representation of a connected thing. A device is something like a switch or a smart bulb that can be controlled remotely. The capabilities of a device are defined using services. See [Service Classes](doc:services) [block:api-header] { "type": "basic", "title": "Defining Capabilities" } [/block] Device capabilities are modeled using Services. A device’s capabilities may be represented using multiple services and also multiple instances of those services. See [Service Classes](doc:services) for a detailed explanation. [block:api-header] { "type": "basic", "title": "Using meta-data" } [/block] A device can have custom meta-data associated with it. The meta-data API is a powerful tool for storing additional information about devices that is useful when presenting the information to your users. See [Meta data](doc:metadata) for a detailed explanation.