WoowTech
WoowTech KNXD complete tutorial
WoowTech's international English KNXD guide, based on pinned sources and making no claims about any live site, hardware, or bus result.
Plain-language delivery status: The complete 22-chapter plain-language tutorial has been delivered. This means only that the documentation is complete; it does not prove the KNX bus, ETS, Home Assistant integration, group operations, physical control, or local-environment compatibility.
Understand the four roles and the path of data responsibility
Current content: Chapters 1–2 use everyday analogies to explain Home Assistant, ETS, KNXD, the KNX device network, and their responsibility boundaries.
Plain-language delivery status: The complete 22-chapter plain-language tutorial has been delivered. This means only that the documentation is complete; it does not prove the KNX bus, ETS, Home Assistant integration, group operations, physical control, or local-environment compatibility.
Understand KNX, KNXD, ETS, and Home Assistant
Use one building-front-desk analogy to distinguish Home Assistant, ETS, KNXD, and the KNX device network.
Plain-language content: Delivered
02Trace responsibilities from Home Assistant to the KNX bus
Use a plain-language diagram that does not represent a live connection to distinguish Home Assistant, KNXD, the KNX interface, and the KNX bus.
Plain-language content: Delivered
Safety preflight and the conditional add-on lifecycle
Current content: Chapters 3–4 cover placeholder-only preflight and lifecycle gates. Before anyone adds the repository or installs, starts, or stops the Add-on, the complete isolated-test conditions, written approval, an approved immutable artifact/image digest, and source-to-build attestation must be in place. If any condition is missing, do not proceed.
Plain-language delivery status: The complete 22-chapter plain-language tutorial has been delivered. This means only that the documentation is complete; it does not prove the KNX bus, ETS, Home Assistant integration, group operations, physical control, or local-environment compatibility.
Complete the safety preflight before installation
Before entering any live values, confirm permissions, backups, source versions, an immutable build, isolation, and stop conditions.
Plain-language content: Delivered
04Confirm the KNXD add-on lifecycle safety gates
Before any change, verify complete isolation, written approval, and an immutable build. Without an approved artifact digest, read only the interface walkthrough.
Plain-language content: Delivered
Prepare the KNX connection
Current content: Chapters 5–12 provide plain-language content, covering interface classification, driver documentation, setting responsibilities, listener boundaries, INI drawer diagrams, link handoffs, ETS offline preflight, and ETS/KNXnet/IP paper concept diagrams.
Plain-language delivery status: The complete 22-chapter plain-language tutorial has been delivered. This means only that the documentation is complete; it does not prove the KNX bus, ETS, Home Assistant integration, group operations, physical control, or local-environment compatibility.
Identify serial interfaces while minimizing data
Classify interface-candidate records without disclosing device paths or serial numbers.
Plain-language content: Delivered
06Choose a driver family within version limits
Compare driver-family terminology against pinned documentation without inferring hardware availability.
Plain-language content: Delivered
07Understand addresses, ports, and exposure boundaries
Distinguish configuration fields, placeholder values, and network exposure without providing live-site identifiers.
Plain-language content: Delivered
08Understand listener and KNXnet/IP boundaries
Explain the source terminology for listeners and KNXnet/IP without claiming that an endpoint is reachable.
Plain-language content: Delivered
09Understand INI structure and option relationships
Map INI sections to configuration responsibilities from the managed template while preserving version limits.
Plain-language content: Delivered
10Understand link-layer and driver diagnostic boundaries
Build a link-layer mental model from documented terminology without treating startup messages as bus evidence.
Plain-language content: Delivered
11Complete the ETS preflight and preserve the no-automation boundary
Prepare a read-only checklist that explicitly excludes automation of ETS downloads and group operations.
Plain-language content: Delivered
12Connect the concepts of ETS and KNXnet/IP
Build a documentation-level connection model and approval boundary without performing ETS or network operations.
Plain-language content: Delivered
Connect to Home Assistant
Current content: Chapters 13–16 provide plain-language content, covering Home Assistant KNX responsibility diagrams, offline setup worksheets, entity labeling models, and pre-execution safety classification.
Plain-language delivery status: The complete 22-chapter plain-language tutorial has been delivered. This means only that the documentation is complete; it does not prove the KNX bus, ETS, Home Assistant integration, group operations, physical control, or local-environment compatibility.
Understand the Home Assistant KNX integration architecture
Distinguish xknx logic inside the Home Assistant KNX integration from the independent KNXD daemon without claiming a live topology.
Plain-language content: Delivered
14Set boundaries for Home Assistant KNX configuration
Organize configuration concepts, placeholders, and pre-change checks from pinned documentation.
Plain-language content: Delivered
15Understand the Home Assistant KNX entity model
Explain documented entity-configuration concepts without providing group-write or physical-control examples.
Plain-language content: Delivered
16Classify tests and evidence with the safety matrix
Use auditable categories to distinguish safe, isolated-test, approval-required, and never-automate work.
Plain-language content: Delivered
Routine operation and troubleshooting
Current content: Chapters 17–22 provide plain-language content, covering backup responsibilities, safety baselines, documented link symptom triage, USB anonymous decision trees, controlled maintenance cadences, and offline incident responsibility manuals.
Plain-language delivery status: The complete 22-chapter plain-language tutorial has been delivered. This means only that the documentation is complete; it does not prove the KNX bus, ETS, Home Assistant integration, group operations, physical control, or local-environment compatibility.
Define project backup and restoration boundaries
Plan backup, inspection, and restoration exercises that contain no secrets or environment identifiers.
Plain-language content: Delivered
18Apply a minimal-exposure security baseline
Review permissions, secrets, network exposure, and approval workflows against a defensive baseline.
Plain-language content: Delivered
19Triage link failures from documentation
Build a failure classification from pinned documentation without presenting diagnostic attempts as successful results.
Plain-language content: Delivered
20Troubleshoot USB and serial interfaces offline
Use de-identified source descriptions to classify missing candidates, changed path categories, and driver-failure concepts.
Plain-language content: Delivered
21Use controlled operations and change records
Define an auditable operations cadence, change records, and stop conditions without performing live maintenance.
Plain-language content: Delivered
22Use the incident response and recovery runbook
Create an offline responsibility runbook for incident classification, stopping, evidence handling, and recovery decisions.
Plain-language content: Delivered