Set boundaries for Home Assistant KNX configuration

Chapter overview

Bottom line: Create one offline configuration worksheet containing only placeholders, data classifications, and review statuses—never deployable settings, live values, or connection details.

Purpose

Create a Home Assistant KNX offline configuration worksheet with only placeholders and categories.

Prepare

A blank worksheet and paper responsibilities map for Chapter 13; without opening Home Assistant.

Time

About 20 minutes

System change

Do not save Home Assistant KNX settings; use only placeholder text in an offline configuration checklist.

Expected result

Recognize configuration responsibilities and pre-change gates without entering a live endpoint or claiming connection or integration results.

Stop conditions

• The task requires a real host, endpoint, address, secret, or device identifier.
• Steps require saving settings, reloading the integration, or testing the connection.

Scope and safety boundaries

The worksheet cannot be taken for execution. Do not open a running Home Assistant and do not provide YAML, API, pastable field shapes, connection details, or any actual values.

Do not add the repository or install or start the Add-on. Work outside this chapter may be evaluated only when complete isolation, written approval, an approved immutable artifact/image digest, and source-to-build attestation are present; this chapter grants no authorization.

Automated group reads, group writes, telegram transmission, ETS programming or downloads, and physical control are prohibited. The offline worksheet does not prove any results from the KNXD, KNX bus, ETS or Home Assistant integration.

Core concepts

The strongest permitted conclusion for a worksheet is "Field responsibilities are ready for manual review." It does not prove that Home Assistant can accept any settings or establish any connection, integration, or bus result.

Preparation and prerequisites

Draw the table header first without filling in the content value. Only the following governance categories are used in the header.

• Requirement name: write only the general purpose, do not write the environment name.
• Responsible role: record which role provided or reviewed, do not write personal information.
• Semantic placeholder: Use the fixed text "To be supplied by an authorized role."
• Data classification: Choose one from public, controlled, secret, or unknown.
• Source boundary: Record file snapshots and Core version metadata separately.
• Review status and stop reason: only the classification is recorded, not the execution results.

As soon as a cell requires real data or executable shape, stop immediately. Do not fill in from old files, images, memories, or online articles.

Steps

Each step deals only with paper sorting.

1. Write the worksheet title. Mark "Offline placeholder worksheet; cannot be imported, pasted, or executed."
2. Create a requirement column. Only general classifications such as connection responsibilities, integration responsibilities, data-model responsibilities, and approval responsibilities are used, and fields are not simulated.
3. Add placeholder text. Only fill in "To be supplied by an authorized role" in each column, and do not add format hints, default values or example values.
4. Add data categories. Mark it as public, controlled, secret, or unknown; controlled, secret, and unknown are not allowed to be added to the public sheet.
5. Separate the source column. The concepts supported by file snapshots and the integration boundaries supported by Core version metadata are noted separately, and are not written as compatibility guarantees.
6. Do an offline review. Confirm that there are no YAML, API structures, connection details, actual values, or action statements, and finally hand it off to another reviewer.

Verification and evidence

Completion means leaving blanks safely, not filling in the form. Each column must show the responsibility, classification, source, and reason for stopping.

• The worksheet is clearly marked offline and not executable.
• Each column only has general requirements, responsibility roles, placeholder text, and categories.
• File snapshots are recorded separately from Core version metadata.
• No YAML, API structures, connections, hosts, addresses, secrets, device data, or actual values.
• There are no saves, reloads, test connections, or claims about results.

Next step: Go to Chapter 15 and use label cards to organize the entity model.

Troubleshooting

• A placeholder looks like a live value: Change everything back to "To be supplied by an authorized role".
• The worksheet resembles settings that could be pasted: Remove hierarchy, syntax, data shapes, and field order, leaving only governance categories.
• Distinct sources are presented as one version: Split them into two columns that explain each source's supported scope and what it cannot prove.
• Someone asked to see the running settings: Stop the offline process and hand over the explicitly approved read-only scope evaluation.
• Someone asked to test the connection: Stop. This chapter does not provide testing or implementation authorization.
• Blank cells are mistaken for omissions: Add the reason for stopping, don’t guess the value.

FAQ