Edward Hails (96b5954d) at 24 Aug 23:33

Edward Hails (c2482e30) at 24 Aug 23:33

... and 30 more commits

Overview

The goal of this branch is to add the ability to change the bed state on WaterElf devices through the DripDash interface.

To perform this, the dashboard will send a mutation requesting the state change to the server, which in turn will be stored in the database.

The next time the WaterElf connects to the server to upload stats, the response to this HTTP request will contain the command to be sent, and the command will be removed from the database as it is now completed.

Sending the command to the Elf device will probably use JSON, although a more simplistic method of encoding this data is preferable to reduce the memory requirements on the IoT device.

Steps

• Add an interface on the device dashboard to send requests to fill and drain specific beds.
• Add the ability to switch between 'automatic' (default) and manual bed control. Should auto be re-enabled after some time?
• Save bed state change requests in a database table linked to a given device. These state changes should have a reasonable TTL, so in the case where the device goes offline for a long time, the command will not unexpectedly be carried out hours or days later.
• Check for pending commands when a device sends data to /collect and respond with any pending requests.
• De-duplicate bed change requests (e.g. if two users request a device to drain a bed, make that just one request with the TTL of the later request).
• See if it's possible to give some indication of when the command has been executed, otherwise just indicate when the command has been saved on the server.
• Fiddle with the WaterElf firmware to check the full thing works.
• Update FakerElf to understand these responses.

Edward Hails (96b5954d) at 24 Aug 23:33

Tested with changes merged from master on FakerElf, behaviour as expected. Marking as ready.

Edward Hails (2d233de7) at 23 Aug 09:46

... and 17 more commits

Edward Hails (4ccdf9f0) at 23 Aug 09:43

Edward Hails (eb67cddc) at 23 Aug 09:40

Edward Hails (959fd7cd) at 23 Aug 09:18

Once states are chosen I'll refactor it into an enum but for now they're just strings.

Devices now receive a JSON list containing commands in this format:

[
    {"subject": "bed 0", "action": "fill"}
]

I still need to update the docs for this. If there aren't any pending commands the status code returned is 204 (no content), if there are pending commands it's a 200.

Edward Hails (b0fdc5b3) at 19 Aug 17:12

... and 1 more commit

Edward Hails (626bb1a1) at 19 Aug 17:08

I'm currently basing the commands and state codes sent back to the devices on the old firmware, as the new firmware is still somewhat in flux.

It might be needed to consolidate device states into just 'fill' and 'drain' on the frontend though in the future.

Edward Hails (985793ed) at 04 Aug 20:11

Edward Hails (027cc05e) at 04 Aug 17:50

... and 1 more commit

Overview

The goal of this branch is to add the ability to change the bed state on WaterElf devices through the DripDash interface.

To perform this, the dashboard will send a mutation requesting the state change to the server, which in turn will be stored in the database.

The next time the WaterElf connects to the server to upload stats, the response to this HTTP request will contain the command to be sent, and the command will be removed from the database as it is now completed.

Sending the command to the Elf device will probably use JSON, although a more simplistic method of encoding this data is preferable to reduce the memory requirements on the IoT device.

Steps

• Add an interface on the device dashboard to send requests to fill and drain specific beds.
• Add the ability to switch between 'automatic' (default) and manual bed control. Should auto be re-enabled after some time?
• Save bed state change requests in a database table linked to a given device. These state changes should have a reasonable TTL, so in the case where the device goes offline for a long time, the command will not unexpectedly be carried out hours or days later.
• Check for pending commands when a device sends data to /collect and respond with any pending requests.
• De-duplicate bed change requests (e.g. if two users request a device to drain a bed, make that just one request with the TTL of the later request).
• See if it's possible to give some indication of when the command has been executed, otherwise just indicate when the command has been saved on the server.
• Fiddle with the WaterElf firmware to check the full thing works.
• Update FakerElf to understand these responses.

Edward Hails (c35bffa1) at 15 Jul 14:23

... and 2 more commits

Edward Hails (42a35cb1) at 12 Jul 16:43

JWT proves the authenticity of the source through signatures but doesn't provide security. Storing the session token in local storage is insecure since local storage can be accessed by javascript. Any compromised node package could lead to user tokens being stolen. Storing the JWT in an HttpOnly cookie with the SameSite attribute helps protect from XSS and CSRF attacks.