iobroker.waip-web 0.7.9 → 0.7.12

package/README.de.md

@@ -130,7 +130,8 @@ und Trigger ohne JSON-Parsing auskommen.
 | `restzeit` | number (s) | Verbleibende Sekunden bis `einsatz.ablaufzeit`, sekündlich aktualisiert |
 | `registeredMonitor` | string | Zuletzt beim Server registrierte Monitor-ID |
 | `registeredMonitorName` | string | Anzeigename dieses Monitors ohne ID (z. B. „Leitstelle: Lausitz"); wird einmalig beim Start von derselben `/waip/`-Übersichtsseite wie das Admin-Dropdown aufgelöst, `null` falls nicht auflösbar |
-| `registrationAccepted` | mixed | `"pending"` direkt nach Connect, `true` sobald das erste Event empfangen wurde, sonst `false` nach Ablauf des Registrierungs-Timeouts |
+| `registrationAccepted` | boolean | `true` sobald das erste Event empfangen wurde, sonst `false` direkt nach Connect oder nach Ablauf des Registrierungs-Timeouts |
+| `registrationPending` | boolean | `true` direkt nach Connect, solange noch auf eine Antwort vom Server gewartet wird, sonst `false` sobald bestätigt oder Timeout erreicht |
 
 ### einsatz
 
@@ -156,7 +157,7 @@ stehen. Der zuletzt abgeschlossene Einsatz bleibt trotzdem über
 | `ablaufzeit` | string (date) | Ende der Standby-Anzeigedauer, Basis für `status.restzeit` |
 | `einsatznummer` | string | Einsatznummer (sofern vom Server vergeben) |
 | `sondersignal` | number | `1` = Sondersignal, sonst kein Sondersignal |
-| `permissions` | mixed | Berechtigungsflag der Registrierung (Vollzugriff auf Detailkarte ja/nein) |
+| `permissions` | string | Berechtigungsflag der Registrierung (Vollzugriff auf Detailkarte ja/nein); wird immer als String gespeichert (z.B. `"true"`), da der Server hier ein rohes Boolean sendet |
 | `latitude` / `longitude` | number | Position des Einsatzortes (normalisiert aus wgs84-Feldern oder GeoJSON-Mittelpunkt) |
 | `json` | string (JSON) | Vollständiges Einsatz-Objekt: alle Felder oben plus `emAlarmiert[]`, `emWeitere[]`, `routen[]`, `rueckmeldungen[]` |
 | `history10` | string (JSON-Array) | Letzte 10 abgeschlossenen Einsätze, gleicher Objekt-Shape wie `json`, geschrieben bei `io.standby` |

package/README.md

@@ -138,7 +138,8 @@ bindings and triggers don't need JSON parsing.
 | `restzeit` | number (s) | Remaining seconds until `einsatz.ablaufzeit`, updated every second |
 | `registeredMonitor` | string | Monitor ID last registered with the server |
 | `registeredMonitorName` | string | Display name of that monitor, without the ID (e.g. "Leitstelle: Lausitz"); resolved once at startup from the same `/waip/` overview page as the admin dropdown, `null` if it couldn't be resolved |
-| `registrationAccepted` | mixed | `"pending"` right after connecting, `true` once the first event was received, otherwise `false` once the registration timeout elapses |
+| `registrationAccepted` | boolean | `true` once the first event was received, `false` right after connecting or once the registration timeout elapses |
+| `registrationPending` | boolean | `true` right after connecting while a response from the server is still awaited, `false` once accepted or timed out |
 
 ### einsatz
 
@@ -164,7 +165,7 @@ live data. The most recently finished incident remains available via
 | `ablaufzeit` | string (date) | End of the standby display duration, basis for `status.restzeit` |
 | `einsatznummer` | string | Incident number (if assigned by the server) |
 | `sondersignal` | number | `1` = special signal (lights & siren), otherwise none |
-| `permissions` | mixed | The registration's permission flag (full access to the detail map yes/no) |
+| `permissions` | string | The registration's permission flag (full access to the detail map yes/no); always stringified (e.g. `"true"`), since the server sends it as a raw boolean |
 | `latitude` / `longitude` | number | Incident location (normalized from wgs84 fields or GeoJSON centroid) |
 | `json` | string (JSON) | Complete incident object: all fields above plus `emAlarmiert[]`, `emWeitere[]`, `routen[]`, `rueckmeldungen[]` |
 | `history10` | string (JSON array) | Last 10 completed incidents, same object shape as `json`, written on `io.standby` |
@@ -206,6 +207,36 @@ inside the JSON value, not their own ioBroker states.
 
 ## Changelog
 
+### 0.7.12 (2026-08-21)
+
+- Fixed **[E3005]**: `einsatz.permissions` is declared as
+  `common.type: "string"`, but `setField()` passed raw
+  booleans/numbers through unchanged (the WAIP server sends this
+  field as a raw boolean flag), so the stored `val` didn't match the
+  declared type. `setField()` now looks up the declared type and
+  always stringifies values for string-typed states, regardless of
+  the incoming JS type - found by the `ioBroker.repositories` object
+  structure check.
+
+### 0.7.11 (2026-08-21)
+
+- Fixed **[E3009]** (57 findings): added the missing channel/folder
+  objects (`status`, `einsatz`, `einsatz.rueckmeldungAnzahl`, `debug`,
+  `tts`) that ioBroker requires for every state path segment - found
+  by the `ioBroker.repositories` object structure check.
+- Fixed **[E3005]**/**[E1009]**: replaced the unsupported
+  `common.type: "mixed"` on `einsatz.permissions` (now `string`) and
+  `status.registrationAccepted` (now split into two booleans:
+  `registrationAccepted` and the new `registrationPending`).
+
+### 0.7.10 (2026-08-21)
+
+- Fixed **[S9508]**: excluded `CHANGELOG_OLD.md` from the npm package
+  (removed from `package.json`'s `files` allowlist) - ioBroker shows
+  the README via a GitHub link, not from the installed npm package, so
+  the file remains fully readable on GitHub without needing to ship
+  inside the tarball.
+
 ### 0.7.9 (2026-08-21)
 
 - Fixed **[E5025]**/**[E5036]**: installed the missing
@@ -236,16 +267,6 @@ inside the JSON value, not their own ioBroker states.
   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)
