iobroker.alias-workbench 0.11.0 → 0.12.0

package/README.md

@@ -187,8 +187,9 @@ Early. Usable, but not finished.
 
 - Works as an admin tab; the adapter itself runs no process (`mode: none`).
   The instance exists only to carry the settings.
-- Interface in German and English, 550 keys each; the settings page in
-  eleven languages
+- Interface in all eleven admin languages, 712 keys each — one dictionary at
+  `admin/i18n/`, shared by the tab and the settings page. An unknown language
+  falls back to English
 - 16 bundled templates: eleven Homematic, four Tasmota, one plain measuring point
 - **Missing:** "who uses this alias" — vis views, Alexa and Google names cannot
   be searched from here, so a rename warns you instead of pretending to be
@@ -590,6 +591,22 @@ imported, and that all eleven language files carry the same keys.
 
 ## Changelog
 
+### 0.12.0 (2026-10-14)
+**Swapping the source**
+* **Swapping now asks the same recognition as the tree.** The existing stages all started from the **old** source — path, remembered template, names, roles. Yet swapping asks the same question the workbench answers anyway when you click a device: which point **there** is the `ELECTRIC_POWER`? Now, before guessing, the draft of the **new** source is computed and mapped through its pattern slots — template first, otherwise the detector. That carries in **both** directions, which was the point: to a device that labels its points (Matter: `role: value.power`, `unit: W`) the detector answers; to one that labels nothing, the template does. Measured at `mqtt-client.0.SmartHome.PC_Jonas`: all ten points without `common.role`, type `mixed`, the type detector makes `info` of it — but the Tasmota template knows that `stat.POWER` is the status point and the power sits in `tele.SENSOR` under `ENERGY.Power`. Swapping from Matter back to MQTT previously found **0 of 7** points; now 6 of 7, with separate read and write sources.
+* **And the formulas come along.** They belong to the source, not to the alias: `JSON.parse(val)?.ENERGY?.Power ?? null` describes how to get a power reading out of a Tasmota telemetry message. Left in place when swapping to Matter, the point sat silently at `null` — four readings empty with no error at all, and `SET` would have written the string from `val ? "ON" : "OFF"` onto a boolean. Each direction now brings its own: none towards Matter, the JSON formula again back to Tasmota.
+* **A point no stage can find can be named by hand.** Until now the only choices were "remove" or leave it. The row now offers a list of every point on the new device, with role and unit beside it. What you pick there carries the mark "by hand" and the note that **formula, unit and value range stay as they are on the alias** — the workbench knows nothing about that point, so it changes nothing about it.
+* **When the unit changes, the numbers sit beside it — nothing is decided for you.** Tasmota delivers `ENERGY.Total` in kWh, Matter `CONSUMPTION` in Wh: the same meter, factor 1000, invisible. Nothing is converted automatically, because the labelling itself is unreliable — Matter writes the unit `mA` on `CURRENT` and delivers amperes (0.926 at 245 W and 228 V). An automation that believed the label would have made 926 A of it. Instead the row states the finding ("on the alias A · new source: none"), shows what the alias displays today, and offers **two free fields**: unit and factor, both at the current state. The result recomputes as you type. Where the workbench knows something, a shortcut sits beside the field (`Wh`, `/ 1000`) — a suggestion from the labelling, checkable against the numbers above. Free fields, because fixed buttons fail where the target carries **no** unit at all: a JSON collector point has none, the unit sits in the field. This is only shown when the **new source** delivers something other than the old one — swapping between devices of the same kind shows nothing.
+* **When swapping, the remembered template is checked against the new source.** An alias remembers which template it came from, and the workbench keeps applying it until you explicitly change it — exactly right for a like-for-like replacement. For a differently built device it was not, and the bad part was the silence: after swapping a Tasmota socket for a Matter one, the channel still read "Tasmota socket, forced, ✕ cmnd.POWER" — and the **formulas** from that same template stayed on the points. `JSON.parse(val)?.ENERGY?.Power ?? null` is meant for a telemetry JSON; Matter delivers a plain number, and the point sat at `null`. Four readings were empty with no error anywhere, and `SET` would have written the string from `val ? "ON" : "OFF"` onto a boolean. The dialog now checks the remembered template against the **new** device: if it still fits, nothing changes; if it does not, it says why, how many points carry formulas, and — if a different template fits the new source — which one. Plus a pre-ticked box that drops the remembering and the formulas along with it. **Nothing is decided automatically**: the formula belongs to the source, not to the alias, and on the way back to MQTT it is needed again — deleting it silently would be the same mistake as silently keeping it. `native.geraetetyp` and the whole of `common` are left untouched; the swap changes the source, not what the device is.
+* **Source swapping now also asks the alias point itself.** Until now all three mapping stages started from the **old source** — its path, its template row, the name or role of the old state. That works while both devices are built alike and fails completely once they are not: moving an alias from a Tasmota socket to a Matter socket produced **0 out of 8** mappings, for two devices that do the same thing. Both reasons were on the source side, never on the target — `mqtt-client` keeps no roles, and five of the eight points read from **one** telemetry JSON. Yet the answer is already in the alias: `ELECTRIC_POWER` carries `role: value.power`, and the new device holds exactly one point of that name with that role. So before guessing, the **alias point** is asked. If **name and role** match and the point exists exactly once, that counts like a path hit and the row carries the grey mark "from alias"; if only the **role** matches, and it too exactly once, it is a suggestion marked "guessed". Two points of the same role cancel each other out instead of one being picked. In the measured case that is six out of eight, spread over **both** Matter endpoints; `TODAY` and `YESTERDAY` stay empty because the new device has no such thing.
+* **If one point at the new device both reads and writes, it may do so.** The rule "the write target is never the read source" guards against a guessed status point (`stat.POWER` instead of `cmnd.POWER`). Where a single point can do both — `OnOffPlugInUnit-1.SET` on Matter, `1.STATE` on Homematic — it was too strict and reported "no write target found" at exactly the point meant for it. The exception applies only to the evidenced hit via the alias point, and only when both sides are writable; a status point such as `ACTUAL` still gets none.
+
+**Tree**
+* **Several branches can be selected as one device.** Some adapters spread one device across sibling branches: Matter stores a socket as a folder without data points of its own, holding two `device` nodes — the switch in one, the readings in the other. The folder was not selectable, and each endpoint on its own produced half a device: at the switch the detector recognised a socket and offered the five readings as "to be created", while the neighbouring branch already had them. **Ctrl-click** now adds a branch to the selection or takes it out; the selection moves to the common parent, and every branch involved is marked in the tree. The same sits in the **context menu**, for anyone without a keyboard, and in the header of the right-hand side as a button **"Add neighbouring branches (N)"** — where the adapter provides evidence, the tooltip says so (Matter writes the same node id to every endpoint). Point names are shortened where they are unambiguous: `OnOffPlugInUnit-1.SET` becomes `SET`. Not for Tasmota — there the branch carries meaning, and the templates address `stat.POWER` and `tele.SENSOR`. **Nothing is merged automatically**: many devices can sit side by side under one node, and only a person knows what counts as one device.
+* **Right-click a node → "Export as mock device".** Everything below that node goes into a file: the objects and the values they carry right now. The point is not backup but rebuilding — from that file a device can be recreated elsewhere, so a template can be built for a device you do not own. What goes in is a positive list, not a filter: `native` is dropped entirely, and from `common` only `name`, `role`, `type`, `unit`, `read`, `write`, `min`, `max`, `def` and `states` are kept. `states` has to come along, otherwise the type detector does not recognise the slots with `statesDefined`. Paths are relative to the exported node, which is why the mock device matches the same templates somewhere else. Levels without an object of their own are recorded as such. 
+* **Before writing the file, the workbench shows what goes into it.** One row per entry with value, path, type, role and name — and a checkbox per value: untick what should not travel, and the object still stays. Values that look like an IP, a MAC or an identifier are highlighted. Above that stands what travels even without `native`: identifiers often sit **in the path and in the names too**, and leaving out `native` does not remove those. Measured on a HomeMatic central: twelve such places, although the file carries no `native` at all.
+* **And read back in.** Right-click → "Import mock device …" takes such a file and builds a device from it again — **always under `0_userdata.0.wb-attrappe.<name>`, never at the original path.** That is not a rule but a way of building: a foreign export cannot overwrite a real device. The templates still match, because they check relative names (`stat.POWER`, `1.LEVEL`) and not the root. Beforehand a dialog shows every object that would appear, with a name to change; a file that does not fit is rejected with a reason. Measured: an HmIP wall thermostat, exported and imported as a mock device, is recognised there by the same template — same device type, the same eleven filled slots.
+
 ### 0.11.0 (2026-10-11)
 **Templates**
 * **Template notes are German and English.** The description, the recognition note and each row note are `{ "de", "en" }`. The tab shows the admin language, otherwise English, otherwise German. The name hint stays one search pattern (`licht|lampe|light|…`): it matches the device name, which does not follow the admin language.
