-
Notifications
You must be signed in to change notification settings - Fork 1k
Labels
Description
Versions
- Python: 3.8
- OS: hastío
- Pymodbus: 2.51
- Modbus Hardware (if used):
Pymodbus Specific
- Client: tcp - sync
Description
The modbus integration in home assistant uses pymodbus, and lately we have started getting more and more issues with
File "/usr/src/homeassistant/homeassistant/components/modbus/modbus.py", line 305, in _pymodbus_call
result = self._pb_call[use_call][ENTRY_FUNC](address, value, **kwargs)
File "/usr/local/lib/python3.9/site-packages/pymodbus/client/common.py", line 103, in write_registers
return self.execute(request)
File "/usr/local/lib/python3.9/site-packages/pymodbus/client/sync.py", line 109, in execute
return self.transaction.execute(request)
File "/usr/local/lib/python3.9/site-packages/pymodbus/transaction.py", line 194, in execute
response, last_exception = self._retry_transaction(retries, "empty", request, expected_response_length, full=full)
File "/usr/local/lib/python3.9/site-packages/pymodbus/transaction.py", line 250, in _retry_transaction
in_waiting = self.client._in_waiting()
AttributeError: 'ModbusTcpClient' object has no attribute '_in_waiting'
We use slave 0 as default, and some users inform that the error goes away if they specify a slave > 0, but this is not consistent.
I am the maintainer of the modbus integration.
Code and Logs
# code and logs here.
https://github.com/home-assistant/core/tree/dev/homeassistant/components/modbusAkkarine