neoformit / hydroweb Goto Github PK

New feature to stop/start hydropi service through web interface

Create a controller panel similar to the config panel where all device controls can be found. This solves the issue of where to put controls for 'headless' devices like the mist and mix controllers - and other controllers whose status is not yet available (pH).

Validating for mS units instead of uS. Should be max 10,000 not 10.

Currently this just raises an error - probably a schema or type mismatch with the table.

Config can be persistently updated in the web UI, but it doesn't seem to be immediately effective within hydropi.
Though the config in the web UI shows the updated values, hydropi still calculates a parameter's status with the old values.

Example: config was update to increase EC_MAX from 1600 to 1800. It seemed to work - refreshed config page showed the new value. But the displayed status for EC was still warning even though it was only as 1720 - hydropi was still referencing the old EC_MAX. So either it's not fetching config from the database, or it's caching the data somewhere.

Restarting the hydroweb service fixes the issue, and hydropi starts reading the new value for calculating EC status.

The UI should have a kill/killall button for tasks/controllers that are currently running.
Better thread management is probably required for this to work, maybe with redis/rq

New UI component to display contents of the dash_history table once that has been populated effectively.
Probably some interactive graphs with plotly.

Would be nice if the UI would show the current state of a controller

This is strange, since other controls seem to work fine, and the controller actually logs the controller switching state as the web UI switches the device on/off:

INFO | 2022-01-22 11:12:10 | controller  | PressurePumpController: switch output state to 0:ON
INFO | 2022-01-22 11:12:16 | controller  | PressurePumpController: switch output state to 1:OFF

Very mysterious.