Jeelink binding init command does not work

Platform information:

  • Hardware: Synology DS1515 / CPU: Alpine AL314 1.4GHz / 2GB RAM
  • OS: DSM 6.1.5-15254
  • Java Runtime Environment: 8.0.151-0014 (Java 8 / Synology)
  • openHAB version:2.2.010
  • Jeelink Binding (binding-jeelink - 2.2.0)

Issue of the topic:
The configuration of the JeeLink Binding allows to define “Init Kommandos” (german version) which will be send after establishing an connection to the JeeLink.
I need to send the a commando to change the data-rate “1r” or “1r v” . But this does not work. The data-rate will not be changed. I need to connect manually to the Jeelink before openHAB connects and send the command “1r” manually. Then the JeeLink bindings works fine.
The Jeelink is connected over TCP.

I just tried to reproduce your problem. I am not sure what 1r is supposed to do, but reading the FHEM wiki page I would expect it to use 17.241 kbps as frequency, which would be the default. Using this as init command did not do anything visible.

But I could use e.g. 3m 30t, which correctly toggled the data rate every 30 seconds. I could as well enable or disable the LED with 0a or 1a, so I sending init commands to the jeelink seems to work just fine.

What do you expect 1r to do?

Thanks for trying to reproduce the error.
1r switches the Jeelink to 9.579 kbps (which is the frequency my sensors are working).
Here an snipplet of a telnet session I need to execute before Openhab takes control over the Jeelink:

[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:17241)]
1r
v
[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:9579)]

“v” only show the version-string again.

Can you please test if this jar fixes your problems:
https://github.com/vbier/openhab2-addons/raw/testjar/addons/binding/org.openhab.binding.jeelink/org.openhab.binding.jeelink-2.3.0-SNAPSHOT.jar

Thanks again but the new jar does not fix the problem.

What I have done:

  1. Uninstalled old Jeelink Binding
  2. Installed snapshot:

bundle:list

241 │ Active │ 80 │ 2.3.0.201803010646 │ JeeLink Binding

  1. restarted my Raspberry Pi with my Jeelink Dongle (connected over ser2net)
  2. After Restart, Binding automatically connects to the Interface and it seems, that the command was sent:

21:51:59.939 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.113.2 port 2006…
21:51:59.949 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.113.2:2006…
21:51:59.965 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP socket created.
21:51:59.973 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 starting…
21:51:59.977 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Sending init commands for port 192.168.113.2:2006: 1r
21:51:59.976 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from OFFLINE (COMMUNICATION_ERROR): Connection refused (Connection refused) to ONLINE
21:51:59.991 [DEBUG] [.connection.AbstractJeeLinkConnection] - Initializing device on port 192.168.113.2:2006 with commands [1r]

  1. But sensors stay offline. Disconnecting Jeelink binding and connect again with telnet. Jeelink still at wrong frequency:

Connected to 192.168.113.2.
Escape character is ‘^]’.
v

[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:17241)]
1r
OK 9 32 1 3 186 60
vOK 9 34 1 3 41 73

[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:9579)]

  1. After manual command and connecting Jeelink binding again, sensor are recognized.

As you can see in the log, the binding also writes “1r” to the stick. I do not see how this could behave differently then doing the same thing over telnet.
The updated jar contained a change that makes sure the init commands are written to the stick right after the connection has been established, instead of waiting for the first reading (which could obviously not have worked before).
This worked when testing it here with a USB connection, so i thought the problem is fixed. I will see if I can reproduce this with a TCP connection when I have the time.

I have updated the jar file once again. It now contains a small delay after the connection has been established before the init commands are written to the stick.
Can you see if that makes a difference? It worked with my jeelink connected over TCP, so I hope it fixes your problem. If not please enable TRACE logging for the jeelink binding, tail the openHAB log and edit the stick thing (e.g. add " v" to the init commands). This should reconnect to the stick and show some ouput containing the sending of the init commands. With v in then init command it should show at least that the version information is read from the stick (which would show that the command has been sent and processd by the stick).

Alright. I install the current snapshot-version of the binding. The version-number is now 2.3.0.201803021048.

I performed the steps you asked for. In the “TRACE output 1” you can see, first there is no difference. At timecode 21:58:28.335 the command “1r” is logged as transmitted, but no sensors are changing to online.
Then at timecode 21:59:55.255 I changed the init-command in the settings to “1r v”. Almost immediately the sensors are changing to ONLINE.

To make sure, that this was not a random behavior, I rebooted my Raspberry with the Jeelink-module again (back to default frequency). In “TRACE output 2” you can see that, at timecode 22:07:47.103 now the command “1r v” logged as transmitted automatically after connection. But the sensors are not changing to online. Than I changed the init-command back to “1r” (22:08:29.873). Also again immediately the sensors are changing to online…

TRACE output 1:

