Choose a driver family within version limits

Chapter overview

Bottom line: Select only a driver family documented by the pinned source, and submit it for later manual review. This is not an installation recommendation, nor is it proof of hardware compatibility. If documentation is insufficient, stop.

Purpose

List a driver-family candidate for manual review based on a pinned source.

Prepare

De-identified classification results for Chapter 5, and documentation comparisons for the pinned versions.

Time

About 15 minutes

System change

Do not modify Home Assistant; only compare driver families offline based on pinned sources.

Expected result

List driver-family candidates for human review without presenting name matching as proof of hardware compatibility or availability.

Stop conditions

• The task asks you to infer driver or hardware compatibility directly from a product name.
• The task requires loading a driver, starting a service, or contacting a physical interface.

Scope and safety boundaries

This chapter reads only pinned sources. Do not guess a driver from a product name, appearance, connector, candidate codename, or online article. Do not try drivers one after another. Without clear documentation for the same version, the answer is "no selection; awaiting further evidence."

This chapter does not add the repository or install or start the Add-on. Any such action requires complete isolation, written approval, and approved immutable artifact/image provenance. This site currently lacks an approved artifact/image digest and therefore remains blocked.

Do not connect the interface or KNX bus. Group reading, group writing, telegram transmission, ETS programming or downloads and physical control are prohibited. Do not record any environment-identifying information.

Core concepts

Ask two questions: Does the pinned Add-on version accept this name? Does the locked upstream file explicitly document a family with the same name? Only when both answers are "yes" may it be listed as a candidate for later manual review.

Preparation and prerequisites

Create an offline decision card. Do not put product name, device path, serial number, host, IP or endpoint. The card only requires:

• Requirement category: Only write roles such as "device-type input" or "endpoint-type input".
• Add-on name evidence: Yes, No, or Unknown.
• Upstream file documentation: Yes, No, or Unknown.
• Manual review status: pending review or stopped.
• Non-conclusion: The local hardware compatibility, driver startup and bus status have not been confirmed.

If the version does not match, look first Versions and compatibility. Do not use other versions to make up your answers.

Steps

1. Write the required role first. Just write which type of input needs to be processed. Do not write the make, model, or actual value.
2. Check the Add-on name. Confirm that the candidate name is in the pinned enumeration for Add-on 0.6.1. If not, stop and don’t change the name on your own.
3. Check the upstream instructions. Confirm that the upstream 0.14.72 pinned source explicitly describes the driver family of the same name. Similar names don't count.
4. Keep at most one candidate. When both documents are clear, write "Documented candidate; pending manual review." If multiple candidates remain or there is no clear answer, make no selection.
5. Add non-conclusion. It states "Hardware compatibility has not been proven, drivers have not been loaded, services have not been started, and the bus has not been contacted."
6. Stop at the file level. Submit the decision card to the approval process. Do not try to start, and do not use live logs to favor a candidate.

Verification and evidence

The completion result must be "Document Candidate" or "Insufficient Evidence". It cannot be written as "Driver Applicable".

• The candidate has both Add-on 0.6.1 name evidence and upstream 0.14.72 explicit documentation.
• Decision cards have no products, paths, serial numbers, hosts, IPs, endpoints, or credentials.
• I left the hardware compatibility, loading, startup, listener and bus status as unverified.
• I didn't take a turn to test the driver, nor did I install, start, or connect the physical interface.

Next step: Go to Chapter 7, only recognize the configuration fields, placeholder text, house number and exposure responsibility.

Troubleshooting

• Only Add-on name, no upstream description: Indicates insufficient evidence and does not establish family correspondence.
• The names are similar but not identical: Treat them as different. Do not infer a match from prefixes, suffixes, or product descriptions.
• There are two documented candidates: Choose neither. List the document gaps and submit them to manual review.
• Some people regard the default value as a recommendation: Remove recommendation statements. A source default is just a schema fact.
• Someone asked to start and take a look: Stop. A test boot is not a file selection, nor does it prove hardware compatibility.

FAQ