iobroker.waip-web 0.7.29 → 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
@@ -182,9 +182,10 @@ Rettungsdienst-Wache:
 - Optionales Einsatzkarten-Bild: ein auf die Einsatz-Koordinaten
   zentriertes PNG, lokal aus OpenStreetMap-Kacheln zusammengesetzt, mit
   dem von WAIP-Web gesendeten Einsatzgebiet als Umriss in
-  konfigurierbarer Farbe/Stärke eingezeichnet (Rückfall auf
-  Punkt-Markierung), zoomt bei Bedarf automatisch so heraus, dass das
-  gesamte Gebiet sichtbar bleibt, Dateipfad als State bereitgestellt -
+  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
@@ -313,21 +314,26 @@ 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, und stempelt
 die von der ODbL-Lizenz vorgeschriebene OpenStreetMap-Attribution unten
-links auf. Das Einsatzgebiet, das WAIP-Web im `geometry`-Feld des
-Events sendet (meist ein kreisförmiges Polygon um den Einsatzort, nicht
-nur dessen Mittelpunkt), wird als Umriss in konfigurierbarer Farbe und
+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. Nur falls kein solches Polygon vorliegt (z.B. enthält das
-Event nur einen Punkt), fällt der Adapter auf eine einfache
-Punkt-Markierung in der Mitte zurück. Das Einsatzgebiet bleibt dabei
-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
+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
@@ -337,17 +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) - ein Maximalwert, wird bei Bedarf automatisch reduziert, damit das Einsatzgebiet vollständig sichtbar bleibt | `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) | `3` |
+| 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
@@ -425,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
@@ -184,9 +184,9 @@ adapter provides – typical use in a fire station/EMS environment:
 - Optional incident map image: a PNG centered on the incident's
   coordinates, composed locally from OpenStreetMap tiles, with the
   incident area WAIP-Web sends drawn as an outline in a configurable
-  color/thickness (falls back to a marker dot), automatically zoomed
-  out as needed to keep the whole area visible, file path exposed as a
-  state - see [Incident map image](#incident-map-image)
+  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
 
@@ -305,37 +305,50 @@ 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, and stamps the OpenStreetMap
 attribution (required by its ODbL license) into the bottom-left corner.
-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. Only if no such polygon
-is available (e.g. the event carries just a point) does the adapter
-fall back to a simple marker dot at the center. The incident area is
-always kept fully visible: 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.
+
+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) - a maximum, automatically reduced if needed to keep the incident area fully visible | `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) | `3` |
+| 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
@@ -411,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") |
@@ -482,6 +495,31 @@ 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
@@ -536,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

@@ -4,7 +4,6 @@
     "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",
-    "contains": "enthält",
     "Description": "Beschreibung",
     "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",
@@ -33,7 +32,7 @@
     "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\") - 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.",
-    "starts with": "beginnt mit",
+    "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.",
@@ -41,7 +40,10 @@
     "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 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"
+    "Zoom level": "Zoomstufe",
+    "contains": "enthält",
+    "starts with": "beginnt mit"
 }

package/admin/i18n/en.json

@@ -33,6 +33,7 @@
     "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\") - 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\".",
@@ -41,6 +42,7 @@
     "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.",
+    "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"

package/admin/i18n/es.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL base del servidor de envío WAIP (punto final Socket.IO, el espacio de nombres /waip se agrega automáticamente)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Color del contorno del área del incidente (y del núcleo del punto marcador de reserva, usado cuando no hay ningún polígono de área disponible).",
     "Connection": "Conexión",
-    "contains": "contiene",
     "Description": "Descripción",
     "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.": "Para cada incidente con coordenadas válidas, descarga teselas de OpenStreetMap y compone un PNG centrado en la ubicación del incidente, con el área del incidente enviada por WAIP-Web dibujada como contorno (recurre a un punto marcador si no hay un polígono de área disponible). La ruta del archivo se escribe en el estado einsatz.kartenbildPfad, por ejemplo para enviarlo como adjunto de Pushover desde un script de Blockly/JavaScript. Solo se conservan las 10 imágenes más recientes, las más antiguas se eliminan automáticamente. Utiliza el servidor público tile.openstreetmap.org - mantén esto en el uso previsto de una imagen por incidente según la OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Generar una imagen de mapa para cada incidente",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Tiempos de espera de registro",
     "Rescue service": "Servicio de rescate",
     "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.": "Esquema de palabras clave del servicio de rescate R<RTW>N<NEF>, seguido opcionalmente de un modificador p/f y/o un sufijo NT (p. ej. \"R1N0\" = 1 ambulancia, sin médico de urgencias). Se reconocen dos escrituras: sin espacio y con guion antes de NT (Leitstelle Lausitz, p. ej. \"R1N1p\", \"R1N0-NT\") y con espacio y sin guion (Leitstelle Brandeburgo/IRLS, p. ej. \"R1N1 p\", \"R1N0 nt\") - no tiene efecto si su central de despacho no utiliza ninguno de estos patrones, ya que la palabra clave simplemente no coincidirá. Tiene prioridad sobre la tabla de la pestaña Descripciones de palabras clave cuando una palabra clave coincide.",
-    "starts with": "comienza con",
+    "Show incident-area polygon": "Mostrar polígono del área del incidente",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Texto añadido cuando la palabra clave termina en \"-NT\" o \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Texto añadido cuando la palabra clave termina en \"f\".",
     "Text appended when the keyword ends in \"p\".": "Texto añadido cuando la palabra clave termina en \"p\".",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Texto utilizado en la descripción generada para la parte R<n>, p.e. \"Rettungswagen: 1\".",
     "WAIP server URL": "URL del servidor WAIP",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Tiempo de espera antes de que el adaptador se vuelva a conectar automáticamente después de una pérdida de conexión o un error de conexión.",
+    "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.": "Cuando está marcado (por defecto), el polígono del área del incidente enviado por WAIP-Web se dibuja como un contorno (recurriendo a un punto marcador centrado solo cuando no hay ningún polígono disponible). Desmárquelo para mostrar siempre el simple punto marcador centrado en su lugar, incluso cuando haya un polígono disponible.",
     "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.": "Si se desactiva, los incidentes cuyo einsatzart los identifica como un aviso del servicio de rescate (contiene \"Rettung\" o \"Krankentransport\", sin distinguir mayúsculas/minúsculas) se ignoran por completo - no se actualiza ningún estado, no se escribe ninguna entrada en el historial, no se activa ningún aviso de voz (TTS). Útil porque algunas centrales de despacho de WAIP solo señalan los incidentes del servicio de rescate de forma poco fiable o no lo hacen en absoluto.",
     "Width of the generated map image in pixels.": "Ancho de la imagen de mapa generada en píxeles.",
