iobroker.waip-web 0.7.28 → 0.7.30

package/README.de.md

@@ -4,7 +4,7 @@
 
 🇬🇧 [English version of this README](README.md)
 
-Inoffizieller ioBroker-Adapter für **Wachalarm IP-Web (WAIP-Web)**
+ioBroker-Adapter für **Wachalarm IP-Web (WAIP-Web)**
 
 Verbindet sich per Socket.IO mit einem WAIP-Web-Wachalarm-Monitor und bildet
 Einsätze, Rückmeldungen, Routen und TTS-Ansagen als ioBroker-States ab –
@@ -31,7 +31,7 @@ ohne dass ein Browser-Tab dauerhaft offen sein muss.
 
 ## Über diesen Adapter
 
-Dieser Adapter ist ein **inoffizielles Community-Projekt** und steht in
+Dieser Adapter ist ein **eigenständiges Community-Projekt** und steht in
 keiner Verbindung zum WAIP-Web-Projekt, zu Robert-112 oder zum Betreiber
 einer konkreten Instanz (z. B. der Integrierten Regionalleitstelle
 Lausitz). Er wurde entwickelt, indem das öffentlich über den Browser
@@ -180,9 +180,13 @@ Rettungsdienst-Wache:
   eigenen Region ohnehin nur unzuverlässig signalisiert, siehe
   [Rettungsdienst](#rettungsdienst)
 - Optionales Einsatzkarten-Bild: ein auf die Einsatz-Koordinaten
-  zentriertes und mit einem Punkt markiertes PNG, lokal aus
-  OpenStreetMap-Kacheln zusammengesetzt, dessen Dateipfad als State
-  bereitsteht - siehe [Einsatzkarte](#einsatzkarte)
+  zentriertes PNG, lokal aus OpenStreetMap-Kacheln zusammengesetzt, mit
+  dem von WAIP-Web gesendeten Einsatzgebiet als Umriss in
+  konfigurierbarer Farbe/Stärke eingezeichnet (umschaltbar auf eine
+  einfache Punkt-Markierung), zoomt bei Bedarf automatisch so heraus,
+  dass das gesamte Gebiet sichtbar bleibt, Dateipfad als State
+  bereitgestellt -
+  siehe [Einsatzkarte](#einsatzkarte)
 
 ## Konfiguration
 
@@ -248,7 +252,7 @@ werden dabei keine Daten irgendwohin gesendet. Dieser Tab ist die erste
 von zwei Quellen, die der Reihe nach geprüft werden (die zweite steht
 unter [Stichwort-Stammdaten](#stichwort-stammdaten)):
 
-**Rettungsdienst-Dekodierung** (Admin-Checkbox, standardmäßig aus):
+**Rettungsdienst-Dekodierung** (Admin-Checkbox, standardmäßig an):
 passt das Stichwort auf das Muster `R<Anzahl RTW>N<Anzahl NEF>[p][f][-NT]`
 (z.B. `R1N0` → "Rettungswagen: 1, Notfalleinsatzfahrzeug: 0"), wird
 automatisch eine Beschreibung erzeugt. Zwei Schreibweisen des
@@ -258,8 +262,9 @@ vor `NT` (z.B. `R1N1p`, `R1N0-NT`, siehe
 dazu) sowie mit Leerzeichen und ohne Bindestrich (z.B. `R1N1 p`,
 `R1N0 nt`, wie von der IRLS Brandenburg verwendet) – dieses Schema
 (in beiden Schreibweisen) wird von mehreren Leitstellen verwendet,
-nicht nur diesen beiden – nur aktivieren, wenn eure Leitstelle eines
-dieser Muster tatsächlich verwendet. Der Text für jeden Teil ist
+nicht nur diesen beiden – hat keine Auswirkung, falls eure Leitstelle
+keines dieser Muster verwendet, da das Stichwort dann einfach nicht
+passt. Der Text für jeden Teil ist
 selbst konfigurierbar (5 zusätzliche Textfelder erscheinen, sobald
 die Checkbox aktiviert ist), da der Adapter mehrsprachig ist und
 diese Bezeichnungen nicht automatisch übersetzt werden:
@@ -307,12 +312,28 @@ Passt weder diese Tabelle noch der Dekoder oben, bleibt
 aus): ist die Checkbox aktiv und liegen für einen Einsatz gültige
 Koordinaten vor, lädt der Adapter die dafür nötigen Kacheln vom
 öffentlichen Server `tile.openstreetmap.org` herunter, setzt sie zu
-einem einzigen PNG zusammen, zentriert auf den Einsatzort, zeichnet eine
-Markierung (roter Punkt, weißer Rand) exakt in die Mitte und stempelt
+einem einzigen PNG zusammen, zentriert auf den Einsatzort, und stempelt
 die von der ODbL-Lizenz vorgeschriebene OpenStreetMap-Attribution unten
-links auf. Der Dateipfad wird in `einsatz.kartenbildPfad` geschrieben
-(siehe [einsatz](#einsatz)) – typische Verwendung ist der Versand dieser
-Datei aus einem Blockly-/JavaScript-Skript heraus, z.B. als
+links auf.
+
+Standardmäßig wird das Einsatzgebiet, das WAIP-Web im `geometry`-Feld
+des Events sendet (meist ein kreisförmiges Polygon um den Einsatzort,
+nicht nur dessen Mittelpunkt), als Umriss in konfigurierbarer Farbe und
+Strichstärke ins Bild eingezeichnet - also die vom Server original
+gesendete Form, keine Markierung an deren Mittelpunkt. **Einsatzgebiet-
+Polygon anzeigen** (Admin-Checkbox, standardmäßig an) steuert das:
+deaktivieren, um stattdessen immer eine einfache Punkt-Markierung in
+der Mitte zu zeigen, auch wenn ein Polygon verfügbar wäre. Liegt gar
+kein Polygon vor (z.B. enthält das Event nur einen Punkt), wird ohnehin
+immer die Punkt-Markierung verwendet, unabhängig von der Checkbox. Das
+Einsatzgebiet bleibt beim Zeichnen des Polygons immer vollständig
+sichtbar: passt es bei der konfigurierten Zoomstufe nicht ins Bild,
+zoomt der Adapter automatisch so weit heraus (nie hinein), wie nötig,
+damit das gesamte Gebiet hineinpasst, statt es am Rand abzuschneiden.
+
+Der Dateipfad wird in `einsatz.kartenbildPfad` geschrieben (siehe
+[einsatz](#einsatz)) – typische Verwendung ist der Versand dieser Datei
+aus einem Blockly-/JavaScript-Skript heraus, z.B. als
 Pushover-Benachrichtigungsanhang. Es werden nur die 10 zuletzt erzeugten
 Bilder aufgehoben, ältere werden automatisch gelöscht, sobald ein neues
 geschrieben wird. Die Bilderzeugung läuft im Hintergrund und verzögert
@@ -322,15 +343,24 @@ sonst bleibt nichts betroffen.
 
 | Feld | Beschreibung | Default |
 | --- | --- | --- |
+| Einsatzgebiet-Polygon anzeigen | Das von WAIP-Web gesendete Original-Polygon zeichnen (an) vs. immer eine zentrierte Punkt-Markierung zeigen (aus) | *(an)* |
 | Bildbreite (px) | Breite des erzeugten PNGs | `600` |
 | Bildhöhe (px) | Höhe des erzeugten PNGs | `400` |
-| Zoomstufe | OpenStreetMap-Zoomstufe (1 = ganze Welt, 19 = Gebäudeebene) | `16` |
+| Zoomstufe | OpenStreetMap-Zoomstufe (1 = ganze Welt, 19 = Gebäudeebene) - ein Maximalwert, wird bei Bedarf automatisch reduziert, damit das Einsatzgebiet vollständig sichtbar bleibt | `19` |
+| Umrissfarbe | Farbe des Einsatzgebiet-Umrisses (und des Kerns der Fallback-Punkt-Markierung) | `#DD2020` |
+| Umriss-Strichstärke (px) | Linienstärke des Umrisses in Pixeln (1-12) | `4` |
 
 Die Bilder liegen im eigenen Datenverzeichnis dieser Adapterinstanz
 (`iobroker-data/<instance>/maps/`), nicht als ioBroker-Dateiobjekte –
 `einsatz.kartenbildPfad` ist deshalb ein echter, absoluter
 Dateisystempfad, den ein auf demselben Host laufendes Skript direkt
-lesen kann.
+lesen kann. Dieses Verzeichnis wird **nicht** automatisch gelöscht,
+wenn der Adapter gestoppt oder seine Instanzkonfiguration
+zurückgesetzt wird; um es bei einer Deinstallation zu entfernen,
+im Bestätigungsdialog beim Löschen der Instanz/des Adapters in Admin
+die Option **"Auch Instanzdaten löschen"** anhaken (seit js-controller
+4.0 / Admin 5 für das Instanzdaten-Verzeichnis jedes Adapters verfügbar
+– standardmäßig nicht angehakt).
 
 > **Hinweis:** Genutzt wird der offizielle, kostenlose Server
 > `tile.openstreetmap.org`, der für gelegentliche/geringe Nutzung
@@ -408,7 +438,7 @@ stehen. Der zuletzt abgeschlossene Einsatz bleibt trotzdem über
 | `ablaufzeit` | string (date) | Ende der Standby-Anzeigedauer, Basis für `restzeit` |
 | `sondersignal` | number | `1` = Sondersignal, sonst kein Sondersignal |
 | `latitude` / `longitude` | number | Position des Einsatzortes (normalisiert aus wgs84-Feldern oder GeoJSON-Mittelpunkt) |
-| `kartenbildPfad` | string | Pfad zum zuletzt erzeugten Einsatzkarten-Bild (PNG) - siehe [Einsatzkarte](#einsatzkarte). Anders als die Felder oben wird dieser State bei `io.standby` **nicht** geleert (gleiches Muster wie `einsatz.tts.last`), bleibt also auch nach Einsatzende noch verfügbar |
+| `kartenbildPfad` | string | Pfad zum zuletzt erzeugten Einsatzkarten-Bild (PNG) - siehe [Einsatzkarte](#einsatzkarte). Wird wie die übrigen Felder oben bei `io.standby` geleert; die zugrundeliegende Bild-Datei selbst wird dabei nicht gelöscht (nur das 10er-Rotationslimit entfernt Dateien, siehe [Einsatzkarte](#einsatzkarte)) |
 | `routenGesamt` | number | Anzahl Routen im aktuellen Einsatz |
 | `rueckmeldungGesamt` | number | Rückmeldungen gesamt im aktuellen Einsatz |
 | `rueckmeldungAnzahl.ek` | number | Anzahl Rückmeldungen als Einsatzkraft |

package/README.md

@@ -12,7 +12,7 @@
 
 🇩🇪 [Deutsche Version dieser README](README.de.md)
 
-Unofficial ioBroker adapter for **Wachalarm IP-Web (WAIP-Web)**
+ioBroker adapter for **Wachalarm IP-Web (WAIP-Web)**
 
 Connects via Socket.IO to a WAIP-Web dispatch monitor and mirrors incidents
 ("Einsatz"), responder feedback ("Rückmeldung"), routes and TTS
@@ -41,7 +41,7 @@ open.
 
 ## About this adapter
 
-This adapter is an **unofficial community project** and has no connection
+This adapter is an **independent, community-built project** and has no connection
 to the WAIP-Web project, to Robert-112, or to the operator of any specific
 instance (e.g. the Integrated Regional Dispatch Center Lausitz /
 Integrierte Regionalleitstelle Lausitz). It was built by analyzing the
@@ -182,9 +182,11 @@ adapter provides – typical use in a fire station/EMS environment:
   history, no TTS) - useful where WAIP only signals them unreliably in
   the first place, see [Rescue service](#rescue-service)
 - Optional incident map image: a PNG centered on the incident's
-  coordinates and marked with a dot, composed locally from OpenStreetMap
-  tiles, with its file path exposed as a state - see
-  [Incident map image](#incident-map-image)
+  coordinates, composed locally from OpenStreetMap tiles, with the
+  incident area WAIP-Web sends drawn as an outline in a configurable
+  color/thickness (switchable to a plain marker dot instead), automatically
+  zoomed out as needed to keep the whole area visible, file path
+  exposed as a state - see [Incident map image](#incident-map-image)
 
 ## Configuration
 
@@ -247,7 +249,7 @@ gap **entirely locally**, no data is sent anywhere. This tab is the
 first of two sources checked, in order (see
 [Keyword descriptions](#keyword-descriptions) for the second):
 
-**Rescue-service decoding** (admin checkbox, off by default): if the
+**Rescue-service decoding** (admin checkbox, on by default): if the
 keyword matches the pattern `R<RTW-count>N<NEF-count>[p][f][-NT]`
 (e.g. `R1N0` → "Rettungswagen: 1, Notfalleinsatzfahrzeug: 0"), a
 description is generated automatically. Two spellings of the `p`/`f`/`NT`
@@ -256,9 +258,9 @@ part are recognized: without a space and with a hyphen before `NT`
 [Leitstelle Lausitz's documented explanation](https://www.leitstelle-lausitz.de/anpassung-der-einsatzstichworte-rettungsdienst/)
 of it), and with a space and without a hyphen (e.g. `R1N1 p`, `R1N0 nt`,
 as used by the IRLS Brandenburg) – this scheme (in either spelling) is
-used by several German dispatch centers, not just these two – only
-enable it if your dispatch center actually uses one of these patterns.
-The text for each part is itself configurable (5 additional text
+used by several German dispatch centers, not just these two – has no
+effect if your dispatch center doesn't use one of these patterns, since
+the keyword just won't match. The text for each part is itself configurable (5 additional text
 fields appear once the checkbox is enabled), since the adapter is
 multi-language and these labels aren't translated automatically:
 
@@ -301,27 +303,52 @@ is simply `null` - not an error.
 default): when enabled and an incident carries valid coordinates, the
 adapter downloads the tiles it needs from the public
 `tile.openstreetmap.org` server, composites them into a single PNG
-centered on the incident's location, draws a marker (red dot, white
-ring) at the exact center, and stamps the OpenStreetMap attribution
-(required by its ODbL license) into the bottom-left corner. The file
-path is written to `einsatz.kartenbildPfad` (see [einsatz](#einsatz)) –
-typical use is attaching that file from a Blockly/JavaScript script,
-e.g. as a Pushover notification attachment. Only the 10 most recently
-generated images are kept on disk; older ones are deleted automatically
-whenever a new one is written. Image generation runs in the background
-and never delays alarm processing – a slow or failing tile download
-just means a missing/delayed image, nothing else is affected.
+centered on the incident's location, and stamps the OpenStreetMap
+attribution (required by its ODbL license) into the bottom-left corner.
+
+By default, the incident area WAIP-Web sends in the `geometry` field of
+the event (usually a circle-shaped polygon around the location, not
+just its center) is drawn onto the image as an outline in a
+configurable color and thickness - the original shape the server sent,
+not a marker at its centroid. **Show incident-area polygon** (admin
+checkbox, on by default) controls this: uncheck it to always show a
+simple marker dot at the center instead, even when a polygon is
+available. The dot is also used automatically whenever the event
+carries no polygon at all (e.g. just a point) - it is then the only
+option regardless of the checkbox. The incident area is
+always kept fully visible when the polygon is drawn: if it wouldn't
+fit into the image at the configured zoom level, the adapter
+automatically zooms out (never in) just enough for the whole area to
+fit, instead of clipping it at the edge.
+
+The file path is written to `einsatz.kartenbildPfad` (see
+[einsatz](#einsatz)) – typical use is attaching that file from a
+Blockly/JavaScript script, e.g. as a Pushover notification attachment.
+Only the 10 most recently generated images are kept on disk; older
+ones are deleted automatically whenever a new one is written. Image
+generation runs in the background and never delays alarm processing –
+a slow or failing tile download just means a missing/delayed image,
+nothing else is affected.
 
 | Field | Description | Default |
 | --- | --- | --- |
+| Show incident-area polygon | Draw the original polygon WAIP-Web sends (on) vs. always show a centered marker dot instead (off) | *(on)* |
 | Image width (px) | Width of the generated PNG | `600` |
 | Image height (px) | Height of the generated PNG | `400` |
-| Zoom level | OpenStreetMap zoom level (1 = whole world, 19 = building level) | `16` |
+| Zoom level | OpenStreetMap zoom level (1 = whole world, 19 = building level) - a maximum, automatically reduced if needed to keep the incident area fully visible | `19` |
+| Outline color | Color of the incident-area outline (and the fallback marker dot's core) | `#DD2020` |
+| Outline thickness (px) | Line thickness of the outline, in pixels (1-12) | `4` |
 
 Images are stored under this adapter instance's own data directory
 (`iobroker-data/<instance>/maps/`), not as ioBroker file objects –
 `einsatz.kartenbildPfad` is therefore a real, absolute filesystem path
-that a script running on the same host can read directly.
+that a script running on the same host can read directly. This
+directory is **not** deleted automatically when the adapter is
+stopped or its instance configuration is reset; to remove it when
+uninstalling, tick **"Also delete instance data"** in the confirmation
+dialog when deleting the instance/adapter in Admin (available since
+js-controller 4.0 / Admin 5 for any adapter's instance data directory
+– unchecked by default).
 
 > **Note:** This uses the official, free `tile.openstreetmap.org`
 > server, which is intended for occasional/low-volume use (see the
@@ -397,7 +424,7 @@ The most recently finished incident remains available via
 | `ablaufzeit` | string (date) | End of the standby display duration, basis for `restzeit` |
 | `sondersignal` | number | `1` = special signal (lights & siren), otherwise none |
 | `latitude` / `longitude` | number | Incident location (normalized from wgs84 fields or GeoJSON centroid) |
-| `kartenbildPfad` | string | Path to the most recently generated incident map image (PNG) - see [Incident map image](#incident-map-image). Unlike the fields above, **not** cleared on `io.standby` (same pattern as `einsatz.tts.last`), so it stays available to pick up the last incident's map after it ended |
+| `kartenbildPfad` | string | Path to the most recently generated incident map image (PNG) - see [Incident map image](#incident-map-image). Cleared like the other fields above on `io.standby`; the underlying image file itself is not deleted (only the 10-image retention limit removes files, see [Incident map image](#incident-map-image)) |
 | `routenGesamt` | number | Number of routes in the current incident |
 | `rueckmeldungGesamt` | number | Total feedback count for the current incident |
 | `rueckmeldungAnzahl.ek` | number | Feedback count as team member ("Einsatzkraft") |
@@ -468,6 +495,52 @@ example.
 
 ## Changelog
 
+### 0.7.30 (2026-08-24)
+
+- [Incident map image](#incident-map-image): new **Show incident-area
+  polygon** checkbox (on by default) - uncheck it to always show the
+  centered marker dot instead, even when the server sends a polygon.
+  The margin kept around the polygon when auto-zooming to fit it was
+  also reduced by 30%, so the area fills more of the image. Default
+  zoom level raised from 16 to 19, default outline thickness from 3 to
+  4 px.
+- `einsatz.kartenbildPfad` is now cleared on `io.standby` like the
+  other `einsatz.*` fields (previously kept, matching
+  `einsatz.tts.last`'s pattern) - the image file itself is unaffected,
+  only the 10-image retention limit ever deletes files.
+- Documented that this adapter's own data directory (generated map
+  images) is only removed on instance/adapter deletion if "Also
+  delete instance data" is checked in Admin's deletion dialog - a
+  native js-controller/Admin feature (unchecked by default), not
+  something this adapter's code controls.
+- Removed "Unofficial"/"Inoffiziell" from both READMEs' wording; the
+  disclaimer about having no connection to the WAIP-Web project/
+  Robert-112 itself is unchanged, just reworded without that word.
+- This Changelog section now shows only the 5 most recent versions -
+  older entries move to [CHANGELOG_OLD.md](CHANGELOG_OLD.md) on every
+  release.
+
+### 0.7.29 (2026-08-24)
+
+- [Incident map image](#incident-map-image): draws the actual incident
+  area WAIP-Web sends in the event's `geometry` field (usually a
+  circle-shaped polygon around the location) as an outline, instead of
+  just a marker dot at its centroid. Falls back to the dot marker if no
+  polygon is available (e.g. only a point). The area always stays
+  fully visible: the adapter automatically zooms out (never in) past
+  the configured zoom level if needed, instead of clipping the area at
+  the image edge. Outline color and thickness (1-12 px) are now
+  configurable too (also used for the fallback marker dot's core).
+- **Rescue-service decoding** (on the [Rescue service](#rescue-service)
+  tab) now defaults to **on** for new installations, matching **Process
+  rescue-service incidents** (already on by default) - previously it
+  defaulted to off. Already-configured instances keep their stored
+  value, this only affects fresh installs.
+- Trimmed the self-justifying "kept the previous behavior" sentence
+  from both checkboxes' admin descriptions and reworded the decoding
+  checkbox's description ("has no effect if your dispatch center
+  doesn't use one of these patterns" instead of "only enable if...").
+
 ### 0.7.28 (2026-08-24)
 
 - New: **Process rescue-service incidents** checkbox on the
@@ -501,153 +574,8 @@ example.
   pattern`), and the table's help text was moved above the table
   instead of below - with many rows it used to sit far out of view.
 
-### 0.7.25 (2026-08-23)
-
-- Updated the admin UI text for the [rescue-service decoder](#rescue-service)
-  to reflect the two supported keyword spellings added in 0.7.23
-  (Leitstelle Lausitz `R1N1p`/`R1N0-NT` and IRLS Brandenburg `R1N1 p`/
-  `R1N0 nt`) - the checkbox label/help and the NT suffix label/help
-  previously only mentioned the hyphenated no-space form.
-
-### 0.7.24 (2026-08-23)
-
-- Extended the default [keyword table](#keyword-descriptions) with two
-  more Brandenburg spelling variants: `B:Gebäude-Groß` and
-  `B:Gebäude-Klein` (hyphen instead of space, as used by some dispatch
-  centers) - same descriptions as the existing `B:Gebäude groß`/`B:Gebäude
-  klein` entries. Only affects the shipped example table for new
-  installs - existing configured tables are untouched.
-
-### 0.7.23 (2026-08-23)
-
-- Extended the default [keyword table](#keyword-descriptions) with the
-  29 `K`/`V`/`M`/`S` keywords (Krankentransport, Verlegung, MANV,
-  Sonderstichwörter) from the IRLS Brandenburg rescue-service catalog
-  (v2.7) - previously only the `R<ambulance>N<physician-vehicle>`
-  scheme and the Brand/THL (`B:`/`H:`) table were covered, so
-  `einsatz.beschreibung` stayed `null` for these.
-- Fixed the [rescue-service keyword](#rescue-service) decoder
-  (`decodeRettungsdienstStichwort`): it only accepted the Leitstelle
-  Lausitz spelling without a space (`R1N1p`, `R1N0-NT`) and silently
-  returned `null` for the IRLS Brandenburg spelling with a space
-  (`R1N1 p`, `R1N0 nt`) - both are now recognized.
-- Only affects the shipped example table and the decoder logic for
-  new installs/upgrades - existing configured tables are untouched.
-
-### 0.7.22 (2026-08-23)
-
-- Extended the default [keyword table](#keyword-descriptions) with
-  `H:Person-TMR` (technical human rescue) and corrected three entries
-  whose pattern didn't match the actual dispatch keyword:
-  `H:Flugunfall` → `H:Flugzeugunfall` (`klein`/`groß`), `H:Öl Wasser`
-  → `H:Öl auf Wasser`, `H:Rettung aus Höhen/Tiefen` → `H:Rettung aus
-  Höhen und Tiefen` (source: Regionalleitstellen Brandenburg keyword
-  list, v7.1). Only affects the shipped example table for new
-  installs - existing configured tables are untouched.
-
-### 0.7.21 (2026-08-23)
-
-- Removed the keyword table's CSV export/import: a bug in ioBroker
-  Admin's own `table` component corrupted German umlauts on CSV
-  import (e.g. `ä`/`Ã` instead of `ä`/`ß`) - confirmed to be entirely
-  inside the Admin UI, not this adapter's code. Use ioBroker's
-  standard instance configuration export/import (JSON) instead - see
-  [Keyword descriptions](#keyword-descriptions) for the reload caveat
-  after using it.
-- Split the admin configuration UI into 3 tabs -
-  [Connection](#connection), [Rescue-service
-  keywords](#rescue-service),
-  [Keyword descriptions](#keyword-descriptions) - each with a
-  matching icon, replacing the single combined settings page.
-- Documentation: restructured the configuration section of the
-  README to mirror the 3 admin tabs, fixed a stale reference to the
-  removed CSV feature, and added a couple of small clarifications
-  (mentioned `einsatz.beschreibung` in the practical-use-cases
-  section, mentioned the 3-tab structure up front). All code comments
-  in `main.js` are now bilingual (German + English).
-
-### 0.7.20 (2026-08-22)
-
-- Added `einsatz.beschreibung`: a plain-language description for
-  `einsatz.stichwort`, resolved entirely locally (also included in
-  `einsatz.json.current`/`.history10`). Two sources, in order:
-  - An optional decoder for the `R<RTW>N<NEF>[p][f][-NT]` rescue-service
-    keyword scheme used by several dispatch centers - the label for
-    each part is fully configurable via 5 new text fields.
-  - A user-maintained keyword table (admin table, CSV export/import,
-    pre-filled with an example fire/rescue keyword list) where the
-    most specific (longest) matching pattern wins automatically,
-    regardless of row order - the table can be freely sorted by
-    keyword.
-  - `null` if nothing matches. See
-    [Alarm keyword descriptions](#alarm-keyword-descriptions).
-
-### 0.7.19 (2026-08-22)
-
-- Fixed a bug where incoming feedback (`io.new_rmld`) was silently
-  dropped as "wrong monitor" whenever the responding station's number
-  (`wache_nr`) differed from the registered monitor ID:
-  `payloadMonitorMatch()` incorrectly treated `wache_nr`/`wache_id`/
-  `wacheId` as monitor-identifying fields, but confirmed against the
-  WAIP-Web server source, `wache_nr` on a feedback event is the station
-  number of the crew that submitted it, unrelated to the monitor/
-  dispatch-center ID. Removed these three from the match candidates -
-  alarms and routes were never affected (they don't carry these
-  fields).
-
-### 0.7.18 (2026-08-22)
-
-- Fixed `debug.lastEvent`/`debug.normalizedPosition` to hold a
-  single-element JSON array instead of a bare object (matching
-  `einsatz.json.current`), for direct VIS table-widget compatibility,
-  and to correctly initialize to `[]` instead of `null` on a fresh
-  install/restart.
-- Removed `einsatz.einsatznummer`/`.objekt`/`.objektteil`/
-  `.besonderheiten`/`.strasse`/`.hausnummer`/`.einsatzdetails`/
-  `.permissions` (and the corresponding fields in
-  `einsatz.json.current`/`.history10`): confirmed via the WAIP-Web
-  server source (`server/waip.js`,
-  `db_user_check_permission_for_waip()`) that these fields are only
-  ever populated for logged-in clients - since this adapter connects
-  anonymously by design, they were always empty/`false`. Removed
-  instead of permanently carrying dead states - see the note in the
-  [`einsatz`](#einsatz) section.
-
-### 0.7.17 (2026-08-22)
-
-- Fixed `cleanupObsoleteObjects()` incorrectly deleting and recreating
-  the `einsatz.json` channel on every restart (it wasn't checking
-  `obj.type`, so the current channel object was mistaken for a leftover
-  state from before the 0.7.15 migration).
-- Fixed a spurious `status.registrationPending` "no existing object"
-  warning that could occur if the adapter was stopped before object
-  initialization had finished.
-- Reduced WAIP registration from three emits to a single emit - Socket.IO
-  already delivers reliably once connected, and the existing registration
-  timeout remains as the safety net for the rare case it doesn't confirm.
-- `permissions` inside `einsatz.json.current`/`.history10` is now always
-  stringified consistently with the standalone `einsatz.permissions`
-  state, and `einsatz.json.current` is wrapped in a single-element array
-  (VIS table widgets require an array at the root, not a bare object).
-- Fixed `einsatz.json.history10`/`debug.monitorAudit` staying `null`
-  instead of `[]` on a fresh install (they're excluded from the
-  per-restart reset to preserve history, which previously also meant
-  they were never initialized at all on first install).
-- Added `registeredMonitor`/`registeredMonitorName` fields to
-  `einsatz.json.current`/`.history10`.
-- Reworked logging: translated all remaining German log text to
-  English; implemented the official first-occurrence-`warn`/
-  repeat-`debug`/recovery-`info` pattern for recurring failures (session
-  cookie, registration, connection); capped noisy Socket.IO ping/pong
-  debug logging; a sustained flood of wrong-monitor events now escalates
-  to `warn` instead of staying at `info` indefinitely. See
-  [LOGGING.md](LOGGING.md) for the full reference.
-- Documentation: added a table of contents, a practical-use-cases
-  section, a known-limitation note (only the single most recently active
-  incident is shown - see [`einsatz`](#einsatz)), and enforced the
-  changelog's own 5-entry limit.
-
-Older entries have moved to [CHANGELOG_OLD.md](CHANGELOG_OLD.md).
+Older entries have moved to [CHANGELOG_OLD.md](CHANGELOG_OLD.md) - this
+section shows only the 5 most recent versions.
 
 ## License
 

package/admin/i18n/de.json

@@ -2,9 +2,10 @@
     "Alarm keyword descriptions": "Stichwort-Stammdaten",
     "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Rettungsdienst-Stichwörter automatisch dekodieren (R<RTW>N<NEF>[p][f][-NT], mit oder ohne Leerzeichen)",
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Basis-URL des WAIP-Leitstellenservers (Socket.IO-Endpunkt, Namespace /waip wird automatisch angehängt)",
+    "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Farbe des Einsatzgebiet-Umrisses (und des Kerns der Fallback-Punkt-Markierung, wenn kein Gebiets-Polygon vorliegt).",
     "Connection": "Verbindung",
     "Description": "Beschreibung",
-    "For every incident with valid coordinates, downloads OpenStreetMap tiles and composes a PNG centered on the incident's location, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "Lädt für jeden Einsatz mit gültigen Koordinaten OpenStreetMap-Kacheln herunter und setzt sie zu einem PNG zusammen, zentriert auf den Einsatzort und mit einem Punkt markiert. Der Dateipfad wird in den State einsatz.kartenbildPfad geschrieben, z.B. um ihn per Blockly/JavaScript-Skript als Pushover-Anhang zu versenden. Es werden nur die 10 neuesten Bilder aufgehoben, ältere werden automatisch gelöscht. Nutzt den öffentlichen Server tile.openstreetmap.org - bitte bei der vorgesehenen Nutzung von einem Bild pro Einsatz bleiben, siehe OSM Tile Usage Policy.",
+    "For every incident with valid coordinates, downloads OpenStreetMap tiles and composes a PNG centered on the incident's location, with the incident area WAIP-Web sends drawn as an outline (falls back to a marker dot if no area polygon is available). The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "Lädt für jeden Einsatz mit gültigen Koordinaten OpenStreetMap-Kacheln herunter und setzt sie zu einem PNG zusammen, zentriert auf den Einsatzort, mit dem von WAIP-Web gesendeten Einsatzgebiet als Umriss eingezeichnet (fällt auf einen Punkt-Marker zurück, falls kein Gebiets-Polygon vorliegt). Der Dateipfad wird in den State einsatz.kartenbildPfad geschrieben, z.B. um ihn per Blockly/JavaScript-Skript als Pushover-Anhang zu versenden. Es werden nur die 10 neuesten Bilder aufgehoben, ältere werden automatisch gelöscht. Nutzt den öffentlichen Server tile.openstreetmap.org - bitte bei der vorgesehenen Nutzung von einem Bild pro Einsatz bleiben, siehe OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Kartenbild für jeden Einsatz erzeugen",
     "Height of the generated map image in pixels.": "Höhe des erzeugten Kartenbilds in Pixeln.",
     "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "Wartezeit auf die Bestätigung der Monitor-Registrierung durch den Server, bevor eine Warnung geloggt wird; die Verbindung läuft in jedem Fall weiter.",
@@ -18,16 +19,20 @@
     "Label for suffix -NT / nt (special ambulance transport)": "Bezeichnung für Suffix -NT / nt (Notfalltransport mit Notfallkrankenwagen)",
     "Label for suffix f (first responder)": "Bezeichnung für Suffix f (First Responder)",
     "Label for suffix p (polytrauma)": "Bezeichnung für Suffix p (Polytrauma)",
+    "Line thickness of the incident-area outline, in pixels.": "Linienstärke des Einsatzgebiet-Umrisses in Pixeln.",
     "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Wird live von der /waip/-Übersichtsseite des konfigurierten Servers geladen - Auswahl nach Leitstelle, Kreis, Träger oder Wache, oder 'Alle Wachalarme' (ID 0) für jeden Einsatz. Ist der Server nicht erreichbar, kann die ID weiterhin manuell eingegeben werden.",
     "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Ordnet einsatz.stichwort eine Beschreibung für einsatz.beschreibung zu. Der Vergleich ist case-insensitiv und behandelt Leerzeichen/Bindestriche als gleichwertig (jede Folge aus beidem wird vor dem Vergleich zu einem Leerzeichen zusammengefasst), sodass z.B. \"H:VU mit P\" und \"H:VU-mit-P\" dieselbe Zeile matchen - keine eigene Zeile pro Schreibvariante nötig. Passen mehrere Zeilen, gewinnt automatisch das spezifischste (längste) Muster - die Zeilenreihenfolge hat keinen Einfluss auf den Abgleich, die Tabelle kann also frei nach jeder Spalte sortiert werden. Vorbefüllt mit einer beispielhaften Feuerwehr-/Rettungsdienst-Stichwortliste als Startpunkt - nicht bestätigt für eure eigene Leitstelle, bei Bedarf anpassen/ersetzen. Zum Sichern/Übertragen dieser Tabelle die Standard-Instanzkonfiguration von ioBroker exportieren/importieren (JSON). Nach einem solchen Import die Admin-Seite neu laden, bevor du diese Tabelle prüfst - der offene Konfigurationsdialog aktualisiert sie bei einem externen Import nicht automatisch (eine State-Sync-Einschränkung der Admin-Tabellenkomponente selbst).",
     "Match": "Abgleich",
     "Monitor ID": "Monitor-ID",
-    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.": "OpenStreetMap-Zoomstufe (1 = ganze Welt, 19 = Gebäudeebene). Höhere Werte zeigen einen kleineren Ausschnitt in mehr Detail.",
+    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.": "OpenStreetMap-Zoomstufe (1 = ganze Welt, 19 = Gebäudeebene). Höhere Werte zeigen einen kleineren Ausschnitt in mehr Detail. Das ist ein Maximalwert, kein fester Wert: Passt das vom Server gesendete Einsatzgebiet bei dieser Zoomstufe nicht vollständig ins Bild, zoomt der Adapter automatisch so weit heraus (nie hinein), wie nötig, um das gesamte Gebiet sichtbar zu halten.",
+    "Outline color": "Umrissfarbe",
+    "Outline thickness (px)": "Umriss-Strichstärke (px)",
     "Process rescue-service incidents": "Rettungsdienst-Einsätze verarbeiten",
     "Reconnect delay (s)": "Wiederverbindungs-Verzögerung (s)",
     "Registration timeout (s)": "Registrierungs-Timeout (s)",
     "Rescue service": "Rettungsdienst",
-    "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rettungsdienst-Stichwortschema R<RTW>N<NEF>, optional gefolgt von einem p/f-Modifikator und/oder einem NT-Suffix (z.B. \"R1N0\" = 1 Rettungswagen, kein Notarzt). Zwei Schreibweisen werden erkannt: ohne Leerzeichen und mit Bindestrich vor NT (Leitstelle Lausitz, z.B. \"R1N1p\", \"R1N0-NT\") sowie mit Leerzeichen und ohne Bindestrich (Leitstelle Brandenburg/IRLS, z.B. \"R1N1 p\", \"R1N0 nt\") - nur aktivieren, wenn eure Leitstelle eines dieser Muster tatsächlich verwendet. Hat Vorrang vor der Tabelle im Tab Stichwort-Stammdaten, wenn ein Stichwort passt.",
+    "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - has no effect if your dispatch center doesn't use one of these patterns, since the keyword just won't match. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rettungsdienst-Stichwortschema R<RTW>N<NEF>, optional gefolgt von einem p/f-Modifikator und/oder einem NT-Suffix (z.B. \"R1N0\" = 1 Rettungswagen, kein Notarzt). Zwei Schreibweisen werden erkannt: ohne Leerzeichen und mit Bindestrich vor NT (Leitstelle Lausitz, z.B. \"R1N1p\", \"R1N0-NT\") sowie mit Leerzeichen und ohne Bindestrich (Leitstelle Brandenburg/IRLS, z.B. \"R1N1 p\", \"R1N0 nt\") - hat keine Auswirkung, falls eure Leitstelle keines dieser Muster verwendet, da das Stichwort dann einfach nicht passt. Hat Vorrang vor der Tabelle im Tab Stichwort-Stammdaten, wenn ein Stichwort passt.",
+    "Show incident-area polygon": "Einsatzgebiet-Polygon anzeigen",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Text, der angehängt wird, wenn das Stichwort auf \"-NT\" oder \" nt\" endet.",
     "Text appended when the keyword ends in \"f\".": "Text, der angehängt wird, wenn das Stichwort auf \"f\" endet.",
     "Text appended when the keyword ends in \"p\".": "Text, der angehängt wird, wenn das Stichwort auf \"p\" endet.",
@@ -35,7 +40,8 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Text für den R<n>-Teil der erzeugten Beschreibung, z.B. \"Rettungswagen: 1\".",
     "WAIP server URL": "WAIP-Server-URL",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Wartezeit, bevor der Adapter nach einem Verbindungsabbruch oder -fehler automatisch neu verbindet.",
-    "When unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.": "Wenn deaktiviert, werden Einsätze, deren einsatzart auf einen Rettungsdienst-Einsatz hindeutet (enthält \"Rettung\" oder \"Krankentransport\", ohne Berücksichtigung von Groß-/Kleinschreibung), komplett ignoriert - keine States werden aktualisiert, kein History-Eintrag geschrieben, keine TTS-Ansage ausgelöst. Sinnvoll, weil manche WAIP-Leitstellen Rettungsdienst-Einsätze nur unzuverlässig oder gar nicht signalisieren. Standardmäßig aktiviert, um das bisherige Verhalten beizubehalten.",
+    "When checked (default), the incident-area polygon WAIP-Web sends is drawn as an outline (falling back to a centered marker dot only when no polygon is available). Uncheck to always show the simple centered marker dot instead, even when a polygon is available.": "Wenn aktiviert (Standard), wird das von WAIP-Web gesendete Einsatzgebiet-Polygon als Umriss eingezeichnet (Rückfall auf eine zentrierte Punkt-Markierung nur, falls kein Polygon vorliegt). Deaktivieren, um stattdessen immer die einfache zentrierte Punkt-Markierung zu zeigen, auch wenn ein Polygon verfügbar wäre.",
+    "When unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all.": "Wenn deaktiviert, werden Einsätze, deren einsatzart auf einen Rettungsdienst-Einsatz hindeutet (enthält \"Rettung\" oder \"Krankentransport\", ohne Berücksichtigung von Groß-/Kleinschreibung), komplett ignoriert - keine States werden aktualisiert, kein History-Eintrag geschrieben, keine TTS-Ansage ausgelöst. Sinnvoll, weil manche WAIP-Leitstellen Rettungsdienst-Einsätze nur unzuverlässig oder gar nicht signalisieren.",
     "Width of the generated map image in pixels.": "Breite des erzeugten Kartenbilds in Pixeln.",
     "Zoom level": "Zoomstufe",
     "contains": "enthält",

package/admin/i18n/en.json

@@ -1,19 +1,18 @@
 {
     "Alarm keyword descriptions": "Alarm keyword descriptions",
-    "Generate a map image for each incident": "Generate a map image for each incident",
-    "For every incident with valid coordinates, downloads OpenStreetMap tiles and composes a PNG centered on the incident's location, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "For every incident with valid coordinates, downloads OpenStreetMap tiles and composes a PNG centered on the incident's location, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.",
-    "Image width (px)": "Image width (px)",
-    "Width of the generated map image in pixels.": "Width of the generated map image in pixels.",
-    "Image height (px)": "Image height (px)",
-    "Height of the generated map image in pixels.": "Height of the generated map image in pixels.",
-    "Incident map image": "Incident map image",
-    "Zoom level": "Zoom level",
-    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.": "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.",
     "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)",
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)",
+    "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).",
     "Connection": "Connection",
+    "contains": "contains",
     "Description": "Description",
+    "For every incident with valid coordinates, downloads OpenStreetMap tiles and composes a PNG centered on the incident's location, with the incident area WAIP-Web sends drawn as an outline (falls back to a marker dot if no area polygon is available). The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "For every incident with valid coordinates, downloads OpenStreetMap tiles and composes a PNG centered on the incident's location, with the incident area WAIP-Web sends drawn as an outline (falls back to a marker dot if no area polygon is available). The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.",
+    "Generate a map image for each incident": "Generate a map image for each incident",
+    "Height of the generated map image in pixels.": "Height of the generated map image in pixels.",
     "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.",
+    "Image height (px)": "Image height (px)",
+    "Image width (px)": "Image width (px)",
+    "Incident map image": "Incident map image",
     "Keyword / pattern": "Keyword / pattern",
     "Keyword descriptions": "Keyword descriptions",
     "Label for N (emergency vehicle count)": "Label for N (emergency vehicle count)",
@@ -21,16 +20,21 @@
     "Label for suffix -NT / nt (special ambulance transport)": "Label for suffix -NT / nt (special ambulance transport)",
     "Label for suffix f (first responder)": "Label for suffix f (first responder)",
     "Label for suffix p (polytrauma)": "Label for suffix p (polytrauma)",
+    "Line thickness of the incident-area outline, in pixels.": "Line thickness of the incident-area outline, in pixels.",
     "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.",
     "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).",
     "Match": "Match",
     "Monitor ID": "Monitor ID",
+    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.": "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.",
+    "Outline color": "Outline color",
+    "Outline thickness (px)": "Outline thickness (px)",
     "Process rescue-service incidents": "Process rescue-service incidents",
-    "When unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.": "When unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.",
     "Reconnect delay (s)": "Reconnect delay (s)",
     "Registration timeout (s)": "Registration timeout (s)",
     "Rescue service": "Rescue service",
-    "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.",
+    "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - has no effect if your dispatch center doesn't use one of these patterns, since the keyword just won't match. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "Rescue-service keyword scheme R<RTW>N<NEF>, optionally followed by a p/f modifier and/or an NT suffix (e.g. \"R1N0\" = 1 ambulance, no emergency physician). Two spellings are recognized: without a space and with a hyphen before NT (Leitstelle Lausitz, e.g. \"R1N1p\", \"R1N0-NT\") and with a space and without a hyphen (Leitstelle Brandenburg/IRLS, e.g. \"R1N1 p\", \"R1N0 nt\") - has no effect if your dispatch center doesn't use one of these patterns, since the keyword just won't match. Takes priority over the table on the Keyword descriptions tab when a keyword matches.",
+    "Show incident-area polygon": "Show incident-area polygon",
+    "starts with": "starts with",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Text appended when the keyword ends in \"-NT\" or \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Text appended when the keyword ends in \"f\".",
     "Text appended when the keyword ends in \"p\".": "Text appended when the keyword ends in \"p\".",
@@ -38,6 +42,8 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".",
     "WAIP server URL": "WAIP server URL",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Wait time before the adapter automatically reconnects after a lost connection or a connection error.",
-    "contains": "contains",
-    "starts with": "starts with"
+    "When checked (default), the incident-area polygon WAIP-Web sends is drawn as an outline (falling back to a centered marker dot only when no polygon is available). Uncheck to always show the simple centered marker dot instead, even when a polygon is available.": "When checked (default), the incident-area polygon WAIP-Web sends is drawn as an outline (falling back to a centered marker dot only when no polygon is available). Uncheck to always show the simple centered marker dot instead, even when a polygon is available.",
+    "When unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all.": "When unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all.",
+    "Width of the generated map image in pixels.": "Width of the generated map image in pixels.",
+    "Zoom level": "Zoom level"
 }