Chapter overview
Bottom line: Complete only one offline review form. There are only categories in the table and no engineering information. You will not start an ETS project, nor perform any KNX actions.
- Purpose
- Use classification to complete offline preflight review of ETS responsibilities, approvals and prohibitions.
- Prepare
- A blank review sheet with designated responsible persons; no ETS, project files or site data required.
- Time
- About 15 minutes
- System change
- Do not modify ETS, Home Assistant or KNX; only create a de-identified offline preflight checklist.
- Expected result
- Classify ETS responsibilities and approval items while keeping programming, download, and group operations outside automation.
- Stop conditions
- The task requires opening a real ETS project or copying individual or group addresses.
- No ETS programming, downloads, or group reads or writes are allowed.
Scope and safety boundaries
This chapter performs only paper classification. Do not open ETS, do not view real projects, and do not copy individual addresses, group addresses, project names, device names, hosts, endpoints, credentials, or other identifying information.
Never automate: ETS programming or downloads, group reads or writes, telegram transmission, and physical control are prohibited. Testing is not an exception.
This chapter does not add the repository, install or start it. This site lacks approved immutable artifact/image digest and source-to-build proof. Any execution actions are blocked, and daemons, listeners, or integrated messages cannot be used in place of ETS or bus evidence.
Core concepts
Start by identifying who is responsible, where data is controlled, and what cannot be done. This table will not take you into action.
Pre-departure review sheet
Think of it this way: Check who is in charge, permissions and prohibited areas before traveling. Checking off the list only means that the paper classification has been completed. It does not prove that you have set off, let alone arrived.
Formal term: Offline ETS preflight and never-automate boundaries.
ETS engineering responsibilities, Add-on configuration responsibilities, approval responsibilities and evidence responsibilities should be separated. In the absence of authoritative information, the classification is "pending authorization confirmation".
Only four results are used in the entire table: "Classification completed", "Authorization confirmation pending", "Not applicable" and "STOP". They describe review status, not ETS, network, interface, or bus status.
Preparation and prerequisites
Create a worksheet that contains no live values. Put only the following fields:
- Responsibility categories: ETS engineering, Add-on setup, approval, evidence identification.
- Responsible role: Only write the role, do not write the person’s name or account number.
- Source status: documented in a pinned source, pending authorization confirmation, or not applicable.
- Safety classification: Available for offline review, or STOP.
- Prohibited matters: programming or downloading, group operations and telegram. Physical control is prohibited.
Do not attach project files, screens, exported data, or logs. When authoritative values are required, they are only checked in controlled locations by authorized roles; public tables still leave only classifications.
Steps
- Write down the purpose of the review. Just write "Offline Responsibility and Approval Classification". Do not write any execution goals.
- Assign four types of responsibilities. Create columns for ETS project, Add-on settings, approval and de-identification review. Just fill in the role.
- Mark source status. Select only pinned sources, pending authorization confirmation, or not applicable for each column. Do not copy engineering values.
- Add prohibited categories. Mark programming, downloads, and telegrams as STOP. Mark every group operation as prohibited. Physical control is prohibited.
- Check identification data. Verify there are no addresses, names, endpoints, devices, serial numbers, secrets or project content.
- Close with a limited conclusion. As a result, only the categories Completed, Pending Authorization Confirmation, Not applicable or STOP are selected. Do not claim that the ETS, interface, or bus is ready.
Verification and evidence
The finished product is a category review sheet. Another reviewer should be able to see responsibilities, gaps, and stopping points using classification alone.
- I only used the categories Complete, Pending Authorization Confirmation, Not applicable and STOP.
- I have separated responsibilities for the ETS project, Add-on configuration, approval, and evidence.
- There are no individual addresses, group addresses, names, endpoints, devices, serial numbers, secrets, or project contents in the table.
- Programming, downloads, group operations, telegram transmission, and physical control are all marked as never to be automated.
Next step: Go to Chapter 12, just organize the conceptual diagrams of ETS and KNXnet/IP on paper.
Troubleshooting
- You do not know which value applies: Do not look for a value. Enter "Pending authorization confirmation" instead.
- Someone sent a picture of the project: Stop sharing it. Public review forms do not retain screenshots or identifying information.
- Two responsible roles disagree: Mark the item "Pending authorization confirmation." Do not compare actual values in a public table.
- Someone asked to turn on ETS confirmation: Mark STOP. There are no ETS operations in this chapter.
- Someone asked to do a read: Mark STOP. Group reading is still never automated.
- Classification completion is written as System Ready: Change it to "Offline classification completed". All execution results remain unconfirmed.
FAQ
Advanced note: preflight details supported by pinned sources
The pinned source of this chapter is the configuration schema and document evidence boundary of Add-on 0.6.1. They support configuration data shapes, field responsibilities, source default existence, and de-identification requirements. They are not ETS versions or evidence of ETS operations.
The pinned sources provide no ETS screens, buttons, backups or operational snapshots. Therefore, this chapter can only classify responsibilities and gaps. Screenshots also cannot prove programming, download, group operations, telegram, bus or physical equipment results.
Does classification completion mean that ETS work can begin?
No. It only proves that the offline review form was completed.
Can I use screenshots to provide evidence?
Screenshots are limited illustrative material at best and cannot prove ETS operations or bus results.
Can test projects be automatically read in groups?
No. Group reading is never automated and there are no test exceptions.
Can you list the screen steps for ETS?
No. The pinned source has no supporting screens or operating procedures.
Can the table be placed in a backup location?
No. Do not record the actual location. Record only "Responsibility for preservation pending authorization confirmation".
Evidence and sources
Evidence class: source-bounded
Feature crosswalk: addon-options-schema, screenshot-evidence-boundary
Pinned sources support only the documented scope. This page does not represent validation of any local environment, hardware, network, or KNX bus.