@@ -734,11 +751,6 @@ All changes in detail, with cause and measurement: [docs/aenderungen-ausfuehrlic
 * The data type now follows the role. A pattern slot prescribes not only the role but also the type, and both sit in the same type-detector record — so picking a role sets the matching type as well. Where a slot allows several types nothing is set, and where it prescribes none any choice stays right. If the type does not fit the slot after all, the workbench says so instead of staying quiet: in the row ("expects number"), as a warning underneath, and in the pattern field, which now gives the reason — "✕ CONSUMPTION: type mixed instead of number" — rather than a bare "does not fit". Before, a state with the right role and the wrong type dropped out of the pattern silently, and the whole device was recognised as something lesser Where a role matches several slots that differ in type — the blind's travel direction sits on DIRECTION as a boolean and on DIRECTION_ENUM as a number — the workbench picks the slot whose type fits, and both forms count as right.
 * Saving a template no longer loses the write targets. Every actuator that keeps its own state writes to the same point it reads - a blind, a dimmer and a thermostat all use 1.LEVEL for both. Saving dropped the write path in exactly that case, and the resulting alias showed the position but could no longer be moved. Rows that only write, like the blind's STOP, disappeared altogether. With Tasmota it never showed, because there tele.STATE is read and cmnd.POWER is written. The device type in the template sheet was affected by a second slip: three patterns are named differently from their type (blinds/blind, mediaPlayer/media, levelSlider/slider), so a blind always claimed to have no type at all
 
-### 0.9.8
-* The changelog only lists versions that actually exist on npm. The entries 0.9.1 to 0.9.6 were local intermediate steps and were never published; their content is now summarised under 0.9.7. Found by the repochecker (E2004, E1032)
-* The README no longer describes how to add the adapter by hand — in the official repository it is picked from the adapter list (E6013)
-* `dependabot.yml` gets a seven-day cooldown for npm packages: what appears today is proposed a week later. If a compromised release is pulled within that time, it never arrives here (E8915). And `@types/node` stays on its major version — the types must match the Node release the adapter runs on (E8917)
-
 Older entries: [CHANGELOG_OLD.md](CHANGELOG_OLD.md).
 
 ## License

package/admin/css/werkbank.css

@@ -191,6 +191,10 @@
   .tree .node.leer { opacity:.45; font-style:italic; }
   .tree .node.leer .kind { background:transparent; border:1px solid var(--line); }
   .tree .node.sel { background:var(--accent); color:var(--accent-ink); font-weight:600; }
+  /* Der gemeinsame Elternknoten einer Mehrfachauswahl: markiert, aber
+     schwaecher als die Zweige selbst. Er ist der Ort, auf dem der
+     Entwurf steht - angeklickt hat ihn niemand. */
+  .tree .node.selEltern { background:var(--accent-soft); font-weight:600; }
   .tree .node.sel .kind { background:rgba(255,255,255,.22); color:inherit; }
   /* Die Vorlagenliste benutzt dieselben Knotenzeilen, hat aber statt
      `kind`/`nam`/`cnt` ein Abzeichen, einen Namen und rechts die Kennung.
@@ -633,6 +637,19 @@
   .rat { font-family:var(--sans); font-size:8px; font-weight:700; letter-spacing:.05em;
          text-transform:uppercase; background:var(--accent-soft); color:var(--accent);
          padding:0 6px; border-radius:999px; margin-left:6px; white-space:nowrap; }
+  /* Name und Marke im Tauschdialog untereinander. Die Namensspalte ist
+     120 Pixel breit; „ERKANNT" hinter `ELECTRIC_POWER` lief sonst in die
+     Pfade der Nachbarzeile (Ricardo, 13.10.2026). */
+  #swap-body .slot .zuname { display:flex; flex-direction:column;
+                             align-items:flex-start; gap:3px; }
+  #swap-body .slot .zuname .rat,
+  #swap-body .slot .zuname .herk { margin-left:0; }
+  /* Herkunftsmarke am Quellentausch: dieselbe Form wie „vermutet", aber
+     grau statt farbig - sie warnt nicht, sie sagt nur, woher die
+     Zuordnung kommt (Stufe 4, ueber den Alias-Punkt). */
+  .herk { font-family:var(--sans); font-size:8px; font-weight:700; letter-spacing:.05em;
+          text-transform:uppercase; background:var(--surface-3); color:var(--ink-3);
+          padding:0 6px; border-radius:999px; margin-left:6px; white-space:nowrap; }
   .erow .nm3 .ratknopf { font-family:var(--sans); font-size:11px; cursor:pointer; margin-left:5px;
                          color:var(--ink-3); padding:0 4px; border-radius:var(--r-sm); }
   .erow .nm3 .ratknopf:hover { background:var(--surface-3); color:var(--ink); }