-    "Zoom level": "Nivel de zoom"
+    "Zoom level": "Nivel de zoom",
+    "contains": "contiene",
+    "starts with": "comienza con"
 }

package/admin/i18n/fr.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL de base du serveur de répartition WAIP (point de terminaison Socket.IO, l'espace de noms /waip est ajouté automatiquement)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Couleur du contour de la zone d'intervention (et du centre du point marqueur de secours, utilisé lorsqu'aucun polygone de zone n'est disponible).",
     "Connection": "Connexion",
-    "contains": "contient",
     "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.": "Pour chaque incident avec des coordonnées valides, télécharge des tuiles OpenStreetMap et compose un PNG centré sur l'emplacement de l'incident, avec la zone d'intervention envoyée par WAIP-Web dessinée en contour (revient à un point marqueur si aucun polygone de zone n'est disponible). Le chemin du fichier est écrit dans l'état einsatz.kartenbildPfad, par exemple pour l'envoyer en pièce jointe Pushover depuis un script Blockly/JavaScript. Seules les 10 images les plus récentes sont conservées, les plus anciennes sont supprimées automatiquement. Utilise le serveur public tile.openstreetmap.org - veillez à respecter l'usage prévu d'une image par incident selon la OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Générer une image de carte pour chaque incident",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Délai(s) d'enregistrement",
     "Rescue service": "Service de secours",
     "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.": "Schéma de mots-clés des services de secours R<RTW>N<NEF>, éventuellement suivi d'un modificateur p/f et/ou d'un suffixe NT (par ex. \"R1N0\" = 1 ambulance, pas de médecin urgentiste). Deux orthographes sont reconnues : sans espace et avec un tiret avant NT (Leitstelle Lausitz, par ex. \"R1N1p\", \"R1N0-NT\") et avec un espace et sans tiret (Leitstelle Brandebourg/IRLS, par ex. \"R1N1 p\", \"R1N0 nt\") - n'a aucun effet si votre centre de répartition n'utilise aucun de ces modèles, le mot-clé ne correspondra alors simplement pas. Prioritaire sur la table de l'onglet Descriptions de mots-clés lorsqu'un mot-clé correspond.",
-    "starts with": "commence par",
+    "Show incident-area polygon": "Afficher le polygone de la zone d'intervention",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Texte ajouté lorsque le mot-clé se termine par \"-NT\" ou \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Texte ajouté lorsque le mot clé se termine par \"f\".",
     "Text appended when the keyword ends in \"p\".": "Texte ajouté lorsque le mot clé se termine par \"p\".",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Texte utilisé dans la description générée pour la pièce R<n>, par ex. \"Rettungswagen: 1\".",
     "WAIP server URL": "URL du serveur WAIP",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Temps d'attente avant que l'adaptateur ne se reconnecte automatiquement après une perte de connexion ou une erreur de connexion.",
+    "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.": "Lorsque coché (par défaut), le polygone de la zone d'intervention envoyé par WAIP-Web est dessiné en contour (revenant à un point marqueur centré uniquement lorsqu'aucun polygone n'est disponible). Décochez pour toujours afficher le simple point marqueur centré à la place, même lorsqu'un polygone est disponible.",
     "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.": "Si désactivé, les incidents dont le einsatzart les identifie comme un appel du service de secours (contient \"Rettung\" ou \"Krankentransport\", sans distinction de casse) sont complètement ignorés - aucun état n'est mis à jour, aucune entrée d'historique n'est écrite, aucune annonce TTS n'est déclenchée. Utile car certains centres de répartition WAIP ne signalent les incidents du service de secours que de manière peu fiable, voire pas du tout.",
     "Width of the generated map image in pixels.": "Largeur de l'image de carte générée en pixels.",
-    "Zoom level": "Niveau de zoom"
+    "Zoom level": "Niveau de zoom",
+    "contains": "contient",
+    "starts with": "commence par"
 }

package/admin/i18n/it.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL di base del server di invio WAIP (endpoint Socket.IO, lo spazio dei nomi /waip viene aggiunto automaticamente)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Colore del contorno dell'area dell'incidente (e del nucleo del punto marcatore di riserva, usato quando non è disponibile alcun poligono d'area).",
     "Connection": "Connessione",
-    "contains": "contiene",
     "Description": "Descrizione",
     "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.": "Per ogni incidente con coordinate valide, scarica i tile di OpenStreetMap e compone un PNG centrato sulla posizione dell'incidente, con l'area dell'incidente inviata da WAIP-Web disegnata come contorno (torna a un punto marcatore se non è disponibile alcun poligono d'area). Il percorso del file viene scritto nello stato einsatz.kartenbildPfad, ad esempio per inviarlo come allegato Pushover da uno script Blockly/JavaScript. Vengono conservate solo le 10 immagini più recenti, quelle più vecchie vengono eliminate automaticamente. Utilizza il server pubblico tile.openstreetmap.org - attenersi all'uso previsto di un'immagine per incidente secondo la OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Genera un'immagine della mappa per ogni incidente",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Timeout registrazione(s)",
     "Rescue service": "Servizio di soccorso",
     "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.": "Schema di parole chiave del servizio di soccorso R<RTW>N<NEF>, opzionalmente seguito da un modificatore p/f e/o un suffisso NT (ad es. \"R1N0\" = 1 ambulanza, nessun medico d'urgenza). Vengono riconosciute due grafie: senza spazio e con trattino prima di NT (Leitstelle Lausitz, ad es. \"R1N1p\", \"R1N0-NT\") e con spazio e senza trattino (Leitstelle Brandeburgo/IRLS, ad es. \"R1N1 p\", \"R1N0 nt\") - non ha alcun effetto se la propria centrale operativa non utilizza nessuno di questi modelli, poiché la parola chiave semplicemente non corrisponderà. Ha la priorità sulla tabella nella scheda Descrizioni delle parole chiave quando una parola chiave corrisponde.",
-    "starts with": "inizia con",
+    "Show incident-area polygon": "Mostra il poligono dell'area dell'incidente",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Testo aggiunto quando la parola chiave termina con \"-NT\" o \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Testo aggiunto quando la parola chiave termina con \"f\".",
     "Text appended when the keyword ends in \"p\".": "Testo aggiunto quando la parola chiave termina con \"p\".",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Testo utilizzato nella descrizione generata per la parte R<n>, ad es. \"Rettungswagen: 1\".",
     "WAIP server URL": "URL del server WAIP",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Tempo di attesa prima che l'adattatore si riconnetta automaticamente dopo una connessione persa o un errore di connessione.",
+    "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.": "Se selezionato (predefinito), il poligono dell'area dell'incidente inviato da WAIP-Web viene disegnato come contorno (tornando a un punto marcatore centrato solo quando non è disponibile alcun poligono). Deselezionare per mostrare invece sempre il semplice punto marcatore centrato, anche quando è disponibile un poligono.",
     "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.": "Se disattivato, gli incidenti il cui einsatzart li identifica come una chiamata del servizio di soccorso (contiene \"Rettung\" o \"Krankentransport\", senza distinzione tra maiuscole e minuscole) vengono ignorati completamente - nessuno stato viene aggiornato, nessuna voce di cronologia viene scritta, nessun annuncio TTS viene attivato. Utile perché alcune centrali operative WAIP segnalano gli incidenti del servizio di soccorso solo in modo inaffidabile o per niente.",
     "Width of the generated map image in pixels.": "Larghezza dell'immagine della mappa generata in pixel.",
-    "Zoom level": "Livello di zoom"
+    "Zoom level": "Livello di zoom",
+    "contains": "contiene",
+    "starts with": "inizia con"
 }

