nottsjs / speakers

A repo for organising talk proposals and discussing talks with speakers
9 stars 0 forks source link

Community Project Evening! #61

Closed Codesleuth closed 4 years ago

Codesleuth commented 4 years ago

Our community has many skills, and with many skills comes a huge variety of possibilities of things we can make together!

For this event I would like to propose a problem statement and guided solutions, and provide assistance along the way. The goal is to produce a working solution prototype within 2 hours, adding more features as time permits.

The problem

I would like to monitor the temperature of a room which contains some temperature-sensitive items. I travel a lot and would like to check the temperature often, from anywhere, so I know if there will be issues when I return.

Equipment

For this problem, I have a Espruino Pixl.js available which contains sensors and is able to connect to a computer via Bluetooth LE. Programming the device is as easy as pairing it and developing directly to it using the online editor. Tutorials exist to assist with this: http://www.espruino.com/Pixl.js#tutorials

Project Management

Essentially this is a group project that can be divided into three groups:

  1. An IoT group who will prepare the device and write the code + connectivity to enable real-time temperature sensing.
  2. A cloud/API group who will be responsible for receiving data, storing it, and providing it to consumers. I suggest using AWS functions to collect data, RDS or queues for storage, and another set of functions for data retrieval, but this is open to do whatever you see fit.
  3. A UI group who will be responsible for providing a way for users to see the data, whether this be web, mobile, or another IoT device.

Expected Timekeeping

  1. 15 minutes standup - ideas capture & groups setup
  2. 15 minutes settling in - tooling setup e.g. decide which laptops to run, how your group will function (pairing?), decide on where to store code, which account to use etc
  3. 30 minutes of hacking in groups - get something working for your group e.g. get the sensors working, get an AWS account set up with a sample function, get a website running/hosted that displays a dummy number
  4. 10 minutes standup - share where your group is at, discuss any problems, plan how to procede
  5. 30 minutes collaborative hacking across all groups - get it working all together!
  6. 20 minutes live demo and Q&A