Skip to content

v3.3.2 · Multi-Watcher/Slot: nested watcher subentries visible

Choose a tag to compare

View all tags
@Levtos-Acc Levtos-Acc released this 07 Jul 05:48
· 24 commits to main since this release
v3.3.2
eced311
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Title Classifier title_classifier v3.3.2 — Multi-Watcher/Slot: nested watcher subentries visible

Fixes that several watcher subentries under one parent (e.g. Stash Slot 1..4) are managed and shown separately in the v3 overview.

Root cause

A watcher subentry ran (own runtime, sensors, catalog sightings) but was invisible to the overview, shared catalog gather, and post-mutation refresh: all_v3_runtimes / select_v3_runtimes only read bucket["runtime"] (top-level), while subentry runtimes live in bucket["subentry_runtimes"]. Only a single Stash watcher appeared.

Changes (Title Classifier only)

  • select_v3_runtimes now includes top-level v3 runtimes and every subentry runtime; all_v3_runtimes delegates to it. Multiple watchers with the same context (e.g. stash) appear separately and share one catalog.
  • Watcher-subentry flow rejects a name whose entity-id slug is already taken by any watcher (top-level or subentry) — new name_taken error (EN/DE). Each slot needs a unique name.
  • New pure watcher_name_slug helper keeps the collision check aligned with the sensor.title_classifier_<slug>_* entity-id contract.

Model

One watcher per slot entity (Option A) using existing stash slot entities — no new attribute field, no A | B string-splitting (one title-key/sighting per slot).

Not touched / safety

No changes to Stash / Jellyfin / other integrations. No migration, no DB cleanup, no overwriting of existing enums, no frontend changes.

Gates

py_compile OK · JSON valid · pytest 198 passed (+5). HACS-ready.

PR #68 · merge eced311 · tag v3.3.2.

Assets 2
Loading