package/admin/i18n/nl.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Basis-URL van de WAIP-verzendingsserver (Socket.IO-eindpunt, naamruimte /waip wordt automatisch toegevoegd)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Kleur van de incidentgebied-contour (en van de kern van de reserve-puntmarkering, gebruikt wanneer er geen gebiedspolygoon beschikbaar is).",
     "Connection": "Verbinding",
-    "contains": "bevat",
     "Description": "Beschrijving",
     "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.": "Downloadt voor elk incident met geldige coördinaten OpenStreetMap-tegels en stelt een PNG samen, gecentreerd op de locatie van het incident, met het door WAIP-Web verzonden incidentgebied als contour getekend (valt terug op een puntmarkering als er geen gebiedspolygoon beschikbaar is). Het bestandspad wordt geschreven naar de state einsatz.kartenbildPfad, bijvoorbeeld om als Pushover-bijlage te versturen vanuit een Blockly/JavaScript-script. Alleen de 10 meest recente afbeeldingen worden bewaard, oudere worden automatisch verwijderd. Gebruikt de openbare server tile.openstreetmap.org - houd dit bij het beoogde gebruik van één afbeelding per incident volgens het OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Kaartafbeelding genereren voor elk incident",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Time-out(s) voor registratie",
     "Rescue service": "Reddingsdienst",
     "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.": "Trefwoordschema van de reddingsdienst R<RTW>N<NEF>, optioneel gevolgd door een p/f-modifier en/of een NT-achtervoegsel (bijv. \"R1N0\" = 1 ambulance, geen spoedarts). Twee schrijfwijzen worden herkend: zonder spatie en met een koppelteken vóór NT (meldkamer Lausitz, bijv. \"R1N1p\", \"R1N0-NT\") en met een spatie en zonder koppelteken (meldkamer Brandenburg/IRLS, bijv. \"R1N1 p\", \"R1N0 nt\") - heeft geen effect als uw meldkamer geen van deze patronen gebruikt, aangezien het trefwoord dan gewoon niet overeenkomt. Heeft voorrang op de tabel op het tabblad Trefwoordbeschrijvingen wanneer een trefwoord overeenkomt.",
-    "starts with": "begint met",
+    "Show incident-area polygon": "Incidentgebied-polygoon tonen",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Tekst die wordt toegevoegd wanneer het trefwoord eindigt op \"-NT\" of \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Tekst toegevoegd wanneer het trefwoord eindigt op \"f\".",
     "Text appended when the keyword ends in \"p\".": "Tekst toegevoegd wanneer het trefwoord eindigt op \"p\".",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Tekst gebruikt in de gegenereerde beschrijving voor het R<n>-deel, b.v. \"Rettungswagen: 1\".",
     "WAIP server URL": "WAIP-server-URL",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Wachttijd voordat de adapter automatisch opnieuw verbinding maakt na een verbroken verbinding of een verbindingsfout.",
+    "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.": "Indien aangevinkt (standaard), wordt de door WAIP-Web verzonden incidentgebied-polygoon als contour getekend (valt alleen terug op een gecentreerde puntmarkering als er geen polygoon beschikbaar is). Vink uit om in plaats daarvan altijd de eenvoudige gecentreerde puntmarkering te tonen, ook wanneer een polygoon beschikbaar is.",
     "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.": "Indien uitgeschakeld, worden incidenten waarvan einsatzart aangeeft dat het om een reddingsdienstmelding gaat (bevat \"Rettung\" of \"Krankentransport\", niet hoofdlettergevoelig) volledig genegeerd - er worden geen states bijgewerkt, geen geschiedenisregel geschreven, geen TTS-melding geactiveerd. Nuttig omdat sommige WAIP-meldkamers reddingsdienstincidenten alleen onbetrouwbaar of helemaal niet signaleren.",
     "Width of the generated map image in pixels.": "Breedte van de gegenereerde kaartafbeelding in pixels.",
-    "Zoom level": "Zoomniveau"
+    "Zoom level": "Zoomniveau",
+    "contains": "bevat",
+    "starts with": "begint met"
 }

package/admin/i18n/pl.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Podstawowy adres URL serwera wysyłkowego WAIP (punkt końcowy Socket.IO, przestrzeń nazw /waip jest dodawana automatycznie)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Kolor konturu obszaru zdarzenia (oraz rdzenia zapasowego znacznika punktowego, używanego, gdy brak jest dostępnego poligonu obszaru).",
     "Connection": "Połączenie",
-    "contains": "zawiera",
     "Description": "Opis",
     "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.": "Dla każdego zdarzenia z prawidłowymi współrzędnymi pobiera kafelki OpenStreetMap i tworzy plik PNG wyśrodkowany na lokalizacji zdarzenia, z obszarem zdarzenia przesłanym przez WAIP-Web narysowanym jako kontur (jeśli brak dostępnego poligonu obszaru, używany jest znacznik punktowy). Ścieżka pliku jest zapisywana w stanie einsatz.kartenbildPfad, np. do wysłania jako załącznik Pushover ze skryptu Blockly/JavaScript. Przechowywanych jest tylko 10 najnowszych obrazów, starsze są usuwane automatycznie. Wykorzystuje publiczny serwer tile.openstreetmap.org - należy trzymać się zamierzonego użycia jednego obrazu na zdarzenie zgodnie z OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Generuj obraz mapy dla każdego zdarzenia",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Limit czasu rejestracji (s)",
     "Rescue service": "Ratownictwo medyczne",
     "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.": "Schemat słów kluczowych pogotowia ratunkowego R<RTW>N<NEF>, opcjonalnie po którym następuje modyfikator p/f i/lub sufiks NT (np. \"R1N0\" = 1 karetka, brak lekarza ratunkowego). Rozpoznawane są dwa zapisy: bez spacji i z myślnikiem przed NT (centrala Lausitz, np. \"R1N1p\", \"R1N0-NT\") oraz ze spacją i bez myślnika (centrala Brandenburgia/IRLS, np. \"R1N1 p\", \"R1N0 nt\") - nie ma żadnego efektu, jeśli twoja centrala dyspozytorska nie używa żadnego z tych wzorców, ponieważ słowo kluczowe po prostu nie będzie pasować. Ma pierwszeństwo przed tabelą na karcie Opisy słów kluczowych, gdy słowo kluczowe pasuje.",
