Controller firmware overhaul (part 1) #179
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I am working on overhauling the controller firmware to be more easy to setup, update, and configure. Ultimately, the goal is to have a single firmware binary that is separate from a user's configuration. You should be able to download the binary file, put it on an ESP32, and then connect to WiFi and MQTT using a captive portal. Then, you can create a config in the UI and publish to the controller.
Part 1, this PR, includes:
Next, I will need:
config
orfirmware
either as part of a Garden or as a child resource in the API (/gardens/{gardenID}/config
)