{"__v":12,"_id":"573df0387fe1642200f2a21f","category":{"project":"573cd7a447337f0e00b6d83c","version":"573cd7a447337f0e00b6d83f","_id":"573df02eb3f88f0e00dcae98","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-19T16:56:14.991Z","from_sync":false,"order":0,"slug":"the-octoblu-platform","title":"The Octoblu Platform"},"parentDoc":null,"project":"573cd7a447337f0e00b6d83c","user":"5564f227f0f70f0d00a9ab20","version":{"__v":10,"_id":"573cd7a447337f0e00b6d83f","project":"573cd7a447337f0e00b6d83c","createdAt":"2016-05-18T20:59:16.635Z","releaseDate":"2016-05-18T20:59:16.635Z","categories":["573cd7a447337f0e00b6d840","573df02eb3f88f0e00dcae98","573df0b11ad1a30e00a84ee7","573df1dd480b75380063ce50","573df21f7fe1642200f2a22c","573df2271ad1a30e00a84ef1","573e3eec53c55617004d4a9f","573f352f804f901700a9e109","573f3bcb87cbd20e00208e2b","573f3e5c87cbd20e00208e3c"],"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":"2016-05-19T16:56:24.620Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"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.\n\nMeshblu allows communication across disparate networks, protocols, and even other IoT platforms.\n\nMeshblu is the backbone of the Octoblu platform. Almost every action that is taken is handled by Meshblu.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Example\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/JMu1DNiyRb2uyolifIbq_Screen%20Shot%202016-05-19%20at%2011.04.13%20AM.png\",\n        \"Screen Shot 2016-05-19 at 11.04.13 AM.png\",\n        \"1586\",\n        \"1450\",\n        \"#5ca2d9\",\n        \"\"\n      ],\n      \"border\": true,\n      \"sizing\": \"smart\"\n    }\n  ]\n}\n[/block]\nHere is a simple flow, a Trigger to a Debug node. When the trigger is clicked, a series of Meshblu APIs are used to process the trigger, and send the result back to the debug node.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/g2vAAl08QpOmIc9QB3S9_Overview%20Meshblu%20Example.svg\",\n        \"Overview Meshblu Example.svg\",\n        \"0\",\n        \"0\",\n        \"#323232\",\n        \"\"\n      ],\n      \"sizing\": \"full\"\n    }\n  ]\n}\n[/block]\nAll communication amongst the different parts of the Octoblu platform are handled by Meshblu.\n* The web browser generates a Meshblu message that represents the button on the trigger, creating an HTTP POST request to the Meshblu HTTP API\n* Meshblu delivers the message to the Flow device\n* The Flow device has a Webhook message forwarder that forwards the message via an additional HTTP POST to the Flow Engine web service\n* The Flow Engine processes the message, and generates a response message, addressed to the Flow\n* The Octoblu Designer is subscribed to the Flow messages and broadcasts, connected through the Meshblu Firehose\n* The Designer receives a copy of the message from the Flow and updates the debug node in the web browser\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"More Information\",\n  \"body\": \"To lean more about Meshblu, visit [https://meshblu.readme.io](https://meshblu.readme.io)\"\n}\n[/block]","excerpt":"","slug":"meshblu","type":"basic","title":"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. Meshblu is the backbone of the Octoblu platform. Almost every action that is taken is handled by Meshblu. [block:api-header] { "type": "basic", "title": "Example" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/JMu1DNiyRb2uyolifIbq_Screen%20Shot%202016-05-19%20at%2011.04.13%20AM.png", "Screen Shot 2016-05-19 at 11.04.13 AM.png", "1586", "1450", "#5ca2d9", "" ], "border": true, "sizing": "smart" } ] } [/block] Here is a simple flow, a Trigger to a Debug node. When the trigger is clicked, a series of Meshblu APIs are used to process the trigger, and send the result back to the debug node. [block:image] { "images": [ { "image": [ "https://files.readme.io/g2vAAl08QpOmIc9QB3S9_Overview%20Meshblu%20Example.svg", "Overview Meshblu Example.svg", "0", "0", "#323232", "" ], "sizing": "full" } ] } [/block] All communication amongst the different parts of the Octoblu platform are handled by Meshblu. * The web browser generates a Meshblu message that represents the button on the trigger, creating an HTTP POST request to the Meshblu HTTP API * Meshblu delivers the message to the Flow device * The Flow device has a Webhook message forwarder that forwards the message via an additional HTTP POST to the Flow Engine web service * The Flow Engine processes the message, and generates a response message, addressed to the Flow * The Octoblu Designer is subscribed to the Flow messages and broadcasts, connected through the Meshblu Firehose * The Designer receives a copy of the message from the Flow and updates the debug node in the web browser [block:callout] { "type": "info", "title": "More Information", "body": "To lean more about Meshblu, visit [https://meshblu.readme.io](https://meshblu.readme.io)" } [/block]