-
-
Notifications
You must be signed in to change notification settings - Fork 630
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: do not persist or map values form force-removed CCs, do not persist values from mapped CCs #6760
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlCalzone
changed the title
fix: do not persist or map values form force-removed CCs
fix: do not persist or map values form force-removed CCs, do not persist values from mapped CCs
Apr 11, 2024
@zwave-js-bot automerge |
zwave-js-bot
previously approved these changes
Apr 11, 2024
zwave-js-bot
previously approved these changes
Apr 11, 2024
zwave-js-bot
previously approved these changes
Apr 11, 2024
zwave-js-bot
approved these changes
Apr 11, 2024
AlCalzone
added a commit
that referenced
this pull request
Apr 12, 2024
### Bugfixes * Firmware updates on Z-Wave Long Range now utilize the larger frame size better (#6759) * Fixed an issue where multicast `setValue` had a `SupervisionCCReport` as the result instead of a `SetValueResult` (#6765) * Parsing of provisioning entries with numeric `supportedProtocols` (#6764) * Fix error when `ConfigurationCCBulkGet` response is missing (#6763) * Values from force-removed or endpoint-mapped CCs are no longer persisted (#6760) ### Config file changes * Fix versioning logic for parameter 26 of Zooz ZEN72 (#6761)
This was referenced Apr 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a long-standing issue where seemingly unsupported values appear for CCs that have been force-removed via a config file.
fixes #6555
TODO: solve #6318 as a followup