Luckily for the WiFi group, we were able to get the raspberry pies sending data to the IoT fairly easily. Dweet.io turned out to be extremely simple to use. Our prototype was coded in python, so we found a nice library that is compatible with dweet called dweepy. The code that we placed into the architecture groups state machine basically consisted of the following lines:

import dweepy  #import the necessary library

SENSOR_ID = “BAT”

dev_name = “org_pmss_berea_{0}”.format(SENSOR_ID)
dweepy.dweet_for(dev_name, PACKAGE) #PACKAGE is defined by the sensing group

The SENSOR_ID was so that each sensor had a unique identifier, that way we could tell which room that the readings were coming from. The built-in-function “dweepy.dweet_for() takes in the unique address of where to send your data, and the data that you are trying to send. The data that we were sending was the average of 5 readings from the DHT11 and 22 for both temperature and humidity. These were nicely wrapped up in the variable PACKAGE.

In order to access the raw data, you can go to:

https://dweet.io/dweet/for/org_pmss_berea_BAT

This shows you that all you do to access your data is put your unique identifier in the correct spot! The raw data that you get is pretty ugly, but you can see that it successfully sent the contents of PACKAGE to the internet. The Dashboard group created a Freeboard for us which displays the data in a much more accessible way, with graphs and text.

I will be part of the group that is going to PMSS this weekend and I am excited to get together our prototypes. I believe that all of the groups are finished with their tasks, except for the sensing group who seems to be having some trouble with the DHT11 library. Hopefully we are able to pull together as a class and produce a working prototype.