modbus-connection 1.0.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,30 @@
1
+ name: CI
2
+
3
+ on:
4
+ push:
5
+ branches: [main]
6
+ pull_request:
7
+
8
+ permissions:
9
+ contents: read
10
+
11
+ jobs:
12
+ lint:
13
+ runs-on: ubuntu-latest
14
+ steps:
15
+ - uses: actions/checkout@v4
16
+ - uses: astral-sh/setup-uv@v6
17
+ - name: Ruff format
18
+ run: uvx ruff format --check .
19
+ - name: Ruff lint
20
+ run: uvx ruff check .
21
+
22
+ test:
23
+ runs-on: ubuntu-latest
24
+ steps:
25
+ - uses: actions/checkout@v4
26
+ - uses: astral-sh/setup-uv@v6
27
+ - name: Install dependencies
28
+ run: uv sync --extra pymodbus --extra tmodbus
29
+ - name: Run tests
30
+ run: uv run pytest
@@ -0,0 +1,34 @@
1
+ name: Publish to PyPI
2
+
3
+ on:
4
+ release:
5
+ types: [published]
6
+
7
+ jobs:
8
+ build:
9
+ runs-on: ubuntu-latest
10
+ steps:
11
+ - uses: actions/checkout@v4
12
+ - uses: astral-sh/setup-uv@v6
13
+ - name: Set package version from release tag
14
+ env:
15
+ RELEASE_TAG: ${{ github.event.release.tag_name }}
16
+ run: sed -i "s/^version = \"0\\.0\\.0\"$/version = \"${RELEASE_TAG}\"/" pyproject.toml
17
+ - run: uv build
18
+ - uses: actions/upload-artifact@v4
19
+ with:
20
+ name: dist
21
+ path: dist/
22
+
23
+ publish:
24
+ needs: build
25
+ runs-on: ubuntu-latest
26
+ environment: pypi
27
+ permissions:
28
+ id-token: write
29
+ steps:
30
+ - uses: actions/download-artifact@v4
31
+ with:
32
+ name: dist
33
+ path: dist/
34
+ - uses: pypa/gh-action-pypi-publish@release/v1
@@ -0,0 +1,21 @@
1
+ # Python
2
+ __pycache__/
3
+ *.py[cod]
4
+ *.egg-info/
5
+ .eggs/
6
+ build/
7
+ dist/
8
+
9
+ # Environments
10
+ .venv/
11
+ .env
12
+
13
+ # Tooling
14
+ .pytest_cache/
15
+ .ruff_cache/
16
+ .mypy_cache/
17
+ .coverage
18
+ htmlcov/
19
+
20
+ # uv
21
+ uv.lock
@@ -0,0 +1,9 @@
1
+ # Run with prek (https://github.com/j178/prek): `prek install` then commits are
2
+ # auto-formatted; `prek run --all-files` to check everything.
3
+ repos:
4
+ - repo: https://github.com/astral-sh/ruff-pre-commit
5
+ rev: v0.15.18
6
+ hooks:
7
+ - id: ruff-format
8
+ - id: ruff-check
9
+ args: [--fix]
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
@@ -0,0 +1,157 @@
1
+ Metadata-Version: 2.4
2
+ Name: modbus-connection
3
+ Version: 1.0.0
4
+ Summary: A small, backend-neutral Modbus connection abstraction (pymodbus / tmodbus).
5
+ Project-URL: Homepage, https://github.com/home-assistant-libs/modbus-connection
6
+ Author: home-assistant-libs
7
+ License: Apache-2.0
8
+ License-File: LICENSE
9
+ Keywords: home-assistant,modbus,pymodbus,tmodbus
10
+ Classifier: License :: OSI Approved :: Apache Software License
11
+ Classifier: Programming Language :: Python :: 3
12
+ Classifier: Topic :: System :: Hardware
13
+ Requires-Python: >=3.12
14
+ Provides-Extra: pymodbus
15
+ Requires-Dist: pymodbus[serial]<3.12,>=3.11; extra == 'pymodbus'
16
+ Provides-Extra: tmodbus
17
+ Requires-Dist: serialx>=0.1; extra == 'tmodbus'
18
+ Requires-Dist: tmodbus>=0.3; extra == 'tmodbus'
19
+ Description-Content-Type: text/markdown
20
+
21
+ # modbus-connection
22
+
23
+ A small, **backend-neutral** Modbus connection abstraction.
24
+
25
+ The top-level `modbus_connection` package is a pure interface — the
26
+ `ModbusConnection` / `ModbusUnit` [Protocols](https://typing.readthedocs.io/en/latest/spec/protocol.html),
27
+ the shared `WordOrder` type, and a tiny exception hierarchy. It imports **no**
28
+ Modbus library and **no** Home Assistant, so consumers can type against it
29
+ without committing to a backend.
30
+
31
+ Two interchangeable backends implement that interface:
32
+
33
+ | Backend | Module | Extra |
34
+ | --- | --- | --- |
35
+ | [pymodbus](https://github.com/pymodbus-dev/pymodbus) | `modbus_connection.pymodbus` | `[pymodbus]` |
36
+ | [tmodbus](https://github.com/wlcrs/tmodbus) | `modbus_connection.tmodbus` | `[tmodbus]` |
37
+
38
+ The bare install pulls neither backend.
39
+
40
+ ## Why
41
+
42
+ One physical Modbus link addresses many units (1–247). Sharing a single,
43
+ internally-serialized connection across many consumers is strictly better than
44
+ each opening a competing socket. This package is the connection abstraction that
45
+ makes that sharing possible while keeping the backend swappable: the
46
+ `Protocol` never changes when the backend does.
47
+
48
+ ## Design
49
+
50
+ - A connection is **transient** and **owner-held**. A backend *connect function*
51
+ returns a live, already-connected instance — there is no `connect()` on the
52
+ object.
53
+ - Requests are serialized per connection — but by the backend library, not by
54
+ this wrapper: pymodbus's transaction manager and tmodbus's smart transport
55
+ each hold a lock for the full request/response cycle, so concurrent unit calls
56
+ on one connection can't interleave.
57
+ - The connection does **not** self-reconnect. On a drop it fires
58
+ `on_connection_lost` (best-effort) and stops; recreating it is the owner's job.
59
+ - Consumers receive a **`ModbusUnit`** (via `connection.for_unit(unit_id)`), a
60
+ stateless per-unit handle with no lifecycle methods. Every method **raises** on
61
+ failure — it never returns `None`.
62
+ - The full 19-function-code Modbus surface is exposed, plus typed reads
63
+ (`read_uint16`, `read_float32`, …) that own datatype + word/byte ordering. A
64
+ backend that cannot implement a code raises `NotImplementedError`.
65
+
66
+ ## Install
67
+
68
+ ```bash
69
+ pip install "modbus-connection[pymodbus]" # pymodbus backend
70
+ pip install "modbus-connection[tmodbus]" # tmodbus backend
71
+ ```
72
+
73
+ ## Use
74
+
75
+ ```python
76
+ import asyncio
77
+ from modbus_connection.pymodbus import connect_tcp
78
+
79
+
80
+ async def main() -> None:
81
+ conn = await connect_tcp("192.168.1.50", port=502)
82
+ try:
83
+ unit = conn.for_unit(1)
84
+ outside_temp = await unit.read_int16(9) # raw register, signed
85
+ flow_setpoint = await unit.read_float32(40, word_order="big")
86
+ pump_on = (await unit.read_coils(56, 1))[0]
87
+ print(outside_temp, flow_setpoint, pump_on)
88
+ finally:
89
+ await conn.close()
90
+
91
+
92
+ asyncio.run(main())
93
+ ```
94
+
95
+ Swapping to tmodbus is a one-line import change:
96
+
97
+ ```python
98
+ from modbus_connection.tmodbus import connect_tcp
99
+ ```
100
+
101
+ ## Exceptions
102
+
103
+ Both backends raise the same neutral types:
104
+
105
+ - `ModbusError` — base class.
106
+ - `ModbusConnectionError` — link down / not connected / transport failure.
107
+ - `ModbusTimeoutError` — request sent, no valid response in time.
108
+ - `ModbusExceptionError` — device returned a Modbus exception response
109
+ (`.exception_code` carries the raw code).
110
+
111
+ ## Testing
112
+
113
+ An in-memory mock backend ships as a `pytest` plugin (auto-registered via an
114
+ entry point — no `conftest` wiring). It implements the same Protocols, so code
115
+ typed against `ModbusUnit` runs against it unchanged.
116
+
117
+ ```python
118
+ async def test_reads_setpoint(mock_modbus_unit):
119
+ mock_modbus_unit.holding[40] = 1234 # single value
120
+ mock_modbus_unit.holding[2] = [0x0001, 0x86A0] # list -> consecutive registers
121
+ mock_modbus_unit.holding[9] = lambda: 7 # callable -> evaluated per read
122
+
123
+ assert await mock_modbus_unit.read_uint16(40) == 1234
124
+ assert await mock_modbus_unit.read_uint32(2) == 100000
125
+ ```
126
+
127
+ Reads resolve against the per-space stores (`holding`, `input`, `coils`,
128
+ `discrete_inputs`); writes mutate them and fire `on_write` callbacks, so a test
129
+ can react to a write by mocking other registers:
130
+
131
+ ```python
132
+ def test_command_sets_ready(mock_modbus_unit):
133
+ def respond(event):
134
+ if event.address == 0: # a command was written
135
+ mock_modbus_unit.holding[100] = 1 # device flips its "ready" flag
136
+ mock_modbus_unit.on_write(respond)
137
+ ```
138
+
139
+ Fixtures: `mock_modbus_connection` (a `MockModbusConnection`) and
140
+ `mock_modbus_unit` (its unit 1). `MockModbusConnection` / `MockModbusUnit` are
141
+ also importable from `modbus_connection.mock` for direct construction.
142
+
143
+ ## Develop
144
+
145
+ ```bash
146
+ uv sync --extra pymodbus
147
+ uv run pytest
148
+ ```
149
+
150
+ Formatting/linting is [ruff](https://docs.astral.sh/ruff/), enforced in CI. Install
151
+ the commit hook with [prek](https://github.com/j178/prek) so code is formatted on
152
+ commit:
153
+
154
+ ```bash
155
+ uvx prek install # set up the git hook
156
+ uvx prek run --all-files # format + lint everything now
157
+ ```
@@ -0,0 +1,137 @@
1
+ # modbus-connection
2
+
3
+ A small, **backend-neutral** Modbus connection abstraction.
4
+
5
+ The top-level `modbus_connection` package is a pure interface — the
6
+ `ModbusConnection` / `ModbusUnit` [Protocols](https://typing.readthedocs.io/en/latest/spec/protocol.html),
7
+ the shared `WordOrder` type, and a tiny exception hierarchy. It imports **no**
8
+ Modbus library and **no** Home Assistant, so consumers can type against it
9
+ without committing to a backend.
10
+
11
+ Two interchangeable backends implement that interface:
12
+
13
+ | Backend | Module | Extra |
14
+ | --- | --- | --- |
15
+ | [pymodbus](https://github.com/pymodbus-dev/pymodbus) | `modbus_connection.pymodbus` | `[pymodbus]` |
16
+ | [tmodbus](https://github.com/wlcrs/tmodbus) | `modbus_connection.tmodbus` | `[tmodbus]` |
17
+
18
+ The bare install pulls neither backend.
19
+
20
+ ## Why
21
+
22
+ One physical Modbus link addresses many units (1–247). Sharing a single,
23
+ internally-serialized connection across many consumers is strictly better than
24
+ each opening a competing socket. This package is the connection abstraction that
25
+ makes that sharing possible while keeping the backend swappable: the
26
+ `Protocol` never changes when the backend does.
27
+
28
+ ## Design
29
+
30
+ - A connection is **transient** and **owner-held**. A backend *connect function*
31
+ returns a live, already-connected instance — there is no `connect()` on the
32
+ object.
33
+ - Requests are serialized per connection — but by the backend library, not by
34
+ this wrapper: pymodbus's transaction manager and tmodbus's smart transport
35
+ each hold a lock for the full request/response cycle, so concurrent unit calls
36
+ on one connection can't interleave.
37
+ - The connection does **not** self-reconnect. On a drop it fires
38
+ `on_connection_lost` (best-effort) and stops; recreating it is the owner's job.
39
+ - Consumers receive a **`ModbusUnit`** (via `connection.for_unit(unit_id)`), a
40
+ stateless per-unit handle with no lifecycle methods. Every method **raises** on
41
+ failure — it never returns `None`.
42
+ - The full 19-function-code Modbus surface is exposed, plus typed reads
43
+ (`read_uint16`, `read_float32`, …) that own datatype + word/byte ordering. A
44
+ backend that cannot implement a code raises `NotImplementedError`.
45
+
46
+ ## Install
47
+
48
+ ```bash
49
+ pip install "modbus-connection[pymodbus]" # pymodbus backend
50
+ pip install "modbus-connection[tmodbus]" # tmodbus backend
51
+ ```
52
+
53
+ ## Use
54
+
55
+ ```python
56
+ import asyncio
57
+ from modbus_connection.pymodbus import connect_tcp
58
+
59
+
60
+ async def main() -> None:
61
+ conn = await connect_tcp("192.168.1.50", port=502)
62
+ try:
63
+ unit = conn.for_unit(1)
64
+ outside_temp = await unit.read_int16(9) # raw register, signed
65
+ flow_setpoint = await unit.read_float32(40, word_order="big")
66
+ pump_on = (await unit.read_coils(56, 1))[0]
67
+ print(outside_temp, flow_setpoint, pump_on)
68
+ finally:
69
+ await conn.close()
70
+
71
+
72
+ asyncio.run(main())
73
+ ```
74
+
75
+ Swapping to tmodbus is a one-line import change:
76
+
77
+ ```python
78
+ from modbus_connection.tmodbus import connect_tcp
79
+ ```
80
+
81
+ ## Exceptions
82
+
83
+ Both backends raise the same neutral types:
84
+
85
+ - `ModbusError` — base class.
86
+ - `ModbusConnectionError` — link down / not connected / transport failure.
87
+ - `ModbusTimeoutError` — request sent, no valid response in time.
88
+ - `ModbusExceptionError` — device returned a Modbus exception response
89
+ (`.exception_code` carries the raw code).
90
+
91
+ ## Testing
92
+
93
+ An in-memory mock backend ships as a `pytest` plugin (auto-registered via an
94
+ entry point — no `conftest` wiring). It implements the same Protocols, so code
95
+ typed against `ModbusUnit` runs against it unchanged.
96
+
97
+ ```python
98
+ async def test_reads_setpoint(mock_modbus_unit):
99
+ mock_modbus_unit.holding[40] = 1234 # single value
100
+ mock_modbus_unit.holding[2] = [0x0001, 0x86A0] # list -> consecutive registers
101
+ mock_modbus_unit.holding[9] = lambda: 7 # callable -> evaluated per read
102
+
103
+ assert await mock_modbus_unit.read_uint16(40) == 1234
104
+ assert await mock_modbus_unit.read_uint32(2) == 100000
105
+ ```
106
+
107
+ Reads resolve against the per-space stores (`holding`, `input`, `coils`,
108
+ `discrete_inputs`); writes mutate them and fire `on_write` callbacks, so a test
109
+ can react to a write by mocking other registers:
110
+
111
+ ```python
112
+ def test_command_sets_ready(mock_modbus_unit):
113
+ def respond(event):
114
+ if event.address == 0: # a command was written
115
+ mock_modbus_unit.holding[100] = 1 # device flips its "ready" flag
116
+ mock_modbus_unit.on_write(respond)
117
+ ```
118
+
119
+ Fixtures: `mock_modbus_connection` (a `MockModbusConnection`) and
120
+ `mock_modbus_unit` (its unit 1). `MockModbusConnection` / `MockModbusUnit` are
121
+ also importable from `modbus_connection.mock` for direct construction.
122
+
123
+ ## Develop
124
+
125
+ ```bash
126
+ uv sync --extra pymodbus
127
+ uv run pytest
128
+ ```
129
+
130
+ Formatting/linting is [ruff](https://docs.astral.sh/ruff/), enforced in CI. Install
131
+ the commit hook with [prek](https://github.com/j178/prek) so code is formatted on
132
+ commit:
133
+
134
+ ```bash
135
+ uvx prek install # set up the git hook
136
+ uvx prek run --all-files # format + lint everything now
137
+ ```
@@ -0,0 +1,52 @@
1
+ [build-system]
2
+ requires = ["hatchling"]
3
+ build-backend = "hatchling.build"
4
+
5
+ [project]
6
+ name = "modbus-connection"
7
+ version = "1.0.0"
8
+ description = "A small, backend-neutral Modbus connection abstraction (pymodbus / tmodbus)."
9
+ readme = "README.md"
10
+ requires-python = ">=3.12"
11
+ license = { text = "Apache-2.0" }
12
+ authors = [{ name = "home-assistant-libs" }]
13
+ keywords = ["modbus", "pymodbus", "tmodbus", "home-assistant"]
14
+ classifiers = [
15
+ "Programming Language :: Python :: 3",
16
+ "License :: OSI Approved :: Apache Software License",
17
+ "Topic :: System :: Hardware",
18
+ ]
19
+ dependencies = []
20
+
21
+ [project.optional-dependencies]
22
+ pymodbus = ["pymodbus[serial]>=3.11,<3.12"]
23
+ tmodbus = ["tmodbus>=0.3", "serialx>=0.1"]
24
+
25
+ [project.entry-points.pytest11]
26
+ modbus_connection = "modbus_connection.pytest_plugin"
27
+
28
+ [project.urls]
29
+ Homepage = "https://github.com/home-assistant-libs/modbus-connection"
30
+
31
+ [dependency-groups]
32
+ dev = [
33
+ "pytest>=8",
34
+ "pytest-asyncio>=0.24",
35
+ "pymodbus[serial]>=3.11,<3.12",
36
+ "tmodbus>=0.3",
37
+ "serialx>=0.1",
38
+ ]
39
+
40
+ [tool.hatch.build.targets.wheel]
41
+ packages = ["src/modbus_connection"]
42
+
43
+ [tool.pytest.ini_options]
44
+ asyncio_mode = "auto"
45
+ testpaths = ["tests"]
46
+
47
+ [tool.ruff]
48
+ target-version = "py312"
49
+ src = ["src"]
50
+
51
+ [tool.ruff.lint]
52
+ select = ["E", "F", "W", "I", "UP", "B"]
@@ -0,0 +1,31 @@
1
+ """modbus_connection — a small, backend-neutral Modbus connection abstraction.
2
+
3
+ The top-level package is the pure interface: the ``ModbusConnection`` /
4
+ ``ModbusUnit`` Protocols, the shared ``WordOrder`` type, and the exception
5
+ hierarchy. It imports no Modbus backend and no Home Assistant.
6
+
7
+ Pick a backend to actually talk to a device:
8
+
9
+ - ``modbus_connection.pymodbus`` — ``connect_tcp`` / ``connect_serial`` over
10
+ pymodbus (install the ``[pymodbus]`` extra).
11
+ - ``modbus_connection.tmodbus`` — the same over tmodbus (the ``[tmodbus]`` extra).
12
+ """
13
+
14
+ from ._protocol import ModbusConnection, ModbusUnit
15
+ from ._types import WordOrder
16
+ from .exceptions import (
17
+ ModbusConnectionError,
18
+ ModbusError,
19
+ ModbusExceptionError,
20
+ ModbusTimeoutError,
21
+ )
22
+
23
+ __all__ = [
24
+ "ModbusConnection",
25
+ "ModbusConnectionError",
26
+ "ModbusError",
27
+ "ModbusExceptionError",
28
+ "ModbusTimeoutError",
29
+ "ModbusUnit",
30
+ "WordOrder",
31
+ ]