iobroker.kanban 0.3.2 → 0.3.3

package/README.md

@@ -13,6 +13,8 @@ Kanban board adapter for ioBroker with its **own web server**, live sync, webhoo
 
 **Full documentation:** [English](docs/en/README.md) · [Deutsch](docs/de/README.md)
 
+**Questions, ideas, bug reports:** [GitHub issues](https://github.com/bmueller77/ioBroker.kanban/issues), or the ioBroker forum threads [Kanban board (English)](https://forum.iobroker.net/topic/85031/new-adapter-kanban-board) and [KanBan-Board (deutsch)](https://forum.iobroker.net/topic/85030/test-kanban-board).
+
 ## Installation
 
 Install the adapter from the ioBroker admin: *Adapters* → filter for `kanban` → install. Then create an instance `kanban.0` and open the web UI at `http://<host>:8095/`.
@@ -122,16 +124,22 @@ Details: [Security & access control](docs/en/README.md#security--access-control)
 
 <!-- Der Platzhalter bleibt stehen. release-script trägt hier die
      nächste Version ein und ersetzt die Überschrift. -->
+### 0.3.3 (2026-09-21)
+* (bmueller77) **Everything the adapter says is in English now.** Thirty-five error messages were German, from `title fehlt` to `Karte '…' existiert nicht`. They reach users in the log, as REST responses and as the answer to a `sendTo` call, so a German message left half the ioBroker world guessing. Cron messages are included
+* (bmueller77) **Five state names were German** and are English now: `Card count`, `Overdue cards`, `Overdue cards (list)` and `Assigned open cards`. Since these objects are created only when they are missing, a new name never reached an existing installation. The adapter now corrects the names of its own objects once at startup, so boards that have been running for months are renamed as well
+* (bmueller77) The HTTP status code of the REST API no longer depends on the wording of an error. It used to test the message for the German `existiert nicht` to decide between 404 and 400, which would have broken silently with the translation. An error that stands for something missing now carries its status itself
+* (bmueller77) `reminderDaysBefore` is held to the range 0 to 30 in the code as well, not only in the settings dialog. The configuration can be edited by hand, and a value far outside that range moved the reminder threshold somewhere nobody would find
+
 ### 0.3.2 (2026-09-10)
 * (bmueller77) **The trash has the sort toggle now**, like every other column. The default stays deletion time, oldest first, so whatever is closest to being removed for good sits on top; sorting by due date, priority or age is available all the same. The broom moved to the left of the toggle so that the sorting sits in the same place in every column
-* (bmueller77) Fix: the **focus ring** took the accent colour unchanged. That works in the light theme; in the dark one the same dark tone stood against dark surfaces, measured down to 1.52:1 on a card in the trash, against the 3:1 that is required. The ring colour is computed now: lightened or darkened from the accent colour in five percent steps, only as far as it takes to clear every surface it lands on, so the instance keeps its colour family
-* (bmueller77) Fix: below 600 px the card editor, the board manager and the views dialog were 32 px narrower and 48 px shorter than the screen and sat pinned to the top left. Their rules hang on their IDs and beat the element rule in the mobile block
+* (bmueller77) Fix: the **focus ring** took the accent colour unchanged. That works in the light theme; in the dark one the same dark tone stood against dark surfaces and was barely visible. The ring colour is computed now: lightened or darkened from the accent colour, only as far as it takes to stand out against every surface it lands on, so the instance keeps its colour family
+* (bmueller77) Fix: below 600 px the card editor, the board manager and the views dialog did not fill the screen and sat pinned to the top left. Their rules hang on their IDs and beat the element rule in the mobile block
 * (bmueller77) Fix: in the same block the tab panel was squashed as a flex child while its content visibly ran out of it. The scroll area did not count the overflowing pixels, and on a short window **Save scrolled out of sight entirely** - anyone who did not think to scroll back lost their input
-* (bmueller77) Fix: the text colour on avatars and chips hung on a fixed brightness threshold of 0.31. The point where black and white give the same contrast is 0.179, and in between the choice came out systematically wrong: on turquoise, white scored 3.0:1 where black would have reached 7.0:1. The calculation itself now stands there instead of a number
+* (bmueller77) Fix: the text colour on avatars and chips hung on a fixed brightness threshold, and around that threshold the choice came out wrong - on turquoise it picked white where black is the more legible of the two. It now compares both and takes the better one
 * (bmueller77) Fix: the **browser's back button** closed the card editor without a word, while Escape and the close cross ask first. The open dialog now adds a history entry; the back button takes it away and raises the same prompt
 * (bmueller77) Fix: if someone changed the same card in another window, the open editor did not notice and **overwrote it silently on save**. It now compares the state it opened with against the current one and asks when they differ. Only the fields the editor edits are compared, so a column change or a fresh completion timestamp does not raise the prompt
-* (bmueller77) **Hit areas below 24 px**: the eye and the broom in the column header measured 22 x 18, the drag handles in the settings 18 x 18, the "+X more" row was 20 px high. All four are on 24 px now, per WCAG 2.5.8. It weighs more on the broom than elsewhere, since an irreversible action sits behind it
-* (bmueller77) Fix: the sort menu carried no roles, the tooltip on a completed card was the only single-line one, a badge without a warning colour stood at 1.21:1 against the white card and now carries a hairline, the disabled menu entry kept the pointing hand, the triangle was lost on a coloured badge, the focus landed on `body` after toggling "+X more", and in drag-handle mode the whole card carried the grab cursor while dragging only starts at the handle
+* (bmueller77) The eye and the broom in the column header, the drag handles in the settings and the "+X more" row were too small to hit reliably, on a touchscreen in particular. All four are bigger now. It weighs more on the broom than elsewhere, since an irreversible action sits behind it
+* (bmueller77) Fix: the sort menu carried no roles, the tooltip on a completed card was the only single-line one, a badge without a warning colour was hard to make out against the white card and now carries a hairline, the disabled menu entry kept the pointing hand, the triangle was lost on a coloured badge, the focus landed on `body` after toggling "+X more", and in drag-handle mode the whole card carried the grab cursor while dragging only starts at the handle
 * (bmueller77) Fix: the explanatory line in the due-date tooltip told the timeline backwards. It runs from yellow to red now, in eleven languages
 * (bmueller77) Fix: the heading above the label switch always read "hide labels", even when it was set to "show only these labels". Fix: the prompt for removing a board member counted the cards correctly but named every future non-member instead of the people actually on those cards
 * (bmueller77) Fix: the subject "card deleted" stood for a move to the trash. The checkbox says "to the trash" and so does the confirmation dialog, only the mail did not. Corrected in eleven languages
@@ -139,21 +147,21 @@ Details: [Security & access control](docs/en/README.md#security--access-control)
 * (bmueller77) **Only IDs that something hangs on are frozen now.** Until now the adapter wrote the marker back for every user on the first start, and every such write restarts the instance - exactly the window in which saving in the admin was lost, reproduced twice, without a message and without a log entry. It hit the setup, the moment when someone sets the port, saves, enters users, saves. A fresh instance with users but no cards no longer writes its configuration back at all
 * (bmueller77) Fix: creating a card fired "card created" and "card assigned", and **both attached the `.ics`** although the manual says the invite comes once. The notifier remembers the dispatch itself now
 * (bmueller77) **Deleting a card sends a cancellation**: an `.ics` with `METHOD:CANCEL`, the same `UID` and the next sequence number, so the calendar clears the entry instead of leaving the appointment standing. Only where an invite was ever sent
-* (bmueller77) The **add button** at the foot of a column is narrower. At 25 percent column width it covered 111 of 423 px and caught the clicks on two rows of an expanded checklist. A "+" does not need that width
+* (bmueller77) The **add button** at the foot of a column is narrower. It used to span a good quarter of the column and caught the clicks on the rows of an expanded checklist below it. A "+" does not need that width
 * (bmueller77) **No cards are created in a done column any more.** A card created there carried no `doneAt` and therefore dropped out of three documented features: the "age in column" sort, the display limit for done cards and the automatic cleanup. It stayed there forever without anyone seeing why. The store refuses it and the UI does not offer it: the card editor leaves done columns out when creating and copying, the transfer dialog likewise, and there is no "+" at the foot of such a column. Moving and editing an existing card keeps the column selectable
 * (bmueller77) Fix: `doneAt` was cleared when a card moved to the trash, so restoring it lost the completion time. Fix: labels created through the interface were all green and now take their colour in turn from the same palette as the UI. Fix: the mirror states of deleted users stayed behind under `users.*`, so a dashboard reading `assignedCount` kept counting people too many. Fix: the "+" at the foot of a column was not blocked when no user existed - only the header button had been secured, the dead end was still reachable by the other route
 * (bmueller77) **Error messages no longer arrive as a browser box.** All eight `alert()` calls go through the in-page hint now: a red border, `role=alert`, and they stay until someone closes them. A modal box halts the page until it is clicked away and is unreadable to any automated check - two testers could only report that the renderer refused scripts and had to leave the wording open
-* (bmueller77) Fix: on a board without columns "+ Card" stayed active, the editor opened, the column field was empty, and only saving ran into the error. Fix: the menus in the column header hang off `body`, so a deleted column left its menu standing and operable. Fix: with fifteen users the chip bar was 1750 px long and pushed the whole page out of a 1584 px window; it wraps now. Fix: markdown tables in the description and the reading window had neither borders nor padding
+* (bmueller77) Fix: on a board without columns "+ Card" stayed active, the editor opened, the column field was empty, and only saving ran into the error. Fix: the menus in the column header hang off `body`, so a deleted column left its menu standing and operable. Fix: with fifteen users the chip bar grew wider than the window and pushed the whole page out of view; it wraps now. Fix: markdown tables in the description and the reading window had neither borders nor padding
 * (bmueller77) The socket around the sticky add button is one pixel wide instead of seven. It only shows when the button floats over a card, and then as a heavy frame
 * (bmueller77) Fix: a saved card that the active filter hides straight away **disappeared without a word**. A tester created six cards and thought saving was broken until the network response 201 told him otherwise. After saving, the board is checked for the card and the UI says so when it is not there
 * (bmueller77) Fix: from the sixth column on, "+ Add column" sat on the edge of the scroll area, half cut off and without effect, and the input that followed was lost. Fix: the recurrence prefilled day and month with today's date even when the card carried a due date. Fix: the remembered expanded state silently overruled a freshly set display limit, so "Max 3" showed seven cards and looked broken. Fix: the board picker still showed the old name after renaming
-* (bmueller77) Fix: the "duration" field took the whole width next to the checkbox, measured 850 px for a value like `01:00`. Fix: the summary of a collapsed section showed raw markdown for the description and only the host for the link, so two cards with different files on the same server looked identical. Fix: the label summary carried no colour dots although the manual describes them. Fix: the interface error texts wrote "zustaendige" without the umlaut
+* (bmueller77) Fix: the "duration" field took the whole width next to the checkbox, for a value like `01:00`. Fix: the summary of a collapsed section showed raw markdown for the description and only the host for the link, so two cards with different files on the same server looked identical. Fix: the label summary carried no colour dots although the manual describes them. Fix: the interface error texts wrote "zustaendige" without the umlaut
 * (bmueller77) Fix: with the WIP limit exceeded and a filter active, the column header read "2/5" in red - the filtered figure before the slash, the colour from the unfiltered one. The column's own figure stands there now, and the tooltip still names how many the filter shows. The rule sat in the middle of the rendering and had been wrong twice for that reason; it lives in `totalLabel()` with five tests beside it
 * (bmueller77) Fix: the plural form still read "card(s)", "tarjeta(s)" in the prompt for removing a board member. Written out in all eleven languages now. Fix: "+ New" in the card editor always assigned green - the palette had only reached the board manager
 * (bmueller77) **A fresh instance no longer ships with two example users.** Since the adapter freezes user IDs, the presets were permanently called "user1" and "user2" and could only be deleted, not renamed, so the first thing to do on a new instance was to throw away two users whose names must not be touched. "+ Card" explains by itself that a user is missing first
 * (bmueller77) Fix: a recurring card left lying for several intervals produced a follow-up card **dated in the past**. Due 28.08., interval 7, completed 07.09. gave 04.09. The calculation now starts from the later of due date and today. Finishing early keeps the calendar as the reference, otherwise the grid would creep forward with every early tick
 * (bmueller77) Fix: without a single user the card editor opened and saving failed on a condition nobody could meet there. Fix: the reason on the blocked "+ Card" never appeared, because Chrome delivers no mouse events on disabled buttons. It uses `aria-disabled` now, so the click is caught and says what is missing
-* (bmueller77) Fix: the column count and the sort button in the column header measured 46x18 and 22x18 px and are on 24 px minimum height now. Fix: "+X more" hung on the column while the add button hung in the card list, so the hint sat below the add button with 40 px to the last card instead of 8, and 4 px further left than the cards
+* (bmueller77) Fix: the column count and the sort button in the column header were too small to hit reliably and are bigger now. Fix: "+X more" hung on the column while the add button hung in the card list, so the hint sat below the add button, set off from the cards and not lined up with them
 * (bmueller77) Fix: `info.orphanedAssignees` was only written on start, so a repair or a restore from the trash left the state stale until the next start. Fix: `info.frozenUserIds` only ever grew, so a user created later with the same ID would have found the field locked from the outset. Fix: `info.apiSecret` was created on fresh instances after all, although the manual has said the opposite since 0.3.0
 * (bmueller77) Fix: "setInterval called, but adapter is shutting down" did not come from a normal restart but from saving the settings: the host stops the instance mid-start while the start is still creating timers. Server, scheduler and the delayed write ask first now
 * (bmueller77) Fix: "2 Karte(n)" in the prompt for removing a board member. Fix: the tooltip on the due date named only the state; the scale stands below it now. Fix: after "+ Add column" and "+ Add label" the focus stayed on the link. Fix: the links in the rendered markdown preview sat in the tab order although it is display only
@@ -177,12 +185,12 @@ Details: [Security & access control](docs/en/README.md#security--access-control)
 * (bmueller77) Fix: an unusable date format was accepted without checking and then printed on every card verbatim. A format without a day, month or year token is discarded with a warning in the log
 * (bmueller77) Fix: Enter inside the checklist saved the whole card and closed the dialog. It creates the next item now; Ctrl and Enter saves from there
 * (bmueller77) Fix: selection and keyboard focus looked identical on the chips, both a two-pixel ring in the accent colour. The focus ring is dashed now
-* (bmueller77) Fix: white on the orange due badge reached 3.08:1, below the 4.5:1 of WCAG AA. The orange is darker (4.59:1). Red as a text colour on a dark surface reached 3.14:1 and now uses a lighter tone through `--danger-fg` (6.85:1)
+* (bmueller77) Fix: white on the orange due badge was hard to read, so the orange is darker now. Red as a text colour on a dark surface got a lighter tone through `--danger-fg`
 * (bmueller77) Fix: the sticky add-card button sat on top of card titles and labels while scrolling. It has an opaque pad in the column colour now
-* (bmueller77) Fix: below 600 px the board row in the settings stretched the board picker and the name field to 140 px, because the column direction turned a `flex-basis` meant as width into a height
-* (bmueller77) The due-date badge has a tooltip naming its state, since a colour on its own does not say whether it is worse than the one beside it. New labels take their colour from a palette in rotation. The pencil and the other card icons have a 24 px hit area. "+ Card" is disabled while no board exists, and the filter button that has been dead since 0.3.0 is gone
+* (bmueller77) Fix: below 600 px the board row in the settings stretched the board picker and the name field far beyond their content, because the column direction turned a `flex-basis` meant as width into a height
+* (bmueller77) The due-date badge has a tooltip naming its state, since a colour on its own does not say whether it is worse than the one beside it. New labels take their colour from a palette in rotation. The pencil and the other card icons are easier to hit. "+ Card" is disabled while no board exists, and the filter button that has been dead since 0.3.0 is gone
 * (bmueller77) **With exactly one user, assignment disappears** (#35). No chips in the header, no avatars on the cards, no assignees field in the editor, no user picker in the views dialog: with one person there is nothing to choose and nothing to filter. The API fills the field in instead of answering `400`, so a script does not fail on a question that answers itself. A card carrying an ID that no longer exists keeps it rather than being silently moved. Adding a second user brings all of it back
-* (bmueller77) The copy button on a done card is `mdi:content-copy` now, two offset sheets (#33). It used to be a sheet with a circular arrow, which at 14 px looked like the recurrence icon sitting on the same card, so people read the copy button as a recurrence marker that had moved. The recurrence icon itself never moved. The documentation gained a table listing every icon that can appear on a card
+* (bmueller77) The copy button on a done card is `mdi:content-copy` now, two offset sheets (#33). It used to be a sheet with a circular arrow, which at that size looked like the recurrence icon sitting on the same card, so people read the copy button as a recurrence marker that had moved. The recurrence icon itself never moved. The documentation gained a table listing every icon that can appear on a card
 * (bmueller77) Labels keep one order everywhere (#32). A card used to list them in the order they had been clicked in the editor, so two cards carrying the same labels looked different. Card, picker and section summary now all follow the order of the board, and that order can be dragged by a handle in the board settings, the same way the columns already worked
 * (bmueller77) Fix: `overdueCount` and `overdueList` ignored the time of day (#31). A card due today at 09:00 turned red in the board at 09:01, while the states kept their old value until midnight, because the counters compared dates only. One function now decides it for the states, the `cardDue` event and the colour alike
 * (bmueller77) **The column header can show more than the card count.** Clicking the number opens a menu with four checkmarks: total, tomorrow, today, overdue. Each ticked entry gets its own badge next to the others, in the same colours the due-date badges use on the cards and following the same arithmetic, lead time and time of day included. The choice is stored per column and per device, like the sort mode. Done columns and the trash have no menu, since every card there counts as completed

package/io-package.json

@@ -1,7 +1,7 @@
 {
   "common": {
     "name": "kanban",
-    "version": "0.3.2",
+    "version": "0.3.3",
     "titleLang": {
       "en": "Kanban Board",
       "de": "Kanban Board",
@@ -74,6 +74,19 @@
       "license": "MIT"
     },
     "news": {
+      "0.3.3": {
+        "de": "- Alle Meldungen des Adapters sind jetzt auf Englisch\n- Fünf Zustandsnamen waren deutsch und heißen jetzt \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" und \"Assigned open cards\"; bestehende Installationen werden beim Start umbenannt\n- Der HTTP-Statuscode der REST-Schnittstelle hängt nicht mehr am Wortlaut der Fehlermeldung\n- \"reminderDaysBefore\" wird auch im Code auf 0 bis 30 begrenzt",
+        "en": "- Every message the adapter produces is in English now\n- Five state names were German and are now \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" and \"Assigned open cards\"; existing installations are renamed at startup\n- The HTTP status code of the REST API no longer depends on the wording of the error message\n- \"reminderDaysBefore\" is held to the range 0 to 30 in the code as well",
+        "ru": "- Все сообщения адаптера теперь на английском языке\n- Пять имён состояний были на немецком, теперь это \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" и \"Assigned open cards\"; существующие установки переименовываются при запуске\n- Код состояния HTTP в REST-интерфейсе больше не зависит от формулировки сообщения об ошибке\n- \"reminderDaysBefore\" ограничивается диапазоном от 0 до 30 и в коде",
+        "pt": "- Todas as mensagens do adaptador estão agora em inglês\n- Cinco nomes de estados estavam em alemão e são agora \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" e \"Assigned open cards\"; as instalações existentes são renomeadas no arranque\n- O código de estado HTTP da API REST já não depende da redação da mensagem de erro\n- \"reminderDaysBefore\" é limitado ao intervalo de 0 a 30 também no código",
+        "nl": "- Alle meldingen van de adapter zijn nu in het Engels\n- Vijf toestandsnamen waren Duits en heten nu \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" en \"Assigned open cards\"; bestaande installaties worden bij het starten hernoemd\n- De HTTP-statuscode van de REST-API hangt niet meer af van de formulering van de foutmelding\n- \"reminderDaysBefore\" wordt ook in de code begrensd op 0 tot 30",
+        "fr": "- Tous les messages de l'adaptateur sont désormais en anglais\n- Cinq noms d'états étaient en allemand et s'appellent maintenant \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" et \"Assigned open cards\" ; les installations existantes sont renommées au démarrage\n- Le code de statut HTTP de l'API REST ne dépend plus de la formulation du message d'erreur\n- \"reminderDaysBefore\" est limité à la plage de 0 à 30 également dans le code",
+        "it": "- Tutti i messaggi dell'adattatore sono ora in inglese\n- Cinque nomi di stato erano in tedesco e ora sono \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" e \"Assigned open cards\"; le installazioni esistenti vengono rinominate all'avvio\n- Il codice di stato HTTP dell'API REST non dipende più dal testo del messaggio di errore\n- \"reminderDaysBefore\" è limitato all'intervallo da 0 a 30 anche nel codice",
+        "es": "- Todos los mensajes del adaptador están ahora en inglés\n- Cinco nombres de estados estaban en alemán y ahora son \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" y \"Assigned open cards\"; las instalaciones existentes se renombran al iniciar\n- El código de estado HTTP de la API REST ya no depende de la redacción del mensaje de error\n- \"reminderDaysBefore\" se limita al rango de 0 a 30 también en el código",
+        "pl": "- Wszystkie komunikaty adaptera są teraz w języku angielskim\n- Pięć nazw stanów było po niemiecku, teraz to \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" i \"Assigned open cards\"; istniejące instalacje są zmieniane przy starcie\n- Kod stanu HTTP interfejsu REST nie zależy już od treści komunikatu o błędzie\n- \"reminderDaysBefore\" jest ograniczany do zakresu od 0 do 30 również w kodzie",
+        "uk": "- Усі повідомлення адаптера тепер англійською мовою\n- П'ять імен станів були німецькими, тепер це \"Card count\", \"Overdue cards\", \"Overdue cards (list)\" та \"Assigned open cards\"; наявні встановлення перейменовуються під час запуску\n- Код стану HTTP інтерфейсу REST більше не залежить від формулювання повідомлення про помилку\n- \"reminderDaysBefore\" обмежується діапазоном від 0 до 30 і в коді",
+        "zh-cn": "- 适配器的所有消息现在均为英文\n- 五个状态名称原为德语，现为 \"Card count\"、\"Overdue cards\"、\"Overdue cards (list)\" 和 \"Assigned open cards\"；现有安装在启动时会被重命名\n- REST 接口的 HTTP 状态码不再取决于错误消息的措辞\n- \"reminderDaysBefore\" 在代码中同样被限制在 0 到 30 之间"
+      },
       "0.3.2": {
         "de": "- Zahlen im Spaltenkopf umschaltbar: Gesamt, Morgen, Heute, Ueberfaellig\n- Aufklappbare Abschnitte im Karteneditor mit Zusammenfassung in der Kopfzeile\n- Benutzer-IDs werden gesperrt, sobald eine Karte oder ein Avatarbild daran haengt; verwaiste Zustaendige lassen sich in der Oberflaeche reparieren\n- Neue Wiederholungsart \"Alle X Tage (nach Erledigung des Vorgaengers)\"\n- Gelb heisst jetzt genau der naechste Kalendertag; die Vorlaufzeit steuert nur noch die Erinnerungsmail\n- In Erledigt-Spalten entstehen keine Karten mehr\n- Beim Loeschen einer Karte mit Einladung geht eine Kalender-Absage raus\n- Der Papierkorb hat denselben Sortier-Umschalter wie jede andere Spalte\n- Frische Instanzen bringen keine Beispielbenutzer mehr mit\n- Dazu rund siebzig Korrekturen aus acht Testpaketen",
         "en": "- Switchable counts in the column header: total, tomorrow, today, overdue\n- Collapsible sections in the card editor, each summarised in its header\n- User IDs are frozen once a card or an avatar hangs on them; orphaned assignees can be repaired in the UI\n- New recurrence kind \"every X days (after the previous one is done)\"\n- Yellow now means exactly the next calendar day; the lead time only drives the reminder mail\n- No cards are created in done columns any more\n- Deleting a card with an invite sends a calendar cancellation\n- The trash has the same sort toggle as every other column\n- Fresh instances no longer ship with example users\n- Plus around seventy fixes from eight test packages",

package/lib/cron.js

@@ -76,7 +76,7 @@ function parseField(raw, field) {
         if (stepPart !== undefined) {
             step = Number(stepPart);
             if (!Number.isInteger(step) || step < 1) {
-                throw new Error(`${field.name}: ungültige Schrittweite '${stepPart}'`);
+                throw new Error(`${field.name}: invalid step '${stepPart}'`);
             }
         }
 
@@ -104,10 +104,10 @@ function parseField(raw, field) {
         }
 
         if (!Number.isInteger(from) || !Number.isInteger(to)) {
-            throw new Error(`${field.name}: '${piece}' ist keine gültige Angabe`);
+            throw new Error(`${field.name}: '${piece}' is not a valid entry`);
         }
         if (from < field.min || to > field.max || from > to) {
-            throw new Error(`${field.name}: '${piece}' liegt außerhalb von ${field.min}-${field.max}`);
+            throw new Error(`${field.name}: '${piece}' is outside ${field.min}-${field.max}`);
         }
         for (let v = from; v <= to; v += step) {
             out.add(v);
@@ -137,7 +137,7 @@ function parseCron(expr) {
     // Ausdruck ueber die token-freie Pruefroute den Event-Loop fuer Sekunden.
     // Das laengste sinnvolle Muster (alle Monatsnamen) bleibt weit darunter.
     if (raw.length > MAX_EXPR_LENGTH) {
-        throw new Error(`Ausdruck zu lang (höchstens ${MAX_EXPR_LENGTH} Zeichen)`);
+        throw new Error(`expression too long (at most ${MAX_EXPR_LENGTH} characters)`);
     }
     const parts = raw.split(/\s+/);
     if (parts.length !== 5) {

package/lib/scheduler.js

@@ -146,7 +146,10 @@ class Scheduler {
                 return;
             }
         }
-        const daysBefore = Number(cfg.reminderDaysBefore) || 0;
+        // Die Grenze 0..30 steht in der jsonConfig, aber die Konfiguration laesst
+        // sich von Hand aendern. Ein absurder Wert verschoebe die Schwelle ins
+        // Nirgendwo, und niemand saehe den Grund.
+        const daysBefore = Math.min(Math.max(Math.floor(Number(cfg.reminderDaysBefore) || 0), 0), 30);
         const threshold = new Date();
         threshold.setDate(threshold.getDate() + daysBefore);
         const thresholdStr = `${threshold.getFullYear()}-${String(threshold.getMonth() + 1).padStart(2, '0')}-${String(threshold.getDate()).padStart(2, '0')}`;

package/lib/server.js

@@ -342,7 +342,7 @@ class Server {
     _apiRoutes(app) {
         const wrap = fn => (req, res) => {
             Promise.resolve(fn(req, res)).catch(e => {
-                const code = /existiert nicht/.test(e.message) ? 404 : 400;
+                const code = Number(e.status) || 400;
                 res.status(code).json({ error: e.message });
             });
         };
@@ -359,7 +359,7 @@ class Server {
                     timeFormat: cfg.timeFormat || '24h',
                     // Die Oberflaeche faerbt das Vorwarnfenster damit ein, damit
                     // Farbe und Erinnerungsmail dieselbe Aussage treffen
-                    reminderDaysBefore: Number(cfg.reminderDaysBefore) || 0,
+                    reminderDaysBefore: Math.min(Math.max(Math.floor(Number(cfg.reminderDaysBefore) || 0), 0), 30),
                     language: this.adapter._language || 'en',
                     trashRetentionDays: TRASH_RETENTION_DAYS,
                 });
@@ -770,7 +770,7 @@ class Server {
 
         const wrap = fn => (req, res) => {
             Promise.resolve(fn(req, res)).catch(e => {
-                const code = /existiert nicht/.test(e.message) ? 404 : 400;
+                const code = Number(e.status) || 400;
                 res.status(code).json({ error: e.message });
             });
         };

package/lib/store.js

@@ -355,7 +355,7 @@ function assertDate(v, field) {
     }
     const s = String(v);
     if (!DATE_RE.test(s)) {
-        throw new Error(`${field} muss im Format YYYY-MM-DD vorliegen, nicht '${s}'`);
+        throw new Error(`${field} must be in YYYY-MM-DD format, not '${s}'`);
     }
     return s;
 }
@@ -365,7 +365,7 @@ function assertTime(v, field) {
     }
     const s = String(v);
     if (!TIME_RE.test(s)) {
-        throw new Error(`${field} muss im Format HH:MM vorliegen, nicht '${s}'`);
+        throw new Error(`${field} must be in HH:MM format, not '${s}'`);
     }
     return s;
 }
@@ -385,17 +385,32 @@ function assertRecurrence(rec) {
     }
     const check = validateCron(rec.cron);
     if (!check.ok) {
-        throw new Error(`Cron-Ausdruck ungültig: ${check.error}`);
+        throw new Error(`Invalid cron expression: ${check.error}`);
     }
     return check.time;
 }
+/**
+ * Fehler mit HTTP-Statuscode. Der REST-Aufsatz hat den Code bisher aus dem Text
+ *  der Meldung geraten (/existiert nicht/). Das haette die Uebersetzung ins
+ *  Englische stillschweigend gebrochen und war ohnehin die falsche Ebene: Ob
+ *  etwas nicht existiert, weiss die Datenhaltung, nicht der Aufsatz.
+ *
+ * @param message Meldung in englischer Sprache
+ * @returns Error mit gesetztem status 404
+ */
+function notFound(message) {
+    const e = new Error(message);
+    e.status = 404;
+    return e;
+}
+
 function assertPriority(v) {
     if (v === undefined || v === null || v === '') {
         return 0;
     }
     const n = Number(v);
     if (!Number.isInteger(n) || n < 0 || n > 2) {
-        throw new Error(`priority kennt nur 0, 1 oder 2, nicht '${v}'`);
+        throw new Error(`priority accepts only 0, 1 or 2, not '${v}'`);
     }
     return n;
 }
@@ -553,7 +568,7 @@ class Store {
     _requireBoard(id) {
         const b = this.boards.get(id);
         if (!b) {
-            throw new Error(`Board '${id}' existiert nicht`);
+            throw notFound(`board '${id}' does not exist`);
         }
         return b;
     }
@@ -588,7 +603,7 @@ class Store {
 
     async createBoard({ id, title }) {
         if (!title) {
-            throw new Error('title fehlt');
+            throw new Error('title is missing');
         }
         let boardId = slugify(id || title);
         let n = 2;
@@ -733,17 +748,17 @@ class Store {
     addCard(boardId, data, source) {
         const board = this._requireBoard(boardId);
         if (!data || !data.title) {
-            throw new Error('title fehlt');
+            throw new Error('title is missing');
         }
         const firstNormal = board.columns.find(c => !c.isTrash);
         // Eine angegebene, aber unbekannte Spalte ist ein Fehler des Aufrufers — die
         // Karte still in der ersten Spalte abzulegen verschleiert das nur.
         if (data.columnId && !board.columns.some(c => c.id === data.columnId && !c.isTrash)) {
-            throw new Error(`Spalte '${data.columnId}' existiert nicht in Board '${boardId}'`);
+            throw notFound(`column '${data.columnId}' does not exist in board '${boardId}'`);
         }
         const columnId = data.columnId || (firstNormal && firstNormal.id);
         if (!columnId) {
-            throw new Error('Board hat keine Spalten');
+            throw new Error('board has no columns');
         }
         // In einer Erledigt-Spalte wird nichts angelegt. Karten wandern dorthin,
         // sie entstehen dort nicht: Was dort neu auftauchte, trug kein doneAt,
@@ -752,8 +767,8 @@ class Store {
         // immer liegen, ohne dass jemand den Grund sah (D2, E12).
         if (this._isDoneColumn(board, columnId)) {
             throw new Error(
-                'Karten werden nicht in einer Erledigt-Spalte angelegt. ' +
-                    'Lege sie in einer offenen Spalte an und verschiebe sie danach.',
+                'cards are not created in a done column. ' +
+                    'Create the card in an open column and move it there afterwards.',
             );
         }
         const due = assertDate(data.due, 'due');
@@ -812,7 +827,7 @@ class Store {
         const board = this._requireBoard(boardId);
         const card = board.cards.find(c => c.id === cardId);
         if (!card) {
-            throw new Error(`Karte '${cardId}' existiert nicht`);
+            throw notFound(`card '${cardId}' does not exist`);
         }
         const oldAssignees = new Set(card.assignees);
         const oldDueAt = `${card.due || ''} ${card.dueTime || ''}`;
@@ -878,10 +893,10 @@ class Store {
         const board = this._requireBoard(boardId);
         const card = board.cards.find(c => c.id === cardId);
         if (!card) {
-            throw new Error(`Karte '${cardId}' existiert nicht`);
+            throw notFound(`card '${cardId}' does not exist`);
         }
         if (!board.columns.some(c => c.id === columnId)) {
-            throw new Error(`Spalte '${columnId}' existiert nicht`);
+            throw notFound(`column '${columnId}' does not exist`);
         }
         const fromColumn = card.columnId;
         const wasDone = this._isDoneColumn(board, fromColumn);
@@ -1108,7 +1123,7 @@ class Store {
         const board = this._requireBoard(boardId);
         const card = board.cards.find(c => c.id === cardId);
         if (!card) {
-            throw new Error(`Karte '${cardId}' existiert nicht`);
+            throw notFound(`card '${cardId}' does not exist`);
         }
         const trash = this._ensureTrashColumn(board);
         const fromColumn = card.columnId;
@@ -1151,13 +1166,13 @@ class Store {
         }
         const idx = board.cards.findIndex(c => c.id === cardId);
         if (idx === -1) {
-            throw new Error(`Karte '${cardId}' existiert nicht`);
+            throw notFound(`card '${cardId}' does not exist`);
         }
         // Nur aus dem Papierkorb: Sonst entfernt ein einzelner Aufruf eine aktive
         // Karte unwiederbringlich und umgeht die Aufbewahrungsfrist. Der Aufraeumlauf
         // und "Papierkorb leeren" gehen ohnehin ueber eigene Wege.
         if (!opts.auto && !this._isTrashColumn(board, board.cards[idx].columnId)) {
-            throw new Error(`Karte '${cardId}' liegt nicht im Papierkorb`);
+            throw new Error(`card '${cardId}' is not in the trash`);
         }
         const [card] = board.cards.splice(idx, 1);
         const col = card.columnId;
@@ -1184,7 +1199,7 @@ class Store {
         const board = this._requireBoard(boardId);
         const card = board.cards.find(c => c.id === cardId);
         if (!card) {
-            throw new Error(`Karte '${cardId}' existiert nicht`);
+            throw notFound(`card '${cardId}' does not exist`);
         }
         if (!this._isTrashColumn(board, card.columnId)) {
             return card;
@@ -1194,7 +1209,7 @@ class Store {
             target = board.columns.find(c => !c.isTrash && !c.isDone) || board.columns.find(c => !c.isTrash);
         }
         if (!target) {
-            throw new Error('Keine Zielspalte für die Wiederherstellung');
+            throw new Error('no target column for the restore');
         }
         const fromColumn = card.columnId;
         this._mutate(board, b => {
@@ -1361,18 +1376,18 @@ class Store {
         // eines Boards passiert per Drag & Drop bzw. über die Spaltenauswahl.
         const sameBoard = fromBoardId === toBoardId;
         if (sameBoard && mode !== 'copy') {
-            throw new Error('Quell- und Ziel-Board sind identisch');
+            throw new Error('source and target board are identical');
         }
         const card = from.cards.find(c => c.id === cardId);
         if (!card) {
-            throw new Error(`Karte '${cardId}' existiert nicht`);
+            throw notFound(`card '${cardId}' does not exist`);
         }
         let target = toColumnId && to.columns.find(c => c.id === toColumnId && !c.isTrash);
         if (!target) {
             target = to.columns.find(c => c.allowAdd && !c.isTrash) || to.columns.find(c => !c.isTrash);
         }
         if (!target) {
-            throw new Error('Ziel-Board hat keine Spalte');
+            throw new Error('target board has no column');
         }
         // Labels über den Namen abgleichen
         const labelName = l =>
@@ -1399,7 +1414,7 @@ class Store {
             assignees = overrides.assignees.filter(a => members.has(a));
         }
         if (!assignees.length) {
-            throw new Error('Ziel-Board: mindestens eine zuständige Person (Mitglied) nötig');
+            throw new Error('target board: at least one assignee who is a member is required');
         }
         const isDone = !!target.isDone;
         const nowIso = new Date().toISOString();
@@ -1576,6 +1591,51 @@ class Store {
         }
     }
 
+    /**
+     * Zustandsnamen aus alten Installationen nachziehen.
+     *
+     * Die Objekte entstehen ueber setObjectNotExistsAsync. Ein geaenderter Name im
+     *  Code erreicht ein bestehendes Objekt deshalb nie: Auf einer Instanz, die es
+     *  vor 0.3.3 schon gab, stuenden weiter die deutschen Namen, und genau die
+     *  landen im Objekt-Dump. Der Durchlauf laeuft einmal je Start ueber die
+     *  eigenen Objekte und kostet einen Lesezugriff.
+     *
+     * @returns Anzahl der umbenannten Objekte
+     */
+    async migrateStateNames() {
+        const NEUE_NAMEN = {
+            'Anzahl Karten': 'Card count',
+            'Überfällige Karten': 'Overdue cards',
+            'Überfällige Karten (Liste)': 'Overdue cards (list)',
+            'Zugewiesene offene Karten': 'Assigned open cards',
+        };
+        let geaendert = 0;
+        let objekte = null;
+        try {
+            objekte = await this.adapter.getAdapterObjectsAsync();
+        } catch (e) {
+            this.adapter.log.warn(`state name migration skipped: ${e.message}`);
+            return 0;
+        }
+        for (const [id, obj] of Object.entries(objekte || {})) {
+            const name = obj && obj.common && obj.common.name;
+            if (typeof name !== 'string' || !NEUE_NAMEN[name]) {
+                continue;
+            }
+            const kurz = id.startsWith(`${this.adapter.namespace}.`) ? id.slice(this.adapter.namespace.length + 1) : id;
+            try {
+                await this.adapter.extendObjectAsync(kurz, { common: { name: NEUE_NAMEN[name] } });
+                geaendert++;
+            } catch (e) {
+                this.adapter.log.warn(`could not rename '${id}': ${e.message}`);
+            }
+        }
+        if (geaendert) {
+            this.adapter.log.info(`${geaendert} state name(s) translated to English`);
+        }
+        return geaendert;
+    }
+
     async _ensureBoardObjects(boardId, title) {
         await this.adapter.setObjectNotExistsAsync(`boards.${boardId}`, {
             type: 'channel',
@@ -1585,8 +1645,8 @@ class Store {
         const stateDefs = {
             data: { name: 'Board JSON', type: 'string', role: 'json', read: true, write: false },
             rev: { name: 'Revision', type: 'number', role: 'value', read: true, write: false },
-            cardCount: { name: 'Anzahl Karten', type: 'number', role: 'value', read: true, write: false },
-            overdueCount: { name: 'Überfällige Karten', type: 'number', role: 'value', read: true, write: false },
+            cardCount: { name: 'Card count', type: 'number', role: 'value', read: true, write: false },
+            overdueCount: { name: 'Overdue cards', type: 'number', role: 'value', read: true, write: false },
         };
         for (const [suffix, common] of Object.entries(stateDefs)) {
             await this.adapter.setObjectNotExistsAsync(`boards.${boardId}.${suffix}`, {
@@ -1660,7 +1720,7 @@ class Store {
             if (alle.length === 1) {
                 return [alle[0]];
             }
-            throw new Error('assignees fehlt - mindestens eine zuständige Person ist Pflicht');
+            throw new Error('assignees is missing - at least one assignee is required');
         }
         const erlaubt = new Set(alle);
         const bekannt = [...erlaubt].sort();
@@ -1669,9 +1729,7 @@ class Store {
         }
         const fremd = [...new Set(list.filter(a => !erlaubt.has(a)))];
         if (fremd.length) {
-            throw new Error(
-                `unbekannte zuständige Person: ${fremd.join(', ')} - vorhanden sind: ${bekannt.join(', ') || '(keine)'}`,
-            );
+            throw new Error(`unknown assignee: ${fremd.join(', ')} - available are: ${bekannt.join(', ') || '(none)'}`);
         }
         return [...new Set(list)];
     }
@@ -1808,7 +1866,7 @@ class Store {
         }
         const known = (this.adapter.config.users || []).map(u => u && u.name).filter(Boolean);
         if (!known.includes(neu)) {
-            throw new Error(`Benutzer '${neu}' existiert nicht`);
+            throw notFound(`user '${neu}' does not exist`);
         }
         let cards = 0;
         const boards = new Set();
@@ -2019,14 +2077,14 @@ class Store {
         });
         const defs = {
             assignedCount: {
-                name: 'Zugewiesene offene Karten',
+                name: 'Assigned open cards',
                 type: 'number',
                 role: 'value',
                 read: true,
                 write: false,
             },
-            overdueCount: { name: 'Überfällige Karten', type: 'number', role: 'value', read: true, write: false },
-            overdueList: { name: 'Überfällige Karten (Liste)', type: 'string', role: 'json', read: true, write: false },
+            overdueCount: { name: 'Overdue cards', type: 'number', role: 'value', read: true, write: false },
+            overdueList: { name: 'Overdue cards (list)', type: 'string', role: 'json', read: true, write: false },
         };
         for (const [suffix, common] of Object.entries(defs)) {
             await this.adapter.setObjectNotExistsAsync(`users.${name}.${suffix}`, {
@@ -2049,5 +2107,6 @@ module.exports = {
     nextDue,
     recMatches,
     nextCronDates,
+    notFound,
     TRASH_RETENTION_DAYS,
 };

package/main.js

@@ -11,7 +11,7 @@ const { cardWithDueAt, boardWithDueAt } = require('./lib/dueat');
 const { Server } = require('./lib/server');
 
 const { freezePlan, prunePlan } = require('./lib/freeze');
-const { hasDateToken } = require('./lib/store');
+const { hasDateToken, notFound } = require('./lib/store');
 
 // Wie oft der Adapter versucht, das Merkmal `fixed` in die Benutzerliste
 // zurueckzuschreiben, bevor er aufgibt. Mehr als einer, weil ein Speichern der
@@ -55,6 +55,8 @@ class Kanban extends utils.Adapter {
         // angelegt und braucht dafür den lokalisierten Namen.
         await this._resolveLanguage();
         await this.store.load();
+        // Namen aus alten Installationen nachziehen (siehe migrateStateNames).
+        await this.store.migrateStateNames();
         // Erst nach dem Laden: Ob eine Kennung festgeschrieben werden muss,
         // haengt daran, ob Karten auf sie zeigen, und die kennt der Store
         // vorher nicht. Schreibt der Adapter dabei seine eigene Konfiguration,
@@ -418,7 +420,7 @@ class Kanban extends utils.Adapter {
                 // Nicht still null liefern: ein Skript, das nur den Statuscode prüft,
                 // hielte das sonst für einen Erfolg.
                 if (!b) {
-                    throw new Error(`Board '${boardId}' existiert nicht`);
+                    throw notFound(`board '${boardId}' does not exist`);
                 }
                 return board(b);
             }
@@ -439,11 +441,11 @@ class Kanban extends utils.Adapter {
             case 'doneCard': {
                 const b = this.store.getBoard(boardId);
                 if (!b) {
-                    throw new Error(`Board '${boardId}' existiert nicht`);
+                    throw notFound(`board '${boardId}' does not exist`);
                 }
                 const doneCol = b.columns.find(c => c.isDone);
                 if (!doneCol) {
-                    throw new Error(`Board '${boardId}' hat keine Erledigt-Spalte`);
+                    throw new Error(`board '${boardId}' has no done column`);
                 }
                 return card(this.store.moveCard(boardId, cardId, doneCol.id, undefined, source));
             }
@@ -472,7 +474,7 @@ class Kanban extends utils.Adapter {
                     ),
                 );
             default:
-                throw new Error(`Unbekanntes Kommando '${cmd}'`);
+                throw new Error(`unknown command '${cmd}'`);
         }
     }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "iobroker.kanban",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Kanban board for ioBroker with webhooks, multi-user support and email notifications",
   "author": {
     "name": "Björn Müller",
@@ -60,7 +60,7 @@
     "@alcalzone/release-script-plugin-manual-review": "^5.2.0",
     "@iobroker/adapter-dev": "^1.5.0",
     "@iobroker/eslint-config": "^2.2.0",
-    "@iobroker/testing": "^5.2.2",
+    "@iobroker/testing": "^6.2.1",
     "@tsconfig/node22": "^22.0.6",
     "@types/node": "^22.0.0"
   }