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: expose Basic CC currentValue when compat flag says so #6964

Merged
merged 5 commits into from
Jun 26, 2024

Conversation

AlCalzone
Copy link
Member

fixes: #6963

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

zwave-js-bot
zwave-js-bot previously approved these changes Jun 25, 2024
@zwave-js-bot zwave-js-bot enabled auto-merge (squash) June 25, 2024 12:04
zwave-js-bot
zwave-js-bot previously approved these changes Jun 25, 2024
zwave-js-bot
zwave-js-bot previously approved these changes Jun 25, 2024
zwave-js-bot
zwave-js-bot previously approved these changes Jun 26, 2024
@zwave-js-bot zwave-js-bot merged commit 44d460b into master Jun 26, 2024
17 checks passed
@zwave-js-bot zwave-js-bot deleted the basic-current-value-compat branch June 26, 2024 07:07
AlCalzone added a commit that referenced this pull request Jun 26, 2024
### Bugfixes
* Fixed an issue where the watchdog feature could cause Z-Wave JS to stall after attempting controller recovery (#6968)
* Reset controller again when transmitting to a problematic node makes the controller become unresponsive again after automatic recovery (#6968)
* Node interviews are now aborted in more cases when node is determined to be dead (#6967)
* Expose Basic CC `currentValue` when certain compat flags are set (#6964)
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.

Basic CC currentValue is not exposed despite compat.mapBasicReport: false
2 participants