Releases ·
Roastwarden 0.17.0
The Roasters section reworked for three users at once: a home roaster, a small shop and a builder of custom roasters. Add roaster is four steps (the roaster and its kind, how it connects, a live check, then control), one connection form serves the wizard and a roaster's page, and the roaster cards say at a glance which roasters are reading and ready.
Changed
- The Roasters section, one pass for three users (Next 74,
docs/ui-structure.md, "Roasters and Add roaster"): a home roaster, a small shop and a builder of custom roasters, with the common path first and the rest folded where it is needed (no basic/advanced mode).- Add roaster is four steps: Roaster (name, the id from it, the kind; a known machine from Artisan's catalogue in one line; description and location folded) → Connection (how it connects in plain words, only the needed fields, an Advanced fold; a Modbus roaster's registers in the same step; Save and check saves it at control off) → Check (the live check; Test the connection; Map its fields right there) → Control (Off, Manual or Full). The kind now comes first, and the check comes before control is switched on.
- One connection form for the wizard and a roaster's Add Connection (the second copy had fewer fields); it fits a phone (the five protocol tabs ran off the screen).
- Roaster cards show reading or silent, kind, connection, control level and the check's verdict; one Found, not added yet list replaces the two tinted boxes; connection templates are a small link at the bottom.
- A roaster's header shows its kind and control level; Delete moved into Edit.
- The browser checks walk the wizard's common path at laptop and phone sizes.
Fixed
- Add roaster's MQTT topic prefix defaulted to a bare
roaster/, so a roaster added with the defaults never heard its data; it is nowroaster/and the roaster's id, as the firmware sends. - A roaster's connection row no longer runs off a phone screen; the device contract says "not heard since the server started" without "API error 404".