Instead of a command line tool, the primary method for users to interact with NodeFlow should be as a website. From this website, users should be able to configure alerting #1,and manage their solenoids (regardless of wifi/LoRaWAN #2).
Considerations:
- This web-based GUI should be self-hostable, either on-premises or through a service like AWS.
- Similarly to how ENTS sets the API endpoint, the solenoid controller must set its NodeFlow API endpoint.
- [High Priority] Mobile-friendly, app first?
This could start with a fork of ENTS-backend, with additional features for the irrigation focus of NodeFlow.
(Also would be good to have some sort of local configuration mode: user can walk up to the device, "auto"-connect and set parameters locally.)
Instead of a command line tool, the primary method for users to interact with NodeFlow should be as a website. From this website, users should be able to configure alerting #1,and manage their solenoids (regardless of wifi/LoRaWAN #2).
Considerations:
This could start with a fork of ENTS-backend, with additional features for the irrigation focus of NodeFlow.
(Also would be good to have some sort of local configuration mode: user can walk up to the device, "auto"-connect and set parameters locally.)