Bump zwave-js-server-python to 0.56.0 #117288
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Breaking change
With this release, you will need to update your
zwave-js-server
instance. You must usezwave-js-server
1.35.0 or greater (schema 35).Proposed change
This bump forces users to upgrade to a zwave-js-server and driver version that support long range. It also adds some new long range specific attributes. This should be a no op for existing code, and just enables us to include the necessary attributes in the
zwave_js/network_status
WS API response.changelog: home-assistant-libs/zwave-js-server-python@0.55.4...0.56.0
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: