Setup instructions here.

Make load_data an asynchronous method, and schedule it to be run every 15 minutes in addition to whenever a device's data is requested.

Include a “downloading” field on the device to act as a lock so multiple refresh requests cannot be made simultaneously

Use recursion instead of nested loops, and improve error reporting by returning a dictionary of each unsuccessfully retrieved file and the error it produced

Stop pushing directly to master

For now, this page will only allow generation of time series using any of the predefined functions (hold, ramp, or sine), as well as removal of time series. In the future, WYSIWYG time series creation, including time series consisting of custom points, will be possible.

Currently the notes field is required by the backend, but the UI does not require it. If left blank, the error message says something went wrong when creating the device. Not a helpful message.

I was bad.

Be good from now on.

Serve the oa_frontend/dest directory, and also proxy the backend.

Write tests for the Devices, Time Series, and Tanks apps within Django.

The add button should appear below the rest of the devices in the list. The remove button should appear on the configuration page (see #10), and should produce an "Are you sure?" prompt.

The current refresh functionality just restarts at the first path that failed on the last refresh, then visits all subsequent paths. This is very inefficient; we should only visit the previously missed paths before moving on to new paths.

Django Q's Schedule does not create a Task object until after the task has finished executing, so we need to find another way to lock while still allowing the lock to be released in the event of a system failure. Consider making the lock a boolean, then releasing all locks whenever the server is restarted.

When a Device object is deleted, its associated scheduled task should also be deleted.

Update the API documentation YAML file with all of the endpoints and their options.

Make time series generator endpoints differentiate between time series type (ph and Temp)

Wait until #4 is complete.

Instead of requesting the entire CSV from the device (which results in a timeout), do so by pages of 100 lines, and stop once a 416 code is returned.

Clicking the wrench icon should display a page where the device's name, IP, and notes can be adjusted.

The information page displays a readout of the current tank as a json string.

Although this gets the job done, it would be better to add some formatting.

1. Create an Information model that maps from the information string.
   https://app.quicktype.io/
2. Use a UI widget like the divider class to format the page.
   https://api.flutter.dev/flutter/material/Divider-class.html

This is to ensure that we are always working with the same device in order to avoid data conflicts.

Replace Device “online” field with “status” field, which can contain one of the following:

• 0 = Device is offline
• 1 = MAC address in DB matches MAC address returned by device
• 2 = MAC address in DB does not match MAC address returned by device

Update device status icon in the frontend to reflect this change.

The error message on the add device page should explain why it failed.

• No device at the IP address
• Invalid mac address response
• Missing form field
• Invalid IP address
• etc.