Closed sickchilly closed 3 years ago
@sickchilly Likely a file exists in the Ferm Active folder from a previous session. It can be moved to the archive (although likely invalid JSON file then) and restart.
OK. There were a number of stale or disconnected sessions for PicoFerm-1. Deleting those allows start/stop fermentation for that device.
@sickchilly if there are no stale sessions in active directory fermentation won't auto start.
Glad with a fresh directory this works 👍
Just updated to 5073c38 and noticed a few issues.
Not related to the recent update, but I noticed that since adding the Stop Fermentation function for PicoFerm, any time the server is restarted, it automatically starts fermentation on the PicoFerm even if it was stopped before the server restart.
After updating to 5073c38, pressing Stop Fermentation produces an Internal Server Error:
Error log: picobrew_pico.log