Modbus binding loses its serial connection every few days without a reason after updating to 2.5.0 Release Build

Hello,

Since I have updated openhab to 2.5 I have had problems with the modbus binding that it seems to lose its serial connection. The first time it happened I could only repair it by removing the modbus binding and reinstalling it again.

The 2nd time it happened I couldn’t restore it with anything. Finally I did a completely new installation of openhab 2.5 and everything worked back immediately.

This went well for 3 days when it fell out again. I could now restore it by restarting openhab.
I currently don’t see any reason that this might cause it to happen?
I have not changed anything in my modbus configuration and the fact that it will go well for a few days I do not think it is in the configuration.

I don’t really know what else I can do now but openhab is not stable at all anymore?
Everything worked perfectly before the update to 2.5…

Platform information:Shuttle Inc. DX30D/FDX30, BIOS 1.03 10/30/2017
Hardware:Celeron® Processor J3355 two x86-64 CPU cores /RAM 4 gig /storage 120gig ssd
OS: Ubuntu 18.04.3 LTS (server)
java Runtime Environment: openjdk version “1.8.0_232”
OpenJDK Runtime Environment (Zulu 8.42.0.21-CA-linux32) (build 1.8.0_232-b18)
OpenJDK Server VM (Zulu 8.42.0.21-CA-linux32) (build 25.232-b18, mixed mode)
openHAB version:openHAB 2.5.0 Release Build.

#########################
## JAVA OPTIONS
## Additional options for the JAVA_OPTS environment variable.
## These will be appended to the execution of the openHAB Java runtime in front of all other options.
## 
## A couple of independent examples:
##   EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0"
##   EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0"
##   EXTRA_JAVA_OPTS="-Djna.library.path=/lib/arm-linux-gnueabihf/ -Duser.timezone=Europe/Berlin -Dgnu.io.rxtx.SerialPorts=/dev/ttyS0"

EXTRA_JAVA_OPTS=""

#########################

[08:28:56] openhabian@openhabian-server:~$ dmesg | grep tty
[    0.000000] console [tty0] enabled
[    1.419194] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    1.440287] 00:02: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[    6.516245] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
[    6.518671] usb 1-6: FTDI USB Serial Device converter now attached to ttyUSB1
[08:45:27] openhabian@openhabian-server:~$ 

2020-01-04 16:59:48.959 [ERROR] [et.wimpi.modbus.net.SerialConnection] - Could not get port identifier, maybe insufficient permissions. gnu.io.NoSuchPortException: null
2020-01-04 16:59:48.961 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@10b779b[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0]
2020-01-04 16:59:48.963 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@10b779b[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0]
2020-01-04 16:59:48.964 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection SerialConnection@10b779b[portName=/dev/ttyUSB0,port=<null>] for endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0]: Could not get port identifier, maybe insufficient permissions. null
2020-01-04 16:59:48.965 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0] -- aborting request ModbusPollerThingHandlerImpl.ModbusPollerReadRequest@c61b81[slaveId=100,functionCode=READ_MULTIPLE_REGISTERS,start=32064,length=31,maxTries=3] [operation ID fea92457-b986-447e-8907-665c60cf9836]
2020-01-04 16:59:48.967 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave105holding:Active_peak_of_current_day 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:48.969 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave105holding:Active_power 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:48.971 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave105holding:Inverter_efficiency 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:48.973 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave105holding:Cabinet_temperature 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:48.974 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave105holding:Device_status 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:48.976 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave105holding:Fault_code 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.414 [ERROR] [et.wimpi.modbus.net.SerialConnection] - Could not get port identifier, maybe insufficient permissions. gnu.io.NoSuchPortException: null
2020-01-04 16:59:49.416 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@14934d4[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0]
2020-01-04 16:59:49.417 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@14934d4[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0]
2020-01-04 16:59:49.419 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection SerialConnection@14934d4[portName=/dev/ttyUSB0,port=<null>] for endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0]: Could not get port identifier, maybe insufficient permissions. null
2020-01-04 16:59:49.420 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0] -- aborting request ModbusPollerThingHandlerImpl.ModbusPollerReadRequest@194f239[slaveId=100,functionCode=READ_MULTIPLE_REGISTERS,start=32016,length=8,maxTries=3] [operation ID 1d28d387-e71f-4209-baad-058ccdd63a54]
2020-01-04 16:59:49.421 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave104holding:Pv_1_Voltage 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.422 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave104holding:Pv_1_Current 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.424 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave104holding:Pv_2_Voltage 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.425 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave100:slave104holding:Pv_2_Current 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1d91c44[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.684 [ERROR] [et.wimpi.modbus.net.SerialConnection] - Could not get port identifier, maybe insufficient permissions. gnu.io.NoSuchPortException: null
2020-01-04 16:59:49.686 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@f5aabd[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0]
2020-01-04 16:59:49.687 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@f5aabd[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0]
2020-01-04 16:59:49.687 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection SerialConnection@f5aabd[portName=/dev/ttyUSB0,port=<null>] for endpoint ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0]: Could not get port identifier, maybe insufficient permissions. null
2020-01-04 16:59:49.688 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0] -- aborting request ModbusPollerThingHandlerImpl.ModbusPollerReadRequest@1cbc010[slaveId=12,functionCode=READ_INPUT_DISCRETES,start=0,length=16,maxTries=3] [operation ID 88532bf2-597b-4ff9-a175-3ed71e92fd98]
2020-01-04 16:59:49.688 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di32 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.690 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di33 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.691 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di34 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.692 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di35 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.693 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di36 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.693 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di37 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.694 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di38 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.694 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di39 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.695 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di40 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.695 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di41 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.695 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di42 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.696 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di43 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.696 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di44 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.697 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di45 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.697 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di46 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.698 [ERROR] [ernal.handler.ModbusDataThingHandler] - Thing modbus:data:slave12:slave12Inputs:di47 'Modbus Data' had ModbusConnectionException error on read: ModbusConnectionException(Error connecting to endpoint=ModbusSerialSlaveEndpoint@1f44cf6[portName=/dev/ttyUSB0])
2020-01-04 16:59:49.828 [ERROR] [et.wimpi.modbus.net.SerialConnection] - Could not get port identifier, maybe insufficient permissions. gnu.io.NoSuchPortException: null

