feat(smarthome): TP3 — Logikketten → native deCONZ-Regeln - #209
Merged
Conversation
This was referenced Jul 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Smart Home TP3 — Logikketten → native deCONZ-Regeln
Der Admin definiert WENN/DANN-Logikketten; GateControl übersetzt sie in native deCONZ-Objekte (
/rules+ bei Verkettung/schedules+ CLIP-Sensor), die autonom auf der Bridge laufen — auch wenn GC offline ist. Reine Admin-Funktion hinter Pro-Keysmarthome. Spec:docs/superpowers/specs/2026-06-30-smarthome-tp3-rules-design.md§1–§13.Inhalt (subagent-getrieben, TDD, zweistufiges Review je Task)
deconzCapabilities.js+ Fixtures). Belegt: Operatoreneq/gt/lt/dx/in,cancelSupported=true,clipDeletable=true, buttonevent-Formelbutton*1000+offset, Daylight-bool-Feld, Schedule-command.addressbraucht/api/<apiKey>-Präfix (Rule-Actions nicht)./rules,/schedules, CLIP-Methoden über den Companion-Proxy-Transport.rulesTranslate.js): dx-Semantik (edge-OR/state-AND), Temp ×100, Szene-Recall{on:true}, plug ohne bri/color; Objekt-Plan je Delay-Modus (schedule-first, damit Platzhalter auflösbar).smarthomeRules.js): CRUD mit Best-Effort-Kompensation (keine Waisen), Update-Atomizität (NULL-before-delete), idempotentes remove (404), Limit-Erkennung (DECONZ_RULE_LIMIT_REACHED), Boot-Resync pendenter Regeln.gateway-count+limit_warn; Admin-Guard vorrequireFeature, CSRF, lokalisierte Fehler. Kein Portal.btn_*-Keys).Tests
Volle Smart-Home-Suite lokal 84/84 grün. Keine neue Migration (
smarthome_rulesaus TP1).Bewusst deferred (Minor, aus Reviews)
gateway-count zählt GC-Sekundärregeln (#reset/#cancel) als extern; kein Gateway-Selector im UI (nutzt erstes Gateway); xy-Farb-Prefill beim Edit fehlt (nur ct); 409-Doppel-Signal (Banner+alert); Client-seitiges
maxlengtham Namen.🤖 Generated with Claude Code