Want to learn about the Internet of Things and how to work with a sensor? I did too! I’ve been experimenting with the “Internet of Things” (IoT) since 2014 and have learned about the challenges with my sensor project: the AirQuality Lab. In the beginning, I just wanted to create something and work with the components. The scope of my side project was to read values from a sensor, transfer it to a thing-backend and then learning from the data. This post starts with the basic setup of the Thing and the following posts will cover further points.
After finishing a project in late 2014, I played around to learn a bit more about the Internet of Things (IoT) stuff for my next project. So, it was (and is) proposed, that “everything is connected in 2020” and I had to think about a product, product strategy and technical implementation in this area. Our thoughts about a domain model for IoT at this time was, to reduce everything to a source and a drain. Well, as hardware is cheap (but this is not all) I bought a Raspberry PI, a bunch of sensors and a small LCD display. Inspired by the CubeSensors, I wanted to measure air quality with the sensors and work with the derived data. This should help to understand how things process data, how to transfer it, how to analyze and derive information from it. I started the AirQuality Lab.
Leave a Comment
In the early days of the Internet of Things hype, the industry stated that computing power and accessories are cheap and ubiquitous. Read: available and ready to use. The good part of this statement is, that it is true. Partly. RaspberryPi, Arduino, Seed Studio Groove, Adafruit Feather and so on are cheap and versatile computing devices, available on many online retailers. Several toolkits and online resources help the hackers and makers to prototype and develop products. Also many online platforms are ready for the users to connect and manage the things.