-    "starts with": "zaczyna się od",
+    "Show incident-area polygon": "Pokaż poligon obszaru zdarzenia",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Tekst dodawany, gdy słowo kluczowe kończy się na \"-NT\" lub \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Tekst dołączany, gdy słowo kluczowe kończy się na „f”.",
     "Text appended when the keyword ends in \"p\".": "Tekst dołączany, gdy słowo kluczowe kończy się na „p”.",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Tekst użyty w wygenerowanym opisie dla części R<n>, np. „Rettungswagen: 1”.",
     "WAIP server URL": "Adres URL serwera WAIP",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Czas oczekiwania, zanim adapter automatycznie ponownie połączy się po utracie połączenia lub błędzie połączenia.",
+    "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.": "Gdy zaznaczone (domyślnie), poligon obszaru zdarzenia wysyłany przez WAIP-Web jest rysowany jako kontur (powrót do wyśrodkowanego znacznika punktowego tylko wtedy, gdy brak jest dostępnego poligonu). Odznacz, aby zamiast tego zawsze pokazywać prosty wyśrodkowany znacznik punktowy, nawet gdy poligon jest dostępny.",
     "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.": "Gdy odznaczone, zdarzenia, których einsatzart wskazuje na wezwanie ratownictwa medycznego (zawiera \"Rettung\" lub \"Krankentransport\", bez rozróżniania wielkości liter) są całkowicie ignorowane - żadne stany nie są aktualizowane, nie zapisuje się wpisu w historii, nie jest uruchamiane żadne powiadomienie TTS. Przydatne, ponieważ niektóre centra dyspozytorskie WAIP sygnalizują zdarzenia ratownictwa medycznego tylko zawodnie lub wcale.",
     "Width of the generated map image in pixels.": "Szerokość wygenerowanego obrazu mapy w pikselach.",
-    "Zoom level": "Poziom powiększenia"
+    "Zoom level": "Poziom powiększenia",
+    "contains": "zawiera",
+    "starts with": "zaczyna się od"
 }

package/admin/i18n/pt.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "URL base do servidor de despacho WAIP (endpoint Socket.IO, namespace /waip é anexado automaticamente)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Cor do contorno da área da ocorrência (e do núcleo do ponto marcador de reserva, usado quando nenhum polígono de área está disponível).",
     "Connection": "Conexão",
-    "contains": "contém",
     "Description": "Descrição",
     "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.": "Para cada ocorrência com coordenadas válidas, baixa blocos do OpenStreetMap e compõe um PNG centrado na localização da ocorrência, com a área da ocorrência enviada pelo WAIP-Web desenhada como contorno (recorre a um ponto marcador se nenhum polígono de área estiver disponível). O caminho do arquivo é gravado no estado einsatz.kartenbildPfad, por exemplo para envio como anexo do Pushover a partir de um script Blockly/JavaScript. Apenas as 10 imagens mais recentes são mantidas, as mais antigas são excluídas automaticamente. Usa o servidor público tile.openstreetmap.org - mantenha isso dentro do uso pretendido de uma imagem por ocorrência conforme a OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Gerar uma imagem de mapa para cada ocorrência",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Tempo limite de registro(s)",
     "Rescue service": "Serviço de resgate",
     "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.": "Esquema de palavras-chave do serviço de resgate R<RTW>N<NEF>, opcionalmente seguido por um modificador p/f e/ou um sufixo NT (por exemplo, \"R1N0\" = 1 ambulância, sem médico de emergência). Duas grafias são reconhecidas: sem espaço e com hífen antes de NT (central de Lausitz, por exemplo, \"R1N1p\", \"R1N0-NT\") e com espaço e sem hífen (central de Brandemburgo/IRLS, por exemplo, \"R1N1 p\", \"R1N0 nt\") - não tem efeito se a sua central de despacho não usar nenhum desses padrões, já que a palavra-chave simplesmente não corresponderá. Tem prioridade sobre a tabela na aba Descrições de palavras-chave quando uma palavra-chave corresponde.",
-    "starts with": "começa com",
+    "Show incident-area polygon": "Mostrar polígono da área da ocorrência",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Texto adicionado quando a palavra-chave termina em \"-NT\" ou \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Texto acrescentado quando a palavra-chave termina em \"f\".",
     "Text appended when the keyword ends in \"p\".": "Texto acrescentado quando a palavra-chave termina em “p”.",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Texto usado na descrição gerada para a parte R<n>, por exemplo. \"Rettungswagen: 1\".",
     "WAIP server URL": "URL do servidor WAIP",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Aguarde o tempo antes que o adaptador se reconecte automaticamente após uma conexão perdida ou um erro de conexão.",
+    "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.": "Quando marcado (padrão), o polígono da área da ocorrência enviado pelo WAIP-Web é desenhado como contorno (recorrendo a um ponto marcador centralizado apenas quando nenhum polígono está disponível). Desmarque para sempre mostrar o simples ponto marcador centralizado, mesmo quando um polígono estiver disponível.",
     "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.": "Se desmarcado, as ocorrências cujo einsatzart as identifica como um chamado do serviço de resgate (contém \"Rettung\" ou \"Krankentransport\", sem diferenciar maiúsculas/minúsculas) são completamente ignoradas - nenhum estado é atualizado, nenhuma entrada de histórico é gravada, nenhum aviso de voz (TTS) é acionado. Útil porque algumas centrais de despacho WAIP só sinalizam ocorrências do serviço de resgate de forma pouco confiável ou não sinalizam de forma alguma.",
     "Width of the generated map image in pixels.": "Largura da imagem de mapa gerada em pixels.",
-    "Zoom level": "Nível de zoom"
+    "Zoom level": "Nível de zoom",
+    "contains": "contém",
+    "starts with": "começa com"
 }

package/admin/i18n/ru.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Базовый URL-адрес сервера отправки WAIP (конечная точка Socket.IO, пространство имен /waip добавляется автоматически)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Цвет контура зоны вызова (и ядра резервной точки-маркера, используемой при отсутствии доступного полигона зоны).",
     "Connection": "Подключение",