@@ -1176,3 +1193,59 @@
   }
   .katalog-laedt .kl-kopf { font-weight:600; font-size:12.5px; color:var(--ink); }
   .katalog-laedt .kl-text { margin-top:3px; font-size:11.5px; color:var(--ink-3); }
+
+  /* Das Menue am Baum (Rechtsklick). Liegt am body, nicht in der Zeile:
+     der Baum scrollt, und ein Kind der Zeile wuerde am Rand abgeschnitten. */
+  .baummenue {
+    position:fixed; z-index:200; min-width:190px;
+    background:var(--surface); border:1px solid var(--line-strong);
+    border-radius:var(--r); box-shadow:var(--shadow-hoch); padding:4px 0;
+  }
+  .baummenue .bm-zeile {
+    padding:6px 13px; font-size:12.5px; color:var(--ink); cursor:pointer;
+    white-space:nowrap;
+  }
+  .baummenue .bm-zeile:hover { background:var(--hover); color:var(--hover-ink); }
+
+  /* Die Vorschau vor dem Ausgeben einer Attrappe. */
+  .mk-kopf { margin-bottom:10px; }
+  .mk-kopf .mk-wurzel { font:12.5px var(--mono); color:var(--ink); word-break:break-all; }
+  .mk-kopf .mk-zahlen { margin-top:3px; font-size:11.5px; color:var(--ink-3); }
+  .mk-kopf .mk-ohne { margin-top:3px; font-size:11.5px; color:var(--ink-2); }
+  .mk-warn {
+    margin:0 0 10px; padding:7px 10px; border-radius:var(--r);
+    background:var(--warn-soft); color:var(--warn); font-size:11.5px;
+  }
+  .mk-warn .mk-warn-kopf { font-weight:600; }
+  .mk-warn .mk-warn-liste { margin:4px 0 0; padding-left:16px; }
+  .mk-warn .mk-warn-liste li { font:11px var(--mono); word-break:break-all; }
+  table.mk-tab { width:100%; border-collapse:collapse; font-size:12px; }
+  table.mk-tab th {
+    text-align:left; font-weight:600; font-size:11px; color:var(--ink-3);
+    border-bottom:1px solid var(--line); padding:4px 7px; position:sticky; top:0;
+    background:var(--surface);
+  }
+  table.mk-tab td { padding:3px 7px; border-bottom:1px solid var(--line); vertical-align:top; }
+  table.mk-tab tr.mk-virt { color:var(--ink-3); }
+  table.mk-tab tr.mk-aus .mk-wtext { text-decoration:line-through; color:var(--ink-3); }
+  .mk-wert label { display:flex; gap:5px; align-items:baseline; cursor:pointer; }
+  .mk-wtext { font:11.5px var(--mono); word-break:break-all; }
+  .mk-wtext.auff { background:var(--warn-soft); color:var(--warn); border-radius:3px; padding:0 3px; }
+  .mk-pfad { font:11.5px var(--mono); }
+  .mk-name { color:var(--ink-2); }
+  .mk-fehler {
+    padding:8px 11px; border-radius:var(--r);
+    background:var(--bad-soft); color:var(--bad); font-size:12px;
+  }
+  .mk-namenszeile { display:flex; gap:7px; align-items:center; margin:7px 0 3px; }
+  .mk-namenszeile .mk-lbl { font-size:11.5px; color:var(--ink-3); }
+  .mk-namenszeile input.tx { max-width:260px; }
+  .mk-schon { color:var(--ink-3); font-size:11px; }
+  /* Von welcher Zeile das Baummenue spricht. Bewusst anders als die
+     Auswahl `.sel`: ein Rechtsklick waehlt nicht aus, und zwei gleich
+     aussehende Zeilen waeren irrefuehrend. */
+  .tree .node.menueziel {
+    outline:2px solid var(--accent); outline-offset:-2px; border-radius:var(--r);
+  }
+  .mk-warn.mk-gross { background:var(--warn-soft); }
+  .mk-mehr { margin-top:6px; font-size:11.5px; color:var(--ink-3); }

package/admin/i18n/de.json

@@ -259,6 +259,32 @@
   "list.tplDiffers": "weicht von der Vorlage ab",
   "list.tplHint": "Hakt genau die Punkte an, die die Vorlage vorschlägt — unabhängig davon, was heute im Alias steht.",
   "list.willBeCreated": "angelegt werden",
