{"_id":"57439c4f9a2c890e0028347d","project":"556742591c38390d00698087","user":"5564f227f0f70f0d00a9ab20","version":{"_id":"5567425a1c38390d0069808a","project":"556742591c38390d00698087","__v":2,"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"},"__v":3,"category":{"_id":"5567425a1c38390d0069808b","project":"556742591c38390d00698087","__v":16,"pages":["5567425c1c38390d0069808d","558f782c1311b80d00ba9d97","558f7986f795be2d00c1164f","558f8069f795be2d00c11655","558f810bf795be2d00c11657","558f82e11311b80d00ba9da1","558f850df795be2d00c1165b","558f85401311b80d00ba9da3","558f85df1311b80d00ba9da5","558f87726742610d0051c4f5","558f87f26742610d0051c4f7","558f886df795be2d00c1165f","55918fec5631432f002d357e","559191f34e50b50d0019612a","5592c8d89a68220d00f1c404","559efaebdf92223500dc50e7"],"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,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-24T00:11:59.958Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"The `config` event is emitted whenever a device is updated. Use the [`conn.subscribe`](#connsubscribeparams) API to subscribe to `config` events. In order to receive config events from a device, your connection must be authenticated as a device that is in the target device's `configure.sent` whitelist. See the [Meshblu whitelist documentation](https://meshblu.readme.io/docs/whitelists-2-0) for more information.\n\n* `device` Meshblu device that was modified\n  * `uuid` Uuid of the device that was modified\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Example config\"\n}\n[/block]\nWhen a device is updated, the config event payload will look like this:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"{\\n  \\\"meshblu\\\": {\\n    \\\"version\\\": \\\"2.0.0\\\",\\n    \\\"whitelists\\\": {},\\n    \\\"hash\\\": \\\"9OAPxo5Yq1oTYNi1szGVBBlg4xuIVni47k8JhHYlXFk=\\\"\\n    }\\n  },\\n  \\\"uuid\\\": \\\"78159106-41ca-4022-95e8-2511695ce64c\\\",\\n  \\\"foo\\\": \\\"bar\\\"\\n}\",\n      \"language\": \"json\",\n      \"name\": \"config-event.json\"\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"event-config","type":"basic","title":"Event: config"}
The `config` event is emitted whenever a device is updated. Use the [`conn.subscribe`](#connsubscribeparams) API to subscribe to `config` events. In order to receive config events from a device, your connection must be authenticated as a device that is in the target device's `configure.sent` whitelist. See the [Meshblu whitelist documentation](https://meshblu.readme.io/docs/whitelists-2-0) for more information. * `device` Meshblu device that was modified * `uuid` Uuid of the device that was modified [block:api-header] { "type": "basic", "title": "Example config" } [/block] When a device is updated, the config event payload will look like this: [block:code] { "codes": [ { "code": "{\n \"meshblu\": {\n \"version\": \"2.0.0\",\n \"whitelists\": {},\n \"hash\": \"9OAPxo5Yq1oTYNi1szGVBBlg4xuIVni47k8JhHYlXFk=\"\n }\n },\n \"uuid\": \"78159106-41ca-4022-95e8-2511695ce64c\",\n \"foo\": \"bar\"\n}", "language": "json", "name": "config-event.json" } ] } [/block]