iobroker.alias-workbench 0.9.0 → 0.9.7

package/README.md

@@ -567,6 +567,83 @@ imported, and that both language files carry the same keys.
 
 ## Changelog
 
+### 0.9.7
+This version was measured on the **production system** — 24,786 objects, 140 aliases. None of it shows on the test system with 2,731 objects.
+
+* The search box no longer blocks. The tree was rebuilt completely on **every** keystroke: a measured **236 ms per keystroke, 1.9 seconds for eight**. It now draws once, 180 ms after the last keystroke — typing stays responsive. Plus three savings in the tree itself: collapsed nodes are no longer built as DOM at all (previously every subtree was created and immediately thrown away), the question “can this be expanded?” is answered once per row instead of on every sort comparison, and an `Intl.Collator` replaces `localeCompare` with an options object. **The whole tree: 263 → 67 ms.**
+* A redraw no longer costs half a second. `kindZustaende`, `aliasFuer` and their neighbours walked the sorted index **linearly** — 24,786 comparisons for ten hits, some twenty times per redraw, and with live values that is every 700 ms. The list is sorted and the range sits together: a binary search finds it in fifteen steps. Plus a reverse map source → alias built once per index state. **Drawing a source 15.8 → 1.6 ms, an alias with 50 points 51.9 → 14.2 ms.** Proven equal: 3,025 devices and all 727 alias points checked against the old versions, zero differences
+* A read formula can no longer freeze the tab for good. Formulas from `common.alias.read` and from templates run as JavaScript in the admin — on every redraw, per row, unasked. That is no new privilege escalation (whoever may write the formula already has it running in the js-controller), but it is an execution site without limits: `try/catch` does not catch an endless loop. Results are now remembered per formula and raw value — 2000 evaluations in 0.6 ms — and whatever once took longer than 250 ms does not run again; the row says why
+* The object counter in the header no longer gets stuck. Four places set the index directly instead of calling `indexNeu()`, so the short-name map kept deleted ids and `hatPunkt` returned hits on points that no longer existed
+* A full detector run per redraw is gone. Its result travelled through two intermediate steps into a parameter nobody reads. Also removed: `e.andere` and the dead symbols `bestandsWert` and `anzeigeText`
+* The write-source rule lives in one place instead of five. It was spelled out identically three times in `entwurf.js` and twice in `zuordnung.js` — and the comments at two of those sites each document a bug that came from exactly that
+* **Correction to 0.9.6:** adapter and instance roots were meant to become unselectable there — but the check used `_tiefe`, which is the height of the subtree **below** a node, not its position in the tree. On the test system that excluded 131 nodes, exactly one of them rightly: the other 130 were branches such as `…Decklenlicht_RGB.cmnd` and folders such as `iot.0.smart`, whose data points sit directly below. Selectable nodes dropped from 449 to 320. The position is checked now; `mqtt-client` and `mqtt-client.0` stay locked, everything else is back
+
+### 0.9.6
+**Display and flow**
+* “All data points” keeps the output and the manual choice. On a multi-output template at output 2 the rows of output 1 came back while the target still read `…Ausgang_2`; and if automatic matching had found nothing and you picked the template by hand, the click dropped you into raw mode with the choice gone
+* “Differs from the alias” now also shows in alias mode. The marker was handed the target, which is never set there — you are already standing on the alias. So it never appeared exactly where it says the most
+* Switching sources quickly no longer fetches the wrong value. The callback stored the value under whatever source was selected when it arrived — and since only missing values are fetched, it stayed that way
+* The source jump list never appears twice. It hangs off the page body so it survives an automatic redraw; the button is a different one afterwards, and the second click laid a second list over the first
+* A room is suggested even when it is the last segment. With a flat adapter such as `sonoff.0.Wohnzimmer` the search over the source path never ran at all
+* Object names follow the admin language. There were two readers for the same question, one fixed on German before English — so on an English admin, objects, rooms and functions showed up in German. And the name match now looks at every language: “Light” in the system failed to find the function “Licht” and created a duplicate beside it
+
+**MQTT and Tasmota**
+* An empty `custom` entry no longer takes anything down. `common.custom` can hold an entry whose value is `null` — ioBroker does not clean it up when an instance disappears. Reaching into it took the whole result view with it
+* `enabled: false` counts as switched off. The field did not appear in the reader at all: `{ enabled: false, publish: true }` counted as publishable although the instance does not serve that point
+* No more false “cannot publish” for ioBroker.mqtt and sonoff. Their objects carry the topic in `native` only; that was reported as a firm “no” instead of “unknown”, the chip was red, and “allow publishing” wrote the object back unchanged — a message that could not be cleared
+* “Answer received” only for a real answer. A `stat.RESULT` left retained from the day before yesterday was enough for the green feedback, even with the device switched off
+* `Vcc` and `Command` are not commands. `{"Command":"Unknown"}` — the reply to an unknown command — stood there as a missing command point, with a create button
+* Command names from foreign JSON no longer reach ids and topics unchecked. A key containing `#` would make a wildcard subscription, one containing `.` an extra level
+
+**Templates and devices**
+* The blind gets its STOP. A button press has no state to read, and that case was unknown to template application: without a read path the point dropped out — not a single blind alias ever had a STOP
+* ON_TIME finds its slot. Four templates carried the role `level.timer` while the slot requires `level.timer.off`, so the point ended up in the info device instead of the switching device
+* An explicit formula beats the field. Where a template gives both, the formula was discarded and a new one built from the field
+
+**Subscriptions and tree**
+* What is subscribed is what is read — not half the adapter. The patterns came from the display grouping: on a flat MQTT device that produced `mqtt-client.0.*` with over three hundred objects on a single alias. It is now the channels of the actual sources, branches of the same device folded into one pattern, and where even that is too wide, the sources one by one
+* Adapter and instance roots can no longer be selected. `mqtt-client.0` is not a device; selecting it would have subscribed the whole namespace
+* Dark admin themes are recognised. The detection knew four names; `blue` and `colored` fell through and landed on the system setting
+* A late answer to `system.config` still counts. After 2.5 seconds it carries on without one — the answer arriving later was discarded entirely, and without it every expert object was missing from the tree
+
+**Housekeeping**
+* The checks touch nothing again. One of them wrote an object from inside the drawing path
+* The delete dialog warns about channels of their own below the target. The hint spoke only of “data points below”
+* Four dead language keys removed — and the test now checks both directions, not just code → JSON
+
+### 0.9.5
+* A broken name hint no longer takes down the whole source view. The text was evaluated as a regular expression unchecked, although neither the template sheet nor the save dialog validates it: after saving `Lampe (Bad`, template matching threw on **every** device selection, no caller caught it, and the right-hand side stayed empty — repairable only through the instance configuration by hand. An unusable expression now counts as “no match” and is flagged in red at the field. The same goes for the nested form `(a+)+`, where the expression engine stalls: a measured 3196 ms for one device name, now none
+* The formula of a fallback source survives updating a template. It was stored under `formel` while every reader looks for `leseformel` — so updating from a device silently dropped it. With `tasmota-steckdose` the consequence was that on devices without `stat.POWER` the boolean alias ended up on the raw JSON text of `tele.STATE` instead of on `POWER`
+* A device type this detector does not know no longer throws. The offered pattern list was filtered, the **selected** type was not — it comes from the template unchecked. An imported template naming a pattern from a newer type-detector made the pattern picker throw, and the draft was never drawn at all
+* Importing now checks more than id and states. `erkennung.erforderlich` as a string instead of a list made template matching throw on **every** device afterwards; a missing `name` threw as soon as the sheet opened. And “import and save” was on screen long before that — you could save a template that then made the tab unusable. `erkennung`, `erforderlich`/`verboten`, `inhalt`, `name`, the name hint and the device type are checked now; a single string that unambiguously means a list is turned into one rather than rejected
+* A hand-typed id no longer replaces someone else's template. Ids were only checked for collisions when switching modes, not after typing — and saving replaces without asking on a matching id, in “new” mode even with version 1. An own template at v7 silently became a different one at v1. The reason is now shown in red at the field and saving is blocked
+* The `%N%` placeholder only hits the output number now. Replacement went purely by trailing digit: on a multi-output device at output 2 the IP row from `tele.INFO2` became `tele.INFO%N%` — and at output 1 that same row reported a foreign output, with “drop the others” throwing it out. Only what actually carries the output becomes a placeholder now: what the template already held as `%N%`, the prefix from `kanalname`, and what appears more than once with the same number
+
+### 0.9.4
+* The tab works again after a dropped connection. It does not load socket.io but the admin's WebSocket shim — and there `connect` fires exactly once per page lifetime, only `reconnect` afterwards. Nobody listened for that, and the shim renews no subscription on its own. After every outage — admin restart, network hiccup, standby — neither object nor state changes arrived, and the dot in the header stayed on “disconnected” although the connection had long been back. `reconnect` is now handled: the display goes back to “connected”, every subscription is renewed and the objects are re-read — anything could have changed while disconnected, and nobody was watching
+* The template mode no longer rebuilds itself every second. Selecting a device with live values and switching to the templates tab rebuilt the whole sheet every 700 ms, including a trial run across all candidates and all templates — the selection deliberately survives the mode switch, but there is no state list on the right any more
+* Where the selection goes, its subscriptions now go too. Unsubscribing only happened when selecting the next node; the four other paths — switching mode, collapsing a branch, leaving expert mode, deleting an alias — unsubscribed from nothing. A subscription then ran on a device no longer shown, and the header counter still claimed “one subscription”
+* Switching nodes while loading no longer leaves the caller hanging. The callback never arrived in that case: “running” stayed on the button forever, and the dry run meant to open after creating missing command points never opened. Twelve seconds of waiting on a SetOption59 query is ample opportunity for that
+
+### 0.9.3
+* An error on the enumerations now stops the move. The first step — creating the new one — always aborted on error, “two rather than none”; the second did not: enumeration errors were collected and the old one was deleted anyway. Afterwards the old alias was gone and the new one sat in no enumeration at all, because the js-controller removes members itself on delete. The assignment was therefore lost outright, not merely orphaned. The same abort now applies one level down, and the button offers “Try again”
+* A partial failure while deleting no longer turns the retry button into a prop. If one delete failed, **all** ids were dropped from the internal store anyway, empty folders and enumerations were cleaned up and the delete target was set to null — which is exactly what `loescheAlias` starts with, so it bailed out immediately. Whatever stayed in the database was out of reach: the workbench considered it deleted. Only what really went is dropped now, the cleanup is skipped, the target stays — and the second click actually finishes the job
+* Orphaned points are deleted on the second attempt too. Their list was cleared after writing **always**, even after a failure; the retry button then wrote the objects but removed nothing, and the message no longer counted them either
+* A load error on your own templates is reported instead of swallowed. If the instance configuration answered with an error, that counted as “no own templates” — the warning chip in the header stayed away, although the timeout path one line above sets it correctly. The consequence was the dangerous part: the workbench considered taken ids free, and the next save would have replaced an existing template with version 1. The chip's tooltip now says so
+
+### 0.9.2
+* Swapping the source no longer writes to the read source: if no new write target is found for a point with separate sources, a plain string was left in `alias.id` — and to the js-controller that means “read and write on the same id”. With Tasmota the command then went to the status topic instead of the command topic: the device does not switch and the feedback is falsified. Worse, the workbench guessed the write source by name and landed on `stat.POWER`, because that too contains “POWER”. A guessed write target now only counts if it is a different point from the read source, the object form is kept, and the row marks the missing match in red
+* Moving recognises two more targets as a collision: one that exists only as a tree node carrying data points — existing points of the same name were overwritten there — and one that sits below the alias itself: `alias.0.X` to `alias.0.X.Sub` took its own parent node along on the final delete
+* A rejected creation of a send point no longer counts as success. The silent path did not even accept the error and entered the object into its own store anyway; after that the guard no longer bit, and “Create now” wrote `alias.id.write` onto an id that never existed in the database — exactly the error the js-controller remembers for good
+* Channel names are cleaned into ids when “Create all” builds one channel per output. “Licht Bar, oben” produced an id with a space and a comma, “Küche.Decke” an extra level including an intermediate folder. And the js-controller does not reject that, it cleans silently — so the object would have appeared under a different id than the one shown. The display name is left untouched
+* A channel keeps its template link across an update, even when the template was deleted or renamed. `native` used to be replaced wholesale; template, version and device type only came back when a template happened to match. The role one line below had long been rescued, `native` had not
+* Hardened: the cleanup of separated sources no longer switches off a point that is itself part of the alias. Whether it happened depended on the order of `Object.keys` — it was not reachable through the interface, because none of the bundled templates puts a reporting row before the controlling one, but the consequence would have been a deleted data point
+
+### 0.9.1
+* A load error on the enumerations can no longer overwrite one: until now a failed `getObjectView` set the store to empty and kept quiet about it. After that the workbench considered every enumeration absent, the catalogue kept offering them because the duplicate filter had nothing to check against, and on writing `setObject` replaced the existing object with a fresh one holding a single member — measured, a room lost three of its four members that way and was given the origin mark that makes it deletable later on. The previous state is now kept, no enumeration is touched, and both the field and the dry run say why room and function are not being written. The alias itself is still created, and a hiccup heals itself after three attempts
+* An enumeration deleted from outside is no longer resurrected: the subscription compared against `objects`, where enumerations never live — on deletion old and new value were therefore both empty and the branch that removes it from the store was never reached. The next alias using that room recreated it with all its old members, including the foreign ones
+* “Create all” now gives every channel its room and its function. The partial drafts carried neither, so not a single channel got an entry — the single route set it, the bulk route did not. A second object for the same enumeration was also discarded, so even then only the first channel would have made it in. And for a channel other than the one shown the assignment counted as empty: if its alias already sat in a room, the bulk route took it **out**. Every channel now keeps what it has, all others get what is set, and members are merged instead of discarded
+
 ### 0.9.0
 * The role list is complete again: the detector hands out the expressions of its slots as text WITH slashes (`/^indicator…$/`), not as a regular expression. Take the slashes for part of the expression and you find neither start nor end afterwards — 210 roles instead of 232, and `indicator.lowbat` of all things was missing, the role every Homematic device writes. In the role picker, no slot of the pattern was offered at all any more, only the line "show all roles"
 * From the same cause, BRIGHTNESS lost its role in six colour-light patterns — the slot could be added over and over and could not be filled by any route. Seven places in the code read a slot expression; they all go through one function now, and a test checks the role list against what the detector actually delivers instead of against hand-written expressions