+  "mock.colName": "Name",
+  "mock.colPath": "Pfad",
+  "mock.colRole": "Rolle",
+  "mock.colType": "Typ",
+  "mock.colValue": "Wert",
+  "mock.counts": "{0} Einträge, {1} mit Wert · geschrieben von alias-workbench {2} · Quelle {3}",
+  "mock.inNames": "Achtung: {0} Kennungen stehen auch im Pfad oder in Namen — das Weglassen von `native` entfernt die nicht",
+  "mock.more": "… und {0} weitere Einträge (nicht gezeigt, aber in der Datei)",
+  "mock.noNative": "`native` ist nicht enthalten. Werte, die nicht mitsollen, einfach abwählen.",
+  "mock.save": "Datei speichern",
+  "mock.suspicious": "Sieht aus wie: {0}",
+  "mock.tooBig": "Das ist viel: {0} Einträge (ein Gerät hat meist weniger als {1})",
+  "mock.tooBigHint": "War ein einzelnes Gerät gemeint? Ausgeben geht trotzdem.",
+  "mockin.bad": "Diese Datei passt nicht",
+  "mockin.badEntry": "{0} Einträge haben keinen Pfad.",
+  "mockin.badFormat": "Format {0}, diese Fassung liest aber {1}.",
+  "mockin.badJson": "Nicht als JSON lesbar.",
+  "mockin.badObjects": "Keine Objekte in der Datei.",
+  "mockin.counts": "{0} Objekte, {1} mit Wert, {2} schon vorhanden",
+  "mockin.create": "Jetzt anlegen",
+  "mockin.exists": "(gibt es schon)",
+  "mockin.from": "Aus {0} · geschrieben von alias-workbench {1} · Quelle {2}",
+  "mockin.name": "Name",
+  "mockin.nameTaken": "Den Namen „{0}\" gibt es schon — dort liegen {1} Objekte",
+  "mockin.nameTakenHint": "Bitte einen anderen Namen wählen. In eine vorhandene Attrappe zu schreiben würde beide vermischen: ersetzt wird nur, wo der Pfad gleich ist, der Rest der alten bleibt stehen — und heraus käme ein Gerät, das es nie gab.",
+  "mockin.noRoot": "Der Eintrag für die Wurzel fehlt.",
   "move.button": "Verlegen …",
   "move.done": "Verlegt. Der Alias steht jetzt unter {0}.",
   "move.exists": "{0} gibt es schon. Erst entfernen oder einen anderen Namen wählen.",
@@ -375,6 +401,9 @@
   "pattern.typeOr": " oder ",
   "pattern.usualOnly": "nur die üblichen",
   "pattern.viaRole": "Rolle {0}",
+  "result.addNeighbours": "Nachbarzweige dazunehmen ({0})",
+  "result.addNeighboursHint": "Manche Adapter verteilen ein Gerät auf Geschwisterzweige. Das hier nimmt alle; einzelne wählt man mit Strg-Klick im Baum.",
+  "result.addNeighboursSame": "Diese Zweige gehören laut Adapter zu einem Gerät — dieselbe Node-Kennung und derselbe Verbindungspunkt. Das hier nimmt alle; einzelne wählt man mit Strg-Klick im Baum.",
   "result.allAnyway": "Trotzdem alle ",
   "result.channelsHint": "Dieses Gerät hat {0} Kanäle. Unten kannst du wählen: alles flach in einem Alias, oder die Struktur der Quelle übernehmen — ein Ordner für das Gerät, darunter je Kanal einer.",
   "result.extraSwitches": "Mit dabei: {0} Punkte aus weiteren Kanälen, für die das {1}-Muster keinen Platz hat. Sie werden angelegt, gelten aber nicht als Schalter oder Rückmeldung des Geräts. Für getrennte Bedienung unten „je Kanal ein Gerät\" wählen.",
@@ -405,18 +434,32 @@
   "roles.slotTaken": "belegt von {0}",
   "swap.blocked": "Erst entscheiden — diese Punkte können nicht mitziehen: {0}. Entweder beim Tauschen entfernen oder den Tausch lassen; ein Punkt, der schreiben soll, braucht ein Schreibziel.",
   "swap.button": "Quelle tauschen …",
+  "swap.byHandCheck": "Formel, Einheit und Wertebereich bleiben, wie sie am Alias stehen — bitte danach prüfen.",
+  "swap.byHandHint": "Diesen Punkt hast du selbst benannt — die Werkbank konnte ihn am neuen Gerät nicht ableiten.",
+  "swap.byHandMark": "von Hand",
   "swap.diffRange": "Wertebereich {0} → {1}",
   "swap.diffType": "Typ {0} → {1}",
   "swap.diffUnit": "Einheit {0} → {1}",
   "swap.done": "Getauscht. Der Alias liest jetzt aus {0}.",
+  "swap.factorField": "Faktor",
+  "swap.formula": "Formel",
+  "swap.formulaNone": "keine",
   "swap.from": "Liest heute aus:",
+  "swap.fromAlias": "Über den Alias-Punkt selbst zugeordnet: unter der neuen Quelle liegt genau ein Punkt, der „{0}“ heißt und die Rolle „{1}“ trägt.",
+  "swap.fromAliasMark": "aus dem Alias",
+  "swap.fromDetect": "Zugeordnet wie beim Anklicken des Geräts im Baum: Die neue Quelle beschriftet ihre Punkte selbst, und der Detektor erkennt dort „{0}“.",
+  "swap.fromDetectMark": "erkannt",
+  "swap.fromTpl": "Zugeordnet wie beim Anklicken des Geräts im Baum: Auf die neue Quelle passt die Vorlage „{0}“, und die weiß, welcher Punkt zu diesem Platz gehört — samt Formel.",
+  "swap.fromTplMark": "aus der Vorlage",
   "swap.goHigher": "eine Ebene höher nehmen",
   "swap.gone": "Dieses Gerät gibt es nicht mehr — genau dafür ist dieser Weg gedacht.",
   "swap.guessHint": "Die mit „vermutet“ gekennzeichneten Zeilen sind über Namen oder Rolle geraten — die bitte einzeln prüfen.",
+  "swap.guessedByAliasRole": "Über die Rolle des Alias-Punkts geraten: unter der neuen Quelle trägt genau ein Punkt die Rolle „{0}“. Bitte prüfen.",
   "swap.guessedByName": "Über den Punktnamen geraten: unter der neuen Quelle heißt ebenfalls etwas „{0}\". Das kann weit danebenliegen — bitte prüfen.",
   "swap.guessedByRole": "Über die Rolle geraten: unter der neuen Quelle trägt ein Punkt dieselbe Rolle „{0}\". Bitte prüfen.",
   "swap.higherLevel": "Eine Ebene höher ({0}) finden {1} von {2} Punkten ein Ziel, hier nur {3}.",
   "swap.keeps": "Der Alias behält seine Kennung, seine Namen, Rollen und Formeln, die Aufzeichnung in der Datenbank sowie Raum und Funktion. Geändert wird nur, woher jeder Punkt liest und wohin er schreibt.",
