Admin: Config Presets

Config presets are reusable relay configurations you can apply to one or more devices in a single action, instead of configuring each device's relays by hand.

What config presets are

A preset defines, per relay:

• Label — a friendly name (e.g. "Router", "Kettle").
• Mode — Normal or Pulse (and any other relay modes your build supports); Pulse relays also get a pulse duration in milliseconds.
• Default state — On or Off.

A preset can optionally specify an "Allocate to organisation" — if set, applying the preset to an unallocated device allocates it into that organization; applying it to a device already in a different organization moves it there (with a confirmation step — see below).

Presets are scoped to a single organization, and preset names and descriptions must be unique within that organization.

Viewing presets

Any Admin or Super-User can open Config Presets and see the full list for an organization — preset name, description, relay chips (showing label and mode, e.g. [Pulse]), and, if set, an "Allocates to: <org>" badge.

Read access for everyone Admin+

The list, its relay details, and the "Apply" action are visible to Admins. Only the create/edit/delete controls are hidden — see below.

Creating / editing a preset (super-user)

Creating, editing, and deleting presets is restricted to Super-Users only (ticket 0385aa83). If you're an Admin, the New Preset, Copy, edit (pencil), and delete (bin) controls are hidden entirely, and the screen shows: "Only super-users can create or edit presets."

For Super-Users, the toolbar offers:

• New Preset — opens a blank editor: name, description, target organization, relay count (4 or 6), and a per-relay table (label / mode / pulse ms / default state).
• Copy — pick an existing preset from a picker list; its relay configuration and settings are copied into a new preset, but the name and description always start blank so you can't accidentally save a duplicate.
• Edit (pencil icon on a preset card) — same editor, pre-filled with the preset's current values.
• Delete (bin icon) — removes the preset after a confirmation prompt. This cannot be undone.

The editor validates that the preset's name and description are each unique within the organization before saving, and will block the save with an explanation if either collides with an existing preset.

Applying a preset to devices

Any Admin or Super-User can apply a preset — click Apply on a preset card to open the device picker:

1. Select one or more devices from the org's device list (checkboxes; Select all / Clear helpers are provided).
2. If the preset has a target organization, you're told up front: "Devices will be allocated/moved to: <org>."
3. Click Apply to N device(s).

Applying a preset replaces the device's relay configuration

The preset's relay config overwrites whatever the device currently has, and its config version (rlyCfgV) is bumped so the change propagates. There is no "merge" option.

Moving devices between organizations: if any selected device currently belongs to a different organization than the preset's target, a move-confirmation step appears before anything happens — it lists exactly which devices will move and where, and asks you to confirm. Unallocated devices don't need this confirmation; they're simply allocated.

After applying, you'll see a summary: "Preset applied to N device(s)" on full success, or "Applied to N, failed for M" if some devices failed — partial failures don't block the ones that succeeded.