Closed bsense-rius closed 8 months ago
hmmm that looks like a bug, but I believe it is solved on dev.
mmm. how could I manually install the develop version and try it? (just zip download from github and replace the pymodbus folder in venv, virtual environment folder?.
I will test asap and give you feedback
download the zip from github and replace the folder should do it.
Thanks for testing.
Specifically here's what we think fixed it: https://github.com/pymodbus-dev/pymodbus/pull/1890
Regarding testing the development version, assuming you have git
installed and are using pip
:
pip install git+https://github.com/pymodbus-dev/pymodbus@dev
v3.6.2 solves this issue.
Versions
Pymodbus Specific
Description
In the previous version 3.5.2, with AsyncModbusSerialClient, whenever an error occurred: slave not responding (e.g. incorrect address, timeout, ...) the library raised a ModbusException and everything was fine.
However in latest version 3.5.4, the very same code, under the same circumstances of error, the library returns what it seems to be an error: "2023-12-04 20:47:12.083 - INFO - ERROR! Exception catched: 'NoneType' object has no attribute 'close'"
The traceback helps to properly locate the point in the transport file
Code and Logs