package/admin/geraetewissen/tasmota-befehle.json

@@ -11,7 +11,9 @@
     "IPAddress",
     "StatusSTS",
     "Wifi",
-    "Berry"
+    "Berry",
+    "Vcc",
+    "Command"
   ],
   "befehle": {
     "POWER": {

package/admin/i18n/de.json

@@ -132,6 +132,7 @@
   "enums.room": "Raum",
   "enums.roomHint": "Ordnet den Alias einem Raum zu. Das steht nicht am Objekt, sondern in der Aufzählung „enum.rooms\" — Alexa, Google und die Oberflächen gruppieren danach.",
   "enums.suggested": "vorgeschlagen",
+  "enums.unknown": "Aufzählungen nicht geladen — Raum und Funktion bleiben unangetastet.",
   "enums.unused": "leer",
   "enums.willCreate": "neu anlegen",
   "folder.aliasMissing": "fehlt",
@@ -165,12 +166,9 @@
   "help.aliasesAdd": "Zum Hinzufügen von Punkten in einem Alias ist der Weg über „zur Quelle →“ (rechts oben neben dem Alias-Namen) bequemer: Dort greift die Vorlage, und alle Datenpunkte des Geräts stehen mit fertigen Rollen zur Auswahl — hier müsstest du jeden einzeln von Hand eintragen.",
   "help.sources": "Links ein Gerät oder einen Kanal wählen. Die Werkbank erkennt, worum es sich handelt, und schlägt einen fertigen Alias vor. Gibt es ihn schon, wird er stattdessen aktualisiert.",
   "help.templates": "Links eine Vorlage wählen. Mitgelieferte lassen sich ansehen und duplizieren, eigene bearbeiten. Der Probelauf zeigt, welche Geräte sie trifft.",
-  "info.countedSeparately": "für die meisten ohne Folgen",
   "info.dlgTitle": "Gehört nicht zum {0}-Muster",
   "info.explain": "funktionieren ganz normal und liegen da, wo du sie angelegt hast. Es entsteht dadurch kein zusätzliches Objekt — der Alias bleibt, wie er ist. Sie gehören nur nicht zu dem, was ioBroker unter einem {0} versteht; dafür passt ihre Rolle nicht. Bedeutung hat das erst, wenn du den Alias an Alexa, Google Home oder eine Gerätesteuerung hängst: die sehen dann ein {0} ohne diese Punkte. In VIS, in Skripten und im Verlauf benutzt du sie wie jeden anderen Datenpunkt.",
   "info.more": "Was das bedeutet",
-  "info.notPartOf": "Gehört nicht zum {0}",
-  "info.sameDatapoints": "{0} — ",
   "leave.body": "An {0} sind Änderungen offen, die noch nicht geschrieben wurden. Wechselst du jetzt, sind sie weg.",
   "leave.discard": "Verwerfen und wechseln",
   "leave.stay": "Hierbleiben",
@@ -208,6 +206,7 @@
   "move.exists": "{0} gibt es schon. Erst entfernen oder einen anderen Namen wählen.",
   "move.from": "von",
   "move.needName": "Ein Name muss stehen bleiben.",
+  "move.nested": "Das Ziel liegt unter dem Alias selbst (oder umgekehrt). Beim Verlegen würde der eigene Elternknoten mitgelöscht — bitte einen Ort daneben wählen.",
   "move.newFolder": "Ordner neu",
   "move.noFolder": "(kein Ordner — direkt unter alias.0)",
   "move.noScripts": "In den Skripten kommt die Kennung nicht vor.",
@@ -284,7 +283,6 @@
   "pattern.manualInstead": "von Hand statt {0}",
   "pattern.missing": "{0} fehlt",
   "pattern.noMatch": "kein Muster passt zu „{0}“",
-  "pattern.noPlaceIn": "kein Platz im {0}-Muster",
   "pattern.noPlaceLegend": "So hinterlegte Zeilen haben keinen Platz im {0}-Muster",
   "pattern.noPlaceLong": "kein Platz im {0}-Muster — der Punkt wird trotzdem angelegt und ist voll benutzbar, nur Alexa & Co. zählen ihn separat",
   "pattern.notDetected": "nicht erkannt",
@@ -335,6 +333,7 @@
   "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.",
   "swap.noDevice": "Kein Gerät gefunden.",
   "swap.noMatch": "kein passender Punkt gefunden",
+  "swap.noWriteMatch": "kein Schreibziel gefunden — dieser Punkt schreibt danach nirgendwohin",
   "swap.now": "Jetzt tauschen",
   "swap.removeIt": "diesen Punkt beim Tauschen entfernen",
   "swap.same": "Das ist dieselbe Quelle wie bisher.",
@@ -424,7 +423,7 @@
   "tpls.id": "Kennung",
   "tpls.json": "Das wird gespeichert",
   "tpls.loadFailed": "eigene Vorlagen nicht geladen",
-  "tpls.loadFailedHint": "Die Instanzkonfiguration hat nicht rechtzeitig geantwortet. Deine eigenen Vorlagen sind nicht verschwunden — sie fehlen nur in dieser Ansicht. Seite neu laden.",
+  "tpls.loadFailedHint": "Die Instanzkonfiguration hat nicht geantwortet oder einen Fehler gemeldet. Deine eigenen Vorlagen sind nicht verschwunden — sie fehlen nur in dieser Ansicht. Solange dieser Hinweis steht, kann ein Speichern eine vorhandene Vorlage überschreiben: erst neu laden.",
   "tpls.losesTo": "verliert gegen {0}",
   "tpls.multiple": "Dieses Gerät hat mehrere Ausgänge",
   "tpls.multipleHelp": "Die {0} in den Pfaden wird durch %N% ersetzt — nur am Ende eines Abschnitts, damit ENERGY.Power heil bleibt.",
@@ -549,6 +548,7 @@
   "write.dryTitleFailed": "Nicht alles ist durchgegangen",
   "write.dryTitleUpdate": "Alias aktualisieren — das würde entstehen",
   "write.duplicateName": "{0}: Name kommt doppelt vor.",
+  "write.enumsUnknown": "Raum und Funktion werden nicht geschrieben: die Aufzählungen konnten nicht geladen werden. Der Alias selbst entsteht wie gezeigt. Ohne verlässlichen Stand würde eine vorhandene Aufzählung durch eine frische mit nur diesem einen Mitglied ersetzt.",
   "write.failed": "{0} Vorgänge gingen schief:",
   "write.new": "neu",
   "write.noName": "Ein Punkt hat keinen Namen.",
@@ -575,5 +575,16 @@
   "write.willKeep": "bleiben stehen: {0}",
   "write.willRemove": "entfernt: {0}",
   "write.writeSourceMissing": "{0}: den Sendepunkt {1} gibt es noch nicht",
-  "write.writing": "schreibe …"
+  "write.writing": "schreibe …",
+  "tpls.idTaken": "Diese Kennung gehört schon „{0}“ (v{1}). Speichern würde sie ersetzen.",
+  "tpls.nameHintBad": "Kein brauchbarer Ausdruck — er zählt als „trifft nicht“.",
+  "tv.badName": "Der Name muss ein Text oder ein Sprachobjekt sein.",
+  "tv.badRecog": "„erkennung“ muss ein Objekt sein.",
+  "tv.badList": "„{0}“ muss eine Liste von Punkten sein.",
+  "tv.badContent": "„erkennung.inhalt“ muss ein Objekt sein.",
+  "tv.badNameHint": "Der Namenshinweis ist kein brauchbarer Ausdruck.",
+  "tv.badType": "Den Gerätetyp „{0}“ kennt dieser Detector nicht.",
+  "check.sendUnknown": "Ob {0} senden darf, steht nicht im Objekt — das Thema liegt nur in `native`. Bei ioBroker.mqtt und sonoff ist das normal.",
+  "del.channelsBelow": "Achtung: {0} eigenständige Kanäle liegen darunter und werden mitgelöscht.",
+  "detail.formulaTooSlow": "Diese Formel hat {0} ms gebraucht und wird nicht mehr ausgeführt. Nach dem Neuladen des Reiters wird sie einmal neu versucht."
 }

package/admin/i18n/en.json

@@ -132,6 +132,7 @@
   "enums.room": "Room",
   "enums.roomHint": "Assigns the alias to a room. This is not stored on the object but in the \"enum.rooms\" enumeration — Alexa, Google and the dashboards group by it.",
   "enums.suggested": "suggested",
+  "enums.unknown": "Enumerations not loaded — room and function stay untouched.",
   "enums.unused": "empty",
   "enums.willCreate": "create new",
   "folder.aliasMissing": "missing",
@@ -165,12 +166,9 @@
   "help.aliasesAdd": "To add points to an alias, the way via “to the source →” (top right, next to the alias name) is easier: the template applies there, and every data point of the device is offered with a ready role — here you would have to enter each one by hand.",
   "help.sources": "Pick a device or channel on the left. The workbench recognises what it is and proposes a finished alias. If one already exists, it is updated instead.",
   "help.templates": "Pick a template on the left. Bundled ones can be viewed and duplicated, your own edited. The trial run shows which devices it matches.",
-  "info.countedSeparately": "no consequences for most setups",
   "info.dlgTitle": "Not part of the {0} pattern",
   "info.explain": "work perfectly normally and stay where you created them. Nothing extra is written — the alias stays as it is. They simply are not part of what ioBroker considers a {0}; their role does not fit any of its slots. It only starts to matter once you hand the alias to Alexa, Google Home or a device UI: those will see a {0} without these points. In VIS, in scripts and in history you use them like any other datapoint.",
   "info.more": "What this means",
-  "info.notPartOf": "Not part of the {0}",
-  "info.sameDatapoints": "{0} — ",
   "leave.body": "There are changes on {0} that have not been written yet. Switching now discards them.",
   "leave.discard": "Discard and switch",
   "leave.stay": "Stay here",
@@ -208,6 +206,7 @@
   "move.exists": "{0} already exists. Remove it first or pick another name.",
   "move.from": "from",
   "move.needName": "A name is required.",
+  "move.nested": "The target sits below the alias itself (or the other way round). Moving would delete its own parent node — please pick a place beside it.",
   "move.newFolder": "new folder",
   "move.noFolder": "(no folder — directly under alias.0)",
   "move.noScripts": "The ID does not appear in any script.",
@@ -284,7 +283,6 @@
   "pattern.manualInstead": "by hand instead of {0}",
   "pattern.missing": "{0} missing",
   "pattern.noMatch": "no pattern matches \"{0}\"",
-  "pattern.noPlaceIn": "no slot in the {0} pattern",
   "pattern.noPlaceLegend": "Rows shaded like this have no slot in the {0} pattern",
   "pattern.noPlaceLong": "no slot in the {0} pattern — the point is still created and fully usable, only Alexa and friends count it separately",
   "pattern.notDetected": "not detected",
@@ -335,6 +333,7 @@
   "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.",
   "swap.noDevice": "No device found.",
   "swap.noMatch": "no matching point found",
+  "swap.noWriteMatch": "no write target found — this point will not write anywhere",
   "swap.now": "Swap now",
   "swap.removeIt": "remove this point while swapping",
   "swap.same": "That is the same source as before.",
@@ -424,7 +423,7 @@
   "tpls.id": "Id",
   "tpls.json": "This is what gets stored",
   "tpls.loadFailed": "own templates not loaded",
-  "tpls.loadFailedHint": "The instance configuration did not answer in time. Your own templates are not gone — they are only missing from this view. Reload the page.",
+  "tpls.loadFailedHint": "The instance configuration did not answer or reported an error. Your own templates are not gone — they are only missing from this view. While this notice stands, saving may overwrite an existing template: reload first.",
   "tpls.losesTo": "loses to {0}",
   "tpls.multiple": "This device has several outputs",
   "tpls.multipleHelp": "The {0} in the paths is replaced by %N% — only at the end of a segment, so ENERGY.Power stays intact.",
@@ -549,6 +548,7 @@
   "write.dryTitleFailed": "Not everything went through",
   "write.dryTitleUpdate": "Update alias — this is what would appear",
   "write.duplicateName": "{0}: name appears twice.",
+  "write.enumsUnknown": "Room and function will not be written: the enumerations could not be loaded. The alias itself is created as shown. Without a reliable state an existing enumeration would be replaced by a fresh one holding just this single member.",
   "write.failed": "{0} operations failed:",
   "write.new": "new",
   "write.noName": "One point has no name.",
@@ -575,5 +575,16 @@
   "write.willKeep": "kept: {0}",
   "write.willRemove": "removed: {0}",
   "write.writeSourceMissing": "{0}: the send datapoint {1} does not exist yet",
-  "write.writing": "writing …"
+  "write.writing": "writing …",
+  "tpls.idTaken": "This id already belongs to “{0}” (v{1}). Saving would replace it.",
+  "tpls.nameHintBad": "Not a usable expression — it counts as “no match”.",
+  "tv.badName": "The name must be a string or a language object.",
+  "tv.badRecog": "“erkennung” must be an object.",
+  "tv.badList": "“{0}” must be a list of points.",
+  "tv.badContent": "“erkennung.inhalt” must be an object.",
+  "tv.badNameHint": "The name hint is not a usable expression.",
+  "tv.badType": "This detector does not know the device type “{0}”.",
+  "check.sendUnknown": "Whether {0} may publish is not stated in the object — the topic sits in `native` only. Normal for ioBroker.mqtt and sonoff.",
+  "del.channelsBelow": "Careful: {0} channels of their own sit below this and will be deleted too.",
+  "detail.formulaTooSlow": "This formula took {0} ms and is no longer executed. Reloading the tab gives it one more try."
 }

