Release v0.8.32 · ideaalab/gui-recorder

What's new

New Manual exclusions (advanced) field for the recorder filters that GUI Recorder doesn't manage per-entity, addressing #5.

Step 1 (import) now auto-transfers unsupported legacy filters (exclude.domains, exclude.entity_globs, exclude.event_types, include.domains, include.entity_globs) directly into the new Manual exclusions field — they were previously just counted and warned about, now they're carried over.
The only filter type still lost on migration is include.entities (allow-list mode), which GUI Recorder can't represent. The UI calls this out explicitly.

Raw YAML textarea, merged into the generated gui_recorder.yaml alongside the per-entity exclusions.
Allowlist: only exclude.{domains,entity_globs,event_types} and include.{domains,entity_globs}. Individual entities (entities: lists) are rejected — those stay exclusively managed by the device/entity toggles so the two systems never fight over the same list.
Validated server-side: invalid YAML or unsupported keys never get persisted, you get an inline error instead.

Migration card: hasUnsupported was not counting exclude.event_types, so the warning banner could be hidden when only event_types filters existed. Fixed.