Skip to content
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.

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

fix: preserve stateful and secret flags for dynamic CC values #6457

Merged
merged 3 commits into from
Oct 24, 2023

Conversation

AlCalzone
Copy link
Member

#5467 added support for these flags, and made it so they couldn't be overridden by dynamic metadata. However the logic didn't consider that .options is always static, even on dynamic values, while .meta isn't - leading to the stateful and secret flags being ignored for dynamic CC values.

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) October 24, 2023 09:08
@zwave-js-bot zwave-js-bot merged commit cc02f5b into master Oct 24, 2023
16 checks passed
@zwave-js-bot zwave-js-bot deleted the stateful-dynamic-value branch October 24, 2023 09:16
AlCalzone added a commit that referenced this pull request Oct 24, 2023
### Bugfixes
* Mark `Central Scene CC` `scene` property as stateless. The previous fix wasn't working. (#6458)
* Preserve `stateful` and `secret` flags for dynamic CC values (#6457)

### Config file changes
* Correct product id for Fakro ZWS12 (#6454)
* add PM-B400ZW-N (#6421)
* Ensure `kWh` is written consistently in parameter units (#6456)

### Changes under the hood
* Bot: Consider `zwave_js` to be a valid logfile name in issue reports (#6459)
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