WoowTech KNXD
Each term starts with an everyday analogy, gives the formal term, and explains how the 22-chapter guide uses it.
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.
Think of it this way: Shared pathways in a building that let switches, sensors, and other devices communicate.
Formal term: KNX building automation network
How the complete guide uses it: The 22-chapter tutorial describes role and evidence boundaries and does not connect to or control the KNX device network.
Think of it this way: A translation desk that converts requests into a form the KNX side can understand.
Formal term: KNXD/KNX daemon
How the complete guide uses it: The 22-chapter tutorial explains KNXD's responsibilities and pinned sources; any lifecycle operations are subject to complete isolation, written approval, immutable artifact provenance, and manual execution gates.
Think of it this way: The design drawings and configuration tool for a KNX system.
Formal term: KNX Engineering Tool Software (ETS)
How the complete guide uses it: The 22-chapter tutorial explains ETS responsibilities and approval boundaries without performing programming or downloads.
Think of it this way: A program that remains on duty in the background.
Formal term: daemon process
How the complete guide uses it: The tutorial treats a running daemon only as process status, not as evidence about the listener, bus, or integration.
Think of it this way: A staffed reception desk does not prove that the road behind it is open.
Formal term: network listener
How the complete guide uses it: The tutorial describes a listener as a waiting service. A listener does not prove endpoint reachability or KNX bus operation.
Think of it this way: The doorway or adapter between the translation desk and the KNX network.
Formal term: KNX physical or network interface
How the complete guide uses it: The 22-chapter tutorial only identifies interface types and responsibilities, and does not require real addresses, device paths or serial numbers.
Think of it this way: A short message travelling across the KNX network.
Formal term: KNX telegram
How the complete guide uses it: The tutorial does not transmit, replay, or automatically generate telegrams.
Think of it this way: A KNX device has its own house number.
Formal term: KNX individual address
How the complete guide uses it: The 22-chapter tutorial does not require, show, or guess actual individual addresses.
Think of it this way: A shared topic mailbox used by multiple devices.
Formal term: KNX group address
How the complete guide uses it: The 22-chapter tutorial does not read, write or demonstrate real group addresses.
Think of it this way: A designated library used by the add-on store to find software.
Formal term: software repository
How the complete guide uses it: The tutorial identifies the approved repository but does not add it to Home Assistant without complete isolation, written approval, and approved artifact provenance.
Think of it this way: An exact archive identifier that points back to a specific source revision.
Formal term: Git commit
How the complete guide uses it: The tutorial uses a commit to pin source content but does not treat it as source-to-build evidence for a store image.
Think of it this way: Placing software into a clean test environment without inheriting previous settings or state.
Formal term: fresh installation
How the complete guide uses it: The 22-chapter tutorial still requires complete isolation, written approval, approved immutable artifact/image digest and source-to-build attestation.
Think of it this way: Communication instructions that tell the translation desk how to speak to a type of interface.
Formal term: interface driver
How the complete guide uses it: The 22-chapter tutorial only classifies driver families according to pinned sources, does not load the driver, and does not infer hardware compatibility from the name.
Think of it this way: A boundary around what the guide explains and what remains unverified.
Formal term: documentation scope
How the complete guide uses it: The guide uses documentation scope to distinguish stated roles and safety boundaries from unproven deployment, compatibility, and KNX results.
Think of it this way: The live-site operation that writes engineering configuration into KNX devices.
Formal term: ETS programming and download
How the complete guide uses it: The tutorial does not perform ETS programming or downloads or delegate such physically consequential tasks to AI automation.