iobroker.waip-web 0.7.2 → 0.7.6

package/CHANGELOG_OLD.md

@@ -0,0 +1,361 @@
+# Older changes
+
+### 0.7.1 (2026-08-21)
+
+- Added a License badge to the README.
+
+### 0.7.0 (2026-08-21)
+
+- Prepared the admin UI for community translation via
+  [ioBroker's Weblate](https://weblate.iobroker.net/engage/adapters/):
+  added `@iobroker/adapter-dev` as a dev dependency (`npm run
+  translate`), converted `admin/jsonConfig.json`'s `label`/`help` fields
+  from inline `en`/`de` objects to plain English keys, and added
+  `admin/i18n/{en,de,ru,pt,nl,fr,it,es,pl,uk,zh-cn}.json` (German
+  curated manually, the rest auto-translated via the official
+  `translate-adapter` tool — the same tool that already maintains the
+  `io-package.json` translations). Added a "Translation status" badge to
+  the README; like the "installed"/"stable" badges, it only shows real
+  data once the adapter is actually registered as a component on
+  weblate.iobroker.net (not done yet).
+
+### 0.6.11 (2026-08-21)
+
+- README: logo now shown enlarged (115×115) via a new
+  `admin/waip-web-logo.png`, nearest-neighbor-scaled from the 32×32
+  source icon for a crisp (if visibly pixelated) result instead of a
+  blurry interpolated one — no higher-resolution source exists anywhere
+  in the WAIP-Web ecosystem (checked the Lausitz instance and the
+  upstream project, both use the same 32×32 favicon). The actual
+  ioBroker adapter icon (`admin/waip-web.png`, referenced from
+  `io-package.json`) is unchanged.
+- Simplified the README title back to "ioBroker.waip-web".
+
+### 0.6.10 (2026-08-21)
+
+- Added the adapter logo and npm/installation badges (NPM version,
+  downloads, installed, stable) to the README, matching standard
+  ioBroker adapter conventions. The "installed"/"stable" badges won't
+  show meaningful data until the adapter is listed in the official
+  [ioBroker.repositories](https://github.com/ioBroker/ioBroker.repositories)
+  ("latest" repository PR pending), but will populate automatically once
+  it is.
+
+### 0.6.9 (2026-08-21)
+
+- Fixed adapter-checker finding **[E254]**: removed `common.news` entries
+  for versions that were never actually published to npm (`0.6.1`–`0.6.5`,
+  `0.6.7` were only version bumps in git/GitHub, without a matching
+  tagged npm release). `common.news` now only lists versions that really
+  exist on the npm registry (`0.6.6`, `0.6.8`); the full history remains
+  in this changelog regardless of what was actually published.
+
+### 0.6.8 (2026-08-21)
+
+- Renamed the README title to "ioBroker-Adapter (ioBroker.waip-web)".
+- This release doubles as the first end-to-end test of the automatic
+  npm publish via Trusted Publishing introduced in 0.6.7.
+
+### 0.6.7 (2026-08-21)
+
+- Enabled automatic npm publishing: the `deploy` job in
+  `.github/workflows/test-and-release.yml` is no longer commented out
+  and now runs on every version tag (`vX.Y.Z`), publishing to npm via
+  [Trusted Publishing](https://docs.npmjs.com/trusted-publishers) (OIDC,
+  no `NPM_TOKEN` secret needed).
+
+### 0.6.6 (2026-08-21)
+
+- Added `.gitattributes` `eol=lf` so all contributors get consistent LF
+  line endings regardless of their local git `autocrlf` setting
+  (previously caused hundreds of spurious local lint errors on Windows
+  without affecting CI, since CI checkouts weren't affected).
+- Added `package-lock.json` and switched CI to the default `npm ci` with
+  caching instead of `npm install` without caching, now that a lockfile
+  exists.
+
+### 0.6.5 (2026-08-21)
+
+- Fixed all issues reported by the official [ioBroker adapter checker](https://adapter-check.iobroker.in/):
+  - Bumped the required `js-controller` dependency to `>=5.0.19` and `@iobroker/adapter-core` to `^3.2.2`
+  - Replaced the deprecated `common.license`/`common.title`/`common.main` fields with `common.licenseInformation`/`common.titleLang`; `common.main` is redundant with `package.json`'s `main` field
+  - Added the required `common.tier` (`2` - external/cloud data source)
+  - Added translations of `titleLang`, `desc` and the kept `common.news` entries into all 10 additional ioBroker admin languages (ru, pt, nl, fr, it, es, pl, uk, zh-cn)
+  - Trimmed `common.news` to the 7 most recent entries, as recommended (the repository builder truncates there anyway); the full history stays in this changelog
+
+### 0.6.4 (2026-08-21)
+
+- New state `status.registeredMonitorName` shows the registered monitor
+  as text without the ID (e.g. "Leitstelle: Lausitz"), resolved once at
+  startup from the same `/waip/` overview page as the admin dropdown.
+  `status.registeredMonitor` is unchanged and keeps showing the ID.
+
+### 0.6.3 (2026-08-21)
+
+- Admin UI: the Monitor ID field is now always full-width, placed on its
+  own row below the WAIP server URL, so the (sometimes long) dropdown
+  entries have enough room to display without being cramped.
+
+### 0.6.2 (2026-08-21)
+
+- Monitor dropdown entries are now sorted by numeric monitor ID instead
+  of following the source page's (per-category) order.
+
+### 0.6.1 (2026-08-21)
+
+- Monitor dropdown entries now start with the actual monitor ID, e.g.
+  "4 - Leitstelle: Lausitz", so the numeric ID stays visible even after
+  a monitor has been selected.
+
+### 0.6.0 (2026-08-21)
+
+- **Admin UI:** Monitor ID is now a live dropdown (`selectSendTo`) instead
+  of a plain text field. The adapter fetches the configured server's
+  public `/waip/` overview page on demand and offers every monitor it
+  finds there, grouped by Leitstelle/Kreis/Träger/Wache, with "Alle
+  Wachalarme" (ID `0`) as an explicit first option. Manual entry remains
+  available if the server can't be reached or uses a different page
+  layout, so existing configurations keep working unchanged.
+- Removed the static "session keepalive interval" info text from the
+  admin UI (the behavior itself is unchanged).
+- Added help text to the "Registration timeout" and "Reconnect delay"
+  fields.
+
+### 0.5.1 (2026-08-21)
+
+- **Logging:** Reclassified log levels so `warn` becomes a reliable signal
+  again. Session-cookie rotation, the known "Fehler beim Erneuern der
+  Session" server message, and detected server restarts are now logged
+  as `info` instead of `warn`, since they're part of this instance's
+  normal, self-healing ~10-minute session cycle. Events discarded for a
+  different monitor ID are now `info` (frequency remains tracked via
+  `debug.ignoredCount`). Failures that only affect internal housekeeping
+  (`debug.monitorAudit`, socket cleanup) are now `debug`. A duplicate
+  `connect_error` log line (logged once at `warn`, once at `info`) was
+  removed. Introduced `error` level for cases where an incident,
+  feedback, route or TTS event genuinely failed to be processed (actual
+  data loss), so these now stand out instead of being buried among
+  routine `warn` noise.
+
+### 0.5.0 (2026-08-20)
+
+- **Behavior change:** On `io.standby`, all `einsatz.*` states (including
+  `einsatz.json` and all counters) are now cleared instead of leaving the
+  finished incident's data in place – matching the official frontend,
+  which also clears keyword, location data etc. on standby.
+  `status.alarmAktiv` is therefore now a reliable switch for whether
+  `einsatz.*` currently holds real live data. The finished incident
+  remains fully available via `einsatz.history10` (archived there first).
+
+### 0.4.9 (2026-08-20)
+
+- **CI fix:** Reverted a self-introduced, unnecessary line wrap in
+  `connect()` (engine-packet preview) – `prettier/prettier` flagged it as
+  superfluous; the line actually fits on one line within the configured
+  print width.
+
+### 0.4.8 (2026-08-20)
+
+- **CI fix:** Fixed the final 16 lint errors – this time the complete,
+  non-truncated error list including the exact desired replacement text
+  was available, so every location could be corrected precisely 1:1
+  (line wraps for overly long calls/objects, one `prefer-template`
+  case). Lint should now be fully green.
+
+### 0.4.7 (2026-08-20)
+
+- **CI fix:** Fixed the remaining lint errors in `main.js` – consistently
+  applied `curly` (braces even for single-line `if`/`for`),
+  `no-unused-vars` for empty `catch` blocks (`catch (e) {}` → `catch {}`
+  where `e` isn't used), and `arrowParens: avoid` (removed parentheses
+  around single-parameter arrow functions). Purely mechanical code-style
+  fixes, no behavior change.
+
+### 0.4.6 (2026-08-20)
+
+- **CI fix:** The `lint` step failed with hundreds of formatting errors
+  (e.g. "Replace 'x' with "x""). Cause: `@iobroker/eslint-config`
+  requires its own `prettier.config.mjs` in addition to
+  `eslint.config.mjs`, re-exporting the ioBroker formatting style
+  (single quotes, 4-space indentation, `trailingComma: 'all'`) – without
+  it, Prettier fell back to its own defaults (double quotes). File added.
+
+### 0.4.5 (2026-08-20)
+
+- **CI fix:** The first pipeline run failed with "Dependencies lock file
+  is not found". Cause: `actions/setup-node`'s built-in npm caching
+  needs a `package-lock.json` for its cache key, independent of the
+  install command used. Since none is committed to the repo yet,
+  `package-cache: 'false'` is now set on both jobs.
+
+### 0.4.4 (2026-08-20)
+
+- Set up the CI pipeline (`.github/workflows/test-and-release.yml`),
+  following the standard pattern of the official
+  `@iobroker/create-adapter` template: a `check-and-lint` job (ESLint
+  via `@iobroker/eslint-config`) and an `adapter-tests` matrix (Node
+  20/22/24 × Ubuntu/Windows/macOS) via the central
+  `testing-action-check`/`testing-action-adapter` actions. Added
+  `test/package.js` and `test/integration.js` (`@iobroker/testing`)
+  plus `eslint.config.mjs` for this; bumped `@iobroker/testing` to
+  `^5.2.2`. Since no `package-lock.json` is committed yet, the pipeline
+  uses `npm install` instead of `npm ci`.
+- Raised `engines.node` in `package.json` to `>=18` (matching the tested
+  Node versions and `@iobroker/testing` 5.x's requirements)
+- A `deploy` job (automatic npm publishing) is prepared but commented
+  out until npm Trusted Publishing is set up
+
+### 0.4.3 (2026-08-20)
+
+- **Bugfix:** `einsatz.id` and `einsatz.sondersignal` were declared as
+  `string`, but the server actually sends them as numbers
+  (`sondersignal`, per `client_waip.js`: `switch (data.sondersignal) {
+  case 1: ... }`) – ioBroker therefore logged a type warning on every
+  incident. Both states are now declared as `number`. Existing objects
+  with the old (wrong) type are automatically recreated on the next
+  adapter start (`migrateObjectTypes()`, generic for future type
+  corrections).
+
+### 0.4.2 (2026-08-20)
+
+- Removed the "Session keepalive interval – upper bound" config field
+  again: the official `/js/session_keepalive.js` on the site hard-codes
+  this upper bound at 5 minutes and doesn't make it configurable. Having
+  an admin field for it wrongly suggested a fixed interval, even though
+  the actual renewal has long been fully automatic (see 0.4.1). The
+  upper bound is now likewise fixed at 5 minutes.
+
+### 0.4.1 (2026-08-20)
+
+- **Robustness:** The session keepalive interval is now adaptive instead
+  of a fixed assumption. WAIP-Web's source code (`server/app_cfg.js`)
+  shows that the session cookie's lifetime is configurable per instance
+  via an environment variable (server default: 60s instead of the
+  previously assumed 10 minutes) – the adapter now derives the renewal
+  interval from the expiry time actually reported by the server
+  (matching `/js/session_keepalive.js` on the site: 80% of the observed
+  lifetime, min. 55s, at most the configured upper bound). The "Session
+  keepalive interval" config option is accordingly now an upper bound
+  rather than a fixed interval.
+- Corrected a comment about `io.version`/server restarts: per
+  `server/auth.js`, WAIP-Web stores sessions persistently (SQLite), not
+  in-memory – a restart therefore normally doesn't clear them. The
+  proactive session refresh + reconnect on server restart remains as a
+  general safeguard, only the previous justification was inaccurate.
+
+### 0.4.0 (2026-08-20)
+
+- **Restructured the object tree:** Feedback and routes are 1:n lists
+  per incident and now live as nested JSON arrays inside one overall
+  object `einsatz.json` (including `emAlarmiert[]`, `emWeitere[]`,
+  `routen[]`, `rueckmeldungen[]`) instead of several loose states.
+- `einsatz.history10` replaces `history.last10` – now with the **full**
+  nested incident object per entry instead of just 6 reduced fields.
+- New counters directly under `einsatz.*`: `routenGesamt`,
+  `rueckmeldungGesamt`, `rueckmeldungAnzahl.{ek,gf,zf,vf,agt,fzf,ma,med}`
+  (replaces `rueckmeldung.counts.*`).
+- `einsatz.latitude`/`einsatz.longitude` replace
+  `geo.latitude`/`geo.longitude` (position is additionally available in
+  `einsatz.json.position`).
+- New state `tts.history10` (last 10 TTS announcements).
+- **Removed:** the entire `vis.*` channel, `json.raw`, `json.einsatz`,
+  `geo.position`, `rueckmeldung.last.json`, `routen.json`,
+  `routen.count`, `einsatz.emWeitere` (now part of `einsatz.json`).
+- The adapter automatically removes all obsolete objects from the
+  previous structure on its first start after the update
+  (`cleanupObsoleteObjects()`).
+
+### 0.3.4 (2026-08-20)
+
+- All state names (`common.name`) consistently switched to German
+  (previously a mix of English and German) – the adapter only makes
+  sense for German-speaking users anyway
+
+### 0.3.3 (2026-08-20)
+
+- **Bugfix (potential data loss):** For a specific monitor ID (≠ `0`),
+  events were silently discarded ("unknownMonitor") after the
+  registration timeout elapsed, because real WAIP payloads, per
+  `client_waip.js`, **never** contain a monitor-identifying field – that
+  assignment happens entirely server-side via Socket.IO rooms. As a
+  result, alarm delivery could stop completely after 10s even though
+  the connection was technically up. `status.registrationAccepted`
+  stayed permanently `false` for the same reason, even for the global
+  monitor (`0`). Now any received event confirms the registration;
+  events are only discarded if a payload explicitly names a different
+  monitor ID.
+
+### 0.3.2 (2026-08-20)
+
+- Also switched the "Registration timeout" and "Reconnect delay" config
+  fields from milliseconds to seconds (`registrationTimeout` →
+  `registrationTimeoutSec`, default `10`; `reconnectDelay` →
+  `reconnectDelaySec`, default `5`). Existing instances without a newly
+  set value automatically use the defaults.
+
+### 0.3.1 (2026-08-20)
+
+- Switched the "Session keepalive interval" config field from
+  milliseconds to seconds (`sessionKeepaliveInterval` →
+  `sessionKeepaliveIntervalSec`, still defaulting to 5 min = `300`).
+  Existing instances without a newly set value automatically use the
+  default.
+
+### 0.3.0 (2026-08-20)
+
+- **Bugfix:** `wgs84_x`/`wgs84_y` were swapped (latitude/longitude). Per
+  the official web frontend (`client_waip.js`), `wgs84_x = latitude,
+  wgs84_y = longitude` – contrary to the usual GIS convention.
+  `geo.latitude`/`geo.longitude` were therefore swapped for directly
+  transmitted coordinates (not the GeoJSON fallback path).
+- Added the missing `io.standby` handler: `status.alarmAktiv` was
+  previously never reset when an incident ended
+- Captured new incident fields (previously only contained in the raw
+  `json.raw`/`json.einsatz`, now as their own states): `zeitstempel`,
+  `einsatznummer`, `objekt`, `objektteil`, `strasse`, `hausnummer`,
+  `einsatzdetails`, `besonderheiten`, `permissions`
+- `em_alarmiert` (alerted resources) is now stored in
+  `vis.fahrzeugTabelle`, `em_weitere` in `einsatz.emWeitere`
+- Feedback is now collected per incident (`vis.rueckmeldungenTabelle`)
+  and aggregated into counters per role/capability
+  (`rueckmeldung.counts.*`), mirroring the live badges
+  (EK/GF/ZF/VF/AGT/FZF/MA/MED) on the web UI
+- New handlers for `io.error` (→ `debug.lastError`) and `io.version`
+  (server-restart detection → session-cookie refresh + forced reconnect)
+- Generalized `reconnectForRotatedSession()` into the more generic
+  `forceReconnect(reason)` (now also used on a server version change)
+
+### 0.2.1 (2026-08-20)
+
+- Detected session-cookie rotation: if `/session/keepalive` returns a
+  different cookie value than before (e.g. because the old session was
+  already invalid server-side – a missed keepalive, a server restart
+  with an in-memory session store), an existing Socket.IO connection is
+  now actively rebuilt with the new session instead of waiting for a
+  silent failure
+
+### 0.2.0 (2026-08-20)
+
+- Introduced session-cookie management: the adapter fetches and renews
+  the WAIP server's `connect.sid` session cookie itself (`GET
+  /session/keepalive`, matching `/js/session_keepalive.js` on the site)
+  and attaches it to the Socket.IO connection. Fixes alarm delivery
+  stopping after about 10 minutes without an active browser session.
+- New state `debug.sessionExpires` and a new config option "Session
+  keepalive interval (ms)" (default `300000`)
+
+### 0.1.1 (2026-08-20)
+
+- Adopted the favicon from `wachalarm.leitstelle-lausitz.de` as the
+  adapter icon (`admin/waip-web.png`), replacing the previous
+  placeholder
+- Renamed the GitHub repository from `ioBroker.WAIP-Web` to
+  `ioBroker.waip-web` (uppercase letters in the repo name prevented
+  installation via `iobroker url` with `Process exited with code 25`);
+  updated all URLs in `package.json`/`io-package.json` accordingly
+
+### 0.1.0 (2026-08-20)
+
+- Initial version: ported the original "WAIP Instrumented v3.9" ioBroker
+  JavaScript-adapter script into a standalone adapter. The URL/monitor
+  ID now come from the admin configuration instead of a runtime state.

package/README.md

@@ -206,6 +206,49 @@ inside the JSON value, not their own ioBroker states.
 
 ## Changelog
 
+### 0.7.6 (2026-08-21)
+
+- Fixed **[W6019]** and **[W0062]**: added `@alcalzone/release-script`
+  and `@alcalzone/release-script-plugin-iobroker` as dev dependencies
+  (with an `npm run release` script), and split this changelog - the 5
+  most recent entries stay here, everything older moved to
+  [CHANGELOG_OLD.md](CHANGELOG_OLD.md). Our existing manual
+  version-bump/tag workflow (see below) is unchanged; the tool is
+  available but not actively used for releasing yet.
+
+### 0.7.5 (2026-08-21)
+
+- Fixed **[E2004]**: removed the orphaned `0.7.3` entry from
+  `common.news` in `io-package.json` - that version (see below) was
+  never actually tagged/published to npm, `0.7.2` was followed directly
+  by `0.7.4`. Confirmed via a bot recheck that every other finding from
+  the last two rounds is now fixed.
+
+### 0.7.4 (2026-08-21)
+
+- Bumped the `ioBroker/testing-action-check` GitHub Action used by the
+  `check-and-lint` CI job from `@v1` to `@v2` (via a
+  [Dependabot](https://github.com/rnc11/ioBroker.waip-web/pull/10) PR -
+  the first one filed by the `.github/dependabot.yml` added in 0.7.3).
+  Purely additive on the action's side (adds an optional `test-command:
+  'false'` flag), no behavior change for us.
+
+### 0.7.3 (2026-08-21)
+
+*(Never tagged/published to npm - superseded directly by 0.7.4; kept
+here for a complete history of what was worked on.)*
+
+- Addressed further findings from the official ioBroker Check and
+  Service Bot (which re-scans the repository after every push):
+  - Removed the deprecated `common.materialize` field from
+    `io-package.json` (superseded by `common.adminUI.config`)
+  - Raised `engines.node` to `>=22` and dropped Node.js 20 (reached
+    End of Life on 2026-04-30) from the CI test matrix
+  - Raised the `admin` dependency to `>=7.8.23`
+  - Moved the `check-and-lint` CI job to Node 24.x
+  - Added `.github/dependabot.yml` for automated dependency updates
+    (weekly `npm`/`github-actions` checks)
+
 ### 0.7.2 (2026-08-21)
 
 - README is now English-only (per the official ioBroker adapter checker,
@@ -230,366 +273,7 @@ inside the JSON value, not their own ioBroker states.
   raised the Node.js version used by the `check-and-lint` and `deploy`
   jobs.
 
-### 0.7.1 (2026-08-21)
-
-- Added a License badge to the README.
-
-### 0.7.0 (2026-08-21)
-
-- Prepared the admin UI for community translation via
-  [ioBroker's Weblate](https://weblate.iobroker.net/engage/adapters/):
-  added `@iobroker/adapter-dev` as a dev dependency (`npm run
-  translate`), converted `admin/jsonConfig.json`'s `label`/`help` fields
-  from inline `en`/`de` objects to plain English keys, and added
-  `admin/i18n/{en,de,ru,pt,nl,fr,it,es,pl,uk,zh-cn}.json` (German
-  curated manually, the rest auto-translated via the official
-  `translate-adapter` tool — the same tool that already maintains the
-  `io-package.json` translations). Added a "Translation status" badge to
-  the README; like the "installed"/"stable" badges, it only shows real
-  data once the adapter is actually registered as a component on
-  weblate.iobroker.net (not done yet).
-
-### 0.6.11 (2026-08-21)
-
-- README: logo now shown enlarged (115×115) via a new
-  `admin/waip-web-logo.png`, nearest-neighbor-scaled from the 32×32
-  source icon for a crisp (if visibly pixelated) result instead of a
-  blurry interpolated one — no higher-resolution source exists anywhere
-  in the WAIP-Web ecosystem (checked the Lausitz instance and the
-  upstream project, both use the same 32×32 favicon). The actual
-  ioBroker adapter icon (`admin/waip-web.png`, referenced from
-  `io-package.json`) is unchanged.
-- Simplified the README title back to "ioBroker.waip-web".
-
-### 0.6.10 (2026-08-21)
-
-- Added the adapter logo and npm/installation badges (NPM version,
-  downloads, installed, stable) to the README, matching standard
-  ioBroker adapter conventions. The "installed"/"stable" badges won't
-  show meaningful data until the adapter is listed in the official
-  [ioBroker.repositories](https://github.com/ioBroker/ioBroker.repositories)
-  ("latest" repository PR pending), but will populate automatically once
-  it is.
-
-### 0.6.9 (2026-08-21)
-
-- Fixed adapter-checker finding **[E254]**: removed `common.news` entries
-  for versions that were never actually published to npm (`0.6.1`–`0.6.5`,
-  `0.6.7` were only version bumps in git/GitHub, without a matching
-  tagged npm release). `common.news` now only lists versions that really
-  exist on the npm registry (`0.6.6`, `0.6.8`); the full history remains
-  in this changelog regardless of what was actually published.
-
-### 0.6.8 (2026-08-21)
-
-- Renamed the README title to "ioBroker-Adapter (ioBroker.waip-web)".
-- This release doubles as the first end-to-end test of the automatic
-  npm publish via Trusted Publishing introduced in 0.6.7.
-
-### 0.6.7 (2026-08-21)
-
-- Enabled automatic npm publishing: the `deploy` job in
-  `.github/workflows/test-and-release.yml` is no longer commented out
-  and now runs on every version tag (`vX.Y.Z`), publishing to npm via
-  [Trusted Publishing](https://docs.npmjs.com/trusted-publishers) (OIDC,
-  no `NPM_TOKEN` secret needed).
-
-### 0.6.6 (2026-08-21)
-
-- Added `.gitattributes` `eol=lf` so all contributors get consistent LF
-  line endings regardless of their local git `autocrlf` setting
-  (previously caused hundreds of spurious local lint errors on Windows
-  without affecting CI, since CI checkouts weren't affected).
-- Added `package-lock.json` and switched CI to the default `npm ci` with
-  caching instead of `npm install` without caching, now that a lockfile
-  exists.
-
-### 0.6.5 (2026-08-21)
-
-- Fixed all issues reported by the official [ioBroker adapter checker](https://adapter-check.iobroker.in/):
-  - Bumped the required `js-controller` dependency to `>=5.0.19` and `@iobroker/adapter-core` to `^3.2.2`
-  - Replaced the deprecated `common.license`/`common.title`/`common.main` fields with `common.licenseInformation`/`common.titleLang`; `common.main` is redundant with `package.json`'s `main` field
-  - Added the required `common.tier` (`2` - external/cloud data source)
-  - Added translations of `titleLang`, `desc` and the kept `common.news` entries into all 10 additional ioBroker admin languages (ru, pt, nl, fr, it, es, pl, uk, zh-cn)
-  - Trimmed `common.news` to the 7 most recent entries, as recommended (the repository builder truncates there anyway); the full history stays in this changelog
-
-### 0.6.4 (2026-08-21)
-
-- New state `status.registeredMonitorName` shows the registered monitor
-  as text without the ID (e.g. "Leitstelle: Lausitz"), resolved once at
-  startup from the same `/waip/` overview page as the admin dropdown.
-  `status.registeredMonitor` is unchanged and keeps showing the ID.
-
-### 0.6.3 (2026-08-21)
-
-- Admin UI: the Monitor ID field is now always full-width, placed on its
-  own row below the WAIP server URL, so the (sometimes long) dropdown
-  entries have enough room to display without being cramped.
-
-### 0.6.2 (2026-08-21)
-
-- Monitor dropdown entries are now sorted by numeric monitor ID instead
-  of following the source page's (per-category) order.
-
-### 0.6.1 (2026-08-21)
-
-- Monitor dropdown entries now start with the actual monitor ID, e.g.
-  "4 - Leitstelle: Lausitz", so the numeric ID stays visible even after
-  a monitor has been selected.
-
-### 0.6.0 (2026-08-21)
-
-- **Admin UI:** Monitor ID is now a live dropdown (`selectSendTo`) instead
-  of a plain text field. The adapter fetches the configured server's
-  public `/waip/` overview page on demand and offers every monitor it
-  finds there, grouped by Leitstelle/Kreis/Träger/Wache, with "Alle
-  Wachalarme" (ID `0`) as an explicit first option. Manual entry remains
-  available if the server can't be reached or uses a different page
-  layout, so existing configurations keep working unchanged.
-- Removed the static "session keepalive interval" info text from the
-  admin UI (the behavior itself is unchanged - see [Why a session cookie
-  is needed](#why-a-session-cookie-is-needed)).
-- Added help text to the "Registration timeout" and "Reconnect delay"
-  fields.
-
-### 0.5.1 (2026-08-21)
-
-- **Logging:** Reclassified log levels so `warn` becomes a reliable signal
-  again. Session-cookie rotation, the known "Fehler beim Erneuern der
-  Session" server message, and detected server restarts are now logged
-  as `info` instead of `warn`, since they're part of this instance's
-  normal, self-healing ~10-minute session cycle. Events discarded for a
-  different monitor ID are now `info` (frequency remains tracked via
-  `debug.ignoredCount`). Failures that only affect internal housekeeping
-  (`debug.monitorAudit`, socket cleanup) are now `debug`. A duplicate
-  `connect_error` log line (logged once at `warn`, once at `info`) was
-  removed. Introduced `error` level for cases where an incident,
-  feedback, route or TTS event genuinely failed to be processed (actual
-  data loss), so these now stand out instead of being buried among
-  routine `warn` noise.
-
-### 0.5.0 (2026-08-20)
-
-- **Behavior change:** On `io.standby`, all `einsatz.*` states (including
-  `einsatz.json` and all counters) are now cleared instead of leaving the
-  finished incident's data in place – matching the official frontend,
-  which also clears keyword, location data etc. on standby.
-  `status.alarmAktiv` is therefore now a reliable switch for whether
-  `einsatz.*` currently holds real live data. The finished incident
-  remains fully available via `einsatz.history10` (archived there first).
-
-### 0.4.9 (2026-08-20)
-
-- **CI fix:** Reverted a self-introduced, unnecessary line wrap in
-  `connect()` (engine-packet preview) – `prettier/prettier` flagged it as
-  superfluous; the line actually fits on one line within the configured
-  print width.
-
-### 0.4.8 (2026-08-20)
-
-- **CI fix:** Fixed the final 16 lint errors – this time the complete,
-  non-truncated error list including the exact desired replacement text
-  was available, so every location could be corrected precisely 1:1
-  (line wraps for overly long calls/objects, one `prefer-template`
-  case). Lint should now be fully green.
-
-### 0.4.7 (2026-08-20)
-
-- **CI fix:** Fixed the remaining lint errors in `main.js` – consistently
-  applied `curly` (braces even for single-line `if`/`for`),
-  `no-unused-vars` for empty `catch` blocks (`catch (e) {}` → `catch {}`
-  where `e` isn't used), and `arrowParens: avoid` (removed parentheses
-  around single-parameter arrow functions). Purely mechanical code-style
-  fixes, no behavior change.
-
-### 0.4.6 (2026-08-20)
-
-- **CI fix:** The `lint` step failed with hundreds of formatting errors
-  (e.g. "Replace 'x' with "x""). Cause: `@iobroker/eslint-config`
-  requires its own `prettier.config.mjs` in addition to
-  `eslint.config.mjs`, re-exporting the ioBroker formatting style
-  (single quotes, 4-space indentation, `trailingComma: 'all'`) – without
-  it, Prettier fell back to its own defaults (double quotes). File added.
-
-### 0.4.5 (2026-08-20)
-
-- **CI fix:** The first pipeline run failed with "Dependencies lock file
-  is not found". Cause: `actions/setup-node`'s built-in npm caching
-  needs a `package-lock.json` for its cache key, independent of the
-  install command used. Since none is committed to the repo yet,
-  `package-cache: 'false'` is now set on both jobs.
-
-### 0.4.4 (2026-08-20)
-
-- Set up the CI pipeline (`.github/workflows/test-and-release.yml`),
-  following the standard pattern of the official
-  `@iobroker/create-adapter` template: a `check-and-lint` job (ESLint
-  via `@iobroker/eslint-config`) and an `adapter-tests` matrix (Node
-  20/22/24 × Ubuntu/Windows/macOS) via the central
-  `testing-action-check`/`testing-action-adapter` actions. Added
-  `test/package.js` and `test/integration.js` (`@iobroker/testing`)
-  plus `eslint.config.mjs` for this; bumped `@iobroker/testing` to
-  `^5.2.2`. Since no `package-lock.json` is committed yet, the pipeline
-  uses `npm install` instead of `npm ci`.
-- Raised `engines.node` in `package.json` to `>=18` (matching the tested
-  Node versions and `@iobroker/testing` 5.x's requirements)
-- A `deploy` job (automatic npm publishing) is prepared but commented
-  out until npm Trusted Publishing is set up
-
-### 0.4.3 (2026-08-20)
-
-- **Bugfix:** `einsatz.id` and `einsatz.sondersignal` were declared as
-  `string`, but the server actually sends them as numbers
-  (`sondersignal`, per `client_waip.js`: `switch (data.sondersignal) {
-  case 1: ... }`) – ioBroker therefore logged a type warning on every
-  incident. Both states are now declared as `number`. Existing objects
-  with the old (wrong) type are automatically recreated on the next
-  adapter start (`migrateObjectTypes()`, generic for future type
-  corrections).
-
-### 0.4.2 (2026-08-20)
-
-- Removed the "Session keepalive interval – upper bound" config field
-  again: the official `/js/session_keepalive.js` on the site hard-codes
-  this upper bound at 5 minutes and doesn't make it configurable. Having
-  an admin field for it wrongly suggested a fixed interval, even though
-  the actual renewal has long been fully automatic (see 0.4.1). The
-  upper bound is now likewise fixed at 5 minutes.
-
-### 0.4.1 (2026-08-20)
-
-- **Robustness:** The session keepalive interval is now adaptive instead
-  of a fixed assumption. WAIP-Web's source code (`server/app_cfg.js`)
-  shows that the session cookie's lifetime is configurable per instance
-  via an environment variable (server default: 60s instead of the
-  previously assumed 10 minutes) – the adapter now derives the renewal
-  interval from the expiry time actually reported by the server
-  (matching `/js/session_keepalive.js` on the site: 80% of the observed
-  lifetime, min. 55s, at most the configured upper bound). The "Session
-  keepalive interval" config option is accordingly now an upper bound
-  rather than a fixed interval.
-- Corrected a comment about `io.version`/server restarts: per
-  `server/auth.js`, WAIP-Web stores sessions persistently (SQLite), not
-  in-memory – a restart therefore normally doesn't clear them. The
-  proactive session refresh + reconnect on server restart remains as a
-  general safeguard, only the previous justification was inaccurate.
-
-### 0.4.0 (2026-08-20)
-
-- **Restructured the object tree:** Feedback and routes are 1:n lists
-  per incident and now live as nested JSON arrays inside one overall
-  object `einsatz.json` (including `emAlarmiert[]`, `emWeitere[]`,
-  `routen[]`, `rueckmeldungen[]`) instead of several loose states.
-- `einsatz.history10` replaces `history.last10` – now with the **full**
-  nested incident object per entry instead of just 6 reduced fields.
-- New counters directly under `einsatz.*`: `routenGesamt`,
-  `rueckmeldungGesamt`, `rueckmeldungAnzahl.{ek,gf,zf,vf,agt,fzf,ma,med}`
-  (replaces `rueckmeldung.counts.*`).
-- `einsatz.latitude`/`einsatz.longitude` replace
-  `geo.latitude`/`geo.longitude` (position is additionally available in
-  `einsatz.json.position`).
-- New state `tts.history10` (last 10 TTS announcements).
-- **Removed:** the entire `vis.*` channel, `json.raw`, `json.einsatz`,
-  `geo.position`, `rueckmeldung.last.json`, `routen.json`,
-  `routen.count`, `einsatz.emWeitere` (now part of `einsatz.json`).
-- The adapter automatically removes all obsolete objects from the
-  previous structure on its first start after the update
-  (`cleanupObsoleteObjects()`).
-
-### 0.3.4 (2026-08-20)
-
-- All state names (`common.name`) consistently switched to German
-  (previously a mix of English and German) – the adapter only makes
-  sense for German-speaking users anyway
-
-### 0.3.3 (2026-08-20)
-
-- **Bugfix (potential data loss):** For a specific monitor ID (≠ `0`),
-  events were silently discarded ("unknownMonitor") after the
-  registration timeout elapsed, because real WAIP payloads, per
-  `client_waip.js`, **never** contain a monitor-identifying field – that
-  assignment happens entirely server-side via Socket.IO rooms. As a
-  result, alarm delivery could stop completely after 10s even though
-  the connection was technically up. `status.registrationAccepted`
-  stayed permanently `false` for the same reason, even for the global
-  monitor (`0`). Now any received event confirms the registration;
-  events are only discarded if a payload explicitly names a different
-  monitor ID.
-
-### 0.3.2 (2026-08-20)
-
-- Also switched the "Registration timeout" and "Reconnect delay" config
-  fields from milliseconds to seconds (`registrationTimeout` →
-  `registrationTimeoutSec`, default `10`; `reconnectDelay` →
-  `reconnectDelaySec`, default `5`). Existing instances without a newly
-  set value automatically use the defaults.
-
-### 0.3.1 (2026-08-20)
-
-- Switched the "Session keepalive interval" config field from
-  milliseconds to seconds (`sessionKeepaliveInterval` →
-  `sessionKeepaliveIntervalSec`, still defaulting to 5 min = `300`).
-  Existing instances without a newly set value automatically use the
-  default.
-
-### 0.3.0 (2026-08-20)
-
-- **Bugfix:** `wgs84_x`/`wgs84_y` were swapped (latitude/longitude). Per
-  the official web frontend (`client_waip.js`), `wgs84_x = latitude,
-  wgs84_y = longitude` – contrary to the usual GIS convention.
-  `geo.latitude`/`geo.longitude` were therefore swapped for directly
-  transmitted coordinates (not the GeoJSON fallback path).
-- Added the missing `io.standby` handler: `status.alarmAktiv` was
-  previously never reset when an incident ended
-- Captured new incident fields (previously only contained in the raw
-  `json.raw`/`json.einsatz`, now as their own states): `zeitstempel`,
-  `einsatznummer`, `objekt`, `objektteil`, `strasse`, `hausnummer`,
-  `einsatzdetails`, `besonderheiten`, `permissions`
-- `em_alarmiert` (alerted resources) is now stored in
-  `vis.fahrzeugTabelle`, `em_weitere` in `einsatz.emWeitere`
-- Feedback is now collected per incident (`vis.rueckmeldungenTabelle`)
-  and aggregated into counters per role/capability
-  (`rueckmeldung.counts.*`), mirroring the live badges
-  (EK/GF/ZF/VF/AGT/FZF/MA/MED) on the web UI
-- New handlers for `io.error` (→ `debug.lastError`) and `io.version`
-  (server-restart detection → session-cookie refresh + forced reconnect)
-- Generalized `reconnectForRotatedSession()` into the more generic
-  `forceReconnect(reason)` (now also used on a server version change)
-
-### 0.2.1 (2026-08-20)
-
-- Detected session-cookie rotation: if `/session/keepalive` returns a
-  different cookie value than before (e.g. because the old session was
-  already invalid server-side – a missed keepalive, a server restart
-  with an in-memory session store), an existing Socket.IO connection is
-  now actively rebuilt with the new session instead of waiting for a
-  silent failure
-
-### 0.2.0 (2026-08-20)
-
-- Introduced session-cookie management: the adapter fetches and renews
-  the WAIP server's `connect.sid` session cookie itself (`GET
-  /session/keepalive`, matching `/js/session_keepalive.js` on the site)
-  and attaches it to the Socket.IO connection. Fixes alarm delivery
-  stopping after about 10 minutes without an active browser session.
-- New state `debug.sessionExpires` and a new config option "Session
-  keepalive interval (ms)" (default `300000`)
-
-### 0.1.1 (2026-08-20)
-
-- Adopted the favicon from `wachalarm.leitstelle-lausitz.de` as the
-  adapter icon (`admin/waip-web.png`), replacing the previous
-  placeholder
-- Renamed the GitHub repository from `ioBroker.WAIP-Web` to
-  `ioBroker.waip-web` (uppercase letters in the repo name prevented
-  installation via `iobroker url` with `Process exited with code 25`);
-  updated all URLs in `package.json`/`io-package.json` accordingly
-
-### 0.1.0 (2026-08-20)
-
-- Initial version: ported the original "WAIP Instrumented v3.9" ioBroker
-  JavaScript-adapter script into a standalone adapter. The URL/monitor
-  ID now come from the admin configuration instead of a runtime state.
+Older entries have moved to [CHANGELOG_OLD.md](CHANGELOG_OLD.md).
 
 ## License
 

package/io-package.json

@@ -1,8 +1,47 @@
 {
   "common": {
     "name": "waip-web",
-    "version": "0.7.2",
+    "version": "0.7.6",
     "news": {
+      "0.7.6": {
+        "en": "Fixed [W6019] and [W0062]: added @alcalzone/release-script and @alcalzone/release-script-plugin-iobroker as dev dependencies (with an npm run release script), and split the README changelog - the 5 most recent entries stay in README.md, everything older moved to a new CHANGELOG_OLD.md. Our existing manual version-bump/tag workflow is unchanged; the release-script tooling is available but not actively used for releasing yet.",
+        "de": "[W6019] und [W0062] behoben: @alcalzone/release-script sowie @alcalzone/release-script-plugin-iobroker als Dev-Dependencies ergänzt (mit npm run release-Skript), README-Changelog aufgeteilt - die 5 neuesten Einträge bleiben in README.md, alles Ältere ist in eine neue CHANGELOG_OLD.md ausgelagert. Unser bisheriger manueller Versions-/Tag-Workflow bleibt unverändert; das release-script-Tooling steht bereit, wird aber noch nicht aktiv zum Veröffentlichen genutzt.",
+        "ru": "Исправлены [W6019] и [W0062]: добавлены dev-зависимости @alcalzone/release-script и @alcalzone/release-script-plugin-iobroker (со скриптом npm run release), а changelog в README разделён — 5 последних записей остаются в README.md, всё более старое перенесено в новый файл CHANGELOG_OLD.md. Наш существующий ручной процесс повышения версии/тегирования не изменился; инструмент release-script доступен, но пока активно не используется для релизов.",
+        "pt": "Corrigidos [W6019] e [W0062]: adicionadas as dependências de desenvolvimento @alcalzone/release-script e @alcalzone/release-script-plugin-iobroker (com um script npm run release), e o changelog do README foi dividido - as 5 entradas mais recentes permanecem no README.md, tudo o que é mais antigo foi movido para um novo CHANGELOG_OLD.md. Nosso fluxo manual existente de aumento de versão/tag permanece inalterado; a ferramenta release-script está disponível, mas ainda não é usada ativamente para lançamentos.",
+        "nl": "[W6019] en [W0062] opgelost: @alcalzone/release-script en @alcalzone/release-script-plugin-iobroker toegevoegd als dev-dependencies (met een npm run release-script), en de README-changelog opgesplitst - de 5 meest recente items blijven in README.md, al het oudere is verplaatst naar een nieuwe CHANGELOG_OLD.md. Onze bestaande handmatige versie-/tag-workflow blijft ongewijzigd; de release-script-tooling is beschikbaar maar wordt nog niet actief gebruikt om te releasen.",
+        "fr": "Correction de [W6019] et [W0062] : ajout de @alcalzone/release-script et @alcalzone/release-script-plugin-iobroker comme dépendances de développement (avec un script npm run release), et division du changelog du README - les 5 entrées les plus récentes restent dans README.md, tout ce qui est plus ancien a été déplacé vers un nouveau CHANGELOG_OLD.md. Notre flux de travail manuel existant de bump de version/tag reste inchangé ; l'outillage release-script est disponible mais pas encore activement utilisé pour publier.",
+        "it": "Risolti [W6019] e [W0062]: aggiunte le dev-dependency @alcalzone/release-script e @alcalzone/release-script-plugin-iobroker (con uno script npm run release), e il changelog del README è stato suddiviso - le 5 voci più recenti restano in README.md, tutto ciò che è più vecchio è stato spostato in un nuovo CHANGELOG_OLD.md. Il nostro flusso di lavoro manuale esistente per bump di versione/tag resta invariato; lo strumento release-script è disponibile ma non ancora usato attivamente per i rilasci.",
+        "es": "Se corrigieron [W6019] y [W0062]: se añadieron @alcalzone/release-script y @alcalzone/release-script-plugin-iobroker como dependencias de desarrollo (con un script npm run release), y se dividió el changelog del README - las 5 entradas más recientes permanecen en README.md, todo lo más antiguo se movió a un nuevo CHANGELOG_OLD.md. Nuestro flujo de trabajo manual existente de incremento de versión/etiquetado no cambia; la herramienta release-script está disponible pero aún no se usa activamente para publicar.",
+        "pl": "Naprawiono [W6019] i [W0062]: dodano @alcalzone/release-script oraz @alcalzone/release-script-plugin-iobroker jako zależności deweloperskie (ze skryptem npm run release), a changelog w README podzielono - 5 najnowszych wpisów pozostaje w README.md, wszystko starsze przeniesiono do nowego pliku CHANGELOG_OLD.md. Nasz dotychczasowy ręczny proces podnoszenia wersji/tagowania pozostaje bez zmian; narzędzie release-script jest dostępne, ale nie jest jeszcze aktywnie używane do wydawania wersji.",
+        "uk": "Виправлено [W6019] і [W0062]: додано @alcalzone/release-script та @alcalzone/release-script-plugin-iobroker як dev-залежності (зі скриптом npm run release), а changelog у README розділено - 5 найновіших записів залишаються в README.md, усе старіше перенесено до нового файлу CHANGELOG_OLD.md. Наш наявний ручний процес підвищення версії/тегування не змінився; інструмент release-script доступний, але поки що активно не використовується для релізів.",
+        "zh-cn": "修复了 [W6019] 和 [W0062]:添加了 @alcalzone/release-script 和 @alcalzone/release-script-plugin-iobroker 作为开发依赖(附带 npm run release 脚本),并拆分了 README 的更新日志——最近的 5 个条目保留在 README.md 中,更早的全部移至新的 CHANGELOG_OLD.md。我们现有的手动版本提升/打标签流程保持不变;release-script 工具已就绪,但目前尚未积极用于发布。"
+      },
+      "0.7.5": {
+        "en": "Fixed [E2004]: removed the orphaned 0.7.3 news entry - that version was never actually tagged/published to npm (0.7.2 was followed directly by 0.7.4). Confirmed via a bot recheck that every other finding from the last two rounds is now fixed.",
+        "de": "[E2004] behoben: verwaisten 0.7.3-News-Eintrag entfernt - diese Version wurde nie tatsächlich getaggt/bei npm veröffentlicht (auf 0.7.2 folgte direkt 0.7.4). Per Bot-Recheck bestätigt, dass alle übrigen Findings der letzten beiden Runden jetzt behoben sind.",
+        "ru": "Исправлено [E2004]: удалена осиротевшая запись новостей 0.7.3 - эта версия так и не была помечена тегом/опубликована на npm (после 0.7.2 сразу последовала 0.7.4). Повторной проверкой бота подтверждено, что все остальные замечания последних двух раундов теперь исправлены.",
+        "pt": "Corrigido [E2004]: removida a entrada de notícias órfã 0.7.3 - essa versão nunca foi de fato marcada com tag/publicada no npm (0.7.2 foi seguida diretamente por 0.7.4). Confirmado por uma nova verificação do bot que todos os outros apontamentos das últimas duas rodadas agora estão corrigidos.",
+        "nl": "[E2004] opgelost: verweesd 0.7.3-nieuwsitem verwijderd - die versie is nooit daadwerkelijk getagd/gepubliceerd op npm (op 0.7.2 volgde direct 0.7.4). Via een herscan van de bot bevestigd dat alle overige bevindingen van de laatste twee rondes nu zijn opgelost.",
+        "fr": "Correction de [E2004] : suppression de l'entrée de nouvelles orpheline 0.7.3 - cette version n'a jamais été réellement taguée/publiée sur npm (0.7.2 a été directement suivie de 0.7.4). Une nouvelle vérification du bot a confirmé que toutes les autres remarques des deux derniers cycles sont désormais corrigées.",
+        "it": "Risolto [E2004]: rimossa la voce di news orfana 0.7.3 - quella versione non è mai stata effettivamente taggata/pubblicata su npm (a 0.7.2 è seguita direttamente 0.7.4). Un nuovo controllo del bot ha confermato che tutte le altre segnalazioni degli ultimi due round sono ora risolte.",
+        "es": "Se corrigió [E2004]: se eliminó la entrada de noticias huérfana 0.7.3 - esa versión nunca se etiquetó/publicó realmente en npm (a 0.7.2 le siguió directamente 0.7.4). Una nueva verificación del bot confirmó que todos los demás hallazgos de las últimas dos rondas ya están corregidos.",
+        "pl": "Naprawiono [E2004]: usunięto osierocony wpis news 0.7.3 - ta wersja nigdy nie została faktycznie otagowana/opublikowana w npm (po 0.7.2 nastąpiło bezpośrednio 0.7.4). Ponowna kontrola bota potwierdziła, że wszystkie pozostałe ustalenia z ostatnich dwóch rund są już naprawione.",
+        "uk": "Виправлено [E2004]: видалено осиротілий запис новин 0.7.3 - цю версію так і не було позначено тегом/опубліковано на npm (після 0.7.2 одразу йшла 0.7.4). Повторна перевірка бота підтвердила, що всі інші зауваження останніх двох раундів тепер виправлені.",
+        "zh-cn": "修复了 [E2004]:移除了孤立的 0.7.3 新闻条目——该版本从未真正打过标签/发布到 npm(0.7.2 之后直接跳到了 0.7.4)。机器人的重新检查已确认最近两轮的其余所有问题现已修复。"
+      },
+      "0.7.4": {
+        "en": "Bumped the ioBroker/testing-action-check GitHub Action used by the check-and-lint CI job from v1 to v2 (Dependabot PR #10) - purely additive (adds an optional test-command: 'false' flag), no behavior change for us.",
+        "de": "GitHub-Action ioBroker/testing-action-check im check-and-lint-CI-Job von v1 auf v2 angehoben (Dependabot-PR #10) - rein additiv (fügt eine optionale test-command: 'false'-Option hinzu), kein Verhaltensunterschied für uns.",
+        "ru": "Обновлён GitHub Action ioBroker/testing-action-check, используемый в задаче CI check-and-lint, с v1 до v2 (Dependabot PR #10) — чисто аддитивное изменение (добавляет опциональный флаг test-command: 'false'), поведение для нас не меняется.",
+        "pt": "Atualizada a GitHub Action ioBroker/testing-action-check usada pelo job de CI check-and-lint de v1 para v2 (Dependabot PR #10) - puramente aditiva (adiciona uma flag opcional test-command: 'false'), sem mudança de comportamento para nós.",
+        "nl": "GitHub Action ioBroker/testing-action-check, gebruikt door de CI-job check-and-lint, bijgewerkt van v1 naar v2 (Dependabot PR #10) - puur additief (voegt een optionele test-command: 'false'-vlag toe), geen gedragsverandering voor ons.",
+        "fr": "Mise à jour de l'action GitHub ioBroker/testing-action-check utilisée par le job CI check-and-lint, de v1 à v2 (PR Dependabot #10) - purement additive (ajoute un indicateur optionnel test-command: 'false'), aucun changement de comportement pour nous.",
+        "it": "Aggiornata l'azione GitHub ioBroker/testing-action-check usata dal job CI check-and-lint da v1 a v2 (PR Dependabot #10) - puramente additiva (aggiunge un flag opzionale test-command: 'false'), nessun cambiamento di comportamento per noi.",
+        "es": "Actualizada la GitHub Action ioBroker/testing-action-check usada por el job de CI check-and-lint de v1 a v2 (PR de Dependabot #10) - puramente aditiva (añade una opción opcional test-command: 'false'), sin cambio de comportamiento para nosotros.",
+        "pl": "Zaktualizowano akcję GitHub ioBroker/testing-action-check używaną przez zadanie CI check-and-lint z v1 do v2 (PR Dependabota #10) - czysto addytywnie (dodaje opcjonalną flagę test-command: 'false'), bez zmiany zachowania dla nas.",
+        "uk": "Оновлено GitHub Action ioBroker/testing-action-check, яку використовує завдання CI check-and-lint, з v1 до v2 (Dependabot PR #10) - суто адитивно (додає опціональний прапорець test-command: 'false'), без зміни поведінки для нас.",
+        "zh-cn": "将 check-and-lint CI 任务使用的 ioBroker/testing-action-check GitHub Action 从 v1 升级到 v2(Dependabot PR #10)——纯增量更新(新增可选的 test-command: 'false' 标志),对我们没有行为影响。"
+      },
       "0.7.2": {
         "en": "Fixed all findings from the official ioBroker Check and Service Bot: raised Node.js/dependency minimums (engines.node >=20, @iobroker/adapter-core ^3.4.1, js-controller >=6.0.11, admin >=7.6.17), split the README into English-only (README.md) and German (README.de.md) since the checker requires English-only READMEs, moved License to the very last section, added the required i18n/size attributes to jsonConfig.json, switched to node: prefixes for built-in requires, removed the redundant .npmignore, and added .commitinfo to .gitignore. Also removed the orphaned 0.7.0 news entry (never actually published to npm).",
         "de": "Alle Findings des offiziellen ioBroker Check and Service Bot behoben: Mindestversionen angehoben (engines.node >=20, @iobroker/adapter-core ^3.4.1, js-controller >=6.0.11, admin >=7.6.17), README aufgeteilt in rein englisches README.md und deutsches README.de.md (der Checker verlangt rein englische READMEs), Lizenz-Abschnitt ans Dateiende verschoben, fehlende i18n-/Größenattribute in jsonConfig.json ergänzt, auf node:-Präfixe bei Built-in-Requires umgestellt, überflüssige .npmignore entfernt und .commitinfo zur .gitignore hinzugefügt. Außerdem den verwaisten 0.7.0-News-Eintrag entfernt (wurde nie tatsächlich bei npm veröffentlicht).",
@@ -54,45 +93,6 @@
         "pl": "Dodano logo adaptera oraz odznaki npm/instalacji (wersja NPM, pobrania, zainstalowano, stabilna) do README, zgodnie ze standardowymi konwencjami adapterów ioBroker.",
         "uk": "До README додано логотип адаптера та значки npm/встановлення (версія NPM, завантаження, встановлено, стабільна версія) відповідно до стандартних угод адаптерів ioBroker.",
         "zh-cn": "已在 README 中添加适配器徽标以及 npm/安装徽章(NPM 版本、下载量、已安装数量、稳定版),符合 ioBroker 适配器的标准约定。"
-      },
-      "0.6.9": {
-        "en": "Removed common.news entries for versions that were never actually published to npm (0.6.1-0.6.5, 0.6.7 - only version bumps in git, no matching npm release), as reported by the official adapter checker.",
-        "de": "common.news-Einträge für Versionen entfernt, die nie tatsächlich bei npm veröffentlicht wurden (0.6.1-0.6.5, 0.6.7 - nur Versionserhöhungen in git, keine passende npm-Veröffentlichung), wie vom offiziellen Adapter-Checker gemeldet.",
-        "ru": "Удалены записи common.news для версий, которые фактически никогда не публиковались в npm (0.6.1–0.6.5, 0.6.7 — только повышения версии в git без соответствующего релиза npm), как сообщил официальный чекер адаптеров.",
-        "pt": "Removidas entradas de common.news para versões que nunca foram realmente publicadas no npm (0.6.1-0.6.5, 0.6.7 - apenas incrementos de versão no git, sem lançamento npm correspondente), conforme relatado pelo verificador oficial de adaptadores.",
-        "nl": "common.news-items verwijderd voor versies die nooit daadwerkelijk op npm zijn gepubliceerd (0.6.1-0.6.5, 0.6.7 - alleen versieverhogingen in git, geen bijbehorende npm-release), zoals gemeld door de officiële adapter-checker.",
-        "fr": "Suppression des entrées common.news pour des versions qui n'ont jamais été réellement publiées sur npm (0.6.1-0.6.5, 0.6.7 - simples incréments de version dans git, sans publication npm correspondante), comme signalé par le vérificateur officiel d'adaptateurs.",
-        "it": "Rimosse le voci common.news per versioni mai effettivamente pubblicate su npm (0.6.1-0.6.5, 0.6.7 - solo incrementi di versione in git, senza una release npm corrispondente), come segnalato dal checker ufficiale degli adapter.",
-        "es": "Se eliminaron las entradas de common.news para versiones que nunca se publicaron realmente en npm (0.6.1-0.6.5, 0.6.7 - solo incrementos de versión en git, sin la correspondiente publicación en npm), según lo indicado por el verificador oficial de adaptadores.",
-        "pl": "Usunięto wpisy common.news dla wersji, które nigdy nie zostały faktycznie opublikowane w npm (0.6.1-0.6.5, 0.6.7 - tylko podniesienia wersji w git, bez odpowiadającego wydania npm), zgodnie z raportem oficjalnego checkera adapterów.",
-        "uk": "Видалено записи common.news для версій, які фактично ніколи не публікувалися в npm (0.6.1-0.6.5, 0.6.7 - лише підвищення версії в git без відповідного релізу npm), як повідомив офіційний перевірник адаптерів.",
-        "zh-cn": "移除了从未真正发布到 npm 的版本的 common.news 条目(0.6.1-0.6.5、0.6.7——仅在 git 中提升了版本号,没有对应的 npm 发布),这是官方适配器检查器报告的问题。"
-      },
-      "0.6.8": {
-        "en": "Renamed the README title to \"ioBroker-Adapter (ioBroker.waip-web)\". This release doubles as the first end-to-end test of the automatic npm publish via Trusted Publishing introduced in 0.6.7.",
-        "de": "README-Titel auf „ioBroker-Adapter (ioBroker.waip-web)\" geändert. Dieses Release dient gleichzeitig als erster Test der in 0.6.7 eingeführten automatischen npm-Veröffentlichung über Trusted Publishing.",
-        "ru": "Заголовок README изменён на «ioBroker-Adapter (ioBroker.waip-web)». Этот релиз одновременно служит первым сквозным тестом автоматической публикации в npm через Trusted Publishing, введённой в версии 0.6.7.",
-        "pt": "Título do README alterado para \"ioBroker-Adapter (ioBroker.waip-web)\". Este lançamento também serve como o primeiro teste completo da publicação automática no npm via Trusted Publishing, introduzida na 0.6.7.",
-        "nl": "README-titel gewijzigd naar \"ioBroker-Adapter (ioBroker.waip-web)\". Deze release dient ook als de eerste end-to-end test van het automatisch publiceren naar npm via Trusted Publishing, geïntroduceerd in 0.6.7.",
-        "fr": "Titre du README changé en « ioBroker-Adapter (ioBroker.waip-web) ». Cette version sert également de premier test de bout en bout de la publication automatique sur npm via Trusted Publishing, introduite dans la 0.6.7.",
-        "it": "Titolo del README modificato in \"ioBroker-Adapter (ioBroker.waip-web)\". Questa release funge anche da primo test end-to-end della pubblicazione automatica su npm tramite Trusted Publishing, introdotta nella 0.6.7.",
-        "es": "Título del README cambiado a \"ioBroker-Adapter (ioBroker.waip-web)\". Esta versión también sirve como la primera prueba de extremo a extremo de la publicación automática en npm mediante Trusted Publishing, introducida en la 0.6.7.",
-        "pl": "Zmieniono tytuł README na \"ioBroker-Adapter (ioBroker.waip-web)\". To wydanie służy również jako pierwszy pełny test automatycznej publikacji w npm przez Trusted Publishing, wprowadzonej w wersji 0.6.7.",
-        "uk": "Заголовок README змінено на «ioBroker-Adapter (ioBroker.waip-web)». Цей реліз також слугує першим наскрізним тестом автоматичної публікації в npm через Trusted Publishing, введеної у версії 0.6.7.",
-        "zh-cn": "已将 README 标题更改为 \"ioBroker-Adapter (ioBroker.waip-web)\"。此版本同时也是对 0.6.7 中引入的通过 Trusted Publishing 自动发布到 npm 功能的首次端到端测试。"
-      },
-      "0.6.6": {
-        "en": "Added .gitattributes eol=lf so all contributors get consistent LF line endings regardless of local git autocrlf settings (previously caused hundreds of spurious local lint errors on Windows without affecting CI). Added package-lock.json and switched CI to the default npm ci with caching instead of npm install without caching.",
-        "de": "eol=lf in .gitattributes ergänzt, damit alle Mitwirkenden unabhängig von ihrer lokalen git-autocrlf-Einstellung konsistente LF-Zeilenenden erhalten (verursachte zuvor unter Windows lokal hunderte unnötige Lint-Fehler, ohne die CI zu betreffen). package-lock.json ergänzt und CI von npm install ohne Caching auf das Standard-npm-ci mit Caching umgestellt.",
-        "ru": "Добавлен eol=lf в .gitattributes, чтобы все участники получали единообразные окончания строк LF независимо от локальной настройки git autocrlf (ранее это вызывало сотни ложных ошибок линтера локально на Windows, не влияя на CI). Добавлен package-lock.json, CI переведён с npm install без кэширования на стандартный npm ci с кэшированием.",
-        "pt": "Adicionado eol=lf ao .gitattributes para que todos os colaboradores tenham finais de linha LF consistentes, independentemente da configuração local de autocrlf do git (antes causava centenas de erros de lint falsos localmente no Windows, sem afetar o CI). Adicionado package-lock.json e o CI foi alterado de npm install sem cache para o npm ci padrão com cache.",
-        "nl": "eol=lf toegevoegd aan .gitattributes zodat alle bijdragers consistente LF-regeleinden krijgen, ongeacht hun lokale git-autocrlf-instelling (veroorzaakte voorheen honderden onnodige lokale lintfouten op Windows, zonder invloed op CI). package-lock.json toegevoegd en CI omgezet van npm install zonder caching naar de standaard npm ci met caching.",
-        "fr": "Ajout de eol=lf dans .gitattributes afin que tous les contributeurs obtiennent des fins de ligne LF cohérentes, quel que soit leur réglage local git autocrlf (provoquait auparavant des centaines de fausses erreurs de lint locales sous Windows, sans affecter la CI). Ajout de package-lock.json et passage de la CI de npm install sans cache au npm ci standard avec cache.",
-        "it": "Aggiunto eol=lf in .gitattributes così tutti i collaboratori ottengono terminazioni di riga LF coerenti indipendentemente dall'impostazione locale di git autocrlf (in precedenza causava centinaia di falsi errori di lint locali su Windows, senza influire sulla CI). Aggiunto package-lock.json e la CI è passata da npm install senza cache al npm ci predefinito con cache.",
-        "es": "Se añadió eol=lf a .gitattributes para que todos los colaboradores obtengan finales de línea LF consistentes, independientemente de su configuración local de git autocrlf (antes causaba cientos de errores de lint falsos localmente en Windows, sin afectar a la CI). Se añadió package-lock.json y la CI pasó de npm install sin caché al npm ci estándar con caché.",
-        "pl": "Dodano eol=lf w .gitattributes, aby wszyscy współtwórcy mieli spójne zakończenia linii LF niezależnie od lokalnego ustawienia git autocrlf (wcześniej powodowało to setki fałszywych lokalnych błędów lint w systemie Windows, nie wpływając na CI). Dodano package-lock.json i przełączono CI z npm install bez cache na domyślne npm ci z cache.",
-        "uk": "Додано eol=lf у .gitattributes, щоб усі учасники отримували однакові закінчення рядків LF незалежно від локального налаштування git autocrlf (раніше це спричиняло сотні хибних локальних помилок лінтера у Windows, не впливаючи на CI). Додано package-lock.json, а CI переведено з npm install без кешування на стандартний npm ci з кешуванням.",
-        "zh-cn": "在 .gitattributes 中添加了 eol=lf,确保所有贡献者无论本地 git autocrlf 设置如何都能获得一致的 LF 换行符(此前在 Windows 上会导致本地出现数百个虚假的 lint 错误,但不影响 CI)。新增了 package-lock.json,并将 CI 从不带缓存的 npm install 切换为带缓存的默认 npm ci。"
       }
     },
     "titleLang": {
@@ -148,7 +148,6 @@
     "messagebox": true,
     "connectionType": "cloud",
     "dataSource": "push",
-    "materialize": false,
     "adminUI": {
       "config": "json"
     },
@@ -159,7 +158,7 @@
     ],
     "globalDependencies": [
       {
-        "admin": ">=7.6.17"
+        "admin": ">=7.8.23"
       }
     ]
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "iobroker.waip-web",
-  "version": "0.7.2",
+  "version": "0.7.6",
   "description": "Wachalarm IP-Web (WAIP) Adapter für ioBroker – bindet Alarmierungen, Rückmeldungen, Routen und TTS-Ansagen per Socket.IO an ioBroker an.",
   "author": {
     "name": "rnc11",
@@ -24,7 +24,7 @@
     "url": "https://github.com/rnc11/ioBroker.waip-web/issues"
   },
   "engines": {
-    "node": ">=20"
+    "node": ">=22"
   },
   "main": "main.js",
   "files": [
@@ -33,13 +33,16 @@
     "io-package.json",
     "main.js",
     "LICENSE",
-    "README.de.md"
+    "README.de.md",
+    "CHANGELOG_OLD.md"
   ],
   "dependencies": {
     "@iobroker/adapter-core": "^3.4.1",
     "socket.io-client": "^4.7.5"
   },
   "devDependencies": {
+    "@alcalzone/release-script": "^5.2.1",
+    "@alcalzone/release-script-plugin-iobroker": "^5.2.0",
     "@iobroker/adapter-dev": "^1.5.0",
     "@iobroker/eslint-config": "^2.2.0",
     "@iobroker/testing": "^5.2.2"
@@ -49,6 +52,7 @@
     "test:integration": "mocha test/integration.js --exit",
     "test": "npm run test:package",
     "lint": "eslint -c eslint.config.mjs .",
-    "translate": "translate-adapter"
+    "translate": "translate-adapter",
+    "release": "release-script"
   }
 }