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: try to handle non-implemented CCs #7080

Merged
merged 2 commits into from
Aug 2, 2024

Conversation

AlCalzone
Copy link
Member

With this PR, non-implemented CCs will no longer be dropped immediately. Instead possible awaiters are invoked first, in case the application is waiting for them.

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

zwave-js-bot
zwave-js-bot previously approved these changes Aug 2, 2024
@zwave-js-bot zwave-js-bot enabled auto-merge (squash) August 2, 2024 19:49
@zwave-js-bot zwave-js-bot merged commit dc71707 into master Aug 2, 2024
17 checks passed
@zwave-js-bot zwave-js-bot deleted the try-handle-unsupported-cc branch August 2, 2024 20:17
AlCalzone added a commit that referenced this pull request Aug 2, 2024
### Features
* Update list of manufacturers and existing CCs (#7060)
* Add `inclusion state changed` event (#7059)
* Add support for new notifications (#7072)
* Bump version of `Association CC` and `Multi Channel Association CC` (#7078)

### Bugfixes
* Preserve granted security classes of provisioning entries when switching protocols (#7058)
* Version of Humidity Control Mode CC is 1, not 2 (#7062)
* Abort S2 bootstrapping when `KEXSetEcho` has reserved bits set (#7070)
* Fixed an issue causing non-implemented CCs to be dropped before applications could handle them (#7080)

### Changes under the hood
* Include default value in `Color Switch CC` mocks (#7071)
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