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: consider max LR payload size in firmware updates #6759

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

AlCalzone
Copy link
Member

@AlCalzone AlCalzone commented Apr 11, 2024

This effectively increases the fragment size and reduces the update time by a factor of 5 🤯

Screencast.from.11.04.2024.09.52.42.webm

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) April 11, 2024 07:58
@zwave-js-bot zwave-js-bot merged commit 07fe7d6 into master Apr 11, 2024
15 checks passed
@zwave-js-bot zwave-js-bot deleted the zwlr-payload-size branch April 11, 2024 08:03
AlCalzone added a commit that referenced this pull request Apr 12, 2024
### Bugfixes
* Firmware updates on Z-Wave Long Range now utilize the larger frame size better (#6759)
* Fixed an issue where multicast `setValue` had a `SupervisionCCReport` as the result instead of a `SetValueResult` (#6765)
* Parsing of provisioning entries with numeric `supportedProtocols` (#6764)
* Fix error when `ConfigurationCCBulkGet` response is missing (#6763)
* Values from force-removed or endpoint-mapped CCs are no longer persisted (#6760)

### Config file changes
* Fix versioning logic for parameter 26 of Zooz ZEN72 (#6761)
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