+  "swap.loadingValues": "Das neue Gerät wird gelesen …",
   "swap.mapping": "Zuordnung",
   "swap.mind": "Darauf achten:",
   "swap.mindHint": "Die Formeln des Alias bleiben unverändert — rechnet die neue Quelle anders als die alte, stimmen die Werte danach nicht mehr. Die Formel steht in der Detailzeile des Punkts.",
@@ -424,13 +467,27 @@
   "swap.noMatch": "kein passender Punkt gefunden",
   "swap.noWriteMatch": "kein Schreibziel gefunden — dieser Punkt schreibt danach nirgendwohin",
   "swap.now": "Jetzt tauschen",
+  "swap.pickByHand": "… oder selbst einen Punkt wählen",
   "swap.pickFirst": "Erst eine neue Quelle wählen.",
   "swap.removeIt": "diesen Punkt beim Tauschen entfernen",
   "swap.same": "Das ist dieselbe Quelle wie bisher.",
   "swap.search": "Suchen (Kennung oder Name) …",
+  "swap.suggestionHint": "Ein Vorschlag aus der Beschriftung — Klick setzt ihn ins Feld. Prüfe ihn an den beiden Werten darüber: die Beschriftung kann falsch sein.",
   "swap.title": "Quelle tauschen",
   "swap.to": "Neue Quelle",
+  "swap.tplDrop": "Gemerkte Vorlage mit entfernen ({0} Objekte)",
+  "swap.tplFormulas": "Die Formeln von {0} Punkten werden ohnehin durch die des neuen Geräts ersetzt — sie gehören zur Quelle, nicht zum Alias. Jede Zeile zeigt, was danach dort steht.",
+  "swap.tplGone": "Diese Vorlage gibt es nicht mehr.",
+  "swap.tplOther": "Auf die neue Quelle passt eine andere Vorlage: „{0}“. Sie lässt sich nach dem Tausch über die Vorlagenwahl anwenden — sie bringt ihre eigenen Formeln und Namen mit.",
+  "swap.tplStale": "Die gemerkte Vorlage „{0}“ passt nicht zur neuen Quelle",
   "swap.unchanged": "unverändert",
+  "swap.unitChanged": "Einheit: am Alias {0} · neue Quelle: {1}",
+  "swap.unitField": "Einheit am Alias",
+  "swap.unitHistWarn": "An diesem Punkt hängt eine Aufzeichnung. Ihre Historie liegt in der alten Einheit — eine Reihe, die mittendrin den Faktor wechselt, lässt sich nicht reparieren.",
+  "swap.unitNoFactor": "Keine Umrechnung angeboten: Diese beiden Einheiten sind kein bekanntes Paar.",
+  "swap.unitNone": "keine",
+  "swap.unitResult": "Ergebnis: {0} {1}",
+  "swap.unitValOld": "Dein Alias zeigt heute: {0} {1}",
   "swap.unknown": "(nicht ermittelbar)",
   "target.alsoRoom": "Raum auch auf „{0}\" setzen?",
   "target.alsoRoomNew": "Raum „{0}\" gibt es nicht — anlegen und zuordnen?",
@@ -574,11 +631,19 @@
   "tpls.whichNumber": "Nummer dieses Ausgangs",
   "tpls.wissen": "+ {0} weitere Punkte als Rollenwissen — greift in der Ansicht „Alle Datenpunkte des Geräts“",
   "tree.aliases": "Alias bearbeiten",
+  "tree.branchAdd": "Diesen Zweig zur Auswahl dazunehmen",
+  "tree.branchForeign": "Diese Zweige liegen nicht in derselben Instanz. Ein Gerät liegt in einer Instanz — nimm Zweige, die einen gemeinsamen Elternknoten haben.",
+  "tree.branchHint": "Manche Adapter verteilen ein Gerät auf Geschwisterzweige — Matter legt den Schalter in den einen und die Messwerte in den anderen. Mehrere Zweige ergeben zusammen ein Gerät. Dasselbe wie Strg-Klick.",
+  "tree.branchRemove": "Diesen Zweig aus der Auswahl herausnehmen",
   "tree.collapseAll": "alles zuklappen",
   "tree.emptyNode": "keine Datenpunkte — der Knoten steht in der Datenbank, ist aber leer",
   "tree.expandAll": "alles aufklappen",
+  "tree.exportMock": "Als Attrappe ausgeben",
+  "tree.exportMockHint": "Schreibt alles unterhalb von {0} in eine Datei: Objekte und aktuelle Werte, ohne native",
   "tree.filter": "filtern …",
   "tree.filterAria": "Objekte filtern",
+  "tree.importMock": "Attrappe einlesen …",
+  "tree.importMockHint": "Landet immer unter {0} — nie am Originalpfad",
   "tree.loading": "lade Objekte …",
   "tree.looksLikeDevice": "sieht wie ein einzelnes Gerät aus",
   "tree.noObjectHint": "kein echter Ordner",

package/admin/i18n/en.json

@@ -259,6 +259,32 @@
   "list.tplDiffers": "differs from the template",
   "list.tplHint": "Checks exactly the points the template proposes — regardless of what the alias holds today.",
   "list.willBeCreated": "will be created:",
+  "mock.colName": "Name",
+  "mock.colPath": "Path",
+  "mock.colRole": "Role",
+  "mock.colType": "Type",
+  "mock.colValue": "Value",
+  "mock.counts": "{0} entries, {1} with a value · written by alias-workbench {2} · source {3}",
+  "mock.inNames": "Watch out: {0} identifiers also sit in the path or in names — leaving out native does not remove those",
+  "mock.more": "… and {0} more entries (not shown, but they go into the file)",
+  "mock.noNative": "native is not included. Untick any value you do not want to pass on.",
+  "mock.save": "Save file",
+  "mock.suspicious": "Looks like: {0}",
+  "mock.tooBig": "That is a lot: {0} entries (a device usually has fewer than {1})",
+  "mock.tooBigHint": "Did you mean a single device? Exporting works anyway.",
+  "mockin.bad": "This file does not fit",
+  "mockin.badEntry": "{0} entries have no path.",
+  "mockin.badFormat": "Format {0}, but this version reads {1}.",
+  "mockin.badJson": "Not readable as JSON.",
+  "mockin.badObjects": "No objects in the file.",
+  "mockin.counts": "{0} objects, {1} with a value, {2} already there",
+  "mockin.create": "Create now",
+  "mockin.exists": "(already there)",
+  "mockin.from": "From {0} · written by alias-workbench {1} · source {2}",
+  "mockin.name": "Name",
+  "mockin.nameTaken": "The name “{0}” is taken — {1} objects already sit there",
+  "mockin.nameTakenHint": "Please choose a different name. Writing into an existing mock device would mix the two: only matching paths are replaced, the rest of the old one stays — and you would end up with a device that never existed.",
+  "mockin.noRoot": "The root entry is missing.",
   "move.button": "Move …",
   "move.done": "Moved. The alias is now at {0}.",
   "move.exists": "{0} already exists. Remove it first or pick another name.",