package/admin/js/aufzaehlungen.js

@@ -221,8 +221,18 @@ export function raumVorschlag(e) {
 
   /* 3. Aus dem Pfad der Quelle */
   if (quelle) {
+    /* Von hinten, das LETZTE Segment eingeschlossen.
+
+       Frueher begann die Schleife eins davor — gedacht fuer
+       `…Wohnzimmer.Lampe`, wo hinten das Geraet steht. Bei einem flachen
+       Adapter wie `sonoff.0.Wohnzimmer` IST das letzte Segment aber der
+       Raum, und die Schleife lief kein einziges Mal: kein Vorschlag,
+       obwohl der Raum im Namen steht (gemessen 09.09.2026 —
+       `sonoff.0.Wohnzimmer.Lampe` ergab `enum.rooms.living_room`,
+       `sonoff.0.Wohnzimmer` nichts). Der Weg ueber den Geraetenamen
+       faengt es nicht auf: der geht bei Name gleich Segment leer aus. */
     var qt = quelle.split('.');
-    for (var j = qt.length - 2; j >= 2; j--) {
+    for (var j = qt.length - 1; j >= 2; j--) {
       var qr = suche(qt[j]);
       if (qr) { return qr; }
     }

package/admin/js/baum.js

@@ -8,7 +8,7 @@ import { S } from './zustand.js';
 import { $, el } from './basis.js';
 import { tr, txt, expertenVorgabe } from './sprache.js';
 import './enums.js';
-import { mitNachfrage } from './entwurf.js';
+import { mitNachfrage, aboLoesen } from './entwurf.js';
 import { zeichneErgebnis } from './ergebnis.js';
 import { zeichneVorlagenListe } from './vorlagenblatt.js';
 
@@ -70,7 +70,7 @@ window.addEventListener('storage', function (e) {
   /* Steht die Auswahl in einem Zweig, den es gleich nicht mehr gibt, muss
      sie weg — sonst zeigt die rechte Seite ein Geraet, das links fehlt. */
   if (S.current && !experte() && nurFuerExperten(S.current, S.objects[S.current])) {
-    S.current = null;
+    S.current = null; aboLoesen();
     S.entwurf = null;
   }
   zeichneBaum();
@@ -94,10 +94,6 @@ export function zusatzName(id) {
   return (n === String(id).split('.').pop()) ? '' : n;
 }
 
-/* Wonach die Zeile gelesen und sortiert wird. */
-export function anzeigeText(k) {
-  return zusatzName(k.id) || k.name;
-}
 
 function baueBaum() {
   var wurzel = { kinder: {}, id: '', name: '' };
@@ -152,6 +148,33 @@ function zaehleZustaende(k, eltern) {
 }
 
 
+/* Ist dieser Knoten aufgeklappt?
+
+   Stand frueher mitten im Zeichnen einer Zeile — und damit erst,
+   nachdem der ganze Teilbaum schon als DOM entstanden war. Fuer
+   „zugeklapptes gar nicht erst zeichnen" muss die Antwort vorher da
+   sein, also hier. */
+function klappStand(k, tiefe) {
+  if ((($('#q') || {}).value || '').trim()) { return true; }
+  var vorgabe = (S.alleKlapp === null) ? (tiefe <= 1) : S.alleKlapp;
+  /* Im Aliasbaum gibt es unterhalb der Wurzel nur eigene Ordner - ganz
+     zugeklappt bliebe eine einzige Zeile `alias` uebrig, und jeder Weg
+     begaenne mit zwei Pflichtklicks. Bis `alias.0` bleibt deshalb offen.
+     Das steht hier und nicht im Zuklapp-Knopf: sonst gilt es nur, wenn
+     man IM Aliasmodus zuklappt - wer in den Quellen zuklappt und dann
+     herueberwechselt, fand den Baum zu weit zu (Ricardo, 25.08.2026).
+     Einzeln zuklappen darf man sie weiterhin, `S.aufgeklappt` gewinnt. */
+  if (S.baumModus === 'aliase' && (k.id === 'alias' || k.id === 'alias.0')) {
+    vorgabe = true;
+  }
+  return S.aufgeklappt[k.id] !== undefined ? S.aufgeklappt[k.id] : vorgabe;
+}
+
+/* Ein Vergleicher fuer den ganzen Baum. `localeCompare` mit
+   Optionsobjekt baut bei jedem Aufruf einen neuen — bei 24.800 Elementen
+   sind das je Sortierlauf zehntausende. */
+var VERGLEICH = new Intl.Collator(undefined, { numeric: true, sensitivity: 'base' });
+
 export function zeichneBaum() {
   if (S.baumModus === 'vorlagen') { return zeichneVorlagenListe(); }
   S.baum = baueBaum();
@@ -232,6 +255,23 @@ export function istWaehlbar(k) {
   /* Notbehelf nur dort, wo im ganzen Zweig keine Typen gepflegt sind.
      Wo es getypte Kanäle gibt, sollen die das Gerät sein. */
   if (k._hatTypen) { return false; }
+  /* Aber niemals die Wurzel selbst.
+
+     `mqtt-client` und `mqtt-client.0` sind kein Geraet, sondern der
+     Adapter und seine Instanz. Waehlbar waren sie trotzdem, sobald im
+     Zweig keine Typen gepflegt sind — und die Auswahl abonniert
+     `<id>.*` und holt die Werte des ganzen Namensraums (am Testsystem
+     322 Objekte, in einer gewachsenen Anlage ein Vielfaches). Aufklappen
+     ja, auswaehlen nein.
+
+     Gemeint ist die STELLE im Baum, nicht `_tiefe`: Das ist die Hoehe
+     des Teilbaums UNTER dem Knoten, nicht seine Position darin. In
+     0.9.6 stand hier `k._tiefe <= 1`, und das schloss am Testsystem 131
+     Knoten aus — genau einen davon zu Recht. Die anderen 130 waren
+     Sparten wie `…Decklenlicht_RGB.cmnd` und Ordner wie `iot.0.smart`,
+     also Knoten, deren Datenpunkte direkt darunter liegen (gefunden
+     10.09.2026 beim Nachmessen von B23). */
+  if (k.id.split('.').length <= 2) { return false; }
   /* Sonst: alles waehlbar. Was ein Geraet ist, weiss nur der Mensch —
      bei Duneweaver ist es der Knoten darueber, bei Tasmota der darunter.
      Statt zu sperren wird geraten (siehe wohlGeraet) und gewarnt. */
@@ -271,12 +311,17 @@ function renderKinder(knoten, filter, tiefe) {
       return c._zust && !(c.art === 'state' && !Object.keys(c.kinder).length);
     });
   }
+  /* Einmal je Reihe, nicht bei jedem Vergleich.
+
+     `klappbar` laeuft ueber alle Enkel, und ein Sortiervergleich ruft es
+     zweimal — bei n Reihen also 2·n·log(n) Enkel-Schleifen statt n.
+     Dasselbe gilt fuer `localeCompare` mit Optionsobjekt: Das baut je
+     Aufruf einen neuen Vergleicher. Ein `Intl.Collator` tut dasselbe
+     einmal. */
+  reihen.forEach(function (r) { r.kl = klappbar(r.k) ? 0 : 1; r.txt = String(r.zus || r.k.name); });
   reihen.sort(function (a, b) {
-    var ba = klappbar(a.k) ? 0 : 1;
-    var bb = klappbar(b.k) ? 0 : 1;
-    if (ba !== bb) { return ba - bb; }
-    return String(a.zus || a.k.name).localeCompare(String(b.zus || b.k.name),
-      undefined, { numeric: true, sensitivity: 'base' });
+    if (a.kl !== b.kl) { return a.kl - b.kl; }
+    return VERGLEICH.compare(a.txt, b.txt);
   });
 
   reihen.forEach(function (reihe) {
@@ -320,8 +365,21 @@ function renderKinder(knoten, filter, tiefe) {
       ? true
       : (!leer && (k.id.toLowerCase().indexOf(filter) !== -1 ||
                    (reihe.zus && reihe.zus.toLowerCase().indexOf(filter) !== -1)));
-    var kinderUl = renderKinder(k, filter, tiefe + 1);
-    var kinderPassen = kinderUl.childNodes.length > 0;
+    /* Zugeklappte Knoten gar nicht erst zeichnen.
+
+       Vorher entstand IMMER der ganze Teilbaum als DOM — auch der eines
+       zugeklappten Knotens, der gleich darauf weggeworfen wurde. Bei
+       einer gewachsenen Anlage ist das der ganz ueberwiegende Teil der
+       Arbeit.
+
+       Zwei Ausnahmen, in denen der Teilbaum gebraucht wird: beim Filtern
+       (ein Treffer weiter unten macht den Elternknoten sichtbar) und
+       wenn der Knoten aufgeklappt ist. Sonst genuegt die Frage, OB es
+       zeigbare Kinder gibt — und die beantwortet `klappbar` ohne DOM. */
+    var aufJetzt = klappStand(k, tiefe);
+    var brauchtKinder = !!filter || aufJetzt;
+    var kinderUl = brauchtKinder ? renderKinder(k, filter, tiefe + 1) : null;
+    var kinderPassen = kinderUl ? kinderUl.childNodes.length > 0 : klappbar(k);
     if (!passt && !kinderPassen) { return; }
 
     var li = el('li');
@@ -329,20 +387,8 @@ function renderKinder(knoten, filter, tiefe) {
     var d = el('div', 'node' + (waehlbar ? ' pick' : ' grp') + (leer ? ' leer' : '') +
       (k.id === S.current ? ' sel' : ''));
 
-    var hatKinder = kinderUl.childNodes.length > 0;
-    var vorgabe = (S.alleKlapp === null) ? (tiefe <= 1) : S.alleKlapp;
-    /* Im Aliasbaum gibt es unterhalb der Wurzel nur eigene Ordner - ganz
-       zugeklappt bliebe eine einzige Zeile `alias` uebrig, und jeder Weg
-       begaenne mit zwei Pflichtklicks. Bis `alias.0` bleibt deshalb offen.
-       Das steht hier und nicht im Zuklapp-Knopf: sonst gilt es nur, wenn
-       man IM Aliasmodus zuklappt - wer in den Quellen zuklappt und dann
-       herueberwechselt, fand den Baum zu weit zu (Ricardo, 25.08.2026).
-       Einzeln zuklappen darf man sie weiterhin, `S.aufgeklappt` gewinnt. */
-    if (S.baumModus === 'aliase' && (k.id === 'alias' || k.id === 'alias.0')) {
-      vorgabe = true;
-    }
-    var auf = filter ? true
-      : (S.aufgeklappt[k.id] !== undefined ? S.aufgeklappt[k.id] : vorgabe);
+    var hatKinder = kinderPassen;
+    var auf = aufJetzt;
     var tw = el('span', 'tw', hatKinder ? (auf ? '▾' : '▸') : '');
     if (hatKinder) {
       tw.addEventListener('click', function (e) {
@@ -394,13 +440,25 @@ function renderKinder(knoten, filter, tiefe) {
       });
     }
     li.appendChild(d);
-    if (hatKinder && auf) { li.appendChild(kinderUl); }
+    if (hatKinder && auf && kinderUl) { li.appendChild(kinderUl); }
     ul.appendChild(li);
   });
   return ul;
 }
 
-$('#q').addEventListener('input', zeichneBaum);
+/* Entprellt, nicht bei jedem Anschlag.
+
+   Der Baum wurde bei JEDEM Tastendruck komplett neu gebaut. Am
+   Produktivsystem mit 24.786 Objekten gemessen (10.09.2026): 236 ms je
+   Anschlag, acht Anschlaege 1,9 Sekunden — die Eingabe hinkte sichtbar
+   hinterher. 180 ms sind kurz genug, dass es nach dem Tippen sofort
+   dasteht, und lang genug, dass eine fluessig getippte Folge nur einmal
+   zeichnet. */
+var suchTimer = null;
+$('#q').addEventListener('input', function () {
+  if (suchTimer) { clearTimeout(suchTimer); }
+  suchTimer = setTimeout(function () { suchTimer = null; zeichneBaum(); }, 180);
+});
 
 /* Alles auf, alles zu. Die einzeln gemerkten Knoten fallen dabei weg -
    sonst bliebe ein Zweig zu, den man eben ausdruecklich zugeklappt hat,
@@ -416,7 +474,7 @@ function klappeAlle(auf) {
      Abschalten des Expertenmodus. Geprueft wird an der gezeichneten
      Liste, nicht an der Datenlage: sichtbar ist, was im Baum steht. */
   if (S.current && !auf && !imBaumSichtbar()) {
-    S.current = null;
+    S.current = null; aboLoesen();
     S.entwurf = null;
     S.openRow = null;
     zeichneErgebnis();
@@ -448,10 +506,10 @@ export function setzeModus(m) {
      Der Vorlagenbaum ist ausgenommen: er hat eine eigene Ansicht, und
      wer von dort zurueckwechselt, findet seine Auswahl wieder vor. */
   if (m === 'quellen' && S.current && S.current.indexOf('alias.') === 0) {
-    S.current = null; S.entwurf = null; S.openRow = null;
+    S.current = null; aboLoesen(); S.entwurf = null; S.openRow = null;
   }
   if (m === 'aliase' && S.current && S.current.indexOf('alias.') !== 0) {
-    S.current = null; S.entwurf = null; S.openRow = null;
+    S.current = null; aboLoesen(); S.entwurf = null; S.openRow = null;
   }
   /* Beim Moduswechsel den Filter fallen lassen und die Geraeteknoepfe
      zurueckholen. Sonst stand man im Vorlagenbaum vor „nichts gefunden"

package/admin/js/detail.js

@@ -149,7 +149,14 @@ export function detailZeile(e, s, idx) {
      Eine Zeile kann beides tragen — etwa nach einem Musterwechsel, der
      die Rolle anpasst: Die neue Rolle weicht dann vom Alias ab, und je
      nachdem auch von der Vorlage (Ricardo, 06.09.2026). */
-  var bstListe = bestandsAbweichung(s, e.ziel);
+  /* `e.ziel || e.kanal` — wie bei den beiden Nachbarn.
+
+     Im Aliasmodus ist `e.ziel` nie gesetzt: Man steht ja schon auf dem
+     Alias, das Ziel waehlt man erst im Quellenmodus. Die Marke „weicht vom
+     Alias ab" erschien dort also NIE — ausgerechnet dort, wo sie am
+     meisten sagt (gemessen 09.09.2026: mit `e.ziel` null Abweichungen, mit
+     `e.ziel || e.kanal` eine). */
+  var bstListe = bestandsAbweichung(s, e.ziel || e.kanal);
   var bstNach = {};
   bstListe.forEach(function (x) { bstNach[x.feld] = x; });
 
@@ -227,8 +234,16 @@ export function detailZeile(e, s, idx) {
     if (selR.value === '__frei__') { s.frei = true; s.srcR = ''; }
     else { s.frei = false; s.srcR = selR.value; }
     if (s.srcR && !S.werte[s.srcR]) {
-      socket.emit('getState', s.srcR, function (err, st) {
-        if (!err && st) { S.werte[s.srcR] = st; zeichneErgebnis(); }
+      /* Die Kennung festhalten, bevor gefragt wird.
+
+         Der Rueckruf legte den Wert unter der Quelle ab, die BEIM
+         EINTREFFEN eingestellt war. Schaltet man in der Zwischenzeit
+         weiter, landet der Wert der alten Quelle unter der neuen — und
+         da nur geholt wird, was noch fehlt, bleibt es dabei: die neue
+         gilt als bekannt (gemessen 09.09.2026). */
+      var geholt = s.srcR;
+      socket.emit('getState', geholt, function (err, st) {
+        if (!err && st) { S.werte[geholt] = st; zeichneErgebnis(); }
       });
     }
     neu();