danielfireman / temp-to-go

Small IoT project: written in #go and fully based on free, open source libs and infrastructure.

Temperature to go

Would you always wanted to know when to turn on the fan or the air conditioner during the night? Good news is that your problem will be solved soon!

Besides solve this very important problem, our small projects has some other goals:

• Fully implemented in Go (yes, from the device to frontend)
• Use only free, open source libraries
• Cheap devices
• Run on free infrastructure

Status

• Device configuration and software: Done 😁
• HTTP API for storing bedroom temperature (crypto): Done 😁
• Fetch Current Weather Worker: Done 😁
• Fetch Weather Forecast and Prediction Worker: Done 😁
• Public HTTP FE: Done 😁
• Authorzed area: Done 😁
• Fan control HTTP FE (authorized area): Done 😁
• Prediction: Done 😁
• Prediction graphs: Not Started 😒

Stack

• Device/Sensor

  • Hardware
    • NodeMCU / ESP8266
    • Grove Temperature Sensor
  • Software
    • Development using gobot.io through firmata protocol

• Server/Worker

  • Platform
    • Heroku: Cloud provider
    • Namecheap: Domain names (mybedroom.live and meuquarto.live)
    • Cloudflare: Better DNS, DoS protection, edge caching and more
    • MongoDB: mongoLab Addon
  • Software
    • globalsign/mgo
    • Gonum, in particular the Linear Regression
    • Labstack Echo
    • Labstack Echo-Contrib/session
    • Gorilla Sessions

• Client

  • GopherJS
  • Frappé-charts

temp-to-go's Issues

Decrease graph.js size

It is currently toooooo big

Store decrypted message in a database

The database schema could be very simple and the database technology easily replaceable (not much think in advance exchanged by good software design). The only requirement is that it should be fast to query by date/time range.

Environment variable mandatory

There are some environment variable mandatory for starting web project. Most of them, shouldn't mandatory tough. I'd like to propose addition a fallback for each one env that is not really mandatory to start the application, such as PUBLIC_HTML=/public, MONGODB_URI=mongodb://127.0.0.1:27017/db and PORT=8080

@danielfireman What do you think ? Is it makes sense ?

Get temperature from Grove Temperature sensor

Use gobot.io to get the temperature from the Grove Temperature sensor.

Create a page or banner to land users when the access is denied.

Currently we are only returning a 403

Move documentation to Wiki

Currently, it is scattered through the code structure. Let's tie stuff together using the github wiki.

Plot history of the bedroom temperature, weather and fan state

Need to take a look at how the weather is plotted it is done out there.

Landing page

Now the server is already on Heroku, it would be awesome if we could a cool landing page describing the project and the purpose :)

Start Frontend on Heroku

This is only to track our Heroku deployment.

Fetch weather forecast

Open Weather Maps has an API which allows us to forecast the next 5 days. We could have another worker, which will run daily and fetch this forecast.

Two things to pay attention:

• Most of our stuff is showed/fetched hourly: the current weather, the prediction
• There will be an overlap, which should result in an update at the database: for instance, the forecast for tomorrow I got yesterday could be different from the one I get today. Let's assume the difference is more accuracy and update the database straight away.

That said, one could key all our entities by UTC time, always flooring to the zero minute of the current hour. With that, we could roll-up the tuple (weather_current, bedroom_info) keyed by timestamp.

The bedroom temperature forecast for each case could be calculated and stored in a different collection, using the same key.

As we are running free, lets used capped collections to having mong automatically cleaning things up for us.

Create worker

Create a Heroku worker, which should get the current forecast for the following geolocation: @-9.6602869,-35.7059512

OpenWeatherMap accepts geolocated queries and it is the one which has the biggest limit of queries and so on. It also has special conditions for opensource projects.

Send temp-to-go encrypted message

Send an encrypted message to the temp-to-go server. The message can as simple as:

base64 encoded(user_token + device token): 64 bits | op : 8 bits | temperature: 32 bits

Whoever gets this issue should choose the appropriate encryption algorithm (bearing in mind it must run in the device and be unencrypted at the server);

Create timer which sends a TCP message every 30 minutes

Use gobot.io to send a TCP message through ESP8266 WIFI every 30 minutes.

The code could start to live in a directory called device

Create a page to easily switch the fan on and off

Of course, this only for authenticated users.

Code a server which receives the TCP message from the device

Let's start this off with a monolith listening to TCP (from the device) and HTTP messages. Should receive the message sent in #3 , unencrypt it and print it.

Store current weather in database

Fields already mapped to go structs at server/worker/main.go

Create a login page

No need to implement a login page. Let's use Google.

Add HW prices to the landing page.

@dialmformart , could you please add the HW prices to the main Readme.md ?

Use GZIP compression

It should be as simple as using the gzip middleware https://echo.labstack.com/middleware/gzip :)