@@ -375,6 +401,9 @@
   "pattern.typeOr": " or ",
   "pattern.usualOnly": "the usual ones only",
   "pattern.viaRole": "role {0}",
+  "result.addNeighbours": "Add neighbouring branches ({0})",
+  "result.addNeighboursHint": "Some adapters split one device across sibling branches. This takes them all; Ctrl-click in the tree picks single ones.",
+  "result.addNeighboursSame": "These branches belong to one device according to the adapter — same node id and same online state. This takes them all; Ctrl-click in the tree picks single ones.",
   "result.allAnyway": "All anyway ",
   "result.channelsHint": "This device has {0} channels. Choose below: everything flat in one alias, or mirror the structure of the source — a folder for the device, one channel each below it.",
   "result.extraSwitches": "Included: {0} points from other channels that the {1} pattern has no slot for. They are created, but do not count as the device’s switch or feedback. For separate control, use \"one device per channel\" below.",
@@ -405,18 +434,32 @@
   "roles.slotTaken": "taken by {0}",
   "swap.blocked": "Decide first — these points cannot come along: {0}. Either remove them during the swap or leave the swap be; a point that is meant to write needs a write target.",
   "swap.button": "Swap source …",
+  "swap.byHandCheck": "Formula, unit and value range stay as they are on the alias — please check them afterwards.",
+  "swap.byHandHint": "You named this point yourself — the workbench could not derive it from the new device.",
+  "swap.byHandMark": "by hand",
   "swap.diffRange": "range {0} → {1}",
   "swap.diffType": "type {0} → {1}",
   "swap.diffUnit": "unit {0} → {1}",
   "swap.done": "Swapped. The alias now reads from {0}.",
+  "swap.factorField": "Factor",
+  "swap.formula": "Formula",
+  "swap.formulaNone": "none",
   "swap.from": "Currently reads from:",
+  "swap.fromAlias": "Mapped from the alias point itself: exactly one point under the new source is called \"{0}\" and carries the role \"{1}\".",
+  "swap.fromAliasMark": "from alias",
+  "swap.fromDetect": "Mapped the same way as clicking the device in the tree: the new source labels its points itself, and the detector recognises \"{0}\" there.",
+  "swap.fromDetectMark": "recognised",
+  "swap.fromTpl": "Mapped the same way as clicking the device in the tree: the template \"{0}\" fits the new source and says which point belongs to this slot — including its formula.",
+  "swap.fromTplMark": "from template",
   "swap.goHigher": "use the level above",
   "swap.gone": "This device no longer exists — which is exactly what this is for.",
   "swap.guessHint": "Rows marked “guessed” were matched by name or role — please check those individually.",
+  "swap.guessedByAliasRole": "Guessed from the role of the alias point: exactly one point under the new source carries the role \"{0}\". Please check.",
   "swap.guessedByName": "Guessed from the point name: something under the new source is also called \"{0}\". That can be far off — please check.",
   "swap.guessedByRole": "Guessed from the role: a point under the new source carries the same role \"{0}\". Please check.",
   "swap.higherLevel": "One level up ({0}) finds a target for {1} of {2} points, here only {3}.",
   "swap.keeps": "The alias keeps its id, names, roles and formulas, its history in the database and its room and function. Only where each point reads from and writes to changes.",
+  "swap.loadingValues": "Reading the new device …",
   "swap.mapping": "Mapping",
   "swap.mind": "Watch out:",
   "swap.mindHint": "The alias formulas stay as they are — if the new source scales differently, the values will be wrong afterwards. The formula sits in the point's detail row.",
@@ -424,13 +467,27 @@
   "swap.noMatch": "no matching point found",
   "swap.noWriteMatch": "no write target found — this point will not write anywhere",
   "swap.now": "Swap now",
+  "swap.pickByHand": "… or pick a point yourself",
   "swap.pickFirst": "Pick a new source first.",
   "swap.removeIt": "remove this point while swapping",
   "swap.same": "That is the same source as before.",
   "swap.search": "Search (id or name) …",
+  "swap.suggestionHint": "A suggestion from the labelling — click to put it in the field. Check it against the two values above: the labelling can be wrong.",
   "swap.title": "Swap source",
   "swap.to": "New source",
+  "swap.tplDrop": "Drop the remembered template as well ({0} objects)",
+  "swap.tplFormulas": "The formulas of {0} points are replaced by those of the new device anyway — they belong to the source, not to the alias. Each row shows what it will read afterwards.",
+  "swap.tplGone": "This template no longer exists.",
+  "swap.tplOther": "A different template fits the new source: \"{0}\". You can apply it after the swap via the template selector — it brings its own formulas and names.",
+  "swap.tplStale": "The remembered template \"{0}\" does not fit the new source",
   "swap.unchanged": "unchanged",
+  "swap.unitChanged": "Unit: on the alias {0} · new source: {1}",
+  "swap.unitField": "Unit on the alias",
+  "swap.unitHistWarn": "A recording hangs on this point. Its history is in the old unit — a series that changes factor halfway cannot be repaired.",
+  "swap.unitNoFactor": "No conversion offered: these two units are not a known pair.",
+  "swap.unitNone": "none",
+  "swap.unitResult": "Result: {0} {1}",
+  "swap.unitValOld": "Your alias shows today: {0} {1}",
   "swap.unknown": "(cannot be determined)",
   "target.alsoRoom": "Set room to \"{0}\" as well?",
   "target.alsoRoomNew": "There is no room \"{0}\" — create and assign it?",