-    "contains": "содержит",
     "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.": "Для каждого вызова с корректными координатами загружает тайлы OpenStreetMap и собирает PNG-изображение, центрированное на месте вызова, с зоной вызова, присланной WAIP-Web, нарисованной в виде контура (если полигон зоны недоступен, используется точка-маркер). Путь к файлу записывается в состояние einsatz.kartenbildPfad, например для отправки в виде вложения Pushover из скрипта Blockly/JavaScript. Хранятся только 10 самых последних изображений, более старые удаляются автоматически. Используется публичный сервер tile.openstreetmap.org - придерживайтесь предполагаемого использования одного изображения на вызов согласно OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Создавать изображение карты для каждого вызова",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Таймаут регистрации (с)",
     "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\") - 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.": "Схема ключевых слов службы спасения R<RTW>N<NEF>, за которой может следовать модификатор p/f и/или суффикс NT (например, \"R1N0\" = 1 машина скорой помощи, без врача). Распознаются два варианта написания: без пробела и с дефисом перед NT (диспетчерская Lausitz, например, \"R1N1p\", \"R1N0-NT\") и с пробелом и без дефиса (диспетчерская Brandenburg/IRLS, например, \"R1N1 p\", \"R1N0 nt\") - не имеет эффекта, если ваша диспетчерская не использует ни один из этих шаблонов, поскольку ключевое слово просто не совпадёт. Имеет приоритет над таблицей на вкладке Описания ключевых слов при совпадении ключевого слова.",
-    "starts with": "начинается с",
+    "Show incident-area polygon": "Показывать полигон зоны вызова",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Текст, добавляемый, если ключевое слово заканчивается на \"-NT\" или \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Текст добавляется, когда ключевое слово заканчивается на «f».",
     "Text appended when the keyword ends in \"p\".": "Текст добавляется, когда ключевое слово заканчивается на «p».",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Текст, используемый в сгенерированном описании части R<n>, например. «Реттунгсваген: 1».",
     "WAIP server URL": "URL-адрес WAIP-сервера",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Время ожидания, прежде чем адаптер автоматически подключится после потери соединения или ошибки соединения.",
+    "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.": "Если отмечено (по умолчанию), полигон зоны вызова, присылаемый WAIP-Web, рисуется в виде контура (переход на центрированную точку-маркер только при отсутствии полигона). Снимите отметку, чтобы всегда показывать простую центрированную точку-маркер, даже если полигон доступен.",
     "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.": "Если флажок снят, вызовы, у которых einsatzart указывает на вызов скорой помощи (содержит \"Rettung\" или \"Krankentransport\", без учёта регистра), полностью игнорируются - состояния не обновляются, запись в историю не делается, голосовое оповещение (TTS) не запускается. Полезно, поскольку некоторые диспетчерские WAIP сигнализируют о вызовах скорой помощи ненадёжно или вообще не сигнализируют.",
     "Width of the generated map image in pixels.": "Ширина создаваемого изображения карты в пикселях.",
-    "Zoom level": "Уровень масштабирования"
+    "Zoom level": "Уровень масштабирования",
+    "contains": "содержит",
+    "starts with": "начинается с"
 }

package/admin/i18n/uk.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "Базова URL-адреса диспетчерського сервера WAIP (кінцева точка Socket.IO, простір імен /waip додається автоматично)",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "Колір контуру зони виклику (і ядра резервної точки-маркера, що використовується за відсутності доступного полігона зони).",
     "Connection": "З'єднання",
-    "contains": "містить",
     "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.": "Для кожного виклику з коректними координатами завантажує тайли OpenStreetMap і формує PNG-зображення, центроване на місці виклику, з зоною виклику, надісланою WAIP-Web, намальованою у вигляді контуру (якщо полігон зони недоступний, використовується точка-маркер). Шлях до файлу записується у стан einsatz.kartenbildPfad, наприклад для надсилання як вкладення Pushover зі скрипту Blockly/JavaScript. Зберігаються лише 10 останніх зображень, старіші видаляються автоматично. Використовується публічний сервер tile.openstreetmap.org - дотримуйтесь передбаченого використання одного зображення на виклик згідно з OSM Tile Usage Policy.",
     "Generate a map image for each incident": "Створювати зображення карти для кожного виклику",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "Час очікування реєстрації (с)",
     "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\") - 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.": "Схема ключових слів служби порятунку R<RTW>N<NEF>, після якої може йти модифікатор p/f та/або суфікс NT (наприклад, \"R1N0\" = 1 машина швидкої допомоги, без лікаря). Розпізнаються два варіанти написання: без пробілу та з дефісом перед NT (диспетчерська Lausitz, наприклад, \"R1N1p\", \"R1N0-NT\") та з пробілом і без дефіса (диспетчерська Brandenburg/IRLS, наприклад, \"R1N1 p\", \"R1N0 nt\") - не має жодного ефекту, якщо ваша диспетчерська не використовує жодного з цих шаблонів, оскільки ключове слово просто не збігатиметься. Має пріоритет над таблицею на вкладці Описи ключових слів, якщо ключове слово збігається.",
-    "starts with": "починається з",
+    "Show incident-area polygon": "Показувати полігон зони виклику",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "Текст, що додається, якщо ключове слово закінчується на \"-NT\" або \" nt\".",
     "Text appended when the keyword ends in \"f\".": "Текст додається, коли ключове слово закінчується на \"f\".",
     "Text appended when the keyword ends in \"p\".": "Текст додається, коли ключове слово закінчується на \"p\".",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "Текст, який використовується в створеному описі для частини R<n>, напр. \"Rettungswagen: 1\".",
     "WAIP server URL": "URL-адреса сервера WAIP",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "Час очікування, перш ніж адаптер автоматично відновить з’єднання після втрати з’єднання або помилки з’єднання.",
+    "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.": "Якщо позначено (типово), полігон зони виклику, надісланий WAIP-Web, малюється у вигляді контуру (перехід на центровану точку-маркер лише за відсутності полігона). Зніміть позначку, щоб завжди показувати просту центровану точку-маркер, навіть якщо полігон доступний.",
     "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.": "Якщо прапорець знято, виклики, у яких einsatzart вказує на виклик швидкої допомоги (містить \"Rettung\" або \"Krankentransport\", без урахування регістру), повністю ігноруються - жодні стани не оновлюються, запис в історію не робиться, голосове сповіщення (TTS) не запускається. Корисно, оскільки деякі диспетчерські WAIP сигналізують про виклики швидкої допомоги лише ненадійно або взагалі не сигналізують.",
     "Width of the generated map image in pixels.": "Ширина створюваного зображення карти в пікселях.",
-    "Zoom level": "Рівень масштабування"
+    "Zoom level": "Рівень масштабування",
+    "contains": "містить",
+    "starts with": "починається з"
 }

package/admin/i18n/zh-cn.json