Why do you have two FTDI USB serial Device converters? One on USB0 and one on USB1?

1 is for modbus and the other 1 for RFXcom.

Ahh okay… I thought you just had one FTDI :slight_smile:

As I understand it, there have been changes in the underlying serial libraries used from 2.4 to 2.5.
I’d be cross checking reports about other difficulties with e.g. zwave sticks and suchlike, since 2.5

Ok so what can we do to solve this problem?I made the symlinks and they are working.

First let it run with symlinks to see if it changes anything (I wouldnt think so, but give it a try anyway).
If the issue occure again, perhaps try to leave out something… Its a pain since you problem only appear after a few days, which is far from optimal troubbleshooting… But there has to be something about the serial driver which is going wrong after a certain amount of time…

I too are struggling with issue I cant seem to get rid off, and I do have a very hard feeling they belong to the serial driver (or libs) as well.

Yea … I’m having issues with my new Modbus TCP binding … similar … after 20 to 30 hours the raspberry pi system crashes and needs a hard reboot.

The Modbus Binding version as follows … binding-modbus - 2.4.0

The previous Modbus binding version 1.x ran for months.

I have 2 systems presently setup with new settings and if (when) they crash I’ll post errors.

Seems like a memory leak … anybody else experiencing similar with Modbus 2.x /

Start a new thread for that, it has absolutely nothing to do with serial and symlinks and disconnects.
In fact, you could start one already and give some details of your configuration in advance.

Note that 2.5 is current release, although the Modbus binding hasn’t changed much.

After I added the symlinks, the problem has not returned.

1 Like

I have exactly the same problem. Sometimes the Modbus binding (more exactly the modbus transport) looses the “connection” to the serial port. Sometimes the connection doesn’t work at all after a restart of OH.

I also played with symlinks and had the strange behavior that sometimes the symlink works and the actual device does not and vice versa. Also, one physical serial port could work and the other physical don’t.

Now, I had luck that the error was persistent i.e. didn’t go away after a restart of OH, nor a openhab-cli clean-cache helped, nor a power on/off of the computer helped.

I digged into the dependencies of the modbus binding, which references an old version of nrjavaserial: org.openhab.binding.modbus -> org.openhab.io.transport.modbus -> jamod -> nrjavaserial 3.12

After compiling jamod and the modbus transport with the currently referenced nrjavaserial version by the OH3 core (5.2.1), the error was gone.

Actually this is a bit strange, since the OH3.M2 distro is delivered with nrjavaserial 5.2.1 and not 3.12. So, I would expect nothing to change by changing the jamod (provided) dependencies.

As there are other threads with the same error and most people changed something and it suddenly worked, I will observe if this fix has a lasting effect. @ssalonen