@@ -574,11 +631,19 @@
   "tpls.whichNumber": "Number of this output",
   "tpls.wissen": "+ {0} more states as role knowledge — used in the “All data points of the device” view",
   "tree.aliases": "Edit alias",
+  "tree.branchAdd": "Add this branch to the selection",
+  "tree.branchForeign": "Those branches are not in the same instance. A device lives in one instance — pick branches that share a parent.",
+  "tree.branchHint": "Some adapters split one device across sibling branches — Matter puts the switch in one and the meter in another. Several branches together form one device. Same as Ctrl-click.",
+  "tree.branchRemove": "Remove this branch from the selection",
   "tree.collapseAll": "collapse all",
   "tree.emptyNode": "no datapoints — the node exists in the database but is empty",
   "tree.expandAll": "expand all",
+  "tree.exportMock": "Export as mock device",
+  "tree.exportMockHint": "Writes everything below {0} to a file: objects and current values, without native",
   "tree.filter": "filter …",
   "tree.filterAria": "Filter objects",
+  "tree.importMock": "Import mock device …",
+  "tree.importMockHint": "Always lands under {0} — never at the original path",
   "tree.loading": "loading objects …",
   "tree.looksLikeDevice": "looks like a single device",
   "tree.noObjectHint": "not a real folder",

package/admin/i18n/es.json

@@ -259,6 +259,32 @@
   "list.tplDiffers": "difiere de la plantilla",
   "list.tplHint": "Comprueba exactamente los puntos que propone la plantilla, independientemente de lo que contenga actualmente el alias.",
   "list.willBeCreated": "se creará:",
+  "mock.colName": "Nombre",
+  "mock.colPath": "Ruta",
+  "mock.colRole": "Rol",
+  "mock.colType": "Tipo",
+  "mock.colValue": "Valor",
+  "mock.counts": "{0} entradas, {1} con valor · escrito por alias-workbench {2} · origen {3}",
+  "mock.inNames": "Atención: {0} identificadores están también en la ruta o en los nombres — omitir `native` no los quita",
+  "mock.more": "… y {0} entradas más (no mostradas, pero van al archivo)",
+  "mock.noNative": "`native` no se incluye. Desmarca los valores que no quieras compartir.",
+  "mock.save": "Guardar archivo",
+  "mock.suspicious": "Parece: {0}",
+  "mock.tooBig": "Son muchas: {0} entradas (un dispositivo suele tener menos de {1})",
+  "mock.tooBigHint": "¿Querías un solo dispositivo? La exportación funciona igualmente.",
+  "mockin.bad": "Este archivo no sirve",
+  "mockin.badEntry": "{0} entradas no tienen ruta.",
+  "mockin.badFormat": "Formato {0}, pero esta versión lee {1}.",
+  "mockin.badJson": "No se puede leer como JSON.",
+  "mockin.badObjects": "No hay objetos en el archivo.",
+  "mockin.counts": "{0} objetos, {1} con valor, {2} ya existen",
+  "mockin.create": "Crear ahora",
+  "mockin.exists": "(ya existe)",
+  "mockin.from": "De {0} · escrito por alias-workbench {1} · origen {2}",
+  "mockin.name": "Nombre",
+  "mockin.nameTaken": "El nombre «{0}» ya existe — allí hay {1} objetos",
+  "mockin.nameTakenHint": "Elige otro nombre. Escribir en un dispositivo simulado existente mezclaría ambos: solo se sustituye lo que tiene la misma ruta, el resto del antiguo permanece — y saldría un dispositivo que nunca existió.",
+  "mockin.noRoot": "Falta la entrada de la raíz.",
   "move.button": "Mover…",
   "move.done": "Se ha trasladado. El alias se encuentra ahora en {0}.",
   "move.exists": "{0} ya existe. Elimínalo primero o elige otro nombre.",
@@ -375,6 +401,9 @@
   "pattern.typeOr": " o ",
   "pattern.usualOnly": "solo los de siempre",
   "pattern.viaRole": "papel {0}",
+  "result.addNeighbours": "Añadir ramas vecinas ({0})",
+  "result.addNeighboursHint": "Algunos adaptadores reparten un aparato entre ramas hermanas. Esto las toma todas; para elegir una sola, Ctrl+clic en el árbol.",
+  "result.addNeighboursSame": "Según el adaptador, estas ramas pertenecen a un aparato — mismo id de nodo y mismo punto de conexión. Esto las toma todas; si no, Ctrl+clic.",
   "result.allAnyway": "En fin, todo ",
   "result.channelsHint": "Este dispositivo tiene {0} canales. Elige una de las siguientes opciones: todo en un único alias, o replicar la estructura de la fuente —una carpeta para el dispositivo y un canal por debajo de cada una—.",
   "result.extraSwitches": "Incluidos: {0} puntos de otros canales para los que el patrón {1} no dispone de ranura. Se crean, pero no cuentan como interruptor ni como retroalimentación del dispositivo. Para un control independiente, utiliza la opción «un dispositivo por canal» que aparece a continuación.",
@@ -405,18 +434,32 @@
   "roles.slotTaken": "tomada por {0}",
   "swap.blocked": "Decide primero: estos puntos no pueden incluirse: {0}. O bien los eliminas durante el intercambio o bien dejas el intercambio tal cual; un punto destinado a la escritura necesita un destino de escritura.",
   "swap.button": "Intercambiar fuente…",
+  "swap.byHandCheck": "Fórmula, unidad y rango se quedan como están en el alias — compruébelos después.",
+  "swap.byHandHint": "Este punto lo ha indicado usted — el banco no pudo deducirlo del nuevo aparato.",
+  "swap.byHandMark": "a mano",
   "swap.diffRange": "intervalo {0} → {1}",
   "swap.diffType": "tipo {0} → {1}",
   "swap.diffUnit": "unidad {0} → {1}",
   "swap.done": "Se ha cambiado. El alias ahora lee desde {0}.",
+  "swap.factorField": "Factor",
+  "swap.formula": "Fórmula",
+  "swap.formulaNone": "ninguna",
   "swap.from": "Actualmente se lee desde:",
