Skip to content

fix(blueprint-creator): clarify vendor field usage #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
anataty wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(blueprint-creator): clarify vendor field usage #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion plugins/enapter/skills/blueprint-creator/references/manifest/gotchas.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down