{"_id":"59e5932cd6cc5c00248ecaf2","project":"568bdc1483d2061900d86cdc","version":{"_id":"59a72290d61777001b6c42c3","project":"568bdc1483d2061900d86cdc","__v":31,"createdAt":"2017-08-30T20:39:44.453Z","releaseDate":"2017-08-30T20:39:44.453Z","categories":["59a7236e3fe4d90025117c10","59a72eb6cb0db3001b84cfe2","59a734eb757d030019b85af8","59c0243b1b2d07001a9d2b76","59c035e42126e10028effb12","59c06c40df5b3c0010584a13","59c1a5852cabe5002641a3e7","59c2fb00b2b45c0010b7a3d7","59c32ceb9aea850010ac4130","59c32e6e190c90003cb0d12f","59c33affb2b45c0010b7aa23","59c7dfa457bd8200105444dc","59c7e975c50cf30010d712a0","59cffdef0cd4dd0010294d54","59d0622ca91a810032c8f60c","59d06733c1aec60026253065","59d174d44ac471001a07b123","59d5a5e323e6e800103defb2","59ecf1d8ed507c001c52b255","59f76fef8581dc0010593e6f","5a0c003680a35b0012c35db0","5a8358722e78660075e45f42","5a846645b5ec3a001203517e","5b258091bc7a6700033b9cb5","5b26e48e024807000315a740","5b44edff3306680003663f5c","5b468abd3d4a9e0003789111","5b468d8f3dcb6a0003c6e374","5b47b0b93d4a9e000378a33a","5b538d114ea24f00033c726f","5b6a0efe402b32000336c33f"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"0.0.0","version":"0"},"category":{"_id":"59cffdef0cd4dd0010294d54","project":"568bdc1483d2061900d86cdc","version":"59a72290d61777001b6c42c3","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-09-30T20:26:23.487Z","from_sync":false,"order":2,"slug":"platform-overview","title":"Platform Overview"},"user":"568bdbc4fe6fcc0d006dc970","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-10-17T05:20:44.558Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"A **device** is the digital representation of a connected thing. This could be a switch or a smart bulb that can be controlled through the Droplit platform.\n\nThe device record is a cloud representation of the physical attributes, capabilities, and present state of the device.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Defining Capabilities\"\n}\n[/block]\nThe capabilities of a device are defined using [Service Classes](doc:services).\n\nA device’s capabilities may be represented using multiple different Service Classes and also multiple instances of the the same Service Class (known as indexed services).\n\nSee [Service Classes](doc:services) for a detailed explanation.\n[block:api-header]\n{\n  \"title\": \"Organization\"\n}\n[/block]\nAll devices are stored in exactly one [Environment](doc:environments). The Environment can be used to group related devices together, assign access rights to users, and broadcast commands to the devices. Devices cannot be moved to a different environment after it is created (with some exceptions).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Metadata\"\n}\n[/block]\nA device can have custom metadata stored in the record. The metadata API is a powerful tool for storing additional information about devices that is useful when presenting the information to your users. For example, you can use it to assign a custom label, icon, or sort order to your device records.\n\nSee [Metadata](doc:metadata) for a detailed explanation.\n[block:api-header]\n{\n  \"title\": \"Alias\"\n}\n[/block]\nA device can be assigned a custom [Alias](doc:aliases) that can be used in place of the system assigned ID anywhere in the Droplit API. Aliases are unique within the scope of the parent container. So for a device, the alias must be unique to the environment.","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. This could be a switch or a smart bulb that can be controlled through the Droplit platform. The device record is a cloud representation of the physical attributes, capabilities, and present state of the device. [block:api-header] { "type": "basic", "title": "Defining Capabilities" } [/block] The capabilities of a device are defined using [Service Classes](doc:services). A device’s capabilities may be represented using multiple different Service Classes and also multiple instances of the the same Service Class (known as indexed services). See [Service Classes](doc:services) for a detailed explanation. [block:api-header] { "title": "Organization" } [/block] All devices are stored in exactly one [Environment](doc:environments). The Environment can be used to group related devices together, assign access rights to users, and broadcast commands to the devices. Devices cannot be moved to a different environment after it is created (with some exceptions). [block:api-header] { "type": "basic", "title": "Metadata" } [/block] A device can have custom metadata stored in the record. The metadata API is a powerful tool for storing additional information about devices that is useful when presenting the information to your users. For example, you can use it to assign a custom label, icon, or sort order to your device records. See [Metadata](doc:metadata) for a detailed explanation. [block:api-header] { "title": "Alias" } [/block] A device can be assigned a custom [Alias](doc:aliases) that can be used in place of the system assigned ID anywhere in the Droplit API. Aliases are unique within the scope of the parent container. So for a device, the alias must be unique to the environment.