-
-*(Also never tagged/published to npm - superseded directly by 0.7.6.)*
-
-- 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.
-
 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.9",
+    "version": "0.7.12",
     "news": {
+      "0.7.12": {
+        "en": "Fixed [E3005]: einsatz.permissions is declared as common.type \"string\", but setField() passed raw booleans/numbers through unchanged (the WAIP server sends this field as a raw boolean flag), so the stored val didn't match the declared type. setField() now looks up the declared type and always stringifies values for string-typed states, regardless of the incoming JS type.",
+        "de": "[E3005] behoben: einsatz.permissions ist als common.type \"string\" deklariert, setField() ließ rohe Booleans/Zahlen aber unverändert durch (der WAIP-Server sendet dieses Feld als rohes Boolean-Flag), wodurch der gespeicherte val nicht zum deklarierten Typ passte. setField() ermittelt jetzt den deklarierten Typ und stringifiziert Werte für string-typisierte States immer, unabhängig vom eingehenden JS-Typ.",
+        "ru": "Исправлено [E3005]: einsatz.permissions объявляется как common.type «строка», но setField() передает необработанные логические значения/числа без изменений (сервер WAIP отправляет это поле как необработанный логический флаг), поэтому сохраненное значение не соответствует объявленному типу. setField() теперь ищет объявленный тип и всегда преобразует в строку значения для состояний строкового типа, независимо от входящего типа JS.",
+        "pt": "Corrigido [E3005]: einsatz.permissions é declarado como common.type \"string\", mas setField() passava booleanos/números brutos inalterados (o servidor WAIP envia este campo como um sinalizador booleano bruto), então o val armazenado não correspondia ao tipo declarado. setField() agora procura o tipo declarado e sempre codifica valores para estados digitados em string, independentemente do tipo JS de entrada.",
+        "nl": "Opgelost [E3005]: einsatz.permissions wordt gedeclareerd als common.type \"string\", maar setField() gaf onbewerkte booleans/getallen ongewijzigd door (de WAIP-server verzendt dit veld als een onbewerkte booleaanse vlag), dus de opgeslagen waarde kwam niet overeen met het gedeclareerde type. setField() zoekt nu het gedeclareerde type op en tekent altijd waarden voor string-getypeerde toestanden, ongeacht het binnenkomende JS-type.",
+        "fr": "Corrigé [E3005] : einsatz.permissions est déclaré comme common.type \"string\", mais setField() transmettait les booléens/nombres bruts sans modification (le serveur WAIP envoie ce champ comme un indicateur booléen brut), donc la valeur stockée ne correspondait pas au type déclaré. setField() recherche désormais le type déclaré et chaîne toujours les valeurs pour les états typés chaîne, quel que soit le type JS entrant.",
+        "it": "Risolto [E3005]: einsatz.permissions è dichiarato come common.type \"string\", ma setField() ha passato booleani/numeri grezzi senza modifiche (il server WAIP invia questo campo come flag booleano grezzo), quindi il val memorizzato non corrispondeva al tipo dichiarato. setField() ora cerca il tipo dichiarato e stringa sempre i valori per gli stati tipizzati come stringa, indipendentemente dal tipo JS in entrata.",
+        "es": "Corregido [E3005]: einsatz.permissions se declara como \"cadena\" common.type, pero setField() pasó números/booleanos sin cambios sin cambios (el servidor WAIP envía este campo como un indicador booleano sin formato), por lo que el valor almacenado no coincidía con el tipo declarado. setField() ahora busca el tipo declarado y siempre codifica valores para estados tipo cadena, independientemente del tipo JS entrante.",
+        "pl": "Naprawiono [E3005]: einsatz.permissions jest zadeklarowane jako common.type „string”, ale setField() przekazała surowe wartości logiczne/liczby bez zmian (serwer WAIP wysyła to pole jako surową flagę boolowską), więc przechowywana wartość nie pasowała do zadeklarowanego typu. setField() wyszukuje teraz zadeklarowany typ i zawsze stringuje wartości dla stanów typu string, niezależnie od przychodzącego typu JS.",
+        "uk": "Виправлено [E3005]: einsatz.permissions оголошено як common.type \"рядок\", але setField() передав необроблені логічні значення/числа без змін (сервер WAIP надсилає це поле як необроблений логічний прапор), тому збережене значення не відповідало заявленому типу. setField() тепер шукає оголошений тип і завжди перетворює значення в рядки для рядкових типів станів, незалежно від вхідного типу JS.",
+        "zh-cn": "已修复 [E3005]：einsatz.permissions 被声明为 common.type“string”，但 setField() 未更改地传递原始布尔值/数字（WAIP 服务器将此字段作为原始布尔标志发送），因此存储的 val 与声明的类型不匹配。 setField() 现在查找声明的类型，并始终对字符串类型状态的值进行字符串化，无论传入的 JS 类型如何。"
+      },
+      "0.7.11": {
+        "en": "Fixed [E3009] (57 findings): added the missing channel/folder objects (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) that ioBroker requires for every state path segment. Fixed [E3005]/[E1009]: replaced the unsupported common.type 'mixed' on einsatz.permissions (now string) and status.registrationAccepted (now split into two booleans: registrationAccepted and the new registrationPending) - all found by the ioBroker.repositories object structure check.",
+        "de": "[E3009] behoben (57 Fundstellen): fehlende Channel-/Folder-Objekte (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) ergänzt, die ioBroker für jedes Pfadsegment eines States benötigt. [E3005]/[E1009] behoben: den nicht unterstützten common.type 'mixed' bei einsatz.permissions (jetzt string) und status.registrationAccepted (jetzt aufgeteilt in zwei Booleans: registrationAccepted und den neuen registrationPending) ersetzt - alles gefunden beim Objektstruktur-Check von ioBroker.repositories.",
+        "ru": "Исправлено [E3009] (57 результатов): добавлены отсутствующие объекты канала/папки (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts), которые ioBroker требует для каждого сегмента пути к состоянию. Исправлено [E3005]/[E1009]: заменен неподдерживаемый common.type «mixed» на einsatz.permissions (теперь строка) и status.registrationAccepted (теперь разделен на два логических значения: RegistrationAccepted и новое RegistrationPending) – все они найдены при проверке структуры объекта ioBroker.repositories.",
+        "pt": "Corrigido [E3009] (57 descobertas): foram adicionados os objetos de canal/pasta ausentes (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) que o ioBroker requer para cada segmento de caminho de estado. Corrigido [E3005]/[E1009]: substituiu o common.type 'mixed' não suportado em einsatz.permissions (agora string) e status.registrationAccepted (agora dividido em dois booleanos: RegistrationAccepted e o novo RegistrationPending) - todos encontrados pela verificação da estrutura do objeto ioBroker.repositories.",
+        "nl": "Opgelost [E3009] (57 bevindingen): de ontbrekende kanaal-/mapobjecten toegevoegd (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) die ioBroker nodig heeft voor elk statuspadsegment. [E3005]/[E1009] opgelost: het niet-ondersteunde common.type 'gemengd' vervangen op einsatz.permissions (nu string) en status.registrationAccepted (nu opgesplitst in twee booleans: RegistrationAccepted en de nieuwe RegistrationPending) - allemaal gevonden door de controle van de objectstructuur van ioBroker.repositories.",
+        "fr": "Corrigé [E3009] (57 résultats) : ajout des objets canal/dossier manquants (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) dont ioBroker a besoin pour chaque segment de chemin d'état. Corrigé [E3005]/[E1009] : remplacement du common.type 'mixed' non pris en charge par einsatz.permissions (maintenant chaîne) et status.registrationAccepted (maintenant divisé en deux booléens : RegistrationAccepted et le nouveau RegistrationPending) - tous trouvés par la vérification de la structure de l'objet ioBroker.repositories.",
+        "it": "Risolto [E3009] (57 risultati): aggiunti gli oggetti canale/cartella mancanti (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) che ioBroker richiede per ogni segmento del percorso di stato. Risolto il problema [E3005]/[E1009]: sostituito il common.type 'mixed' non supportato su einsatz.permissions (ora stringa) e status.registrationAccepted (ora diviso in due booleani: RegistrationAccepted e il nuovo RegistrationPending) - tutti trovati dal controllo della struttura dell'oggetto ioBroker.repositories.",
+        "es": "Corregido [E3009] (57 hallazgos): se agregaron los objetos de canal/carpeta faltantes (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts) que ioBroker requiere para cada segmento de ruta de estado. Se corrigió [E3005]/[E1009]: reemplazó el common.type 'mixed' no admitido en einsatz.permissions (ahora cadena) y status.registrationAccepted (ahora dividido en dos booleanos: RegistrationAccepted y el nuevo RegistrationPending): todos encontrados mediante la verificación de la estructura del objeto ioBroker.repositories.",
+        "pl": "Naprawiono [E3009] (57 wyników): dodano brakujące obiekty kanału/folderu (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts), których ioBroker wymaga dla każdego segmentu ścieżki stanu. Naprawiono [E3005]/[E1009]: zastąpiono nieobsługiwany typ common.type „mixed” w einsatz.permissions (teraz ciąg znaków) i status.registrationAccepted (teraz podzielony na dwie wartości logiczne: RegistrationAccepted i nowa rejestracjaPending) – wszystkie znalezione podczas sprawdzania struktury obiektu ioBroker.repositories.",
+        "uk": "Виправлено [E3009] (57 знахідок): додано відсутні об’єкти каналу/папки (status, einsatz, einsatz.rueckmeldungAnzahl, debug, tts), які потрібні ioBroker для кожного сегмента шляху стану. Виправлено [E3005]/[E1009]: замінено непідтримуваний common.type «mixed» на einsatz.permissions (тепер рядок) і status.registrationAccepted (тепер розділений на два логічних значення: registrationAccepted і нове registrationPending) — усе це виявлено під час перевірки структури об’єкта ioBroker.repositories.",
+        "zh-cn": "修复了 [E3009]（57 个结果）：添加了 ioBroker 为每个状态路径段所需的缺失通道/文件夹对象（状态、einsatz、einsatz.rueckmeldungAnzahl、调试、tts）。修复了 [E3005]/[E1009]：替换了 einsatz.permissions（现在为字符串）和 status.registrationAccepted（现在分为两个布尔值：registrationAccepted 和新的 RegistrationPending）上不支持的 common.type 'mixed' - 所有这些都由 ioBroker.repositories 对象结构检查找到。"
+      },
+      "0.7.10": {
+        "en": "Fixed [S9508]: excluded CHANGELOG_OLD.md from the npm package (removed from package.json's files allowlist) - ioBroker shows the README via a GitHub link, not from the installed npm package, so the file remains fully readable on GitHub without needing to ship inside the tarball.",
+        "de": "[S9508] behoben: CHANGELOG_OLD.md aus dem npm-Paket ausgeschlossen (aus der files-Liste in package.json entfernt) - ioBroker zeigt das README über einen GitHub-Link an, nicht aus dem installierten npm-Paket, die Datei bleibt also auf GitHub weiterhin vollständig lesbar, ohne im Tarball enthalten sein zu müssen.",
+        "ru": "Исправлено [S9508]: CHANGELOG_OLD.md исключён из npm-пакета (удалён из списка files в package.json) - ioBroker показывает README по ссылке на GitHub, а не из установленного npm-пакета, поэтому файл остаётся полностью читаемым на GitHub без необходимости включать его в архив.",
+        "pt": "Corrigido [S9508]: CHANGELOG_OLD.md excluído do pacote npm (removido da lista files em package.json) - o ioBroker exibe o README via link do GitHub, não a partir do pacote npm instalado, então o arquivo permanece totalmente legível no GitHub sem precisar estar no tarball.",
+        "nl": "[S9508] opgelost: CHANGELOG_OLD.md uitgesloten van het npm-pakket (verwijderd uit de files-lijst in package.json) - ioBroker toont het README via een GitHub-link, niet vanuit het geïnstalleerde npm-pakket, dus het bestand blijft volledig leesbaar op GitHub zonder in de tarball te hoeven zitten.",
+        "fr": "Correction de [S9508] : exclusion de CHANGELOG_OLD.md du paquet npm (retiré de la liste files dans package.json) - ioBroker affiche le README via un lien GitHub, pas depuis le paquet npm installé, le fichier reste donc entièrement lisible sur GitHub sans devoir être inclus dans l'archive.",
+        "it": "Risolto [S9508]: escluso CHANGELOG_OLD.md dal pacchetto npm (rimosso dall'elenco files in package.json) - ioBroker mostra il README tramite un link GitHub, non dal pacchetto npm installato, quindi il file resta pienamente leggibile su GitHub senza dover essere incluso nel tarball.",
+        "es": "Se corrigió [S9508]: se excluyó CHANGELOG_OLD.md del paquete npm (eliminado de la lista files en package.json) - ioBroker muestra el README mediante un enlace de GitHub, no desde el paquete npm instalado, por lo que el archivo sigue siendo totalmente legible en GitHub sin necesidad de incluirlo en el tarball.",
+        "pl": "Naprawiono [S9508]: wykluczono CHANGELOG_OLD.md z pakietu npm (usunięto z listy files w package.json) - ioBroker wyświetla README przez link do GitHub, a nie z zainstalowanego pakietu npm, więc plik pozostaje w pełni czytelny na GitHub bez konieczności umieszczania go w tarballu.",
+        "uk": "Виправлено [S9508]: виключено CHANGELOG_OLD.md з npm-пакета (видалено зі списку files у package.json) - ioBroker показує README через посилання на GitHub, а не з встановленого npm-пакета, тож файл залишається повністю доступним для читання на GitHub без потреби включати його до архіву.",
+        "zh-cn": "修复了 [S9508]:已将 CHANGELOG_OLD.md 从 npm 包中排除(从 package.json 的 files 列表中移除)——ioBroker 通过 GitHub 链接显示 README,而不是从已安装的 npm 包中读取,因此该文件在 GitHub 上仍然完全可读,无需包含在发布包中。"
+      },
       "0.7.9": {
         "en": "Fixed [E5025]/[E5036]: installed the missing @alcalzone/release-script-plugin-license devDependency required for the 'license' plugin referenced in .releaseconfig.json.",
         "de": "[E5025]/[E5036] behoben: fehlende Dev-Dependency @alcalzone/release-script-plugin-license nachinstalliert, die für das in .releaseconfig.json referenzierte 'license'-Plugin benötigt wird.",
@@ -80,19 +119,6 @@
         "pl": "Naprawiono wszystkie ustalenia oficjalnego ioBroker Check and Service Bot: podniesiono minimalne wersje (engines.node >=20, @iobroker/adapter-core ^3.4.1, js-controller >=6.0.11, admin >=7.6.17), README podzielono na anglojęzyczny README.md i niemiecki README.de.md (checker wymaga README wyłącznie po angielsku), sekcję License przeniesiono na sam koniec, dodano brakujące atrybuty i18n/rozmiaru w jsonConfig.json, przełączono na prefiks node: dla wbudowanych require, usunięto zbędny .npmignore i dodano .commitinfo do .gitignore. Usunięto też osierocony wpis news 0.7.0 (nigdy faktycznie nie opublikowany w npm).",
         "uk": "Виправлено всі зауваження офіційного ioBroker Check and Service Bot: підвищено мінімальні версії (engines.node >=20, @iobroker/adapter-core ^3.4.1, js-controller >=6.0.11, admin >=7.6.17), README розділено на англомовний README.md та німецький README.de.md (перевірник вимагає README лише англійською), розділ License переміщено в самий кінець, додано відсутні атрибути i18n/розміру в jsonConfig.json, вбудовані require переведено на префікс node:, видалено зайвий .npmignore та додано .commitinfo до .gitignore. Також видалено осиротілий запис новин 0.7.0 (ніколи не публікувався на npm).",
         "zh-cn": "修复了官方 ioBroker Check and Service Bot 报告的所有问题:提升了最低版本要求(engines.node >=20、@iobroker/adapter-core ^3.4.1、js-controller >=6.0.11、admin >=7.6.17);将 README 拆分为纯英文的 README.md 和德文的 README.de.md(检查器要求 README 仅使用英文);将 License 部分移动到文件末尾;为 jsonConfig.json 添加了缺失的 i18n/尺寸属性;将内置模块的 require 改为使用 node: 前缀;移除了多余的 .npmignore;并在 .gitignore 中添加了 .commitinfo。同时移除了从未真正发布到 npm 的孤立新闻条目 0.7.0。"
-      },
-      "0.7.1": {
-        "en": "Added a License badge to the README.",
-        "de": "Lizenz-Badge im README ergänzt.",
-        "ru": "В README добавлен значок лицензии.",
-        "pt": "Adicionado um selo de licença ao README.",
-        "nl": "Licentiebadge toegevoegd aan de README.",
-        "fr": "Ajout d'un badge de licence au README.",
-        "it": "Aggiunto un badge di licenza al README.",
-        "es": "Se añadió una insignia de licencia al README.",
-        "pl": "Dodano odznakę licencji do README.",
-        "uk": "До README додано значок ліцензії.",
-        "zh-cn": "已在 README 中添加许可证徽章。"
       }
     },
     "titleLang": {

package/main.js

@@ -95,6 +95,17 @@ const OBSOLETE_OBJECT_IDS = [
     'routen.count',
 ];
 
+// Übergeordnete Channel/Folder-Objekte, die für jeden State-Zweig existieren müssen.
+// ioBroker verlangt ein eigenes Objekt für jedes Segment eines State-Pfads - reine
+// State-Blätter (siehe STATE_DEFS) reichen dafür nicht aus.
+const CHANNEL_DEFS = [
+    { id: 'status', type: 'channel', name: 'Verbindungs- und Registrierungsstatus' },
+    { id: 'einsatz', type: 'channel', name: 'Aktueller Einsatz' },
+    { id: 'einsatz.rueckmeldungAnzahl', type: 'folder', name: 'Rückmeldungen nach Funktion' },
+    { id: 'debug', type: 'channel', name: 'Diagnose- und Debug-Informationen' },
+    { id: 'tts', type: 'channel', name: 'TTS-Ansagen' },
+];
+
 // Definition aller States, die beim Start sichergestellt werden.
 const STATE_DEFS = [
     {
@@ -122,9 +133,17 @@ const STATE_DEFS = [
     },
     {
         id: 'status.registrationAccepted',
-        type: 'mixed',
+        type: 'boolean',
+        role: 'indicator',
+        name: 'Registrierung bestätigt',
+        def: false,
+    },
+    {
+        id: 'status.registrationPending',
+        type: 'boolean',
         role: 'indicator',
-        name: 'Registrierung bestätigt (true/false/pending)',
+        name: 'Registrierung angefragt, Antwort vom Server steht noch aus',
+        def: false,
     },
     { id: 'debug.lastEvent', type: 'string', role: 'json', name: 'Letztes empfangenes Socket-Event' },
     { id: 'debug.normalizedPosition', type: 'string', role: 'json', name: 'Letzte normalisierte Position' },
@@ -162,7 +181,7 @@ const STATE_DEFS = [
     { id: 'einsatz.ablaufzeit', type: 'string', role: 'date', name: 'Ablaufzeit' },
     { id: 'einsatz.einsatznummer', type: 'string', role: 'text', name: 'Einsatznummer' },
     { id: 'einsatz.sondersignal', type: 'number', role: 'value', name: 'Sondersignal', def: 0 },
-    { id: 'einsatz.permissions', type: 'mixed', role: 'json', name: 'Berechtigungs-Flag der Registrierung' },
+    { id: 'einsatz.permissions', type: 'string', role: 'json', name: 'Berechtigungs-Flag der Registrierung' },
     { id: 'einsatz.latitude', type: 'number', role: 'value.gps.latitude', name: 'Breitengrad' },
     { id: 'einsatz.longitude', type: 'number', role: 'value.gps.longitude', name: 'Längengrad' },
     // verschachteltes Gesamtobjekt + Historie
@@ -236,6 +255,8 @@ const STATE_DEFS = [
     { id: 'tts.lastTimestamp', type: 'string', role: 'date', name: 'Zeitstempel letzte TTS-Ansage' },
     { id: 'tts.history10', type: 'string', role: 'json', name: `Letzte ${HISTORY_SIZE} TTS-Ansagen (JSON-Array)` },
 ];
+// Schneller Zugriff von setField() auf den deklarierten Typ eines States (siehe dort).
+const STATE_DEF_BY_ID = new Map(STATE_DEFS.map(def => [def.id, def]));
 
 /* Prüft ob eine monitorID gültig ist (nicht-leer). */
 function isValidMonitor(mon) {
@@ -572,6 +593,13 @@ class WaipWeb extends utils.Adapter {
     }
 
     async initObjects() {
+        for (const def of CHANNEL_DEFS) {
+            await this.setObjectNotExistsAsync(def.id, {
+                type: def.type,
+                common: { name: def.name },
+                native: {},
+            });
+        }
         for (const def of STATE_DEFS) {
             await this.setObjectNotExistsAsync(def.id, {
                 type: 'state',
@@ -934,7 +962,16 @@ class WaipWeb extends utils.Adapter {
     async setField(path, val) {
         try {
             let toSet;
-            if (val === null || typeof val === 'string' || typeof val === 'number' || typeof val === 'boolean') {
+            const def = STATE_DEF_BY_ID.get(path);
+            if (val === null) {
+                toSet = null;
+            } else if (def && def.type === 'string') {
+                // Der State ist als "string" deklariert (z.B. role "json") - unabhängig vom
+                // tatsächlichen JS-Typ der Serverantwort (etwa ein rohes Boolean/Number-Flag
+                // wie bei einsatz.permissions) muss "val" den deklarierten Typ einhalten,
+                // sonst schlägt die ioBroker-Objektstrukturprüfung fehl (E3005).
+                toSet = typeof val === 'string' ? val : JSON.stringify(val);
+            } else if (typeof val === 'string' || typeof val === 'number' || typeof val === 'boolean') {
                 toSet = val;
             } else {
                 toSet = JSON.stringify(val);
@@ -1028,6 +1065,7 @@ class WaipWeb extends utils.Adapter {
                         this.registrationTimer = null;
                     }
                     this.registrationPending = false;
+                    this.setState('status.registrationPending', false, true);
                 }
 
                 try {
@@ -1448,6 +1486,7 @@ class WaipWeb extends utils.Adapter {
             this.socket = null;
             this.connecting = false;
             this.registrationPending = false;
+            this.setState('status.registrationPending', false, true);
             if (this.registrationTimer) {
                 this.clearTimeout(this.registrationTimer);
                 this.registrationTimer = null;
@@ -1512,13 +1551,15 @@ class WaipWeb extends utils.Adapter {
         // Gecachter Anzeigename (siehe refreshMonitorName) - keine erneute HTTP-Abfrage
         // bei jedem (Re-)Connect, ist ggf. beim allerersten Connect noch null.
         this.setState('status.registeredMonitorName', this.monitorName, true);
-        this.setState('status.registrationAccepted', 'pending', true);
+        this.setState('status.registrationAccepted', false, true);
+        this.setState('status.registrationPending', true, true);
         if (this.registrationTimer) {
             this.clearTimeout(this.registrationTimer);
             this.registrationTimer = null;
         }
         this.registrationTimer = this.setTimeout(async () => {
             this.registrationPending = false;
+            this.setState('status.registrationPending', false, true);
             const accState = await this.getStateAsync('status.registrationAccepted');
             const acc = accState ? accState.val : null;
             if (acc !== true) {
@@ -1545,6 +1586,7 @@ class WaipWeb extends utils.Adapter {
         this.logDisconnect(`Socket disconnected: ${reason}`);
         this.registrationPending = false;
         this.setState('status.registrationAccepted', false, true);
+        this.setState('status.registrationPending', false, true);
         if (this.registrationTimer) {
             this.clearTimeout(this.registrationTimer);
             this.registrationTimer = null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "iobroker.waip-web",
-  "version": "0.7.9",
+  "version": "0.7.12",
   "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",
@@ -33,8 +33,7 @@
     "io-package.json",
     "main.js",
     "LICENSE",
-    "README.de.md",
-    "CHANGELOG_OLD.md"
+    "README.de.md"
   ],
   "dependencies": {
     "@iobroker/adapter-core": "^3.4.1",

package/CHANGELOG_OLD.md

@@ -1,410 +0,0 @@
-# Older changes
-
-### 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,
-  which flags mixed-language READMEs); the German version moved to a
-  separate [README.de.md](README.de.md), linked near the top.
-- Moved the License section to the very end of the file (was before the
-  Changelog) - the checker requires License to be the last section.
-- `package.json`: raised `engines.node` to `>=20` and `@iobroker/adapter-core`
-  to `^3.4.1`.
-- `io-package.json`: raised the `js-controller` dependency to `>=6.0.11`
-  and the `admin` dependency to `>=7.6.17`; removed the `0.7.0` news
-  entry (never published to npm, only `0.7.1` and later actually are).
-- `admin/jsonConfig.json`: added the root `"i18n": true` attribute (now
-  required since the fields resolve translations from `admin/i18n/*.json`)
-  and explicit `xs`/`xl` grid sizes on all fields.
-- `main.js`: `require('http')`/`require('https')`/`require('url')` now
-  use the `node:` prefix for Node's built-in modules.
-- `.gitignore`: added `.commitinfo`.
-- Removed `.npmignore` - redundant with the `files` allowlist already
-  used in `package.json`.
-- CI: `adapter-tests` now explicitly declares `needs: check-and-lint`;
-  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).
-- 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.