PQA006 — functions.yaml not found in embedded resources

The framework catalogue of functions cannot be located, so no function or status code is generated.

functions.yaml is the framework's catalogue of device functions — what states each one carries, which events and commands belong to it. The generator reads it from the adapter's additional files, and otherwise from the resources embedded in the framework assembly. This is reported when neither source yields it.

Why the build refuses this

Without the catalogue there are no functions at all. Every device type in the adapter references functions by name; with nothing to resolve them against, the generated Things carry no state, no transition methods and no status surface, and the hand-written code written against them does not compile.

This is an environment fault, not a modelling mistake. Nothing in the adapter's own declarations causes it. A damaged package restore, a trimmed or repackaged framework assembly, or a framework and generator from different versions are the causes worth checking.

How to fix it

Restore the framework package cleanly. Clear the local package cache, restore, and rebuild — a partially downloaded package is the most common cause.

Check the framework and generator versions match. Two packages from different releases can disagree about where the catalogue lives.

When the adapter deliberately supplies its own catalogue, declare functions.yaml as an AdditionalFiles item in the adapter project so the generator reads it from there.

If you disagree with a report

Do not suppress it. A wrong report is a bug in the check — report it with the project file and package versions that triggered it.