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.
Adapter now consults the exclude-pattern list (new `native.excludePatterns`
config option, multi-line string) at two points:
- `parseStates()` skips matching entities entirely. They are not registered
as ioBroker objects and no state is written. A summary INFO line reports
the count when the filter dropped anything from a sync.
- The `state_changed` event handler short-circuits matching live updates
with a DEBUG line, so a filtered entity that still emits state changes
in HA does not cause any churn in ioBroker.
Patterns are parsed once at adapter start: trimmed, empty lines and lines
starting with `#` are dropped. An empty resulting list means the filter is
inactive — adapter behaviour is then identical to the previous version.
Default config ships with example comments only, so existing installations
see no functional change after the update.
Glob-based entity_id matcher used by the upcoming exclude-filter feature.
Single wildcard `*` (matches any sequence including dots), all other characters
matched literally with regex metacharacters escaped. Case-sensitive, anchored.
Empty pattern array always returns false, so the helper is a no-op when the
adapter is not configured to filter anything.
New mocha unit-test suite invoked via `npm run test:unit` (separate from the
existing js-controller-backed test:integration).
mokusone