21:58:27.280 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.113.2:2006…
21:58:27.307 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP socket created.
21:58:27.325 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 starting…
21:58:27.328 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from OFFLINE (COMMUNICATION_ERROR): Connection refused (Connection refused) to ONLINE
21:58:28.335 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Sending init commands for port 192.168.113.2:2006: 1r
21:58:28.358 [DEBUG] [.connection.AbstractJeeLinkConnection] - Initializing device on port 192.168.113.2:2006 with commands [1r]
21:58:29.676 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006:
21:58:29.698 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: [LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:17241)]
21:59:53.804 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Closing TCP connection to port 192.168.113.2:2006…
21:59:53.854 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Shutting down reader for TCP port 192.168.113.2:2006…
21:59:53.934 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Socket closed
21:59:53.994 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.113.2 port 2006…
21:59:53.991 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.113.2:2006 aborted (Socket closed). Reconnect scheduled.
21:59:54.096 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.113.2:2006…
21:59:54.060 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
21:59:54.191 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP socket created.
21:59:54.144 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 finished…
21:59:54.247 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 starting…
21:59:54.215 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
21:59:54.330 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
21:59:54.357 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
21:59:54.384 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
21:59:54.409 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘jeelink:jeelinkTcp:92ca4f20’ has been updated.
21:59:54.433 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
21:59:54.458 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
21:59:54.482 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
21:59:54.509 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
21:59:54.535 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from OFFLINE (BRIDGE_OFFLINE) to OFFLINE
21:59:54.587 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from OFFLINE (COMMUNICATION_ERROR): Socket closed to ONLINE
21:59:55.255 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Sending init commands for port 192.168.113.2:2006: 1r v
21:59:55.278 [DEBUG] [.connection.AbstractJeeLinkConnection] - Initializing device on port 192.168.113.2:2006 with commands [1r v]
21:59:55.325 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006:
21:59:55.347 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: [LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:9579)]
21:59:57.549 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 43 1 4 96 33
21:59:57.598 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from OFFLINE to ONLINE
21:59:59.212 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 32 1 3 185 61
21:59:59.261 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from OFFLINE to ONLINE
21:59:59.483 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 34 1 3 44 75
21:59:59.531 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from OFFLINE to ONLINE
22:00:00.295 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 28 1 4 80 55
22:00:00.344 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from OFFLINE to ONLINE
22:00:01.609 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 22 1 3 149 74
22:00:01.660 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from OFFLINE to ONLINE
22:00:03.995 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP connection to port 192.168.113.2:2006 is already open!
22:00:05.285 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 28 1 4 80 56
22:00:06.611 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 22 1 3 149 75
22:00:07.539 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 43 1 4 96 33
22:00:09.216 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 32 1 3 185 61
22:00:09.484 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 34 1 3 44 75

TRACE output 2:

22:07:45.963 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.113.2 port 2006…
22:07:46.045 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.113.2:2006…
22:07:46.073 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP socket created.
22:07:46.092 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 starting…
22:07:46.094 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from OFFLINE (COMMUNICATION_ERROR): Connection refused (Connection refused) to ONLINE
22:07:47.103 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Sending init commands for port 192.168.113.2:2006: 1r v
22:07:47.127 [DEBUG] [.connection.AbstractJeeLinkConnection] - Initializing device on port 192.168.113.2:2006 with commands [1r v]
22:07:48.446 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006:
22:07:48.469 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: [LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:17241)]
22:08:28.470 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Closing TCP connection to port 192.168.113.2:2006…
22:08:28.512 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Shutting down reader for TCP port 192.168.113.2:2006…
22:08:28.564 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.113.2:2006 aborted (Socket closed). Reconnect scheduled.
22:08:28.595 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.113.2 port 2006…
22:08:28.566 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Socket closed
22:08:28.753 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.113.2:2006…
22:08:28.643 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 finished…
22:08:28.816 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP socket created.
22:08:28.769 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
22:08:28.868 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.113.2:2006 starting…
22:08:28.900 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
22:08:28.954 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
22:08:28.981 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
22:08:29.008 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from OFFLINE to OFFLINE (BRIDGE_OFFLINE)
22:08:29.050 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘jeelink:jeelinkTcp:92ca4f20’ has been updated.
22:08:29.073 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:jeelinkTcp:92ca4f20’ changed from OFFLINE (COMMUNICATION_ERROR): Socket closed to ONLINE
22:08:29.106 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
22:08:29.133 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
22:08:29.159 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
22:08:29.186 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
22:08:29.211 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
22:08:29.237 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from ONLINE to OFFLINE
22:08:29.260 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from ONLINE to OFFLINE
22:08:29.302 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from ONLINE to OFFLINE
22:08:29.330 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from ONLINE to OFFLINE
22:08:29.353 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from ONLINE to OFFLINE
22:08:29.873 [DEBUG] [nding.jeelink.internal.JeeLinkHandler] - Sending init commands for port 192.168.113.2:2006: 1r
22:08:29.896 [DEBUG] [.connection.AbstractJeeLinkConnection] - Initializing device on port 192.168.113.2:2006 with commands [1r]
22:08:31.617 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 22 1 3 149 75
22:08:31.665 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:22’ changed from OFFLINE to ONLINE
22:08:32.544 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 43 1 4 96 33
22:08:32.592 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:43’ changed from OFFLINE to ONLINE
22:08:34.222 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 32 1 3 184 62
22:08:34.272 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:32’ changed from OFFLINE to ONLINE
22:08:35.293 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 28 1 4 80 55
22:08:35.340 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:28’ changed from OFFLINE to ONLINE
22:08:36.619 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 22 1 3 148 75
22:08:37.547 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 43 1 4 95 33
22:08:38.574 [DEBUG] [ernal.connection.JeeLinkTcpConnection] - TCP connection to port 192.168.113.2:2006 is already open!
22:08:39.224 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 32 1 3 184 61
22:08:39.512 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: OK 9 34 1 3 44 75
22:08:39.560 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘jeelink:lacrosse:34’ changed from OFFLINE to ONLINE

