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: ignore LR nodes when computing neighbor discovery timeout #7367

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

AlCalzone
Copy link
Member

fixes: #7269

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) November 5, 2024 12:57
@zwave-js-bot zwave-js-bot merged commit a21ca52 into master Nov 5, 2024
23 checks passed
@zwave-js-bot zwave-js-bot deleted the fix-neighbor-discovery-timeout branch November 5, 2024 13:00
AlCalzone added a commit that referenced this pull request Nov 6, 2024
### Features
* Allow specifying RF region for OTA firmware updates if the region is unknown or cannot be queried (#7369)
* Add `tryUnzipFirmwareFile` utility to support zipped OTA firmware files (#7372)

### Bugfixes
* Parse negative setback state consistently (#7366)
* Ignore LR nodes when computing neighbor discovery timeout (#7367)
* Automatically fall back to `Europe` when setting region to `Default (EU)` (#7368)

### Changes under the hood
* Improve bundler-friendlyness of `@zwave-js/core` and `@zwave-js/shared` with new browser-specific entry points and `sideEffects` hints (#7374)
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.

computeNeighborDiscoveryTimeout should ignore LR nodes
2 participants