WoowTech KNXD

Help, stopping, and safe restoration

Find a stable entry point by symptom. These entries help you interpret evidence, de-identify records, and stop safely; they do not prove KNX bus operation.

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.

Check readiness before starting

Use the same eight-item checklist as Chapter 3 to decide whether work may continue.

Criteria: Confirm each item: Home Assistant installation type, administrative rights, Home Assistant backup, source and version, interface category, network planning, stop conditions, and restoration decision. Source and version readiness also requires an approved artifact/image digest and source-to-build attestation.
Observable result: Classify each of the eight items as met, not met, or unknown. Readiness requires all eight to be met.
Stop action: If any item is not met or remains unknown, do not add the repository, install the Add-on, or start it. This site has no approved artifact digest, so source and version readiness remains unknown.
Restore caution: A backup is not necessarily restorable. Verify its scope, responsible role, and availability before relying on it.

Go to Chapter 3 and complete the eight preflight checks

Interpret Add-on status

Distinguish a running process and a waiting listener from the evidence required to prove a working KNX bus.

Criteria: Use de-identified evidence to classify process, listener, and bus status separately.
Observable result: Record “running” only as process status, a listener only as a waiting service, and KNX bus status as unconfirmed.
Stop action: If you cannot identify the evidence layer, do not change settings, attempt a connection, or restart in order to guess.
Restore caution: Status interpretation alone does not require restoration. Evaluate any previous unapproved change against its change record.

How to share logs safely

Retain only the error category; remove addresses, hosts, paths, serial numbers, tokens, and sessions.

Criteria: Remove hostnames, IP addresses, KNX addresses, tokens, sessions, accounts, device names, paths, and serial numbers before sharing.
Observable result: The remaining record contains only a broad time range, component, and error category and cannot be traced back to a home or host environment.
Stop action: If you find an identifying value, stop sharing, remove the public copy, and create a newly de-identified version.
Restore caution: Clearing the logs does not restore system state; if the logs reveal a secret, the secret must be revoked or rotated.

When to stop and how to restore

When an unknown write, unexpected physical action, or unexplained state occurs, stop first. Then use the change scope to decide whether restoration should be considered.

Criteria: Determine whether stopping the Add-on is sufficient or whether an authorized role must consider restoring a Home Assistant backup.
Observable result: Stopping the Add-on ends only its service; it does not restore settings. A Home Assistant backup restores only the scope covered by that backup.
Stop action: If an unknown write, unexpected physical action, or unexplained state occurs, stop the Add-on and retain only de-identified evidence.
Restore caution: Do not call stopping the Add-on a restoration. Before restoring a backup, check its scope and its impact on other changes.

Check version applicability

Check the version boundaries for the Add-on, KNXD, Home Assistant, and each cited file.

Criteria: Each Add-on, KNXD, Home Assistant, and file version must point to a pinned source or an explicitly recorded evidence gap.
Observable result: List each project version separately; do not imply compatibility or live results by placing versions together.
Stop action: If the version or source does not match, stop applying the tutorial steps, record the differences and locate the matching source.
Restore caution: A version mismatch normally requires stopping, not restoration. If settings changed, assess restoration separately against the backup scope.

Report a documentation problem

Provide the chapter, version, expected text, and reproducible offline evidence without secrets or environment identifiers.

Criteria: Record the chapter, edition, expected text, and reproducible offline evidence, with all environment data de-identified.
Observable result: The report lets a maintainer reproduce the documentation problem without granting operational authority or claiming a live result.
Stop action: If evidence still contains secrets or would require a live operation, stop the submission and narrow the evidence.
Restore caution: File reports do not change or restore the environment; do not attach backups, settings, or credentials to the issue.