Change README.

Author: janiversen

README.md

@@ -34,33 +34,15 @@ Enjoy a working modbus, if you encounter a problem feel free to open a issue [di
 I do also monitor the home assistant issues.
 
 
-Testing 
-===
-
-To run the test suite create a virtualenv and install test dependencies::
-
-   $ python3 -m venv venv
-   $ pip install -r requirements.test.txt
-
-After the test dependencies are installed you can simply invoke `pytest` to run
-the test suite::
-
-   $ pytest
-
-
 Custom modbus in a nutshell
 ===
 
-This is a custom component version of the official Homeassistant modbus,
-with active maintenance.
-
-The custom component is Homeassistant modbus++, because changes in the official
-component are integrated here on a regular basis.
-
-Both homeassistant issues and the homeassistant user forum are monitored and
-problems are fixed as fast as possible.
+This is a custom component version of the official Homeassistant modbus, The
+custom component is Homeassistant modbus++, because the official version is the
+base for all commits in here. Whenever the official version changes, this repository
+is updated.
 
-REMARK: custom modbus is part of the pymodbus development organisation, tying it
+REMARK: custom modbus is part of the pymodbus development organisation, connecting it
 firmly to pymodbus.
 
 
@@ -70,28 +52,26 @@ Why a custom component ?
 The reason involves a bit of history.
 
 I maintained the homeassistant modbus component for years and had 
-developer status in the homeassistant repo. In fact at the time of writing 
-this I am still #34 alltime most active contributor in
-[homeassistant](https://github.com/home-assistant/core/graphs/contributors)
+developer status in the homeassistant repo due to being very active.
 
-For a lot of reasons I decided to take a leave of absence, however the Core team
-retained my developer status.
+For a lot of reasons I decided to take a leave of absence, however my developer
+status was untouched.
 
 When I started contributing again, the Core team cancelled my developer status,
 signalling that my contributions were no longer welcome.
 
-Since I need a working modbus component, I maintained a private version,
-lately after talks with several users, I decided to turn it into a HACS custom component,
-giving modbus users an alternative to the broken official component.
+After talks with several users, I turned my private version into a HACS
+custom component, giving modbus users an alternative to the broken official
+component.
 
-This is NOT the preferred way, nor the best way, but for me the only way !
+This is NOT the preferred way, nor the best way, but I saw no other way !
 
 
 Contributing
 ===
 
 We actively monitor both homeassistant issues and the homeassistant user forum for
-modbus issues, and then solves (if possible) the problems in this component.
+modbus issues, and try to solve them (if possible) in this component.
 
 If we have missed your problem/issue, then please feel free to open an issue in
 [here](https://github.com/pymodbus-dev/homeassistant_modbus/issues>)
@@ -102,5 +82,3 @@ License Information
 
 Released under a modified [APACHE 2 License](https://github.com/pymodbus-dev/homeassistant_modbus/blob/dev/LICENSE)
 
-Remark: the license prohibits use or copy content of this repository in order to update
-the official modbus component.

custom_components/modbus/WARNING

@@ -1,3 +1,3 @@
-Please remark, the license do not permit copying or using the source code in anyform for the purpose of integrating into homeassistant modbus without the express permission of the author.
+Please remark, the license do not permit copying or using the source code in any form for the purpose of integrating into homeassistant modbus without the express permission of the author.
 
-Such permission will be given if files containing source code from this repository contains a link to this directory.
+Such permission will be given if files containing source code from this repository contains a link to this repository.

custom_components/modbus/manifest.json

@@ -7,5 +7,5 @@
   "issue_tracker": "https://github.com/pymodbus-dev/homeassistant_modbus/issues",
   "loggers": ["pymodbus"],
   "requirements": ["pymodbus==3.11.0"],
-  "version": "1.0.1"
+  "version": "1.0.2"
 }

open_issues

@@ -5,16 +5,14 @@
 
 # Issues from HA
 #128554 Create Modbus Devices for each listed connection point in Modbus configuration
-#130093 Something is blocking Home Assistant from wrapping up the start up phase
-#138077 Modbus value spike issues since last update (2025.2.x) : values mixed from wrong sensor
+#138077 Modbus value spike issues : values mixed from wrong sensor
 #138585 [pymodbus.logging] Exception response 132 / 0
 #140580 Modbus integration gets stuck every few days
 #142658 TCP/IP modbus connection work only once at HA start
 #146179 Mising information in modbus warning message
 #146246 Modbus integration ignores scan_interval and polls sensors far too frequently
 #146872 Modbus configuration doesn't create a device
 #147016 Modbus reading some values wrong from the same device
-#147271 MODBUS - deviation
 #147383 Issue with modbus integration
 #147564 Existing modbus integration of a Smartmeter stopped working as expected after HA update to 2025.6.1
 #148329 Modbus sensors can deliver wrong values, when modbus tries to reconnect.
@@ -24,3 +22,6 @@
 #149649 Modbus slave sensors not available when master sensor is deactivated
 #150191 Modbus dep problem after update to 2025.8.0
 
+# Not solveable
+#147271 MODBUS - deviation
+