@@ -4,7 +4,6 @@
     "Base URL of the WAIP dispatch server (Socket.IO endpoint, namespace /waip is appended automatically)": "WAIP 调度服务器的基本 URL（Socket.IO 端点，命名空间 /waip 自动附加）",
     "Color of the incident-area outline (and of the fallback marker dot's core, used when no area polygon is available).": "事件区域轮廓的颜色（以及在没有可用区域多边形时使用的备用圆点标记核心的颜色）。",
     "Connection": "连接",
-    "contains": "包含",
     "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.": "对于每个具有有效坐标的事件，下载 OpenStreetMap 瓦片并合成一张以事件位置为中心的 PNG 图像，将 WAIP-Web 发送的事件区域绘制为轮廓（如果没有可用的区域多边形，则回退为圆点标记）。文件路径写入状态 einsatz.kartenbildPfad，例如可从 Blockly/JavaScript 脚本作为 Pushover 附件发送。仅保留最近的 10 张图像，较旧的会自动删除。使用公共服务器 tile.openstreetmap.org——请遵守 OSM Tile Usage Policy 中每个事件一张图像的预期用途。",
     "Generate a map image for each incident": "为每个事件生成地图图像",
@@ -33,7 +32,7 @@
     "Registration timeout (s)": "注册超时（秒）",
     "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\") - 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.": "救援服务关键字方案 R<RTW>N<NEF>，可选地后跟 p/f 修饰符和/或 NT 后缀（例如 \"R1N0\" = 1辆救护车，无急诊医生）。可识别两种写法：不带空格且NT前带连字符（勒鲁西茨调度中心写法，例如 \"R1N1p\"、\"R1N0-NT\"）以及带空格且不带连字符（勃兰登堡/IRLS调度中心写法，例如 \"R1N1 p\"、\"R1N0 nt\"）——如果你的调度中心不使用这些格式中的任何一种，此选项也不会有任何影响，因为关键字只是不会匹配。当关键字匹配时，优先于\"关键字描述\"标签页中的表格。",
-    "starts with": "开始于",
+    "Show incident-area polygon": "显示事件区域多边形",
     "Text appended when the keyword ends in \"-NT\" or \" nt\".": "当关键字以 \"-NT\" 或 \" nt\" 结尾时附加的文本。",
     "Text appended when the keyword ends in \"f\".": "当关键字以“f”结尾时附加的文本。",
     "Text appended when the keyword ends in \"p\".": "当关键字以“p”结尾时附加的文本。",
@@ -41,7 +40,10 @@
     "Text used in the generated description for the R<n> part, e.g. \"Rettungswagen: 1\".": "生成的 R<n> 部分描述中使用的文本，例如“Rettungswagen：1”。",
     "WAIP server URL": "WAIP 服务器 URL",
     "Wait time before the adapter automatically reconnects after a lost connection or a connection error.": "连接丢失或连接错误后适配器自动重新连接之前的等待时间。",
+    "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.": "选中时（默认），将 WAIP-Web 发送的事件区域多边形绘制为轮廓（仅在没有可用多边形时才回退为居中的圆点标记）。取消选中则始终显示简单的居中圆点标记，即使有多边形可用。",
     "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.": "取消勾选后，einsatzart 表明为急救服务呼叫的事件（包含 \"Rettung\" 或 \"Krankentransport\"，不区分大小写）将被完全忽略——不更新任何状态，不写入历史记录，不触发语音播报（TTS）。这在某些 WAIP 调度中心只能不可靠地或根本不发出急救服务事件信号时很有用。",
     "Width of the generated map image in pixels.": "生成的地图图像宽度（像素）。",
-    "Zoom level": "缩放级别"
+    "Zoom level": "缩放级别",
+    "contains": "包含",
+    "starts with": "开始于"
 }

package/admin/jsonConfig.json

@@ -214,6 +214,17 @@
                     "lg": 12,
                     "xl": 12
                 },
