Download as PDF, PPTX
![if (!client.connected()) {
client.connect("arduino");
}
client.loop();
char s[10];
itoa(get_temperature(), s, 10);
client.publish("temp", s);
on Arduino: publishing](https://image.slidesharecdn.com/aaa-130809162948-phpapp01/75/Making-things-that-work-with-us-Distill-42-2048.jpg)
![if (!client.connected()) {
client.connect("arduino");
}
client.loop();
char s[10];
itoa(get_temperature(), s, 10);
client.publish("temp", s);
This is called a topic,
and it is where we publish
data on MQTT.
on Arduino: publishing](https://image.slidesharecdn.com/aaa-130809162948-phpapp01/75/Making-things-that-work-with-us-Distill-43-2048.jpg)
Uploaded byMatteo Collina
Making things that work with us - Distill
The document discusses the Internet of Things and how devices and applications can communicate. It describes how devices often use lightweight protocols like MQTT that are optimized for low-power connectivity and publishing data, while applications typically use REST APIs. It then introduces Ponte, an open-source bridge that allows REST applications to access MQTT devices by translating between the two protocols. Ponte uses Node.js, MQTT.js, and Mosca to provide both an MQTT broker and REST interface for bridging the divide between "things" and web applications.
More Related Content
Similar to Making things that work with us - Distill
![[Forward4 Webinar 2016] Building IoT Prototypes w/ Raspberry Pi](https://cdn.slidesharecdn.com/ss_thumbnails/raspberrypiwebinar-171022063713-thumbnail.jpg?width=640&height=640&fit=bounds)
Making things that work with us - Distill
- 1.
- 2.
- 3.
- 4. Did you see itcoming http://www.flickr.com/photos/12738000@N00/360231193/
- 5.
- 6.
- 7. 7:11 PMiPad How dowe #code an App?
- 8. 7:11 PMiPad We #codea response to some kind of user action
- 9. Pop-up Dialog OK This messagecome from the server! Cancel Web ServerTap We #code a remote web server
- 10. Web and Mobile appsare based on HTTP REST
- 11.
- 12. What's next (hint: it'sa big number) X0.000.000.000
- 13.
- 14. X0.000.000.000 Number of connected “things”by 2020: 1.000.000.000 Number of smartphones users in 2012
- 15.
- 16. http://500px.com/photo/4766384 In the future,this chain will be connected to the Internet
- 17.
- 18. http://500px.com/photo/26425201 We want to#code the real world.
- 19. Arduino is anopen source microcontroller that you can use to hack things http://www.flickr.com/photos/mattrichardson/5029708468/
- 20.
- 21. Control my house from GTalkor Twitter Goal:
- 22. I want to chatwith my house
- 23. >: hi house himatteo >: what's the temperature? 36 >: turn airconditioning on consider it done!
- 24. >: 4 815 16 23 42
- 25. Hubot © 2012GitHub Inc. All rights Enter Hubot
- 26. Hubot © 2012GitHub Inc. All rights A programmable robot that can receive commands through chat
- 27. We can superchargemy house with hubot
- 28. We can superchargemy house with hubot My house needs to: 1. publish sensed data to the web 2. receive commands from the web
- 29. Our control room isin the Cloud How can we send and receive the updates
- 30. In order tosend commands to Things from the Web, we need to: 1. subscribe the Thing to some event 2. publish the new event
- 31.
- 32. In order topublish live data, we need to: 1. sense it 2. send it in the cloud 3. build a web API to access it
- 33. Pidgeons are nota communication protocol See RFC1149 http://500px.com/photo/32895129
- 34.
- 35. We need afast, binary protocol http://www.flickr.com/photos/grrphoto/305649629
- 37. • Binary • Publish/Subscribe •Free • Standard (in a few months) • Offline/Disconnected mode
- 38. • 93x fasterthroughput • 11.89x less battery to send • 170.9x less battery to receive • 1/2 as much power to keep connection open • 8x less network overhead MQTT vs HTTPS for Mobile Push Notifications Source: http://mobilebit.wordpress.com/2013/05/03/rest-is-for-sleeping-mqtt-is-for-mobile/
- 39.
- 40.
- 41. on Arduino: Setup Stringserver = String("qest.me"); PubSubClient client = PubSubClient(server, 1883, callback);
- 42. if (!client.connected()) { client.connect("arduino"); } client.loop(); chars[10]; itoa(get_temperature(), s, 10); client.publish("temp", s); on Arduino: publishing
- 43. if (!client.connected()) { client.connect("arduino"); } client.loop(); chars[10]; itoa(get_temperature(), s, 10); client.publish("temp", s); This is called a topic, and it is where we publish data on MQTT. on Arduino: publishing
- 44. Your “thing” speaksMQTT. Your App speaks HTTP. http://500px.com/photo/35382862
- 45. Your App cannotserve two masters. http://500px.com/photo/35382862
- 46. http://500px.com/photo/31083423 We need aBridge between the Web and the “Things” world
- 47. (bridge in Italian) http://eclipse.org/proposals/technology.ponte/ http://github.com/mcollina/ponte AM2M/IoT bridge for REST developers
- 48. • MQTT broker •REST interface • can be deployed on top of a lot pub/sub systems and databases • built in node.js ponte
- 49. ponte’s pillars • Node.js •Ascoltatori, the pub/sub library for node backed for every broker out there! npm.im/ascoltatori • Mosca, the multi-transport MQTT broker for node.js. npm.im/mosca • MQTT.js, the MQTT library for node: npm.im/mqtt
- 50.
- 51. TL;DR • The Internetof Things will be big • Devices need binary formats and pub/sub protocols • Apps are built on top of REST APIs • Ponte does both
- 52. Matteo Collina (matteo.collina2@unibo.it) ThankYou! @matteocollina http://www.flickr.com/photos/axel-d/479627824/