Chapter overview
Bottom line: Draw only this tutorial's candidate responsibility diagram on paper. Its five cards represent the Home Assistant KNX integration, xknx logic within that integration, the independent KNXD daemon, the KNX interface, and the KNX bus. The arrangement is neither a universal architecture nor a proven live path, and KNXD is not an inherent layer of the integration.
- Purpose
- Use this tutorial's five candidate responsibility cards to identify roles without drawing them as proven paths.
- Prepare
- One blank paper and five blank cards; no Home Assistant or onsite materials required.
- Time
- About 15 minutes
- System change
- Do not add or configure Home Assistant KNX integration; only read architectural responsibilities from pinned sources.
- Expected result
- Distinguish xknx logic in the Home Assistant KNX integration, the independent KNXD daemon, and KNX-side responsibilities while keeping candidate topologies and live results unproven.
- Stop conditions
- The task requires adding the integration, entering endpoints, or reloading Home Assistant.
- Do not refer to the existence of a version or component as a working integration.
Scope and safety boundaries
Only paper and blank cards are allowed in this chapter. Do not open Home Assistant, KNXD, or ETS; connect or probe anything; reload software; or enter environment data. The five-card diagram is only a candidate responsibility topology, not configuration instructions, a universal layering rule, or evidence of a live path.
Do not add the repository or install or start the Add-on. Those actions may be evaluated separately only when complete isolation, written approval, an approved immutable artifact/image digest, and source-to-build attestation are all present; this chapter does not provide those conditions.
Group reads must not be automated. Group writing is not allowed. Telegrams may not be sent. ETS programming or downloads must not be performed. Do not control physical equipment. Paper diagrams do not prove anything about KNXD, interface, KNX bus, ETS or Home Assistant integration.
Core concepts
Look at the responsibility first, then the name. Each desk handles only its own work; just because the previous desk has finished sorting the paper, it does not prove that the next desk has received the items.
A row of handover tables
Think of it this way: The first desk manages the service counter, the second desk is the rule book used within the counter, and the third desk is another independent office. Then put two candidate responsibility cards for the handover interface and the building's internal network. This is just to facilitate this tutorial to ask questions one by one. It does not prove that the five cards must be lined up in one road, nor does it mean that the handover has occurred.
Formal term: Candidate responsibilities for the Home Assistant KNX integration, the xknx library/KNX logic within that integration, a standalone KNXD daemon, the interface, and the KNX bus.
xknx is a library/logic used within the Home Assistant KNX integration boundary, not KNXD. KNXD is a standalone daemon and is not an inherent layer of the integration itself. The pinned Core manifest only supports xknx dependency boundaries declared in this version; the five-card arrangement is a candidate responsibility topology for this tutorial, and it cannot be inferred that integration must go through KNXD, the interface, or any proven live path.
Write on all five cards: "Their states are independent; this arrangement is not a universal path." The existence of a file or component supports only its name and documented responsibility, not claims about loading, wiring, transmission, or control.
Preparation and prerequisites
All you need to do is prepare a non-valued worksheet. Draw five empty boxes and leave two columns for "Source Supported" and "Cannot Prove".
- The five cards only contain role names, not host, address, port, secret, project or device data.
- For each card, fill in "Status Unknown" first.
- The candidate relationship line only writes "conceptual responsibility", without drawing direction or parameters, nor does it imply that integration must go through KNXD.
- Have another person review the diagram; the review establishes no configuration steps or live results.
- If someone requests live-environment information, immediately stop the paper process and hand over to the approval process.
Steps
After completion, you only get a paper architecture diagram.
- Put down the integration table. Write "Manage integration responsibilities within Home Assistant" and add "No evidence that it was added or loaded."
- Put down the logic table. Write "xknx library/KNX logic is located within the Home Assistant KNX integration boundary" and add "Declaring dependencies does not prove that it is operational."
- Put down the KNXD card. Write "standalone KNXD daemon; not an inherent layer of the Home Assistant KNX integration." Do not add daemon or listener status to the diagram.
- Put down the interface table. Write "Keep handover boundaries" and do not include the interface type, name, or live-site status.
- Put down the bus table. Write "Onsite network responsibility; no evidence of results in this chapter."
- Mark candidate relationships. No directional arrows are used; each line is marked only with "Responsibility of this Teaching Candidate" and finally "Not a common or proven path; no settings, connections, or success claims."
Verification and evidence
The qualified results are five responsibility cards, not proof of implementation of the system diagram. You should be able to tell what each card is responsible for, and also tell which card it cannot vouch for.
- I have five separate responsibility cards, and the status of each card is unknown.
- I can tell that the xknx library/logic lies within the Home Assistant KNX integration boundary.
- I separated the standalone KNXD daemon from the Home Assistant KNX integration and did not draw KNXD as an inherent layer.
- I separated the interface from the KNX bus and marked the five cards as non-generic, unproven candidate responsibility topologies.
- The diagram does not contain any environmental information, settings, operating procedures or functional suggestions.
- I do not operate ETS or the Home Assistant integration. I do not read or write groups, send telegrams, or control physical equipment.
Next step: Go to Chapter 14, organize the setting requirements into an offline placeholder worksheet.
Troubleshooting
- xknx and KNXD appear to be the same thing: Rewrite the former as "library/logic used within the integration boundary" and the latter as "independent daemon, not an inherent integration layer".
- The arrows look like the execution flow: Remove directions and verbs, leaving only "candidate responsibilities for this tutorial; neither a universal nor a proven path."
- Component presence is described as operational: Replace the claim with "The pinned source defines this role; execution status is unknown."
- Someone wants to add connection information: Stop. Environmental information will not be collected for paper drawings.
- Someone asked to join the integration confirmation: Stop. There are no setup or test authorizations in this chapter.
- Someone wants to use the bus action to verify: Refuse. No automated group actions, no telegrams, and no physical control.
FAQ
Advanced note: What can each of the two pinned sources say?
The pinned Home Assistant KNX file snapshot supports the configuration concepts present in that file. Separately locked Core version manifests support the version's integration registration and xknx dependency boundaries. The juxtaposition of the two sources does not prove that the versions correspond exactly to each other, nor does it prove that the package has been loaded, the integration has been established, or the KNX bus has results.
Is xknx/KNX logic KNXD?
No. xknx is the library/logic used within the boundaries of the Home Assistant KNX integration; KNXD is an independent daemon, not an inherent layer of the integration itself.
Does the presence of KNXD represent the presence of integration?
No. The two have different lifecycles and evidence.
Does the interface card mean that the interface has execution evidence?
No. The card only states the handover of responsibilities.
Do the five cards on paper represent a universal or live path?
No. It is only a candidate responsibility topology for this tutorial and is not evidence of wiring, transmission, or live paths.
Does this chapter prove that Home Assistant or KNX bus can work?
No. This chapter has no implementation or live results.
Evidence and sources
Evidence class: source-bounded
Feature crosswalk: home-assistant-knx-concepts, home-assistant-knx-core-release-boundary
Pinned sources support only the documented scope. This page does not represent validation of any local environment, hardware, network, or KNX bus.