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: populate tone names in metadata for Sound Switch CC defaultToneId #6452

Merged
merged 1 commit into from
Oct 23, 2023

Conversation

AlCalzone
Copy link
Member

No description provided.

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) October 23, 2023 14:36
@AlCalzone AlCalzone changed the title fix: populate tone names in metadata for default tone ID fix: populate tone names in metadata for Sound Switch CC defaultToneId Oct 23, 2023
@zwave-js-bot zwave-js-bot merged commit 3c729a4 into master Oct 23, 2023
14 checks passed
@zwave-js-bot zwave-js-bot deleted the default-tone-id-states branch October 23, 2023 14:43
AlCalzone added a commit that referenced this pull request Oct 24, 2023
### Bugfixes
* Fixed an issue where nodes would appear to have two lifeline associations, one with and one without target endpoint 0 (#6448)
* Writing to the `volume` value of the `Sound Switch CC` no longer throws an error, but pre-sets the volume to use for the next tone to be played using the `toneId` value (#6450, #6451)
* The `defaultToneId` value of the `Sound Switch CC` now also lists the names for each possible tone (#6452)

### Config file changes
* Treat `Binary Switch Set` and `Thermostat Mode Set` as reports for `SRT321 HRT4-ZW` (#6423)

### Changes under the hood
* Add compat flag to treat `Set` commands as `Report` (#6423)
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