When enabled, on each adapter start the adapter scans all existing
hass.0.entities.* channels and deletes those whose entity_id matches
any of the configured excludePatterns. This complements the existing
filter (which only prevents new objects from being created) by also
cleaning up objects that were synced before the filter was activated
or before the patterns were extended.
Safety:
- Channels (and any of their sub-states) holding common.custom config
(history/influxdb/sql) are kept and a warning is logged so the user
can decide manually.
- Existing deleteStaleObjects() 50% sanity-guard is intentionally NOT
applied here — the user explicitly opted in to the cleanup.
- Per-id deletion only logs when verboseFilterLog is also active.
Default is false (opt-in). Adds new admin checkbox + i18n keys for all
11 languages (machine translations for non-en/de still pending).
New `verboseFilterLog` boolean (default `false`). When enabled, the initial
sync logs every excluded entity_id individually on INFO level. This is
useful when iterating on exclude patterns or verifying that the filter
catches the intended entities.
The verbose output is intentionally limited to the first sync. Subsequent
debouncedSync() calls only emit the aggregate count to avoid log spam
during normal operation. Live `state_changed` events for filtered entities
remain on DEBUG.
Admin UI gets a checkbox below the patterns field; i18n keys added for
all 11 supported languages.
JSON-Config field `excludePatterns` (multiline textarea, 6 rows by default,
full width). Help text explains the syntax: glob with `*`, `#` for comments,
empty = filter inactive.
i18n translations added for all 11 supported languages so the label and
help text are localised consistently with the rest of the admin UI.
GermanBluefox
mokusone
diemadeandWeblate
Ingo Fischer
mcm1957andWeblate