Skip to content

Conversation

@janiversen
Copy link
Collaborator

No description provided.

@janiversen janiversen merged commit 2f87de9 into dev Mar 6, 2025
1 check passed
@janiversen janiversen deleted the slave branch March 6, 2025 18:09
@hyrodium
Copy link

This is a breaking change. I think the latest release should be v4.0.0, not v3.10.0.

@janiversen
Copy link
Collaborator Author

Did you read the README, pymodbus does minor API. changes in x.y releases.

It is clearly documented what releases can contain ! you might like to have another way of doing it, but we have quite a lot of reasons for not doing semver.

v3.10 contains changes which you can solve with a simple edit. v4.0.0 will require a rewrite of parts of your program.

@hyrodium
Copy link

Oh, I am sorry that I have overlooked the README. I mistakenly thought it was semantic versioning.

svasek added a commit to svasek/homeassistant-vistapool-modbus that referenced this pull request Sep 4, 2025
* Fixed compatibility with pymodbus versions 3.9.x and 3.10+
* Introduced `modbus_acall` and `modbus_scall` for async and sync methods.
* Added `address_kwargs` to handle device_id and slave addressing.
* Created tests for the new compatibility functions to ensure correctness.

Related changes:
* pymodbus-dev/pymodbus#2600
* https://github.com/pymodbus-dev/pymodbus/blob/dev/API_changes.rst#api-changes-3100
* home-assistant/core#150129
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.

3 participants