Keg.io
•
1 like•1,084 views
This document summarizes an experiential analysis of developing a Node.js and Arduino-powered keg monitoring system called keg.io while under the influence of beer. It describes how earlier versions of keg.io used Node.js to communicate with Arduinos via serial connections and how newer versions leverage the cloud. It also provides an example of a typical workflow involving monitoring keg temperature and tap activity like drink scans and pours. The goals are to make the project openly contributable and deploy it in many developer offices.
Recommended
More Related Content
Viewers also liked
Viewers also liked (15)
Similar to Keg.io
Similar to Keg.io (20)
Recently uploaded
Recently uploaded (20)
Keg.io
- 1. Experiential Analysis of the Ballmer Peak: Node.js, Arduino, and Beer
- 2. keg.i
- 3. Likes beer
- 4. Likes beer
- 8. Yes, this is in Excel
- 10. What is keg.io?
- 11. + +
- 15. Why build this?
- 16. NO F-ING IDEA
- 17. Dylan Carney Garrett Patterson Carl Krauss
- 26. How’s it work?
- 27. v1: node.js talks serial
- 28. The Cast ardui node no .js se rver serial cable web brow ser
- 29. v2: node.js and the cloud (persistent, seattle-style)
- 30. The Cast ardui node no .js se rver web brow ser
- 31. A typical day in the world of keg.io
- 32. Brrrr, 42° in here.. PUT /api/kegerator/1111/temp/42
- 33. Hey clients listening to 1111, she’s 42° (websocket)
- 35. Hey, card scan! GET /api/kegerator/1111/scan/440055F873
- 36. Ok, let that guy drink (HTTP 200 response) GET /api/kegerator/1111/scan/440055F873
- 37. Hey clients listening to 1111, Chris just scanned (websocket)
- 39. ok, 11oz. Got it. (HTTP 200 response) PUT /api/kegerator/1111/flow/1100
- 40. Hey clients listening to 1111, Chris poured 11oz (websocket)
- 42. G A B- T IC E K I DAT W E T A I K E ST LES A P A P C FI SO
- 43. DEMO
- 44. What’s next?
- 45. More stats and data visualizations TA DA I A P
- 47. Too many ideas!
- 48. Too many ideas!
- 49. Two Goals
- 50. Get to the point where anyone can contribute to the project T IC AT A A D ST LES P I FI A
- 51. Get one setup in as many nerdy, developer-filled offices as possible (your office?)
- 52. THANKS!
Editor's Notes
- Hi. So, we’re going to talk about keg.io now and this is probably going to be the best talk you’ve seen all day.\nWhat’s keg.io? First, it’s about beer.\n
- Hi. So, we’re going to talk about keg.io now and this is probably going to be the best talk you’ve seen all day.\nWhat’s keg.io? First, it’s about beer.\n
- And who doesn’t like beer, right?\n
- This guy likes beer\n
- You know what’s funny? One of my coworkers asked me how many hours I’ve been putting in to this project. When I told her, she said I needed to find a girlfriend.\n
- I’m Chris Castle\n@crc\nAnd I work at...\n
- Simply Measured.\nI’m a Product Manager\nBut on the inside I’m a big nerd.\n
- We make software that pumps out beautiful reports\n
- \n
- So what is keg.io?\n
- keg.io is node.js + arduino + beer\n
- We’ve got this kegerator with a whole bunch of sensors attached to it\n
- We’ve got an Arduino microcontroller, which talks to all the sensors and valves\nIt’s 8-bit and kind of dumb and i have a love/hate relationship with it\n
- And then we’ve got a node.js server that chats with the Arduino\n
- So why did we build this thing?\nWell? My never-ending desire to start new projects that I never finish?\n
- No freaking idea.\nSeriously\nI think about it now, and there are so many reasons NOT to work on it\nThere are so many OTHER things I could be doing with my time:\njob\nfriends\nfamily\nhouse chores\nexercise\n\nBut I love this shit.\n
- I get to hang out with these three guys.\nCarl had worked with Arduino before.\nGarrett actually had some design sense and knew how to make GUIs.\nDylan is just a better developer than all of us.\nAnd we all like beer.\n
- So the genesis of keg.io is mustaches.\nWe hatched the idea while growing mustaches for a company party.\nSome of us were more successful than others.\nWe thought it would be great to build this for the “Stache Bash” at the end of the month.\n
- So we figured we’d get a kegerator from Amazon, an Arduino, some valves, some chips, write some code, and wire it all up.\nHow hard could that be?\n
- So we figured we’d get a kegerator from Amazon, an Arduino, some valves, some chips, write some code, and wire it all up.\nHow hard could that be?\n
- So we figured we’d get a kegerator from Amazon, an Arduino, some valves, some chips, write some code, and wire it all up.\nHow hard could that be?\n
- So we figured we’d get a kegerator from Amazon, an Arduino, some valves, some chips, write some code, and wire it all up.\nHow hard could that be?\n
- So we figured we’d get a kegerator from Amazon, an Arduino, some valves, some chips, write some code, and wire it all up.\nHow hard could that be?\n
- A lot harder than we thought.\nMany late nights leading up to the Stache Bash, but we got it done.\n
- \n
- \n
- So in v1 we had the arduino talking to the node.js server over serial.\nThere’s the arduino connected to all the sensors in the kegerator,\nThe node.js server sitting beside it,\nand a web browser that had to be able to hit the server.\nIt was kinda flakey.\nIt was good at crashing and not letting anyone have beer, and you’d be amazed at how angry people get when their access to beer is cut off.\nIt was very good incentive to make sure our code was either bug-free or failed gracefully.\n
- \n
- Our cast, again. Pretty similar.\nThis time we had the arduino and node.js server talk to each other over the internet.\nThe node.js server sits in AWS.\nThe arduino can be anywhere it can get wifi.\nThe browser just needs to be able to access the node.js server, so that’s pretty much anywhere (assuming we set up our security groups correctly)\n
- \n
- This put request tells the node.js server that it’s 42 degrees inside kegerator 1111\n
- The node.js server then sends a websocket message out to all clients (i.e. web browsers) listening for updates for kegerator 1111\n
- Here’s one of those web browsers\nAnd it updates the temperature\n
- This get request tells the node.js server that an RFID card with this ID was scanned at kegerator 1111\n
- The node.js server does a lookup in its database, sees that this is a valid RFID card ID, and responds with a 200 to tell that kegerator that it’s ok to let that person drink.\n
- The node.js server also sends a websocket message out to clients listening to updates for kegerator 1111.\n
- Then the kegerator pipes up again saying that 11oz was dispensed\n
- Node.js stores this...\n
- ...and then reports it to the clients\n
- And the GUI updates\n
- So here are all the pieces.\nThis is the money shot here. This is why I’m excited about node.\nThe node server has 4 roles\nstatic file server: the HTML, CSS, JS for the GUI\nkeg api: the HTTP interface that kegerators talk to\ndata api: the HTTP interface the GUI talks to to show graphs and data about beer consumption\nand websocket server: the way the GUI gets notified that something new happened\nAll of these were so easy with node, and they demonstrate node’s strength in an event-driven context.\n
- So let’s try it out and hope the demo gods look kindly upon us\nFirst I’m going to show the node.js server running locally and a test client running locally. Think of the test client as a kegerator mock. We couldn’t always be near a kegerator while working on this so we made a little node.js script that acts like a kegerator.\n\nNow are you ready for the real thing? Here, the server is running at AWS, and the client is this kegerator with its arduino, right here.\n
- So what’s next for keg.io?\n
- More stats and data visualizations.\nRemember the Data API part?\n
- You know how git or github can do something after a successful git commit? That’s called a post-commit hook.\nWell, I’m coining the term “post-pour hook”.\nThis is going to allow a user to provide a URL to which node.js will make a POST request upon a successful beer pour.\nYou could make it tweet about your pours, do you foursquare check-in, keep a personal diary of your drinking patterns, really anything...\n
- And I could keep coming up with new ideas until my head exploded.\n
- So I’ve kind of settled on two goals for now\n
- Get to the point where anyone can contribute to the project.\nRemember the static files? Well, those make up the GUI. We could use an admin interface, not to mention a better “currently drinking” dashboard.\nAnd we could use some charts too. So that’s the Data API.\n
- Get one setup in every nerdy, developer-filled office.\nSo hit me on Twitter or email or come talk to me if you’re interested.\n
- So that’s all I’ve got.\nThanks very much.\n
- Again, my name is Chris Castle.\nAnd, shameless plug, Simply Measured is hiring.\nWe’re looking for a Javascript, SVG/canvas, data visualization person.\n