Releases ·

Roastwarden 0.6.0

The first step toward other roasters: each roaster now says what rustRoast may send it. A roaster added from now on only records until the owner switches its control on; the ESP32 and the virtual roaster keep full control and work as before.

Added

  • Roaster setup and the control gate (ROADMAP Next 41, Roaster kind and control level): each roaster has a kind and a control level, off (logs only: nothing is sent, not even STOP), manual (heater, fan, heater on/off, STOP) or full. One check in the transport registry refuses what the level does not allow, for every feature (control, the roast sequence, alarm actions, Profile drive, fan assist, the gain schedule, the autotune, the Modbus bridge): 409 CONTROL_OFF. A roaster added or discovered from now on starts off; the ones that existed (the ESP32, the virtual roaster) are full and work as before. Roasters → a roaster → Control opens with Setup (owner only); the Roast page shows what a roaster below full cannot do; Roasters → Add ends with the setup. GET|PUT /api/roaster/{id}/setup; roast roasters and roast roaster show print the level.