{"__v":1,"_id":"558f886df795be2d00c1165f","category":{"__v":16,"_id":"5567425a1c38390d0069808b","pages":["5567425c1c38390d0069808d","558f782c1311b80d00ba9d97","558f7986f795be2d00c1164f","558f8069f795be2d00c11655","558f810bf795be2d00c11657","558f82e11311b80d00ba9da1","558f850df795be2d00c1165b","558f85401311b80d00ba9da3","558f85df1311b80d00ba9da5","558f87726742610d0051c4f5","558f87f26742610d0051c4f7","558f886df795be2d00c1165f","55918fec5631432f002d357e","559191f34e50b50d0019612a","5592c8d89a68220d00f1c404","559efaebdf92223500dc50e7"],"project":"556742591c38390d00698087","version":"5567425a1c38390d0069808a","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-05-28T16:29:14.942Z","from_sync":false,"order":9999,"slug":"documentation","title":"Documentation"},"parentDoc":null,"project":"556742591c38390d00698087","user":"5564f227f0f70f0d00a9ab20","version":{"__v":2,"_id":"5567425a1c38390d0069808a","project":"556742591c38390d00698087","createdAt":"2015-05-28T16:29:14.412Z","releaseDate":"2015-05-28T16:29:14.412Z","categories":["5567425a1c38390d0069808b","57214d354758d90e009e6638"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-06-28T05:38:53.913Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":13,"body":"Remove a device from the Meshblu device registry. In order to unregister a target device, your connection must be authenticated as a device that is in the target device's `configure.update` whitelist. See the [Meshblu whitelist documentation](https://meshblu.readme.io/docs/whitelists-2-0) for more information.\n\n### Event: `\"unregister\"`, `query`, `callback`\n\n* `query` Query object, must contain only the `uuid` property.\n  * `uuid` UUID of the device to unregister.\n* `callback` Function that will be called with a `result`.\n  * `result` Response from the unregister call. Will contain either a `uuid` or an `error`, but never both.\n    * `uuid` Uuid of the device that was unregistered\n    * `error` String explaining the what went wrong. Is only present if something went wrong.\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"No 404\",\n  \"body\": \"In Meshblu, it is not possible to distinguish between a device not existing and not having permission to view a device. In most of the Meshblu API calls, the error in both cases yields the protocol-specific equivalent of an `HTTP 404: Not Found`. The Socket.IO API, however, returns the error `Forbidden`. This is for backwards compatibility and will likely change with the next major version release of the Socket.IO API.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Successful Response\"\n}\n[/block]\nWhen unregister is called for a device the authenticated device may modify:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"uuid\\\": \\\"26de691f-8068-4cdc-907a-4cb5961a1aba\\\"\\n}\",\n      \"language\": \"json\",\n      \"name\": \"response.json\"\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Error Response\"\n}\n[/block]\nWhen unregister is called for a non-existing device, or device the authenticated device may modify:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"error\\\": \\\"Forbidden\\\"\\n}\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]","excerpt":"Removes a device record","slug":"unregister","type":"basic","title":"Unregister"}

Unregister

Removes a device record

Remove a device from the Meshblu device registry. In order to unregister a target device, your connection must be authenticated as a device that is in the target device's `configure.update` whitelist. See the [Meshblu whitelist documentation](https://meshblu.readme.io/docs/whitelists-2-0) for more information. ### Event: `"unregister"`, `query`, `callback` * `query` Query object, must contain only the `uuid` property. * `uuid` UUID of the device to unregister. * `callback` Function that will be called with a `result`. * `result` Response from the unregister call. Will contain either a `uuid` or an `error`, but never both. * `uuid` Uuid of the device that was unregistered * `error` String explaining the what went wrong. Is only present if something went wrong. [block:callout] { "type": "info", "title": "No 404", "body": "In Meshblu, it is not possible to distinguish between a device not existing and not having permission to view a device. In most of the Meshblu API calls, the error in both cases yields the protocol-specific equivalent of an `HTTP 404: Not Found`. The Socket.IO API, however, returns the error `Forbidden`. This is for backwards compatibility and will likely change with the next major version release of the Socket.IO API." } [/block] [block:api-header] { "type": "basic", "title": "Successful Response" } [/block] When unregister is called for a device the authenticated device may modify: [block:code] { "codes": [ { "code": "{\n \"uuid\": \"26de691f-8068-4cdc-907a-4cb5961a1aba\"\n}", "language": "json", "name": "response.json" } ] } [/block] [block:api-header] { "type": "basic", "title": "Error Response" } [/block] When unregister is called for a non-existing device, or device the authenticated device may modify: [block:code] { "codes": [ { "code": "{\n \"error\": \"Forbidden\"\n}", "language": "json" } ] } [/block]