Understand KNX, KNXD, ETS, and Home Assistant

Task card for this chapter

You are already familiar with Home Assistant add-ons, integrations, and entities. This chapter does not require you to install or configure anything; it only explains four roles. Once those roles are clear, you will not have to guess when later chapters refer to KNX as the device communication path, ETS as the project-planning tool, or KNXD as the translation desk.

Purpose

Explain the differences between Home Assistant, ETS, KNXD, and the KNX device network in your own words.

Prepare

Know how to use Home Assistant; no knowledge of KNX, Linux or network engineering.

Time

About 10 minutes

System change

Do not modify Home Assistant.

Expected result

Distinguish Home Assistant, ETS, KNXD, and the KNX device network, and understand that a running process does not prove bus operation.

Stop conditions

• The task requires a real KNX address, host data, or a secret.
• Stop if the task would require a KNX bus connection or physical-device control.

Keep the safety boundary first

This chapter is a reading exercise about roles. Do not activate the Add-on, send a KNX telegram, or read or write a group address. Even if "Running" appears on screen, it means only that a process is running; it does not mean that the KNX device network is connected.

Remember: A running process does not prove that the bus is operational. A translator sitting at the desk does not prove that the telephone line is connected or that building equipment has received a message. This chapter does not certify any result for an ETS project, the Home Assistant KNX integration, or physical equipment.

Environment-identifying information includes real hostnames, IP addresses, individual addresses, and group addresses. Secrets or device identifiers include USB serial numbers, tokens, and credentials. Do not copy or share either type of data.

Learn about the four roles using the building counter

All you need to know before you start

You do not need to prepare hardware, ETS projects or network data. First use a piece of paper to write down four boxes: Home Assistant, ETS, KNXD, KNX device network. Then put a plain-language description of each role into the corresponding grid.

• Home Assistant is the control desk where you make your requests.
• ETS is a tool for planning and setting up KNX projects, not another name for KNXD.
• In the path described by this guide, KNXD is the translation desk; the Add-on lets Home Assistant manage it.
• In this site's responsibility diagram, the KNX device network is on the device side; the status of other software cannot prove its status.

Go through it in four sentences

This is only a verbal exercise; do not operate any interface. At every step, ask "Who is responsible?" Don't ask "What value should be filled in?"

1. Identify the control point. You make the request in Home Assistant, so it's the control desk.
2. Identify project planning. When it comes to describing how a KNX project is designed, that is the role of ETS, not the Home Assistant Add-on.
3. Identify the intermediary. The Add-on path used in this guide places KNXD between the Home Assistant management side and the KNX device network; the Add-on is responsible for managing this program in Home Assistant.
4. Finally, keep the result boundaries. The presence or execution of the KNXD program proves only the status of the process layer; whether the KNX bus is connected has not yet been confirmed.

If you can finish four sentences without mentioning any IPs, addresses, or settings, you've completed the plain-language thread of this chapter.

Completion check

Check yourself with the checklist below. The completion here is "mental model completion", not system deployment completion.

• I can tell that Home Assistant is the control desk and ETS is the building blueprint and configuration tool.
• I can tell that KNXD is the translation desk and KNX is the device communication network.
• I know that an Add-on appearing to run is not evidence that the KNX bus is operational.
• I'm not connecting to buses, operating ETS, reading or writing groups, or controlling physical equipment.

Next step: Go to Chapter 2, use the same building as a metaphor to understand which roles the data responsibilities will pass through in order.

What to do when the role is placed in the wrong place

This chapter does not troubleshoot service faults. It addresses the common mistake of confusing roles or evidence layers. Use the guidance below to correct each statement.

• ETS is mistaken for a Home Assistant integration: Separate the roles. ETS is the planning and setting tool for KNX projects, and integration is another role within Home Assistant.
• KNXD is mistaken for a KNX device: Put KNXD back at the translation desk; the device network remains downstream.
• When “Running” is mistaken for a bus connection: Limit the conclusion to process status; keep bus status unconfirmed.
• I feel that we must first obtain live-environment information: Stop collecting; this chapter only requires role names, not any environment-identifying information.

Advanced notes and FAQ