+  "swap.fromAlias": "Asignado por el propio punto del alias: bajo la nueva fuente hay exactamente un punto llamado «{0}» con el rol «{1}».",
+  "swap.fromAliasMark": "del alias",
+  "swap.fromDetect": "Asignado igual que al pulsar en el árbol: la nueva fuente etiqueta sus propios puntos y el detector reconoce allí «{0}».",
+  "swap.fromDetectMark": "reconocido",
+  "swap.fromTpl": "Asignado igual que al pulsar el aparato en el árbol: a la nueva fuente le encaja la plantilla «{0}», que sabe qué punto corresponde a este puesto — fórmula incluida.",
+  "swap.fromTplMark": "de la plantilla",
   "swap.goHigher": "utiliza el nivel superior",
   "swap.gone": "Este dispositivo ya no existe, y precisamente para eso sirve esto.",
   "swap.guessHint": "Las filas marcadas como «supuestas» se han emparejado por nombre o cargo; por favor, compruébalas una por una.",
+  "swap.guessedByAliasRole": "Deducido del rol del punto del alias: bajo la nueva fuente exactamente un punto tiene el rol «{0}». Compruébelo.",
   "swap.guessedByName": "Por lo que se deduce del nombre del punto: hay algo en la nueva fuente que también se llama «{0}». Puede que esté muy lejos; compruébalo, por favor.",
   "swap.guessedByRole": "Lo deduzco por la función: un punto debajo de la nueva fuente tiene la misma función «{0}». Por favor, compruébalo.",
   "swap.higherLevel": "Un nivel más arriba ({0}) encuentra un objetivo para {1} de {2} puntos; aquí solo {3}.",
   "swap.keeps": "El alias conserva su identificador, sus nombres, sus roles y sus fórmulas, su historial en la base de datos, así como su sala y su función. Lo único que cambia es el origen y el destino de las lecturas y escrituras de cada punto.",
+  "swap.loadingValues": "Leyendo el nuevo aparato …",
   "swap.mapping": "Cartografía",
   "swap.mind": "Cuidado:",
   "swap.mindHint": "Las fórmulas de los alias se mantienen tal y como están: si la nueva fuente se escala de forma diferente, los valores serán erróneos posteriormente. La fórmula se encuentra en la fila de detalles del punto.",
@@ -424,13 +467,27 @@
   "swap.noMatch": "No se ha encontrado ningún punto coincidente",
   "swap.noWriteMatch": "No se ha encontrado ningún destino de escritura: este punto no se escribirá en ningún sitio",
   "swap.now": "Cambia ahora",
+  "swap.pickByHand": "… o elija usted mismo un punto",
   "swap.pickFirst": "Elige primero una nueva fuente.",
   "swap.removeIt": "eliminar este punto al intercambiar",
   "swap.same": "Es la misma fuente que antes.",
   "swap.search": "Buscar (ID o nombre) …",
+  "swap.suggestionHint": "Una sugerencia del etiquetado — al pulsar se pone en el campo. Compruébela con los dos valores de arriba: la etiqueta puede estar mal.",
   "swap.title": "Intercambiar fuente",
   "swap.to": "Nueva fuente",
+  "swap.tplDrop": "Quitar también la plantilla recordada ({0} objetos)",
+  "swap.tplFormulas": "Las fórmulas de {0} puntos se sustituyen de todos modos por las del nuevo aparato — pertenecen a la fuente, no al alias. Cada fila muestra lo que quedará.",
+  "swap.tplGone": "Esta plantilla ya no existe.",
+  "swap.tplOther": "Otra plantilla encaja con la nueva fuente: «{0}». Puede aplicarla tras el cambio desde la selección de plantillas — trae sus propias fórmulas y nombres.",
+  "swap.tplStale": "La plantilla recordada «{0}» no encaja con la nueva fuente",
   "swap.unchanged": "sin cambios",
+  "swap.unitChanged": "Unidad: en el alias {0} · nueva fuente: {1}",
+  "swap.unitField": "Unidad en el alias",
+  "swap.unitHistWarn": "Hay un registro asociado a este punto. Su histórico está en la unidad antigua — una serie que cambia de factor a mitad no se puede reparar.",
+  "swap.unitNoFactor": "Sin conversión: estas dos unidades no son un par conocido.",
+  "swap.unitNone": "ninguna",
+  "swap.unitResult": "Resultado: {0} {1}",
+  "swap.unitValOld": "Su alias muestra hoy: {0} {1}",
   "swap.unknown": "(no se puede determinar)",
   "target.alsoRoom": "¿También se debe establecer la sala en «{0}»?",
   "target.alsoRoomNew": "No existe la carpeta «{0}»: ¿quieres crearla y asignarla?",
@@ -574,11 +631,19 @@
   "tpls.whichNumber": "Número de esta salida",
   "tpls.wissen": "+ {0} estados más como información de rol — se utiliza en la vista «Todos los puntos de datos del dispositivo»",
   "tree.aliases": "Editar alias",
+  "tree.branchAdd": "Añadir esta rama a la selección",
+  "tree.branchForeign": "Esas ramas no están en la misma instancia. Un aparato vive en una instancia — elija ramas con un nodo padre común.",
+  "tree.branchHint": "Algunos adaptadores reparten un aparato entre ramas hermanas — Matter pone el interruptor en una y las medidas en otra. Varias ramas forman juntas un aparato. Lo mismo que Ctrl+clic.",
+  "tree.branchRemove": "Quitar esta rama de la selección",
   "tree.collapseAll": "ocultar todo",
   "tree.emptyNode": "No hay datos: el nodo existe en la base de datos, pero está vacío.",
   "tree.expandAll": "Mostrar todo",
+  "tree.exportMock": "Exportar como dispositivo simulado",
+  "tree.exportMockHint": "Escribe todo lo que hay debajo de {0} en un archivo: objetos y valores actuales, sin native",
   "tree.filter": "filtrar …",
   "tree.filterAria": "Filtrar objetos",
+  "tree.importMock": "Importar dispositivo simulado …",
+  "tree.importMockHint": "Siempre acaba bajo {0} — nunca en la ruta original",
   "tree.loading": "Cargando objetos…",
   "tree.looksLikeDevice": "parece un único dispositivo",
   "tree.noObjectHint": "no es una carpeta real",