A complete framework (including and IoT device) which enables individuals to track Temperature Zones within their domiciles / workplaces.
Temperature data will be specific to a Zone (room), precise (to 1/10 of degree Fahrenheit), time-stamped and named (room) and will be collected every five seconds.
The data can be used to better understand :
- Energy use
- Hot / Cool perception of people in zones
- Effectiveness of current comfort (heating / cooling) systems.
- Easily compare Zones via multi-line graph which superimposes all Rooms over each other so you can discover cold / hot zones. This can help you understand if people are perceiving drastic temps or if a zone is hot / cold.
- (Future) Direct feedback to local Comfort device (heating / cooling).
Very simple basic & static prototype displaying two rooms with temperature data.
First of all, here are some screenshots of the IoT Device (Temperature Tracker)
The Temperature Tracker devices are very easy to build as shown in the schematic. This prototype would also be much smaller using an Arduino Nano and wiring would be the same.
This will use New Relic to show a line chart of specific values and do comparison overlays of two or more rooms so it is easier to quickly see cold / hot spots.
Each Temperature Zone (a room in the domicile or workplace) will contain one low-power IoT device (Temperature Tracker) which gathers timestamped, named (room), precise temperature data once every five seconds (20 times a minute).
The temperature data from each IoT device can be gathered and examined via Phone app (Android) via Bluetooth.
A press of a button in the Phone App allows the user to gather data (via Bluetooth) from all local Temperature Zones and upload it to New Relic.
This allows the Phone to serve as the Internet connection and alleviates the necessity of adding Internet access to each local Temperature Tracker.
The real power comes from the power of New Relic for a number of reasons.
The locally sourced temperature data will grow extremely large over time (days / weeks / months of data) and would overwhelm an Android device storage limits (wasting valuable space on your phone).
Additionally, keeping the data on the Arduino SD card and having the Arduino process for average temperatures or display the data in meaningful ways (graphs, charts, etc.) is not realistic because an Arduino is built for low-power and not maximum processing of data like that.
On the other hand, New Relic is perfect for this type of data.
With New Relic the user will be able to
- Calculate average temperature for each zone.
- View graphs which represent a temperature zone over time so the user can tell if there are certain times when temperature tends to hit outliers.
- Analyze huge amounts of data over the entire year to determine if temperature is staying in ranges.
- The New Relic data will allow users to compare graphs from different zones so that with a glance at the graph you can quickly determine that certain zones tend to be cooler or warmer than others.
All source is available at my GitHub repo.
The GitHub repo includes:
- Arduino code -- for IoT Temperature gathering devices
- Android App -- View local temp zones, upload data to New Relic from all devices
- Web UI - View Metric data (T-Zone data) stored in New Relic. https://github.com/raddevus/T-Zone
MIT License (License file is included at GitHub repo).
All code under the GitHub repo is shared under MIT License.
I've always said, "HVAC (Heating Ventilation Air-Conditioning isn't Rocket Science, you know?" But, every work-place I've ever worked (over 25 years) has always had Hot & Cold Zones (it's the same in my domicile). Depending on where you sit in the building you may be extremely hot or extremely cold.
After all those years of not seeing a good solution, I've begun to believe that Comfort Systems are more complex than Rocket Science.
These Hot & Cold Zones create an ongoing battle between people who "feel" cold and others who "feel" hot.
This creates a battle over the thermostat.
No one really knows if the problem is the feelings of particular people (the way they perceive hot/cold) or if the problem is the actual comfort (heating/cooling) system.
This also leads to large furnaces and air-conditioning systems be overused. At times the two systems (heating & cooling) may even kick on and off fighting the effects of each other and wasting more energy.
T-Zone is made up of a few different projects:
- IoT Temperature Tracker - Arduino code
- Android App - Kotlin code
- New Relic API -
- Using the New Relic Metric API to post data from all IoT Temperature Trackers.
- Implementing New Relic dashboard to display Temperature Zones for easy comparison of temperatures in different Zones. At a glance a user can see that certain Zones are hotter or cooler than others.
- New Relic data storage allows IoT SD card data to be removed continually to insure they do not become full and unusable.
- New Relic data storage insures local data isn't lost but stored in the cloud and always accessible to all users even if they don't have the data gathering Android App. This means one "manager" of IoT devices can gather data, but other users can view zones. At a large company this can help with user perception of temperatures in zones.
In the process of building my “Out of this World” app, here’s what I learned about observability and technology in the fight against climate change…
(Explain what you learned about software as it relates to saving our planet from the negative effects of climate change. How can observability tools help scientists, technologists, and everyday people protect our earth?)
In the future the data could be used as direct feedback to a particular comfort (heating/cooling) device in a specific Temperature Zone.
Instead of one central thermostat that controls one large heating/cooling unit, the data could feed into separate devices located in each Temperature Zone, creating a better experience for people and less energy use.
This would help realize:
- Less energy used - Example: Why turn on cooling system for the entire domicile when only one Temperature Zone needs to be cooled?
- Individuals experience more comfort Each Temperature zone will be far closer to the temperature that the individuals are expecting -- whereas a system with only one thermostat an never be as precise for all zones in the domicile.
- Individuals have better understanding of perception of temperature -- Individuals will have a better idea that the temperature experience is managed much more specifically so if they are feeling "hot" or "cold" then it may be an individual perception and they may need to dress differently.
This system could easily be implemented right now. Here's how.
If you currently have one zone in your domicile that tends toward one extreme or the other (hot or cold) and causes your central Thermostat to often kick on, you could solve this with my solution and see the benefits.
With the advent of Arduino and other low-price, easy to develop components you could implement a partial system now with the following steps:
Continue use of your Centralized Thermostat System as normal but :
- Add the IoT Temperature Tracker which reads the precise temperature data for the zone.
- Buy a small heating unit to place in the "cold zone".
- Plug the heating unit into a switch that can be controlled over Bluetooth (these are available on Amazon and many places - they're consumer devices now).
- Write a script that reads the data from the IoT Temperature Tracker so that when the temperature hits a certain threshold for a number of seconds then the local device turns on. Of course it will check when it needs to turn off also.
This will allow you save your Central Comfort system from running due to this one zone becoming too cool and save energy.
- Home floor plan image from pixabay.com open license.