{"_id":"5564f26b1fd04c0d00dc9ab0","api":{"settings":"","url":"","auth":"required","params":[],"results":{"codes":[]}},"hidden":false,"type":"basic","updates":[],"version":"5564f26a1fd04c0d00dc9aad","category":"5564f26b1fd04c0d00dc9aae","excerpt":"machine-to-machine instant messaging","githubsync":"","link_url":"","parentDoc":null,"project":"5564f26a1fd04c0d00dc9aaa","user":"5564f227f0f70f0d00a9ab20","body":"[![Gitter chat](https://badges.gitter.im/gitterHQ/gitter.png)](https://gitter.im/octoblu/meshblu)\n\nMeshblu is the core communication layer of our offering. It is a secure, cross-protocol scalable cloud-based system enabling communication between smart devices, sensors, cloud resources, Arduinos, Raspberry Pi’s, and any other IP based hardware device, non-IP based hardware device or software API.\n\nMeshblu allows communication across disparate networks, protocols, and even other IoT platforms. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/zYIWvivvR9GITm9hlXoV_Meshblu%20Summary.svg\",\n        \"Meshblu Summary.svg\",\n        \"0\",\n        \"0\",\n        \"#323232\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nIn the scenario above, a sensor can be emitting data via CoAP. That data could be simultaneously delivered to a Machine Learning algorithm subscribed via AMQP, a users smart phone over HTTP, and a bot connected through XMPP that is configured to automatically take action if the temperature exceeds a certain threshold. The bot could send a message that would result in a webhook posting to the Temperature API. The user could also manually send the same message from their phone via HTTP that would result in a webhook to the Temperature API.\n\nEach device in this scenario only needs to know how to send and receive Meshblu messages. They don't need to implement a special API for every consumer of the information, nor do they need to know anything about the Temperature API. More devices could be added to this scenario without having to alter the code of the other devices.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Device Directory\"\n}\n[/block]\nMeshblu provides a queriable device directory API for registering and discovering nodes on the Meshblu network. Meshblu also maintains presence for each device making it easy to know what is on/offline\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Device Security\"\n}\n[/block]\nMeshblu issues a unique 36 character UUID and secret token for each device connecting to our network. These device \"credentials\" are required for authentication, API calls, and subscriptions. [More Info](/v1.0/docs/security)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Messaging\"\n}\n[/block]\nMeshblu provides near real-time messaging between devices. There are three distinct message types: broadcast, configure, message.","createdAt":"2015-05-26T22:23:39.963Z","isReference":false,"link_external":false,"order":0,"slug":"getting-started","__v":11,"sync_unique":"","title":"Welcome to Meshblu","childrenPages":[]}

Welcome to Meshblu

machine-to-machine instant messaging

[![Gitter chat](https://badges.gitter.im/gitterHQ/gitter.png)](https://gitter.im/octoblu/meshblu) Meshblu is the core communication layer of our offering. It is a secure, cross-protocol scalable cloud-based system enabling communication between smart devices, sensors, cloud resources, Arduinos, Raspberry Pi’s, and any other IP based hardware device, non-IP based hardware device or software API. Meshblu allows communication across disparate networks, protocols, and even other IoT platforms. [block:image] { "images": [ { "image": [ "https://files.readme.io/zYIWvivvR9GITm9hlXoV_Meshblu%20Summary.svg", "Meshblu Summary.svg", "0", "0", "#323232", "" ] } ] } [/block] In the scenario above, a sensor can be emitting data via CoAP. That data could be simultaneously delivered to a Machine Learning algorithm subscribed via AMQP, a users smart phone over HTTP, and a bot connected through XMPP that is configured to automatically take action if the temperature exceeds a certain threshold. The bot could send a message that would result in a webhook posting to the Temperature API. The user could also manually send the same message from their phone via HTTP that would result in a webhook to the Temperature API. Each device in this scenario only needs to know how to send and receive Meshblu messages. They don't need to implement a special API for every consumer of the information, nor do they need to know anything about the Temperature API. More devices could be added to this scenario without having to alter the code of the other devices. [block:api-header] { "type": "basic", "title": "Device Directory" } [/block] Meshblu provides a queriable device directory API for registering and discovering nodes on the Meshblu network. Meshblu also maintains presence for each device making it easy to know what is on/offline [block:api-header] { "type": "basic", "title": "Device Security" } [/block] Meshblu issues a unique 36 character UUID and secret token for each device connecting to our network. These device "credentials" are required for authentication, API calls, and subscriptions. [More Info](/v1.0/docs/security) [block:api-header] { "type": "basic", "title": "Messaging" } [/block] Meshblu provides near real-time messaging between devices. There are three distinct message types: broadcast, configure, message.