Looking at the log, you can see that the init commands are sent before the header line is read from the stick:

21:58:28.358 [DEBUG] [.connection.AbstractJeeLinkConnection] - Initializing device on port 192.168.113.2:2006 with commands [1r]
21:58:29.676 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006:
21:58:29.698 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 192.168.113.2:2006: [LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:17241)]

Where does the header line come from? Is this the ser2net banner or does the line come from the stick itself? Can you post your ser2net configuration for the stick?

I am wondering if the binding is still sending the init commands too early.

Can you configure ser2net to log in- and output with timestamps and check if the init commands are coming through?

[-]tb= trace both read and written data to the same file. Note that this is independent of tr and tw, so you may be tracing read, write, and both to different files.
[-]timestamp adds (- removes) a timestamp to all of the trace files. A timestamp is prepended to each line if hexdump is active for the trace file. A timestamped line is also recorded in the trace file when a remote client connects or disconnects from the port.

And afterwards try the updated version of the jar. I increased the time the binding waits before sending the init commands to 5 seconds.

Here is the ser2net configuration (after activating logging as suggested). Originally it consists only of one line per adapter (the line with the #).
I have not invested much time to configure ser2net. The configuration you see here, I found somewhere at the internet.

TRACEFILE:trace1:/var/log/ser2net.2006.log

#2006:raw:0:/dev/ttyJEE868:57600 NONE 1STOPBIT 8DATABITS
2006:raw:0:/dev/ttyJEE868:57600 tb=trace1 timestamp NONE 1STOPBIT 8DATABITS

After restarting the Pi again, the following log was generated by ser2net. At 15:02:03 the binding connected automatically and the 1r was received (!). But the next line shows, that the frequency was not changed.
At 15:04:36 I changed manually the init commands to “1r v”. Now the frequency was changed and the sensors are received…

2018/03/03 15:02:03 OPEN (::ffff:192.168.113.5:53221)
1r
[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:17241)]
2018/03/03 15:04:36 CLOSE (tcp read close)
2018/03/03 15:04:36 OPEN (::ffff:192.168.113.5:53224)
1r v
[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:9579)]
OK 9 34 1 3 41 73
OK 9 28 1 4 84 53
OK 9 43 1 4 94 34
OK 9 34 1 3 41 73
OK 9 32 1 4 50 40
OK 9 34 1 3 40 73
OK 9 28 1 4 84 53
OK 9 43 1 4 94 34
OK 9 34 1 3 40 73
OK 9 32 1 4 50 40

Installed the new version (2.3.0.201803030942) afterwards.
The longer delay solves the problem!
Here is the new ser2net-log:

2018/03/03 15:28:38 OPEN (::ffff:192.168.113.5:53446)
1r v
[LaCrosseITPlusReader.10.1s (RFM69CW f:868300 r:9579)]
OK 9 34 1 3 40 73
OK 9 32 1 4 45 40
OK 9 43 1 4 93 33
OK 9 22 1 3 236 51
OK 9 32 1 4 44 40
OK 9 34 1 3 40 73
OK 9 32 1 4 45 40
OK 9 43 1 4 93 33
OK 9 22 1 3 236 51

Thank you very much for your support!

Could you test the new binding version before I create a pull request?

I installed the version 2.3.0.201803071402.
After “bundle:start” and restarting the raspberry pi this the Jeelink, the binding stock in uninitialized state. But the sensor are coming online. Unfortunally, I have no logs from this event.

After restarting the Openhab-server and also the raspberry pi with the Jeelink, binding and sensors working fine (init command was sent, sensors and binding are online).