Modbus issues - values can be read but log full of errors

Hello,
modbus binding is running on an openhab 2.5 server. Information should be collected from a SMA inverter.
I am receiving values via modbus but additionally my logs are full with this error message:

2022-03-08 13:45:41.706 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@31225d41[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@3bda3631[address=192.168.100.48,port=502]
2022-03-08 13:45:41.706 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@31225d41[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@3bda3631[address=192.168.100.48,port=502]
2022-03-08 13:45:41.706 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@31225d41[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@3bda3631[address=192.168.100.48,port=502]: connect timed out
2022-03-08 13:45:41.707 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@3bda3631[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@5db32de1[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID 8b8938ae-827c-45b7-8e87-fe400c5edaf6]
2022-03-08 13:45:51.215 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@5db32de1[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 0 [operation ID fff6b0ad-6875-41d7-aec1-0d722a2c8b34]
2022-03-08 13:45:51.275 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint@5db32de1[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IndexOutOfBoundsException null [operation ID fff6b0ad-6875-41d7-aec1-0d722a2c8b34]
2022-03-08 13:45:51.735 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@5db32de1[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 0 [operation ID 3daef0fc-0c22-40d0-a012-abbd5a42b2c0]
2022-03-08 13:45:51.796 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint@5db32de1[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IndexOutOfBoundsException null [operation ID 3daef0fc-0c22-40d0-a012-abbd5a42b2c0]
2022-03-08 13:45:52.215 [ERROR] [rt.modbus.internal.ModbusManagerImpl] - Last try 3 failed when executing request (ModbusReadRequestBlueprint@5db32de1[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Aborting. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 0 [operation ID 3daef0fc-0c22-40d0-a012-abbd5a42b2c0]

Do you have any ideas what could be wrong?
Here a stripped things and items setup (this is already doing error messages)

Bridge modbus:tcp:tripower "SMA Sunny Tripower 9000TL-20"  [ host="192.168.100.48", port=502, id=3, reconnectAfterMillis=6000 ] {
	Bridge poller devicedaten_30053 "Geraete Spezifikation" [ start=30053, length=4, refresh=60000, type="input" ] {
        Thing data sma_type_30053 "SMA Wechselrichter Type" [ readStart="30053", readValueType="uint32" ]
        }

        Bridge poller input_30769_114 "TP_Input_30769_114" [ start=30773, length=114, refresh=2000, type="input" ] {
        Thing data 30773_2 "TP_30773_2" [ readStart="30773", readValueType="int32"]
        Thing data 30775_2 "TP_30775_2" [ readStart="30775", readValueType="int32"]
        Thing data 30839_2 "TP_30839_2" [ readStart="30839", readValueType="uint32"]
}
Number TPDCInput1               "DC-Input 1 [%d W]"   (gPV)  { channel=" modbus:data:tripower:input_30769_114:30773_2:number" }

Number TPLeistung               "Leistung [%d W]"   (gPV)  { channel=" modbus:data:tripower:input_30769_114:30775_2:number" }

Number TPLeistungsbegrenzung    "Leistungsverwendung [%d %%]"   (gPV)  { channel=" modbus:data:tripower:input_30769_114:30839_2:number" }

String sma_type_30053           "Wechselrichter Typ [%s]"   (gPV)  { channe

That is clear enough. No response from the other end.

Possible network congestion, incorrect address targets, slave device too busy to respond.

You might consider changing from default here, to reduce churn on the connection.
See the TCP section here -

I understand the "connect time out " issue but why do my items receive (reasonable) values from this things even if the error tells us it can not connect?

Because it is polling every two seconds, and presumably works sometimes. That’s good, your basic addressing is correct.

I deleted the " reconnectAfterMillis=6000 "

but error keeps going

2022-03-09 13:11:00.554 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@383137ab[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@5ce0fbb8[address=192.168.100.48,port=502]
2022-03-09 13:11:00.555 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@383137ab[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@5ce0fbb8[address=192.168.100.48,port=502]
2022-03-09 13:11:00.555 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@383137ab[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@5ce0fbb8[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:11:00.557 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@5ce0fbb8[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@24f1fdf3[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30053,length=4,maxTries=3] [operation ID fac6219c-d946-4799-b137-a1e33ecba4b8]

Then I added timeBetweenReconnectMillis=5000 becaus my thought was maybe the requests are coming too fast for the SMA but similar errors

I don’t see why. Stuff usually works better if you are able to extend this time, saves thrashing about on reconnects.

Bear in mind many Modbus TCP slaves only permit one TCP connection at a time, so don’t have other systems using your SMA Modbus at the same time.

Maybe I misunderstood.

What would your recommendation to add?

Try it at ten minutes, and see what happens. You’ve not told us how often you get the error.

Caution - small edits to Things configuration in xxx.things files are not always acted on immediately, sometimes a binding restart is needed.

You should really read that linked TCP post carefully - you may need to allow a longer time between reconnect as well or instead of extended after a period…

I tried it with 30000 and restarted openhab container afterwards.

2022-03-09 13:43:45.551 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@58eab685[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:43:45.552 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@58eab685[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:43:45.552 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@58eab685[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:43:45.558 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@40157826[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30053,length=4,maxTries=3] [operation ID dc3f0050-25b9-4a6f-b540-4167adf8dc22]
2022-03-09 13:43:55.566 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@347b1c0b[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:43:55.567 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@347b1c0b[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:43:55.567 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@347b1c0b[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:43:55.581 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@13c66fb3[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID 63131ed2-eb6b-406e-b819-15006ec96cca]
2022-03-09 13:44:05.589 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@17f9f994[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:05.589 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@17f9f994[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:05.589 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@17f9f994[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:44:05.590 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@25c9bad4[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3] [operation ID 017b39e5-bc92-4ab3-a872-695d4e43469a]
2022-03-09 13:44:15.594 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@21f63a32[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:15.595 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@21f63a32[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:15.595 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@21f63a32[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:44:15.596 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@13c66fb3[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID 0d427d3c-35d9-4a16-bb63-fc40ed7863f7]
2022-03-09 13:44:25.596 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@d6b85c2[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:25.597 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@d6b85c2[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:25.597 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@d6b85c2[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:44:25.598 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@40157826[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30053,length=4,maxTries=3] [operation ID 8f4224fb-c1de-46b2-b29b-242f2cfff81b]
2022-03-09 13:44:35.600 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@219b5624[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:35.600 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@219b5624[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]
2022-03-09 13:44:35.600 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@219b5624[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502]: connect timed out
2022-03-09 13:44:35.601 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7008c093[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@13c66fb3[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID 0cc58b62-f6e1-42d6-b2c5-92636d5eb673]

You can see the reconnect attempt fails at first. Go and read that linked post, use timeBetweenReconnectMillis as well.

I read it several times but maybe due to my lack of English or IT skills I do not see the point … sorry

I changed it now to this:
Bridge modbus:tcp:tripower “SMA Sunny Tripower 9000TL-20” [ host=“192.168.100.48”, port=502, id=3, reconnectAfterMillis=300000, timeBetweenReconnectMillis=60000 ] {

error messages are still coming but less frequently, as expected (every 10 sec)
But the items are now empty, no values displayed

Let’s see those then.

There is an issue with the SMA Tripower inverter when reading an Uint32 register, try to set length=4 for a single uint32 register.

That worked for me,


2022-03-09 14:58:27.918 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@2fbad534[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:27.919 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@2fbad534[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:27.919 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@2fbad534[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]: connect timed out
2022-03-09 14:58:27.919 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@29ab4f18[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3] [operation ID 3f11b088-4e11-48c8-ab97-5a066eeacdf5]
2022-03-09 14:58:37.928 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@78d62e65[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:37.929 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@78d62e65[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:37.929 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@78d62e65[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]: connect timed out
2022-03-09 14:58:37.929 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@2ed47be2[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID 2f9e8f25-41ee-4f78-adc1-95210a8ee1f7]
2022-03-09 14:58:47.937 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@780b6e41[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:47.937 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@780b6e41[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:47.938 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@780b6e41[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]: connect timed out
2022-03-09 14:58:47.938 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@29ab4f18[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3] [operation ID 44b88a73-36eb-48c8-b4d1-8791dddd8654]
2022-03-09 14:58:57.943 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@3f8c3b6b[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:57.944 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@3f8c3b6b[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:58:57.944 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@3f8c3b6b[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]: connect timed out
2022-03-09 14:58:57.944 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@6a59ffdd[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30053,length=4,maxTries=3] [operation ID c1bd1f2d-6390-4cd8-a33b-07ec2ee5d74c]
2022-03-09 14:59:07.952 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@25d67dc2[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:59:07.952 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@25d67dc2[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]
2022-03-09 14:59:07.953 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@25d67dc2[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502]: connect timed out
2022-03-09 14:59:07.954 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@7fe97bdc[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@2ed47be2[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID b7704f32-cb88-4dc5-8da4-0d8f96899704]

I tried a little more.
On inverter I switched modbus server off an again on.
Things file had been renamed while I did that.
After restarting all again:

2022-03-09 15:18:23.650 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@2b2aac0e[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. The response did not match the request. Reseting the connection. Error details: org.openhab.io.transport.modbus.exception.ModbusUnexpectedTransactionIdException Transaction id of request (4) does not equal response (65283). Slave response is invalid. [operation ID 6034d712-e4a4-4d03-8ffe-89306c7643ed]
2022-03-09 15:20:23.842 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@2b2aac0e[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. The response did not match the request. Reseting the connection. Error details: org.openhab.io.transport.modbus.exception.ModbusUnexpectedTransactionIdException Transaction id of request (6) does not equal response (65285). Slave response is invalid. [operation ID c125b0ce-1352-4874-95af-0da74551e4e6]
2022-03-09 15:20:50.947 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'sma.things'
2022-03-09 15:20:50.962 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 0/1 error: sleep interrupted. Aborting since interrupted. Connection TCPMasterConnection@a4be995[socket=<null>]. Endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502].
2022-03-09 15:20:50.963 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@2b2aac0e[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3] [operation ID c421e5b9-8990-439b-b716-9625f2c33eaf]
2022-03-09 15:22:32.181 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@2b2aac0e[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: SocketTimeoutException Read timed out [operation ID a8019263-bea5-4868-b00a-41bdbc903684]
2022-03-09 15:24:38.254 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint@2b2aac0e[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30773,length=114,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: SocketTimeoutException Read timed out [operation ID 6034d712-e4a4-4d03-8ffe-89306c7643ed]

but still no values in items to see

Make sure you have defined only one TCP bridge for your device. You may have duplicated by renaming files - look in the GUI at your Things.

Simplify your problem by reducing to one poller.

Respond to earlier comments about possible conflict with other services accessing the SMA modbus.

OK, my things file is now looking like that:
I commented the additionals out.

Just for my better understanding for future setup

I should do
a bridge poller with only one thing data below? or can there be more thing datas?

Bridge modbus:tcp:tripower "SMA Sunny Tripower 9000TL-20"  [ host="192.168.100.48", port=502, id=3, reconnectAfterMillis=300000, timeBetweenReconnectMillis=120000 ] {

        /*Bridge poller devicedaten_30053 "Geraete Spezifikation" [ start=30053, length=4, refresh=60000, type="input" ] {

        Thing data sma_type_30053 "SMA Wechselrichter Type" [ readStart="30053", readValueType="uint32" ]

        }

 

        Bridge poller input_30769_114 "TP_Input_30769_114" [ start=30773, length=114, refresh=2000, type="input" ] {

        Thing data 30773_2 "TP_30773_2" [ readStart="30773", readValueType="int32"]

        Thing data 30775_2 "TP_30775_2" [ readStart="30775", readValueType="int32"]

        Thing data 30839_2 "TP_30839_2" [ readStart="30839", readValueType="uint32"]

        }*/

        Bridge poller input_30949_34 "TP_Input_30949_34" [ start=30961, length=4, refresh=2000, type="input" ] {

        Thing data 30961_2 "TP_30961_2" [ readStart="30961", readValueType="int32"]

        }

}

The good thing I am receiving now a value for this thing data

log is now showing warnings … :

2022-03-09 15:47:02.934 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: SocketTimeoutException Read timed out [operation ID cfef3a43-3554-48bb-a91d-ca04b6c21a4d]
2022-03-09 15:49:00.155 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 0 [operation ID de86d93b-b0a9-4b35-918c-4d7897dcc695]
2022-03-09 15:49:00.217 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IndexOutOfBoundsException null [operation ID de86d93b-b0a9-4b35-918c-4d7897dcc695]
2022-03-09 15:51:00.206 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 0 [operation ID ed2713fc-2fb3-4402-8eac-5cb17af57484]
2022-03-09 15:51:00.267 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 2 out of 3 failed when executing request (ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3]). Will try again soon. Error was I/O error, so reseting the connection. Error details: net.wimpi.modbus.ModbusIOException I/O exception: IndexOutOfBoundsException null [operation ID ed2713fc-2fb3-4402-8eac-5cb17af57484]

A poller fetches a defined block of registers. Each poller may have many data Thing children, which define how to interpret those registers.

Your device is timing out when we are attempting a TCP connection. Possible causes, slow to respond, ignoring us, busy, network congestion or error rate.

What can I do to find the issue out.

we having the error message again

2022-03-09 16:03:20.188 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@142582ab[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502]
2022-03-09 16:03:20.188 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@142582ab[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502]
2022-03-09 16:03:20.188 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@142582ab[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502]: connect timed out
2022-03-09 16:03:20.189 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3] [operation ID b2a1857e-d32a-403e-b299-12f2053dda03]
2022-03-09 16:03:32.197 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: connect timed out. Connection TCPMasterConnection@5c0f4be3[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502]
2022-03-09 16:03:32.197 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: connect timed out. Connection TCPMasterConnection@5c0f4be3[socket=Socket[unconnected]]. Endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502]
2022-03-09 16:03:32.197 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection TCPMasterConnection@5c0f4be3[socket=Socket[unconnected]] for endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502]: connect timed out
2022-03-09 16:03:32.198 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusTCPSlaveEndpoint@3380c987[address=192.168.100.48,port=502] -- aborting request ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3] [operation ID 87c31716-e2c5-42af-87e5-49b65968aa9c]
2022-03-09 16:03:43.822 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Try 1 out of 3 failed when executing request (ModbusReadRequestBlueprint@47c6980a[slaveId=3,functionCode=READ_INPUT_REGISTERS,start=30961,length=4,maxTries=3]). Will try again soon. Error was: net.wimpi.modbus.ModbusSlaveException Error Code = 0 [operation ID 216f0bd6-fc92-40b4-87ac-874a4ba1c2b6]