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: handle notification enum behavior "replace" correctly #6282

Merged
merged 1 commit into from
Sep 15, 2023

Conversation

AlCalzone
Copy link
Member

We already had a test for this, but the test didn't match the expectations explained in the comment.
fixes: #6281

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) September 15, 2023 15:32
@zwave-js-bot zwave-js-bot merged commit 5e89385 into master Sep 15, 2023
15 checks passed
@zwave-js-bot zwave-js-bot deleted the fix-notification-enum-replace branch September 15, 2023 15:39
AlCalzone added a commit that referenced this pull request Sep 21, 2023
### Bugfixes
* Fixed an issue where some `Notification CC Reports` including an enumeration value would cause the corresponding value ID to be set to the wrong value (#6282)
* When the Serial API on a controller restarts unexpectedly, the node ID length is now synchronized again (#6271)

### Config file changes
* Add Heatit Z-TRM6 (#6263)
* Increase poll delay for ZW500D (#6270)
* Add fingerprint for Simon IO Master Roller Blind (#6262)
* Add HOPPE eHandle ConnectSense (#6269)
* Add parameters to Zooz ZEN17 from firmware 1.30 (#6189)
* Update Zooz ZEN32 config to the latest firmware, include 800 series (#6283)
* Add warnings about broken controller firmware versions (#6293)

### Changes under the hood
* Some Z-Wave JS specific checks are now done using a custom ESLint plugin (#6276, #6279)
* `yarn test` now only runs tests affected by changed files by default. This is also done on CI in PRs to speed up check times (#6274)
AlCalzone added a commit that referenced this pull request Sep 21, 2023
### Bugfixes
* Fixed an issue where some `Notification CC Reports` including an enumeration value would cause the corresponding value ID to be set to the wrong value (#6282)
* When the Serial API on a controller restarts unexpectedly, the node ID length is now synchronized again (#6271)

### Config file changes
* Add warnings about broken controller firmware versions (#6293)
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.

Wrong Home Health, VOC level status values
2 participants