How did you confirm the version of nrjavaserial used by the runtime? I would agree with your assessment that all bindings use whatever is provided by openHAB distro.

You mention “the error”. Can you please explain the error?

Regarding nrjavaserial, oh3 world is looking more bright Modbus binding loses its serial connection every few days without a reason after updating to 2.5.0 Release Build

Previous versions of openhab used a forked version which suffered from some issues cleaning up the locking of serial ports.

The OH core reference to nrjavaserial is here and the release file from the website contains only the 5.2.1 JAR: openhab-3.0.0.M2.zip\runtime\system\com\neuronrobotics\nrjavaserial\5.2.1\nrjavaserial-5.2.1.jar.

The error is the following:

[ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection SerialConnection@1bffe68[portName=/dev/rs485-stick,port=<null>] for endpoint ModbusSerialSlaveEndpoint@f68504[portName=/dev/rs485-stick]: Could not get port identifier, maybe insufficient permissions. null

Unfortunately, the error came back last night.

I observed a deadlock after fiddling around with the serial ports in the modbus serial slave Thing configuration. The binding doesn’t seem to do anything, then. When disabling the Thing, the following message appears:

[WARN ] [rt.modbus.internal.ModbusManagerImpl] - Error getting a new connection for endpoint ModbusSerialSlaveEndpoint@365cd3[portName=/dev/rs485-stick]. Error was: java.lang.InterruptedException null

If I see correctly this happens only if the serial port cannot be retrieved from the connection pool: https://github.com/openhab/openhab-addons/blob/main/bundles/org.openhab.io.transport.modbus/src/main/java/org/openhab/io/transport/modbus/internal/ModbusManagerImpl.java#L380

Maybe this is only a subsequent error, but it might be worth to dig into it.

When the error occurred, I noticed the following message on stdout:

initialise_event_info_struct: initialise failed!

This is a known bug in nrjavaserial:

I applied the suggested fix to disable locking in the native libraries and it seems to sucessfully work around the Could not get port identifier, maybe insufficient permissions. issue.

Hey,
I’m having same problem in my OH3M2.
After few days serial modbus stoped working. An now it gives:

2020-11-20 10:42:50.991 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - connect try 1/1 error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@180b55[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@89eacd[portName=/dev/ttyUSB0]
2020-11-20 10:42:50.992 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - re-connect reached max tries 1, throwing last error: Could not get port identifier, maybe insufficient permissions. null. Connection SerialConnection@180b55[portName=/dev/ttyUSB0,port=<null>]. Endpoint ModbusSerialSlaveEndpoint@89eacd[portName=/dev/ttyUSB0]
2020-11-20 10:42:50.994 [ERROR] [ing.ModbusSlaveConnectionFactoryImpl] - Error connecting connection SerialConnection@180b55[portName=/dev/ttyUSB0,port=<null>] for endpoint ModbusSerialSlaveEndpoint@89eacd[portName=/dev/ttyUSB0]: Could not get port identifier, maybe insufficient permissions. null
2020-11-20 10:42:50.996 [WARN ] [rt.modbus.internal.ModbusManagerImpl] - Could not connect to endpoint ModbusSerialSlaveEndpoint@89eacd[portName=/dev/ttyUSB0] -- aborting request ModbusReadRequestBlueprint@1d174b8[slaveId=1,functionCode=READ_INPUT_REGISTERS,start=30,length=2,maxTries=3] [operation ID ba0b7154-5502-49f5-a389-c26859afd956]

Did someone managed to fix it?

As stated above, I compiled the serial library without locks and it works without problems since a week.

Here is the JAR with disabled locks: https://cloud.cc-h.de/index.php/s/u1fbjFhowhlFMjl

It replaces the JAR in this location:
/usr/share/openhab/runtime/system/com/neuronrobotics/nrjavaserial/5.2.1

1 Like

Thank You very much! It is working now.
Question: does people making new OH3 know about this so they would implement this in new versions?

@fwolter to my understanding this would be mean new openHAB 2.5 core release (Is nrjavaserial still maintained?) which is likely not going to happen anymore since 3.0 is hopefully soon out.

Looks like in 3.0 the situation is better?

Modbus binding itself cannot unfortunately control the nrjavaserial library provided by the OH runtime.

@Kamil_Matuszczak and I encountered the problem with OH3.M2, which uses a newer version of nrjavaserial. The question is if this a general problem with the newer nrjavaserial version. @ssalonen did you already try OH3 with modbus?

Did You write ticket in github OH3M2 distro?
Cause now we changed it manually, but after Update of OH3 to M3 we will need another time to change it manually…