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: reset controller again when transmit stalls after reset, don't block by enabling watchdog #6968

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

AlCalzone
Copy link
Member

If the repeated communication attempt after recovering the controller with a soft-reset also made the controller become unresponsive, the controller would stay unresponsive until some other action would reset it again.

With this PR, we try to recover the controller in this situation again. Also, enabling the watchdog after a planned soft-reset now no longer blocks everything.

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) June 26, 2024 11:20
@zwave-js-bot zwave-js-bot merged commit e4dad3f into master Jun 26, 2024
15 checks passed
@zwave-js-bot zwave-js-bot deleted the fix-unresponsive-recovery branch June 26, 2024 11:26
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.

None yet

2 participants