Release v1.0.1

• registrationTimeoutSec and reconnectDelaySec are now clamped in
  code to their admin UI range (1-120s), matching how every other
  numeric configuration value (e.g. historySize, mapImageWidth) was
  already handled - a direct instance config JSON edit/import can no
  longer set them outside that range.
• The stateChange listener (used only for dashboard.refreshNow) is
  now registered only while the Dashboard feature is enabled, matching
  its subscribeStates() call, instead of unconditionally in the
  constructor.
• Fixed the "Number of Installations" and "Current version in stable
  repository" badges, which pointed at the shields.io homepage instead
  of the actual iobroker.live badge images and therefore rendered as
  broken links.

Release v1.0.0

• Breaking change: the einsatz channel is renamed to einsatzAktuell
  (to distinguish it from the dashboard.einsatz1 … einsatzN dashboard
  channels), and einsatzAktuell.json.history10 is renamed to
  einsatzAktuell.json.history, now holding a configurable number of
  entries (new "Number of incidents in history" setting on the
  Connection tab, 1-100, default 10). Update any VIS
  bindings/scripts referencing the old einsatz.*/einsatz.json.history10
  paths - they are removed automatically on upgrade, along with their
  values.
• Dashboard channel/state display names no longer use "Slot" - they now
  say "Einsatz N" consistently with the einsatzAktuell.* naming, and
  the redundant "flat JSON array" phrase was removed from every state
  name. Object IDs are unaffected, only the display names shown in
  Admin/VIS.

Release v0.12.1

• Fixed the Dashboard admin config: the tab was mistranslated as "Armaturenbrett"
  (car dashboard) in German instead of "Dashboard", its help texts used
  wrong/mistranslated terms ("Versandzentrum"/"Vorfall" instead of
  "Leitstelle"/"Einsatz"), and the refresh interval label was missing its "(s)"
  unit suffix.
• Fixed routen[].lat/.lon (both einsatz.json.routen and
  dashboard.einsatzN.json.routen): previously resolved to the geometric
  bounding-box center of the entire route line - a point with no real meaning,
  since it lies "somewhere along the way" rather than at any actual location.
  Now resolves to the alerted station's own location instead (the first point of
  the route line, matching a separate coordinate-pair format the server sends
  when no route could be calculated for a station). Also fixed
  dashboard.einsatzN.json.routen specifically: it was missing the same geo
  normalization einsatz.json.routen already applied, so a route's raw,
  unresolved geometry (dozens of coordinate pairs) or the raw fallback
  coordinate field ended up in the written JSON instead of flat lat/lon.

Release v0.7.38

Also:

• add addPlaceholder to .releaseconfig.json so the WORK IN PROGRESS
  marker is restored automatically after each release (the first run
  consumed it and the next release then failed its changelog check)
• restore the CHANGELOG_OLD.md link that the changelog rotation dropped
  (E6022)
• shorten the generated 0.7.38 news entries from ~1300 to ~450 chars per
  language; the plugin copies the README changelog verbatim, which is
  too long for the admin update popup

Release v0.7.37

v0.7.37

Release v0.7.36

Merge branch 'feature/0.7.36-object-renames'

Release v0.7.35

Merge branch 'feature/0.7.35-rueckmeldung-restructure'

Release v0.7.34

Merge branch 'fix/0.7.34-mapimage-help-texts'

Release v0.7.33

Follow-up correction to the just-merged 0.7.33 admin UI reorg (not yet
tagged/pushed, so amended into the same version rather than bumping
again): Image width/height apply to the marker-dot display just as
much as to the polygon display (they set the canvas size regardless
of what gets drawn onto it), so hiding them while "Show incident-area
polygon" is off - as the first pass did - would make it impossible to
adjust image size via the Admin UI in marker mode. Moved them to sit
above the checkbox alongside Zoom level and Marker & outline color
(hidden: "!data.mapImageEnabled" only, dropping the
"|| !data.mapImageShowPolygon" clause), leaving Outline thickness as
the only field still gated on that checkbox - it's the one setting
that genuinely only affects the polygon outline (buildEinsatzMapImage
computes the marker dot's size from width/height directly, never from
mapImageOutlineThickness).

Updated their help text (new i18n key per language, old one removed -
re-verified zero missing/orphaned i18n keys programmatically) to note
they're used for both display modes. Updated both READMEs' Incident
map image section/field table and the not-yet-released 0.7.33
changelog entry/news text (both READMEs and io-package.json, all 11
languages) to describe the corrected, final field arrangement.

npm run lint: clean. npm run test:package: 57/57 passing.

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01FSLJEYeTD4fqt8kQDtTtgL

Release v0.7.31

Merge branch 'feature/0.7.31-map-timeout'