+                "mapImageShowPolygon": {
+                    "type": "checkbox",
+                    "label": "Show incident-area polygon",
+                    "help": "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.",
+                    "hidden": "!data.mapImageEnabled",
+                    "xs": 12,
+                    "sm": 12,
+                    "md": 12,
+                    "lg": 12,
+                    "xl": 12
+                },
                 "mapImageWidth": {
                     "type": "number",
                     "label": "Image width (px)",

package/io-package.json

@@ -1,8 +1,21 @@
 {
   "common": {
     "name": "waip-web",
-    "version": "0.7.29",
+    "version": "0.7.30",
     "news": {
+      "0.7.30": {
+        "en": "New \"Show incident-area polygon\" checkbox for the incident map image (on by default, switch to a centered dot instead); the auto-zoom-fit margin around the polygon is 30% smaller, default zoom raised to 19, default outline thickness to 4px. einsatz.kartenbildPfad is now cleared on io.standby like other fields. Documented Admin's \"delete instance data\" option for removing generated map images on uninstall. Dropped \"Unofficial\" from both READMEs. Changelog now shows only the 5 most recent versions.",
+        "de": "Neue Checkbox \"Einsatzgebiet-Polygon anzeigen\" für die Einsatzkarte (standardmäßig an, umschaltbar auf einen zentrierten Punkt); der Rand beim automatischen Heranzoomen an das Polygon ist 30% kleiner, Standard-Zoom auf 19 erhöht, Standard-Strichstärke auf 4px. einsatz.kartenbildPfad wird jetzt wie die übrigen Felder bei io.standby geleert. Admin-Option \"Instanzdaten löschen\" zum Entfernen der Kartenbilder bei Deinstallation dokumentiert. \"Inoffiziell\" aus beiden READMEs entfernt. Der Changelog zeigt jetzt nur noch die letzten 5 Versionen.",
+        "es": "Nueva casilla \"Mostrar polígono del área del incidente\" para la imagen de mapa del incidente (activada por defecto, cambiable a un punto centrado); el margen del ajuste automático de zoom alrededor del polígono es un 30% más pequeño, el zoom predeterminado se elevó a 19, el grosor de contorno predeterminado a 4px. einsatz.kartenbildPfad ahora se borra en io.standby como los demás campos. Se documentó la opción \"eliminar datos de instancia\" de Admin para eliminar las imágenes de mapa generadas al desinstalar. Se eliminó \"Unofficial\" de ambos README. El registro de cambios ahora muestra solo las 5 versiones más recientes.",
+        "fr": "Nouvelle case à cocher \"Afficher le polygone de la zone d'intervention\" pour l'image de carte de l'incident (activée par défaut, permet de basculer vers un point centré) ; la marge d'ajustement automatique du zoom autour du polygone est réduite de 30 %, le zoom par défaut passe à 19, l'épaisseur de contour par défaut à 4px. einsatz.kartenbildPfad est désormais effacé lors d'un io.standby comme les autres champs. Documentation de l'option \"supprimer les données d'instance\" d'Admin pour supprimer les images de carte générées lors de la désinstallation. Suppression de \"Unofficial\" des deux README. Le journal des modifications n'affiche désormais que les 5 versions les plus récentes.",
+        "it": "Nuova casella \"Mostra il poligono dell'area dell'incidente\" per l'immagine della mappa dell'incidente (attiva per impostazione predefinita, passa a un punto centrato); il margine dello zoom automatico attorno al poligono è ridotto del 30%, lo zoom predefinito aumentato a 19, lo spessore del contorno predefinito a 4px. einsatz.kartenbildPfad ora viene cancellato su io.standby come gli altri campi. Documentata l'opzione \"elimina dati istanza\" di Admin per rimuovere le immagini della mappa generate alla disinstallazione. Rimosso \"Unofficial\" da entrambi i README. Il changelog ora mostra solo le 5 versioni più recenti.",
+        "nl": "Nieuw selectievakje \"Incidentgebied-polygoon tonen\" voor de incidentkaartafbeelding (standaard aan, omschakelbaar naar een gecentreerde stip); de marge van de automatische zoom-aanpassing rond de polygoon is 30% kleiner, standaardzoom verhoogd naar 19, standaard contourdikte naar 4px. einsatz.kartenbildPfad wordt nu bij io.standby gewist zoals de andere velden. Admin-optie \"instantiegegevens verwijderen\" gedocumenteerd voor het verwijderen van gegenereerde kaartafbeeldingen bij deïnstallatie. \"Unofficial\" uit beide READMEs verwijderd. Changelog toont nu alleen de 5 meest recente versies.",
+        "pl": "Nowe pole wyboru \"Pokaż poligon obszaru zdarzenia\" dla obrazu mapy zdarzenia (domyślnie włączone, można przełączyć na wyśrodkowany punkt); margines automatycznego dopasowania powiększenia wokół poligonu jest o 30% mniejszy, domyślne powiększenie zwiększone do 19, domyślna grubość konturu do 4px. einsatz.kartenbildPfad jest teraz czyszczony przy io.standby tak jak inne pola. Udokumentowano opcję Admina \"usuń dane instancji\" do usuwania wygenerowanych obrazów mapy przy odinstalowywaniu. Usunięto \"Unofficial\" z obu plików README. Dziennik zmian pokazuje teraz tylko 5 najnowszych wersji.",
+        "pt": "Nova caixa de seleção \"Mostrar polígono da área da ocorrência\" para a imagem de mapa da ocorrência (ativada por padrão, pode ser alternada para um ponto centralizado); a margem de ajuste automático de zoom ao redor do polígono é 30% menor, zoom padrão aumentado para 19, espessura de contorno padrão para 4px. einsatz.kartenbildPfad agora é limpo no io.standby como os outros campos. Documentada a opção \"excluir dados da instância\" do Admin para remover imagens de mapa geradas ao desinstalar. Removido \"Unofficial\" de ambos os READMEs. O changelog agora mostra apenas as 5 versões mais recentes.",
+        "ru": "Новый флажок \"Показывать полигон зоны вызова\" для изображения карты вызова (по умолчанию включён, можно переключить на центрированную точку); отступ автоматического масштабирования вокруг полигона уменьшен на 30%, масштаб по умолчанию увеличен до 19, толщина контура по умолчанию до 4px. einsatz.kartenbildPfad теперь очищается при io.standby, как и другие поля. Задокументирована опция Admin \"удалить данные экземпляра\" для удаления сгенерированных изображений карты при удалении. Из обоих README удалено слово \"Unofficial\". В журнале изменений теперь отображаются только 5 последних версий.",
+        "uk": "Новий прапорець \"Показувати полігон зони виклику\" для зображення карти виклику (типово увімкнено, можна перемкнути на центровану точку); відступ автоматичного масштабування навколо полігона зменшено на 30%, типовий масштаб збільшено до 19, типову товщину контуру до 4px. einsatz.kartenbildPfad тепер очищається при io.standby, як і інші поля. Задокументовано опцію Admin \"видалити дані екземпляра\" для видалення згенерованих зображень карти при видаленні. З обох README видалено слово \"Unofficial\". Журнал змін тепер показує лише 5 останніх версій.",
+        "zh-cn": "为事件地图图像新增\"显示事件区域多边形\"复选框（默认启用，可切换为居中圆点）；多边形周围自动缩放适配的边距缩小了30%，默认缩放级别提高到19，默认轮廓粗细提高到4px。einsatz.kartenbildPfad 现在会像其他字段一样在 io.standby 时清空。已记录 Admin 中用于卸载时删除生成的地图图像的\"删除实例数据\"选项。已从两个 README 中删除\"Unofficial\"一词。更新日志现在仅显示最近的5个版本。"
+      },
       "0.7.29": {
         "en": "Incident map image now draws the actual incident area WAIP-Web sends (usually a circle polygon), not just a marker dot at its center - falls back to the dot if no polygon is available. Rescue-service keyword decoding now defaults to on for new installations (previously off), matching the rescue-service processing checkbox. Trimmed a redundant justification sentence from both checkboxes' descriptions. The incident area now also always stays fully visible - the adapter automatically zooms out past the configured zoom level if needed, instead of clipping it at the image edge. Outline color and thickness are now configurable too.",
         "de": "Die Einsatzkarte zeichnet jetzt das tatsächliche vom WAIP-Web gesendete Einsatzgebiet (meist ein kreisförmiges Polygon) statt nur eine Punkt-Markierung in dessen Mitte - fällt auf den Punkt zurück, falls kein Polygon vorliegt. Die Rettungsdienst-Stichwort-Dekodierung ist bei Neuinstallationen jetzt standardmäßig aktiviert (vorher deaktiviert), passend zur Checkbox für die Rettungsdienst-Verarbeitung. Ein redundanter Begründungssatz wurde aus beiden Checkbox-Beschreibungen entfernt. Das Einsatzgebiet bleibt jetzt außerdem immer vollständig sichtbar - der Adapter zoomt bei Bedarf automatisch über die konfigurierte Zoomstufe hinaus heraus, statt es am Bildrand abzuschneiden. Umrissfarbe und -stärke sind jetzt ebenfalls konfigurierbar.",
@@ -519,11 +532,12 @@
     "rdLabelF": "First Responder",
     "rdLabelNT": "Notfalltransport mit Notfallkrankenwagen",
     "mapImageEnabled": false,
+    "mapImageShowPolygon": true,
     "mapImageWidth": 600,
     "mapImageHeight": 400,
-    "mapImageZoom": 16,
+    "mapImageZoom": 19,
     "mapImageOutlineColor": "#dd2020",
-    "mapImageOutlineThickness": 3
+    "mapImageOutlineThickness": 4
   },
   "objects": [],
   "instanceObjects": [

package/main.js

@@ -155,9 +155,9 @@ const OSM_MIN_AUTO_ZOOM = 3;
 const OSM_TILE_USER_AGENT = 'ioBroker.waip-web (+https://github.com/rnc11/ioBroker.waip-web)';
 const DEFAULT_MAP_IMAGE_WIDTH = 600;
 const DEFAULT_MAP_IMAGE_HEIGHT = 400;
-const DEFAULT_MAP_IMAGE_ZOOM = 16;
+const DEFAULT_MAP_IMAGE_ZOOM = 19;
 const DEFAULT_MAP_IMAGE_OUTLINE_COLOR = '#dd2020';
-const DEFAULT_MAP_IMAGE_OUTLINE_THICKNESS = 3;
+const DEFAULT_MAP_IMAGE_OUTLINE_THICKNESS = 4;
 const MAP_IMAGE_OUTLINE_THICKNESS_MIN = 1;
 const MAP_IMAGE_OUTLINE_THICKNESS_MAX = 12;
 // DE: Wie viele erzeugte Kartenbilder maximal aufgehoben werden - ältere werden nach jeder
@@ -972,11 +972,13 @@ function fitZoomToPolygon(rings, maxZoom, width, height) {
     }
 
     // DE: Rand, damit die (mit gewisser Strichstärke gezeichnete) Umrisslinie nicht exakt am
-    // Bildrand klebt.
+    // Bildrand klebt. 4,2 %/6px statt 6 %/8px (30 % kleinerer Rand) - das Einsatzgebiet-
+    // Polygon soll den Bildausschnitt großzügiger ausfüllen.
     // EN: Margin so the (drawn with some line thickness) outline doesn't sit exactly at the
-    // image edge.
-    const marginX = Math.max(8, Math.round(width * 0.06));
-    const marginY = Math.max(8, Math.round(height * 0.06));
+    // image edge. 4.2%/6px instead of 6%/8px (30% smaller margin) - the incident-area
+    // polygon should fill more of the image area.
+    const marginX = Math.max(6, Math.round(width * 0.042));
+    const marginY = Math.max(6, Math.round(height * 0.042));
     const availableWidth = Math.max(1, width - 2 * marginX);
     const availableHeight = Math.max(1, height - 2 * marginY);
 
@@ -1137,6 +1139,13 @@ class WaipWeb extends utils.Adapter {
         // width/height/zoom are defensively clamped in case the admin configuration (e.g.
         // via an external JSON import) contains a nonsensical value.
         this.mapImageEnabled = !!this.config.mapImageEnabled;
+        // DE: Default true - zeigt das vom Server gesendete Einsatzgebiet-Polygon, falls
+        // vorhanden (siehe buildEinsatzMapImage()). false erzwingt immer den zentrierten
+        // Punkt-Marker, auch wenn ein Polygon verfügbar wäre.
+        // EN: Defaults to true - shows the incident-area polygon sent by the server, if
+        // available (see buildEinsatzMapImage()). false always forces the centered marker
+        // dot, even when a polygon would be available.
+        this.mapImageShowPolygon = this.config.mapImageShowPolygon !== false;
         this.mapImageWidth = clampNumber(this.config.mapImageWidth, 100, 2000, DEFAULT_MAP_IMAGE_WIDTH);
         this.mapImageHeight = clampNumber(this.config.mapImageHeight, 100, 2000, DEFAULT_MAP_IMAGE_HEIGHT);
         this.mapImageZoom = clampNumber(this.config.mapImageZoom, 1, OSM_MAX_ZOOM, DEFAULT_MAP_IMAGE_ZOOM);
@@ -2036,15 +2045,18 @@ class WaipWeb extends utils.Adapter {
        canvas background color, but a total failure of all tiles propagates via
        Promise.all(). Throws on a hard failure (e.g. not a single tile loadable) - caller
        generateEinsatzMapImage() catches that.
-       Zoom level: if an incident-area polygon is supplied, the actual zoom used deviates
-       downward (zooms out) from the configured this.mapImageZoom as needed, so the full
-       area stays visible in the image instead of being clipped at the edge - see
-       fitZoomToPolygon(). Without a polygon (falling back to the point marker), it stays at
-       the configured zoom. */
+       Zoom level: if an incident-area polygon is supplied (and mapImageShowPolygon is on),
+       the actual zoom used deviates downward (zooms out) from the configured
+       this.mapImageZoom as needed, so the full area stays visible in the image instead of
+       being clipped at the edge - see fitZoomToPolygon(). Without a polygon (falling back
+       to the point marker), it stays at the configured zoom.
+       mapImageShowPolygon: when off, the polygon is never extracted/drawn at all - the
+       function behaves exactly as if the incident carried no geometry, always falling back
+       to the centered marker dot at the configured zoom. */
     async buildEinsatzMapImage(lat, lon, geometry) {
         const width = this.mapImageWidth;
         const height = this.mapImageHeight;
-        const rings = extractPolygonRings(geometry);
+        const rings = this.mapImageShowPolygon ? extractPolygonRings(geometry) : [];
         let zoom = this.mapImageZoom;
         if (rings.length) {
             const fittedZoom = fitZoomToPolygon(rings, zoom, width, height);
@@ -2804,6 +2816,14 @@ class WaipWeb extends utils.Adapter {
         tasks.push(this.setStateAsync('einsatz.beschreibung', null, true));
         tasks.push(this.setStateAsync('einsatz.latitude', null, true));
         tasks.push(this.setStateAsync('einsatz.longitude', null, true));
+        // DE: Anders als einsatz.tts.last (dessen Vorbild ursprünglich für kartenbildPfad
+        // übernommen wurde) wird kartenbildPfad jetzt doch wie die übrigen einsatz.*-Felder
+        // geleert - kein Alarm aktiv soll auch bedeuten, dass kein Kartenbild mehr referenziert
+        // wird.
+        // EN: Unlike einsatz.tts.last (whose pattern was originally borrowed for
+        // kartenbildPfad), kartenbildPfad is now cleared like the other einsatz.* fields
+        // after all - no active alarm should also mean no map image is referenced anymore.
+        tasks.push(this.setStateAsync('einsatz.kartenbildPfad', null, true));
         tasks.push(this.writeJsonArrayState('einsatz.json.current', []));
         tasks.push(this.writeJsonArrayState('einsatz.json.routen', []));
         tasks.push(this.writeJsonArrayState('einsatz.json.rueckmeldungen', []));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "iobroker.waip-web",
-  "version": "0.7.29",
+  "version": "0.7.30",
   "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",