iobroker.waip-web 0.7.28 → 0.7.29

package/README.de.md

@@ -180,9 +180,12 @@ Rettungsdienst-Wache:
   eigenen Region ohnehin nur unzuverlässig signalisiert, siehe
   [Rettungsdienst](#rettungsdienst)
 - Optionales Einsatzkarten-Bild: ein auf die Einsatz-Koordinaten
-  zentriertes und mit einem Punkt markiertes PNG, lokal aus
-  OpenStreetMap-Kacheln zusammengesetzt, dessen Dateipfad als State
-  bereitsteht - siehe [Einsatzkarte](#einsatzkarte)
+  zentriertes PNG, lokal aus OpenStreetMap-Kacheln zusammengesetzt, mit
+  dem von WAIP-Web gesendeten Einsatzgebiet als Umriss in
+  konfigurierbarer Farbe/Stärke eingezeichnet (Rückfall auf
+  Punkt-Markierung), zoomt bei Bedarf automatisch so heraus, dass das
+  gesamte Gebiet sichtbar bleibt, Dateipfad als State bereitgestellt -
+  siehe [Einsatzkarte](#einsatzkarte)
 
 ## Konfiguration
 
@@ -248,7 +251,7 @@ werden dabei keine Daten irgendwohin gesendet. Dieser Tab ist die erste
 von zwei Quellen, die der Reihe nach geprüft werden (die zweite steht
 unter [Stichwort-Stammdaten](#stichwort-stammdaten)):
 
-**Rettungsdienst-Dekodierung** (Admin-Checkbox, standardmäßig aus):
+**Rettungsdienst-Dekodierung** (Admin-Checkbox, standardmäßig an):
 passt das Stichwort auf das Muster `R<Anzahl RTW>N<Anzahl NEF>[p][f][-NT]`
 (z.B. `R1N0` → "Rettungswagen: 1, Notfalleinsatzfahrzeug: 0"), wird
 automatisch eine Beschreibung erzeugt. Zwei Schreibweisen des
@@ -258,8 +261,9 @@ vor `NT` (z.B. `R1N1p`, `R1N0-NT`, siehe
 dazu) sowie mit Leerzeichen und ohne Bindestrich (z.B. `R1N1 p`,
 `R1N0 nt`, wie von der IRLS Brandenburg verwendet) – dieses Schema
 (in beiden Schreibweisen) wird von mehreren Leitstellen verwendet,
-nicht nur diesen beiden – nur aktivieren, wenn eure Leitstelle eines
-dieser Muster tatsächlich verwendet. Der Text für jeden Teil ist
+nicht nur diesen beiden – hat keine Auswirkung, falls eure Leitstelle
+keines dieser Muster verwendet, da das Stichwort dann einfach nicht
+passt. Der Text für jeden Teil ist
 selbst konfigurierbar (5 zusätzliche Textfelder erscheinen, sobald
 die Checkbox aktiviert ist), da der Adapter mehrsprachig ist und
 diese Bezeichnungen nicht automatisch übersetzt werden:
@@ -307,10 +311,21 @@ Passt weder diese Tabelle noch der Dekoder oben, bleibt
 aus): ist die Checkbox aktiv und liegen für einen Einsatz gültige
 Koordinaten vor, lädt der Adapter die dafür nötigen Kacheln vom
 öffentlichen Server `tile.openstreetmap.org` herunter, setzt sie zu
-einem einzigen PNG zusammen, zentriert auf den Einsatzort, zeichnet eine
-Markierung (roter Punkt, weißer Rand) exakt in die Mitte und stempelt
+einem einzigen PNG zusammen, zentriert auf den Einsatzort, und stempelt
 die von der ODbL-Lizenz vorgeschriebene OpenStreetMap-Attribution unten
-links auf. Der Dateipfad wird in `einsatz.kartenbildPfad` geschrieben
+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
+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
 Pushover-Benachrichtigungsanhang. Es werden nur die 10 zuletzt erzeugten
@@ -324,7 +339,9 @@ sonst bleibt nichts betroffen.
 | --- | --- | --- |
 | Bildbreite (px) | Breite des erzeugten PNGs | `600` |
 | Bildhöhe (px) | Höhe des erzeugten PNGs | `400` |
-| Zoomstufe | OpenStreetMap-Zoomstufe (1 = ganze Welt, 19 = Gebäudeebene) | `16` |
+| Zoomstufe | OpenStreetMap-Zoomstufe (1 = ganze Welt, 19 = Gebäudeebene) - ein Maximalwert, wird bei Bedarf automatisch reduziert, damit das Einsatzgebiet vollständig sichtbar bleibt | `16` |
+| 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` |
 
 Die Bilder liegen im eigenen Datenverzeichnis dieser Adapterinstanz
 (`iobroker-data/<instance>/maps/`), nicht als ioBroker-Dateiobjekte –

package/README.md

@@ -182,9 +182,11 @@ adapter provides – typical use in a fire station/EMS environment:
   history, no TTS) - useful where WAIP only signals them unreliably in
   the first place, see [Rescue service](#rescue-service)
 - Optional incident map image: a PNG centered on the incident's
-  coordinates and marked with a dot, composed locally from OpenStreetMap
-  tiles, with its file path exposed as a state - see
-  [Incident map image](#incident-map-image)
+  coordinates, composed locally from OpenStreetMap tiles, with the
+  incident area WAIP-Web sends drawn as an outline in a configurable
+  color/thickness (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)
 
 ## Configuration
 
@@ -247,7 +249,7 @@ gap **entirely locally**, no data is sent anywhere. This tab is the
 first of two sources checked, in order (see
 [Keyword descriptions](#keyword-descriptions) for the second):
 
-**Rescue-service decoding** (admin checkbox, off by default): if the
+**Rescue-service decoding** (admin checkbox, on by default): if the
 keyword matches the pattern `R<RTW-count>N<NEF-count>[p][f][-NT]`
 (e.g. `R1N0` → "Rettungswagen: 1, Notfalleinsatzfahrzeug: 0"), a
 description is generated automatically. Two spellings of the `p`/`f`/`NT`
@@ -256,9 +258,9 @@ part are recognized: without a space and with a hyphen before `NT`
 [Leitstelle Lausitz's documented explanation](https://www.leitstelle-lausitz.de/anpassung-der-einsatzstichworte-rettungsdienst/)
 of it), and with a space and without a hyphen (e.g. `R1N1 p`, `R1N0 nt`,
 as used by the IRLS Brandenburg) – this scheme (in either spelling) is
-used by several German dispatch centers, not just these two – only
-enable it if your dispatch center actually uses one of these patterns.
-The text for each part is itself configurable (5 additional text
+used by several German dispatch centers, not just these two – has no
+effect if your dispatch center doesn't use one of these patterns, since
+the keyword just won't match. The text for each part is itself configurable (5 additional text
 fields appear once the checkbox is enabled), since the adapter is
 multi-language and these labels aren't translated automatically:
 
@@ -301,9 +303,19 @@ is simply `null` - not an error.
 default): when enabled and an incident carries valid coordinates, the
 adapter downloads the tiles it needs from the public
 `tile.openstreetmap.org` server, composites them into a single PNG
-centered on the incident's location, draws a marker (red dot, white
-ring) at the exact center, and stamps the OpenStreetMap attribution
-(required by its ODbL license) into the bottom-left corner. The file
+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
@@ -316,7 +328,9 @@ just means a missing/delayed image, nothing else is affected.
 | --- | --- | --- |
 | Image width (px) | Width of the generated PNG | `600` |
 | Image height (px) | Height of the generated PNG | `400` |
-| Zoom level | OpenStreetMap zoom level (1 = whole world, 19 = building level) | `16` |
+| Zoom level | OpenStreetMap zoom level (1 = whole world, 19 = building level) - a maximum, automatically reduced if needed to keep the incident area fully visible | `16` |
+| 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` |
 
 Images are stored under this adapter instance's own data directory
 (`iobroker-data/<instance>/maps/`), not as ioBroker file objects –
@@ -468,6 +482,27 @@ example.
 
 ## Changelog
 
+### 0.7.29 (2026-08-24)
+
+- [Incident map image](#incident-map-image): draws the actual incident
+  area WAIP-Web sends in the event's `geometry` field (usually a
+  circle-shaped polygon around the location) as an outline, instead of
+  just a marker dot at its centroid. Falls back to the dot marker if no
+  polygon is available (e.g. only a point). The area always stays
+  fully visible: the adapter automatically zooms out (never in) past
+  the configured zoom level if needed, instead of clipping the area at
+  the image edge. Outline color and thickness (1-12 px) are now
+  configurable too (also used for the fallback marker dot's core).
+- **Rescue-service decoding** (on the [Rescue service](#rescue-service)
+  tab) now defaults to **on** for new installations, matching **Process
+  rescue-service incidents** (already on by default) - previously it
+  defaulted to off. Already-configured instances keep their stored
+  value, this only affects fresh installs.
+- Trimmed the self-justifying "kept the previous behavior" sentence
+  from both checkboxes' admin descriptions and reworded the decoding
+  checkbox's description ("has no effect if your dispatch center
+  doesn't use one of these patterns" instead of "only enable if...").
+
 ### 0.7.28 (2026-08-24)
 
 - New: **Process rescue-service incidents** checkbox on the

package/admin/i18n/de.json

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

package/admin/i18n/en.json

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

@@ -2,10 +2,11 @@
     "Alarm keyword descriptions": "Descripciones de palabras clave de alarma",
     "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Decodificar automáticamente las palabras clave del servicio de rescate (R<RTW>N<NEF>[p][f][-NT], con o sin espacios)",
     "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, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "Para cada incidente con coordenadas válidas, descarga teselas de OpenStreetMap y compone un PNG centrado en la ubicación del incidente, marcado con un punto. 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.",
+    "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",
     "Height of the generated map image in pixels.": "Alto de la imagen de mapa generada en píxeles.",
     "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "Cuánto tiempo esperar para que el servidor confirme el registro del monitor antes de registrar una advertencia; la conexión en sí sigue funcionando en cualquier sentido.",
@@ -19,16 +20,19 @@
     "Label for suffix -NT / nt (special ambulance transport)": "Etiqueta para el sufijo -NT / nt (transporte especial en ambulancia)",
     "Label for suffix f (first responder)": "Etiqueta para el sufijo f (primer interviniente)",
     "Label for suffix p (polytrauma)": "Etiqueta para el sufijo p (politraumatismo)",
+    "Line thickness of the incident-area outline, in pixels.": "Grosor de línea del contorno del área del incidente, en píxeles.",
     "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Cargado en vivo desde la página de descripción general /waip/ del servidor configurado: elija Leitstelle, Kreis, Träger o Wache, o elija 'Alle Wachalarme' (ID 0) para cada incidente. Si no se puede acceder al servidor, aún se puede ingresar una identificación manualmente.",
     "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Asigna einsatz.stichwort a einsatz.beschreibung. La comparación no distingue mayúsculas/minúsculas y trata los espacios/guiones como equivalentes (cualquier secuencia de ambos se reduce a uno antes de comparar), de modo que, por ejemplo, \"H:VU mit P\" y \"H:VU-mit-P\" coinciden con la misma fila - no es necesaria una fila separada por cada variante de escritura. Si varias filas coinciden, el patrón más específico (el más largo) gana automáticamente; el orden de las filas no tiene ningún efecto en la coincidencia, ordene libremente por cualquier columna. Precompletado con una lista de palabras clave de ejemplo de incendio/rescate como punto de partida; no se confirma que coincida con las palabras clave reales de su propio centro de despacho, edite/reemplace según sea necesario. Para hacer una copia de seguridad o transferir esta tabla, utilice la exportación/importación estándar de la configuración de instancia de ioBroker (JSON). Después de usar esa importación estándar, recargue la página de administración antes de comprobar esta tabla - el cuadro de diálogo de configuración abierto no la actualiza automáticamente desde una importación externa (una limitación de sincronización de estado del propio componente de tabla de administración).",
     "Match": "Fósforo",
     "Monitor ID": "Identificador del monitor",
-    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.": "Nivel de zoom de OpenStreetMap (1 = todo el mundo, 19 = nivel de edificio). Valores más altos muestran un área más pequeña con más detalle.",
+    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.": "Nivel de zoom de OpenStreetMap (1 = todo el mundo, 19 = nivel de edificio). Valores más altos muestran un área más pequeña con más detalle. Este es un valor máximo, no fijo: si el área del incidente enviada por el servidor no cupiera por completo en la imagen con este zoom, el adaptador aleja automáticamente el zoom (nunca lo acerca) lo justo para mantener toda el área visible.",
+    "Outline color": "Color del contorno",
+    "Outline thickness (px)": "Grosor del contorno (px)",
     "Process rescue-service incidents": "Procesar incidentes del servicio de rescate",
     "Reconnect delay (s)": "Retardo(s) de reconexión",
     "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\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "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\") - actívelo solo si su central de despacho utiliza realmente uno de estos patrones. Tiene prioridad sobre la tabla de la pestaña Descripciones de palabras clave cuando una palabra clave coincide.",
+    "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",
     "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\".",
@@ -37,7 +41,7 @@
     "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 unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.": "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. Activado por defecto para mantener el comportamiento anterior.",
+    "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"
 }

package/admin/i18n/fr.json

@@ -2,10 +2,11 @@
     "Alarm keyword descriptions": "Descriptions des mots-clés d'alarme",
     "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Décoder automatiquement les mots-clés des services de secours (R<RTW>N<NEF>[p][f][-NT], avec ou sans espaces)",
     "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, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "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, marqué d'un point. 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.",
+    "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",
     "Height of the generated map image in pixels.": "Hauteur de l'image de carte générée en pixels.",
     "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "Combien de temps attendre que le serveur confirme l'enregistrement du moniteur avant d'enregistrer un avertissement ; la connexion elle-même continue de fonctionner dans les deux sens.",
@@ -19,16 +20,19 @@
     "Label for suffix -NT / nt (special ambulance transport)": "Libellé pour le suffixe -NT / nt (transport spécial en ambulance)",
     "Label for suffix f (first responder)": "Étiquette pour le suffixe f (premier intervenant)",
     "Label for suffix p (polytrauma)": "Étiquette pour le suffixe p (polytraumatisme)",
+    "Line thickness of the incident-area outline, in pixels.": "Épaisseur de ligne du contour de la zone d'intervention, en pixels.",
     "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Chargé en direct depuis la page de présentation /waip/ du serveur configuré - choisissez par Leitstelle, Kreis, Träger ou Wache, ou choisissez 'Alle Wachalarme' (ID 0) pour chaque incident. Si le serveur n'est pas accessible, un identifiant peut toujours être saisi manuellement.",
     "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Mappe einsatz.stichwort à einsatz.beschreibung. La comparaison ne tient pas compte de la casse et traite les espaces/tirets comme équivalents (toute suite de l'un ou l'autre est ramenée à un seul avant la comparaison), de sorte que par exemple \"H:VU mit P\" et \"H:VU-mit-P\" correspondent à la même ligne - pas besoin d'une ligne distincte par variante d'orthographe. Si plusieurs lignes correspondent, le modèle le plus spécifique (le plus long) l'emporte automatiquement - l'ordre des lignes n'a aucun effet sur la correspondance, triez-la librement par n'importe quelle colonne. Pré-rempli avec un exemple de liste de mots-clés d'incendie/sauvetage comme point de départ - il n'est pas confirmé qu'il correspond aux mots-clés réels de votre propre centre de répartition, modifiez/remplacez si nécessaire. Pour sauvegarder ou transférer ce tableau, utilisez l'export/import standard de la configuration d'instance d'ioBroker (JSON). Après avoir utilisé cet import standard, rechargez la page Admin avant de vérifier ce tableau - la boîte de dialogue de configuration ouverte ne l'actualise pas automatiquement après un import externe (une limitation de synchronisation d'état du composant de tableau Admin lui-même).",
     "Match": "Correspondre",
     "Monitor ID": "ID du moniteur",
-    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.": "Niveau de zoom OpenStreetMap (1 = monde entier, 19 = niveau du bâtiment). Des valeurs plus élevées affichent une zone plus petite avec plus de détails.",
+    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.": "Niveau de zoom OpenStreetMap (1 = monde entier, 19 = niveau du bâtiment). Des valeurs plus élevées affichent une zone plus petite avec plus de détails. Il s'agit d'une valeur maximale, pas fixe : si la zone d'intervention envoyée par le serveur ne tenait pas entièrement dans l'image à ce niveau de zoom, l'adaptateur dézoome automatiquement (jamais ne zoome) juste ce qu'il faut pour garder toute la zone visible.",
+    "Outline color": "Couleur du contour",
+    "Outline thickness (px)": "Épaisseur du contour (px)",
     "Process rescue-service incidents": "Traiter les incidents du service de secours",
     "Reconnect delay (s)": "Délai(s) de reconnexion",
     "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\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "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\") - à activer uniquement si votre centre de répartition utilise effectivement l'un de ces modèles. Prioritaire sur la table de l'onglet Descriptions de mots-clés lorsqu'un mot-clé correspond.",
+    "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",
     "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\".",
@@ -37,7 +41,7 @@
     "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 unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.": "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. Activé par défaut pour conserver le comportement précédent.",
+    "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"
 }

package/admin/i18n/it.json

@@ -2,10 +2,11 @@
     "Alarm keyword descriptions": "Descrizioni delle parole chiave degli allarmi",
     "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Decodifica automaticamente le parole chiave del servizio di soccorso (R<RTW>N<NEF>[p][f][-NT], con o senza spazi)",
     "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, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "Per ogni incidente con coordinate valide, scarica i tile di OpenStreetMap e compone un PNG centrato sulla posizione dell'incidente, contrassegnato con un punto. 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.",
+    "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",
     "Height of the generated map image in pixels.": "Altezza dell'immagine della mappa generata in pixel.",
     "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "Quanto tempo attendere affinché il server confermi la registrazione del monitor prima di registrare un avviso; la connessione stessa continua a funzionare in entrambi i casi.",
@@ -19,16 +20,19 @@
     "Label for suffix -NT / nt (special ambulance transport)": "Etichetta per il suffisso -NT / nt (trasporto speciale in ambulanza)",
     "Label for suffix f (first responder)": "Etichetta per il suffisso f (primo soccorritore)",
     "Label for suffix p (polytrauma)": "Etichetta per il suffisso p (politrauma)",
+    "Line thickness of the incident-area outline, in pixels.": "Spessore della linea del contorno dell'area dell'incidente, in pixel.",
     "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Caricato in tempo reale dalla pagina di panoramica /waip/ del server configurato: scegli Leitstelle, Kreis, Träger o Wache oppure seleziona \"Alle Wachalarme\" (ID 0) per ogni incidente. Se il server non è raggiungibile, è comunque possibile inserire manualmente un ID.",
     "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Mappa einsatz.stichwort su einsatz.beschreibung. Il confronto non distingue tra maiuscole e minuscole e tratta spazi/trattini come equivalenti (qualsiasi sequenza dell'uno o dell'altro viene ridotta a uno solo prima del confronto), quindi ad es. \"H:VU mit P\" e \"H:VU-mit-P\" corrispondono alla stessa riga - non serve una riga separata per ogni variante di scrittura. Se più righe corrispondono, il modello più specifico (più lungo) vince automaticamente: l'ordine delle righe non ha alcun effetto sulla corrispondenza, ordinala liberamente per qualsiasi colonna. Precompilato con un esempio di elenco di parole chiave per vigili del fuoco/soccorso come punto di partenza: non è confermato che corrisponda alle parole chiave effettive del tuo centro di spedizione, modifica/sostituisci secondo necessità. Per eseguire il backup o trasferire questa tabella, utilizza l'esportazione/importazione standard della configurazione dell'istanza di ioBroker (JSON). Dopo aver utilizzato quell'importazione standard, ricarica la pagina di amministrazione prima di controllare questa tabella - la finestra di configurazione aperta non la aggiorna automaticamente da un'importazione esterna (una limitazione di sincronizzazione dello stato del componente tabella di amministrazione stesso).",
     "Match": "Incontro",
     "Monitor ID": "Monitorare l'identità",
-    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.": "Livello di zoom di OpenStreetMap (1 = mondo intero, 19 = livello edificio). Valori più alti mostrano un'area più piccola con più dettagli.",
+    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.": "Livello di zoom di OpenStreetMap (1 = mondo intero, 19 = livello edificio). Valori più alti mostrano un'area più piccola con più dettagli. Questo è un valore massimo, non fisso: se l'area dell'incidente inviata dal server non entrasse completamente nell'immagine a questo livello di zoom, l'adattatore riduce automaticamente lo zoom (mai lo aumenta) quanto basta per mantenere visibile l'intera area.",
+    "Outline color": "Colore del contorno",
+    "Outline thickness (px)": "Spessore del contorno (px)",
     "Process rescue-service incidents": "Elaborare gli incidenti del servizio di soccorso",
     "Reconnect delay (s)": "Ritardo/i di riconnessione",
     "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\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "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\") - attivare solo se la propria centrale operativa utilizza effettivamente uno di questi modelli. Ha la priorità sulla tabella nella scheda Descrizioni delle parole chiave quando una parola chiave corrisponde.",
+    "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",
     "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\".",
@@ -37,7 +41,7 @@
     "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 unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.": "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. Attivato per impostazione predefinita per mantenere il comportamento precedente.",
+    "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"
 }

package/admin/i18n/nl.json

@@ -2,10 +2,11 @@
     "Alarm keyword descriptions": "Beschrijvingen van alarmtrefwoorden",
     "Automatically decode rescue-service keywords (R<RTW>N<NEF>[p][f][-NT], with or without spaces)": "Trefwoorden van de reddingsdienst automatisch decoderen (R<RTW>N<NEF>[p][f][-NT], met of zonder spaties)",
     "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, marked with a dot. The file path is written to the einsatz.kartenbildPfad state, e.g. for sending as a Pushover attachment from a Blockly/JavaScript script. Only the 10 most recent images are kept, older ones are deleted automatically. Uses the public tile.openstreetmap.org server - keep this to the intended one-image-per-incident use per the OSM Tile Usage Policy.": "Downloadt voor elk incident met geldige coördinaten OpenStreetMap-tegels en stelt een PNG samen, gecentreerd op de locatie van het incident, gemarkeerd met een stip. 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.",
+    "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",
     "Height of the generated map image in pixels.": "Hoogte van de gegenereerde kaartafbeelding in pixels.",
     "How long to wait for the server to confirm the monitor registration before logging a warning; the connection itself keeps running either way.": "Hoe lang moet worden gewacht totdat de server de monitorregistratie heeft bevestigd voordat een waarschuwing wordt geregistreerd; de verbinding zelf blijft hoe dan ook draaien.",
@@ -19,16 +20,19 @@
     "Label for suffix -NT / nt (special ambulance transport)": "Label voor achtervoegsel -NT / nt (speciaal ambulancetransport)",
     "Label for suffix f (first responder)": "Label voor achtervoegsel f (eerstehulpverlener)",
     "Label for suffix p (polytrauma)": "Label voor achtervoegsel p (polytrauma)",
+    "Line thickness of the incident-area outline, in pixels.": "Lijndikte van de incidentgebied-contour, in pixels.",
     "Loaded live from the configured server's /waip/ overview page - choose by Leitstelle, Kreis, Träger or Wache, or pick 'Alle Wachalarme' (ID 0) for every incident. If the server can't be reached, an ID can still be entered manually.": "Live geladen vanaf de /waip/ overzichtspagina van de geconfigureerde server - kies voor Leitstelle, Kreis, Träger of Wache, of kies 'Alle Wachalarme' (ID 0) voor elk incident. Als de server niet bereikbaar is, kan er alsnog handmatig een ID worden ingevoerd.",
     "Maps einsatz.stichwort to einsatz.beschreibung. Comparison is case-insensitive and treats spaces/hyphens as equivalent (any run of either collapses to one before comparing), so e.g. \"H:VU mit P\" and \"H:VU-mit-P\" match the same row - no need for a separate row per spelling. If several rows match, the most specific (longest) pattern wins automatically - row order has no effect on matching, sort by any column freely. Pre-filled with an example fire/rescue keyword list as a starting point - it is not confirmed to match your own dispatch center's actual keywords, edit/replace as needed. To back up or transfer this table, use ioBroker's standard instance configuration export/import (JSON). After using that import, reload the Admin page before checking this table - the open config dialog doesn't refresh it from an external import automatically (a state-sync limitation of the Admin table component itself).": "Kaarten einsatz.stichwort naar einsatz.beschreibung. De vergelijking is niet hoofdlettergevoelig en behandelt spaties/koppeltekens als gelijkwaardig (elke reeks van beide wordt vóór de vergelijking teruggebracht tot één spatie), zodat bijv. \"H:VU mit P\" en \"H:VU-mit-P\" dezelfde rij matchen - geen aparte rij per schrijfwijze nodig. Als meerdere rijen overeenkomen, wint het meest specifieke (langste) patroon automatisch. De rijvolgorde heeft geen invloed op het matchen, sorteer vrij op elke kolom. Vooraf ingevuld met een voorbeeldlijst met trefwoorden voor brand/redding als uitgangspunt. Er is niet bevestigd dat deze overeenkomt met de daadwerkelijke trefwoorden van uw eigen meldkamer. Bewerk/vervang indien nodig. Gebruik voor het back-uppen of overzetten van deze tabel de standaard export/import van de ioBroker-instantieconfiguratie (JSON). Herlaad na het gebruik van die standaardimport de Admin-pagina voordat u deze tabel controleert - de geopende configuratiedialoog wordt niet automatisch bijgewerkt na een externe import (een status-synchronisatiebeperking van de Admin-tabelcomponent zelf).",
     "Match": "Overeenkomst",
     "Monitor ID": "Monitor-ID",
-    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail.": "OpenStreetMap-zoomniveau (1 = hele wereld, 19 = gebouwniveau). Hogere waarden tonen een kleiner gebied in meer detail.",
+    "OpenStreetMap zoom level (1 = whole world, 19 = building level). Higher values show a smaller area in more detail. This is a maximum, not a fixed value: if the incident area sent by the server wouldn't fully fit in the image at this zoom, the adapter automatically zooms out (never in) just enough to keep the whole area visible.": "OpenStreetMap-zoomniveau (1 = hele wereld, 19 = gebouwniveau). Hogere waarden tonen een kleiner gebied in meer detail. Dit is een maximum, geen vaste waarde: als het door de server verzonden incidentgebied bij dit zoomniveau niet volledig in de afbeelding zou passen, zoomt de adapter automatisch uit (nooit in) net genoeg om het hele gebied zichtbaar te houden.",
+    "Outline color": "Contourkleur",
+    "Outline thickness (px)": "Contourdikte (px)",
     "Process rescue-service incidents": "Reddingsdienst-incidenten verwerken",
     "Reconnect delay (s)": "Vertraging(en) opnieuw verbinden",
     "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\") - only enable if your dispatch center actually uses one of these patterns. Takes priority over the table on the Keyword descriptions tab when a keyword matches.": "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\") - alleen inschakelen als uw meldkamer daadwerkelijk een van deze patronen gebruikt. Heeft voorrang op de tabel op het tabblad Trefwoordbeschrijvingen wanneer een trefwoord overeenkomt.",
+    "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",
     "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\".",
@@ -37,7 +41,7 @@
     "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 unchecked, incidents whose einsatzart identifies them as a rescue-service call (contains \"Rettung\" or \"Krankentransport\", case-insensitive) are ignored completely - no states are updated, no history entry is written, no TTS announcement is triggered. Useful because some WAIP dispatch centers only ever signal rescue-service incidents unreliably or not at all. Enabled by default to match previous behavior.": "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. Standaard ingeschakeld om het eerdere gedrag te behouden.",
+    "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"
 }