From 9c0435e8317b342bfc3d57d64816598941bb894c Mon Sep 17 00:00:00 2001 From: Tatyana Date: Mon, 23 Mar 2026 09:44:58 +0100 Subject: [PATCH] fix(blueprint-creator): clarify vendor field usage --- .../skills/blueprint-creator/references/manifest/gotchas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/enapter/skills/blueprint-creator/references/manifest/gotchas.md b/plugins/enapter/skills/blueprint-creator/references/manifest/gotchas.md index 83d54ec..9028d95 100644 --- a/plugins/enapter/skills/blueprint-creator/references/manifest/gotchas.md +++ b/plugins/enapter/skills/blueprint-creator/references/manifest/gotchas.md @@ -12,7 +12,7 @@ If the device has operational states (e.g. `idle`, `running`, `fault`), encode t - `alerts` field in telemetry: this field is automatically added during manifest compilation. - `lua_api_ver_3` to `requirements` -- `vendor` +- top-level `vendor:` metadata field (e.g. `vendor: sma` at the same level as `display_name:`). This is the blueprint-level vendor tag, distinct from `properties.vendor` which is a perfectly valid property declaration for exposing the device vendor as readable telemetry. ## List all alerts