Skip to content

Add new metadata fields from zwave-js v15.21.0#1367

Draft
AlCalzone wants to merge 2 commits intohome-assistant-libs:mainfrom
AlCalzone:new-metadata-fields
Draft

Add new metadata fields from zwave-js v15.21.0#1367
AlCalzone wants to merge 2 commits intohome-assistant-libs:mainfrom
AlCalzone:new-metadata-fields

Conversation

@AlCalzone
Copy link
Contributor

https://github.com/zwave-js/zwave-js/releases/tag/v15.21.0 adds new metadata fields:

  • allowed for defining value ranges with gaps and step sizes on config parameters and other value metadata
  • purpose for annotating a config parameter with a semantic meaning.

This PR adds both to the client lib.

Copy link
Contributor

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this data passed through from the server without any changes in the server?

writeable: bool # required
description: str
label: str
description: str
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why change the order?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes more sense IMO, since the description further clarifies the label. This is also how zwave-js defines it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a comment about that.

@AlCalzone
Copy link
Contributor Author

This needs a new release of zwave-js-server with a schema bump. Going back to draft for now.

@AlCalzone AlCalzone marked this pull request as draft February 16, 2026 12:55
Co-authored-by: Martin Hjelmare <marhje52@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments