sjaks / esp32-tempmonitor

A simple temperature monitoring station based on the ESP32 board with a barebones chart.js web interface

Source code for my homepage

Accessible at https://sjaks.iki.fi/.

Development

In the root directory of this repository, you can run

python -m http.server

to serve the website with a simple http server.

esp32-tempmonitor's Issues

Acually utilize temp sensors

The switch from RPi to ESP32 introduced a major bug; just dummy data is sent to the backend. Find a way to send actual data...

Rewrite backend

Use some microframework for the backend. Currently Nodejs HTTP(s) module is used and it makes the implementation complex and ugly.

Express should work but it might be too bloaty...

Use timezone offset

The ESP program uses GMT and this time is shown directly in the UI. The UI should offset the ESP time correctly to the user's timezone.

Allow custom timezones in the ESP32 program

Current the timezone offset is set to some 0 value (GMT?) Maybe create a constant so that user can easily alter this.

Also check whether summer time changes are handled correctly...

Simplify frontend

• Streamline HTML
• Move all CSS to .css files
• Utilize jQuery more
• Utilize JS functions more
• Split the chart.js chart class into smaller parts
• Remove unnecessary chart.js config

Save data into a database

Use a database instead of the barebones json file method for saving data.

Maybe use SQLite since it saves data into a file and this program doesn't really need db authentication.

ESP32

Use ESP32 board for fetching data because RPi is overkill as a temperature reader.

Let the server handle all datetime stuff

Currently the ESP board sends the temperature fetch time to a server. ESP relies on a simple Arduino ntp library to get the time which doesn't have automatic timezone support. To simplify things, reimplement the API can API calls so that only temperature values are sent to the endpoint and the server attaches the current server time to the data.

Rel: #8

Move `.env` under `server/`

There is no point in storing the env file in the root anymore as the ino program cannot read it. Place it under the server dir since it is related to that stuff...