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.

Sign up for GitHub

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

Jump to bottom

fix: set priority for messages to sleeping nodes again #6953

Merged
merged 1 commit into from
Jun 22, 2024
Merged

fix: set priority for messages to sleeping nodes again #6953

merged 1 commit into from
Jun 22, 2024

Conversation

AlCalzone
Copy link
Member

#6944 broke queuing message to sleeping nodes due to too much code being removed. This PR adds a test for the situation and fixes the break.

fixes: #6952

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) June 22, 2024 20:06
@zwave-js-bot zwave-js-bot merged commit cf55e06 into master Jun 22, 2024
15 checks passed
@zwave-js-bot zwave-js-bot deleted the fix-sleeping-blocker branch June 22, 2024 20:08
AlCalzone added a commit that referenced this pull request Jun 22, 2024
@AlCalzone
chore: release v12.11.2
686c698 
### Bugfixes
* Fixed a regression from 12.11.1 causing commands to sleeping nodes to block the send queue (#6953)
* Fixed how routes for inbound frames are parsed in Zniffer (#6945)
@tonymartino
Copy link

Thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@zwave-js-bot zwave-js-bot zwave-js-bot approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Controller Becomes Unresponsive After Setting New Config Value For Battery Device
3 participants
@AlCalzone @tonymartino @zwave-js-bot