New Jeelink Openhab2 Binding

vbier · November 2, 2017, 12:02pm

Sorry to disappoint you, but I am mostly busy with other stuff (aka HABPanelViewer) at the moment. You can send me the device, and I will look into it when I have time, but I can not make any promises on how long it will take to add support.

arosswog · November 3, 2017, 10:21pm

No problem, as a HABPanel-User I`m happy to see you are working on this (that’s great too !).
Just send me your address, i will ship a PCA301 to you (doesn’t matter how long it will take )

vbier · November 17, 2017, 8:40am

The PCA301 has arrived. I will try to add support as soon as I have the time. I will keep you updated with the progress.

vbier · November 19, 2017, 4:47pm

Unfortunately, the PCA301 sketch does not seem to work with Jeelink v3c, which is the one I have. I have now ordered some parts to build a Jeelink clone.

OpenHab_User · November 19, 2017, 8:25pm

Hi Volker,

first of all thank you very much for providing your JeeLink binding!
Unfortunately I have problems to get it running.
I am completely new to openHab2 and are migrating from fhem.
I am running a Synology DS211 with DSM 6.1.3 and I have installed openHab 2.2.0 Build 1082. After installing the JeeLink binding 2.2.0.201711182329 and creating a JeeLink usb receiver thing, the openHab service is crashing everytime it gets started.
My JeeLink usb receiver is connected to /dev/ttyUSB0 and was running under fhem without any problems (using the LaCrosse sketch).
I have read about putting this line somewhere, but I don’t know where to put this on my Synology:
EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0"

Do you have an idea what is going wrong?

Regards,
openhab_user

Here are some log file details:
2017-11-19 19:16:19.931 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at http://192.168.0.2:8080
2017-11-19 19:16:20.125 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at https://192.168.0.2:8443
2017-11-19 19:17:40.923 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-11-19 19:17:43.000 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2017-11-19 19:17:43.324 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-11-19 19:17:44.248 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2017-11-19 19:17:45.323 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-11-19 19:17:45.645 [DEBUG] [org.openhab.binding.jeelink ] - BundleEvent STARTING - org.openhab.binding.jeel
ink
2017-11-19 19:17:45.651 [DEBUG] [org.openhab.binding.jeelink ] - BundleEvent STARTED - org.openhab.binding.jeeli
nk
2017-11-19 19:17:45.782 [DEBUG] [org.openhab.binding.jeelink ] - ServiceEvent REGISTERED - {org.eclipse.smarthom
e.core.thing.binding.ThingHandlerFactory}={component.name=binding.jeelink, component.id=215, service.id=338, service.bun
dleid=208, service.scope=bundle} - org.openhab.binding.jeelink
2017-11-19 19:17:46.644 [DEBUG] [elink.internal.JeeLinkHandlerFactory] - creating JeeLinkHandler for thing 59271af4…
2017-11-19 19:17:46.695 [DEBUG] [elink.internal.JeeLinkHandlerFactory] - registering sensor discovery service…
2017-11-19 19:17:46.771 [DEBUG] [org.openhab.binding.jeelink ] - ServiceEvent REGISTERED - {org.eclipse.smarthom
e.config.discovery.DiscoveryService}={service.id=341, service.bundleid=208, service.scope=singleton} - org.openhab.bindi
ng.jeelink
2017-11-19 19:17:47.534 [DEBUG] [l.connection.JeeLinkSerialConnection] - Creating serial connection for port /dev/ttyUSB
0 with baud rate 57600…
2017-11-19 19:17:47.542 [DEBUG] [l.connection.JeeLinkSerialConnection] - Opening serial connection to port /dev/ttyUSB0
with baud rate 57600…

I have found another JRE crash log file:

A fatal error has been detected by the Java Runtime Environment:

SIGILL (0x4) at pc=0x4a0c9c1c, pid=2736, tid=0x4e23f470

JRE version: Java™ SE Embedded Runtime Environment (8.0_151-b12) (build 1.8 .0_151-b12)

Java VM: Java HotSpot™ Embedded Client VM (25.151-b12 mixed mode linux-arm )

Problematic frame:

C [libNRJavaSerial.so+0x9c1c] JNI_OnLoad+0x28

Core dump written. Default location: /volume1/homes/openhab2/userdata/core or core.2736

If you would like to submit a bug report, please visit:

xxxhttp://bugreport.java.com/bugreport/crash.jsp

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j java.lang.ClassLoader$NativeLibrary.load(Ljava/lang/String;Z)V+0
j java.lang.ClassLoader.loadLibrary0(Ljava/lang/Class;Ljava/io/File;)Z+328
j java.lang.ClassLoader.loadLibrary(Ljava/lang/Class;Ljava/lang/String;Z)V+48
j java.lang.Runtime.load0(Ljava/lang/Class;Ljava/lang/String;)V+57
j java.lang.System.load(Ljava/lang/String;)V+7
j gnu.io.NativeResource.loadResource(Ljava/io/File;)V+41
j gnu.io.NativeResource.inJarLoad(Ljava/lang/String;)V+33
j gnu.io.NativeResource.loadLib(Ljava/lang/String;)V+37
j gnu.io.NativeResource.load(Ljava/lang/String;)V+138
j gnu.io.SerialManager.()V+23
j gnu.io.SerialManager.getInstance()Lgnu/io/SerialManager;+10
j gnu.io.RXTXCommDriver.()V+39
v ~StubRoutines::call_stub
j java.lang.Class.forName0(Ljava/lang/String;ZLjava/lang/ClassLoader;Ljava/lang /Class;)Ljava/lang/Class;+0
j java.lang.Class.forName(Ljava/lang/String;)Ljava/lang/Class;+11
j gnu.io.CommPortIdentifier.()V+12
v ~StubRoutines::call_stub
j org.openhab.binding.jeelink.internal.connection.JeeLinkSerialConnection.openC onnection()V+33
j org.openhab.binding.jeelink.internal.JeeLinkHandler.initialize()V+77
j org.eclipse.smarthome.core.thing.internal.ThingManager$6.call()Ljava/lang/Voi d;+4
j org.eclipse.smarthome.core.thing.internal.ThingManager$6.call()Ljava/lang/Obj ect;+1
j org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call()Ljav a/lang/Object;+11
J 1857 C1 java.util.concurrent.FutureTask.run()V (126 bytes) @ 0x40b31c80 [0x40b 31be0+0xa0]
J 2019 C1 java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurren t/ThreadPoolExecutor$Worker;)V (225 bytes) @ 0x40b5d4c4 [0x40b5d2f0+0x1d4]
j java.util.concurrent.ThreadPoolExecutor$Worker.run()V+5
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub

vbier · November 20, 2017, 5:09am

It looks like there is a problem with the native code of the NRJavaSerial library that openhab uses to access the serial ports. Try to find libNRJavaSerial.so and check if it has missing dependencies with ldd.

See https://github.com/openhab/openhab-core/issues/111, which might be your problem (or at least related).

OpenHab_User · November 20, 2017, 7:24pm

Thanks for your response.
I have tried the ldd, but I get only this result:

/volume1/@appstore/openHAB2/userdata/tmp/libNRJavaSerial_openhab2_0$ ldd libNRJavaSerial.so
ldd: warning: you do not have execution permission for `./libNRJavaSerial.so’
statically linked

Calling with sudo does not help. Do you have any ideas?

vbier · November 20, 2017, 8:30pm

I have no idea how to check if the library has undefined symbols. Did you try to replace the library with the updated one from the linked bug report? See https://github.com/openhab/openhab-core/issues/111#issuecomment-324117437.

You can also ask in the more general part of the forum, as I am pretty sure this is not jeelink related, but a problem with the nrjavaserial lib.

vbier · November 27, 2017, 3:54pm

I have received the parts for the Jeelink clone, soldered and programmed it. Just did a quick test on the serial console and was able to “see” the socket you have sent me. I could as well turn it on and off with the serial console, so the hardware works.

vbier · November 29, 2017, 1:41pm

I have added support for PCA301 sockets.

The new version should support discovery of pca301 sockets, as well as getting the values and turning the socket on and off. I have tested it with the socket you sent me, it’s your part to test with several devices.

Get the jar from here: https://github.com/vbier/openhab2-addons/blob/pcaTest/addons/binding/org.openhab.binding.jeelink/org.openhab.binding.jeelink-2.2.0-SNAPSHOT.jar

Please test and report back if there are problems or if it works as expected.

WiredLife · November 29, 2017, 7:30pm

Hello Volker, greetings from Magdeburg! Genialer Nachname
I’ve assembled a LaCrosseGateway with 3x RFM69HCW and got it working with your bindings tcp support,
but there some problems.
If the connection to the LGW is lost, it does not reconnect, i must restart the whole openhab with “service openhab2 restart” then it works again.
And with the newest version i cant see any PCA301 entry @ Paper UI, is it for manually config only?
Thanks!

vbier · November 30, 2017, 5:09am

The LaCrosseGateway works differently than the Jeelink with pcaSerial sketch. It does not support the commands to list the known devices, or to switch or poll the socket.
Therefore discovery only works if you are lucky and the sensor actually sends a value while discovery is in progress. So make sure you can see the pca301 in the LaCrosseGateway web UI and adjust the polling rate to 5 seconds for the discovery.
If the sensors are still not found enable TRACE level and send me the relevant part of the log.

But as I already said, you will only be able to see the values, not to control the socket.

Edit: regarding the connection problem: enable DEBUG level, wait for disconnect and send me the relevant part of the log.

WiredLife · November 30, 2017, 11:58am

When i add init parameters and save it via Paper UI, it saves but the connection is not coming on again

12:49:55.468 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Closing TCP connection to port 192.168.179.4:81...
12:49:55.475 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Shutting down reader for TCP port 192.168.179.4:81...
12:49:55.535 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'jeelink:jeelinkTcp:lgw' has been updated.
12:49:55.543 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lgw' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Socket closed
12:49:55.556 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.179.4 port 81...
12:49:55.563 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:591E' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.572 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:16' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.575 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:5828' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.568 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.179.4:81...
12:49:55.594 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - TCP socket created.
12:49:55.611 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:13' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.615 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:B0A7' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.610 [DEBUG] [ding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.179.4:81 aborted (Socket closed). Reconnect scheduled.
12:49:55.620 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:46' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.628 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:BC81' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.629 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.179.4:81 finished...
12:49:55.636 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:5828' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.646 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:591E' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.646 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:13' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.676 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:29' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.680 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:46' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.687 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:29' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE)
12:49:55.689 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lgw' changed from OFFLINE (COMMUNICATION_ERROR): Socket closed to ONLINE
12:49:55.696 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:16' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.705 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:B0A7' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
12:49:55.711 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:BC81' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE

i know it says online but there no more log entrys and no updates

edit:
it does not work even after bundle:stop bundle:start

15:41:48.292 [DEBUG] [org.openhab.binding.jeelink         ] - BundleEvent STOPPING - org.openhab.binding.jeelink
15:41:48.312 [DEBUG] [org.openhab.binding.jeelink         ] - BundleEvent STOPPED - org.openhab.binding.jeelink
15:41:53.804 [DEBUG] [org.openhab.binding.jeelink         ] - BundleEvent STARTING - org.openhab.binding.jeelink
15:41:53.846 [DEBUG] [org.openhab.binding.jeelink         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={component.name=binding.jeelink, component.id=204, service.id=348, service.bundleid=240, service.scope=bundle} - org.openhab.binding.jeelink
15:41:53.874 [DEBUG] [org.openhab.binding.jeelink         ] - BundleEvent STARTED - org.openhab.binding.jeelink
15:41:53.987 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:591E' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
15:41:53.990 [DEBUG] [elink.internal.JeeLinkHandlerFactory] - creating JeeLinkHandler for thing lgw...
15:41:53.992 [DEBUG] [elink.internal.JeeLinkHandlerFactory] - registering sensor discovery service...
15:41:53.998 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:5828' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
15:41:54.004 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:B0A7' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
15:41:54.005 [DEBUG] [org.openhab.binding.jeelink         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=349, service.bundleid=240, service.scope=singleton} - org.openhab.binding.jeelink
15:41:54.029 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:BC81' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to UNINITIALIZED (BRIDGE_UNINITIALIZED)
15:41:54.031 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.179.4 port 81...
15:41:54.033 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.179.4:81...
15:41:54.037 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lgw' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
15:41:54.043 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - TCP socket created.
15:41:54.052 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lgw' changed from INITIALIZING to ONLINE
15:41:54.079 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:46' changed from UNINITIALIZED to INITIALIZING
15:41:54.088 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:46' changed from INITIALIZING to UNKNOWN
15:41:54.108 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:13' changed from UNINITIALIZED to INITIALIZING
15:41:54.121 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:13' changed from INITIALIZING to UNKNOWN
15:41:54.154 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:16' changed from UNINITIALIZED to INITIALIZING
15:41:54.180 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:16' changed from INITIALIZING to UNKNOWN
15:41:54.191 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:29' changed from UNINITIALIZED to INITIALIZING
15:41:54.199 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:lacrosse:29' changed from INITIALIZING to UNKNOWN
15:41:54.251 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Closing TCP connection to port 192.168.179.4:81...
15:41:54.254 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Shutting down reader for TCP port 192.168.179.4:81...
15:41:54.259 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.179.4 port 81...
15:41:54.263 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.179.4:81...
15:41:54.269 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - TCP socket created.
15:41:54.281 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'jeelink:jeelinkTcp:lgw' has been updated.
15:41:54.295 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'jeelink:lacrosse:46' has been updated.
15:41:54.311 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'jeelink:lacrosse:13' has been updated.
15:41:54.321 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'jeelink:lacrosse:16' has been updated.
15:41:54.336 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'jeelink:lacrosse:29' has been updated.
15:41:54.373 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:BC81' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
15:41:54.386 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:BC81' changed from INITIALIZING to UNKNOWN
15:41:54.402 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:B0A7' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
15:41:54.412 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:B0A7' changed from INITIALIZING to UNKNOWN
15:41:54.428 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:5828' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
15:41:54.441 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:5828' changed from INITIALIZING to UNKNOWN
15:41:54.455 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:591E' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
15:41:54.466 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'jeelink:ec3k:591E' changed from INITIALIZING to UNKNOWN

only a openhab restart helps

64matze · November 30, 2017, 5:42pm

Hello Volker,
after a long time I restarted with a new openhab installation.
Now I red that the binding is in the official release, but I can not find it in the paperUI at bindings.
How to install the binding?
Do I still need to download a jar file?
If so, do you have a link?

Thank you in advance.

Matthias

WiredLife · November 30, 2017, 7:15pm

Hey Matze, look 4 posts over you for the link

vbier · December 1, 2017, 6:14am

The last lines show that the sensors come online. They only do that when they get a reading. If you enable TRACE, you will most likely see that something is read from the lgw.

I have now updated the binding once again to support LGWs (and added more logging). Can you please test if this works better? If not, please enable TRACE level and post the relevant part of the log.

Edit: just to make that clear, discovery still needs a high polling rate set by an init command, but you should now be able to control the socket with the LGW. I have also fixed a bug in the TCP connection code.

vbier · December 1, 2017, 6:34am

I was a little too fast in saying that the binding is now part of the official distribution. It is, but only from 2.2-SNAPSHOT onwards. So if you are on 2.2-SNAPSHOT, you can install it normally. If you are still on 2.1, you can use the jar from here:
https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/binding/org.openhab.binding.jeelink/2.1.0-SNAPSHOT/org.openhab.binding.jeelink-2.1.0-SNAPSHOT.jar

WiredLife · December 1, 2017, 11:41am

Hi Volker,
these logs were with enabled TRACE.
TRACE shows the raw readings, but as you see, there was the problem, no readings.
I try your new version and report back.
Thanks!

P.S. I use the 2.2.0 SNAPSHOT under 2.1, is it ok?

WiredLife · December 1, 2017, 1:45pm

Hi Volker,
i did a reboot of the LGW but the binding doesnt reconnect.
Here the log:

14:41:51.793 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 9 13 1 4 24 76
14:41:51.795 [TRACE] [.LaCrosseTemperatureReadingConverter] - Creating reading from: OK 9 13 1 4 24 76
14:41:51.799 [DEBUG] [sse.LaCrosseTemperatureSensorHandler] - updating states for thing Thermometer Balkon (13): temp=4.8 (4.8), humidity=76, batteryNew=false, batteryLow=false
14:41:52.820 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 9 29 1 4 185 48
14:41:52.822 [TRACE] [.LaCrosseTemperatureReadingConverter] - Creating reading from: OK 9 29 1 4 185 48
14:41:52.826 [DEBUG] [sse.LaCrosseTemperatureSensorHandler] - updating states for thing Thermometer Schlafzimmer (29): temp=20.9 (20.9), humidity=48, batteryNew=false, batteryLow=false
14:41:52.841 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 9 46 1 4 197 46
14:41:52.844 [TRACE] [.LaCrosseTemperatureReadingConverter] - Creating reading from: OK 9 46 1 4 197 46
14:41:52.848 [DEBUG] [sse.LaCrosseTemperatureSensorHandler] - updating states for thing Thermometer Bad (46): temp=22.1 (22.1), humidity=46, batteryNew=false, batteryLow=false
14:41:52.972 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 22 89 30 1 148 181 78 1 148 179 239 0 11 47 165 11 247 43 32 1 0
14:41:52.977 [DEBUG] [link.internal.ec3k.Ec3kSensorHandler] - updating states for thing 591E: currWatt=306.3 (306.3), maxWatt=1104.0, consumption=733, secondsOn=26522607, secondsTotal=26522958
14:41:53.111 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 9 16 1 4 32 106
14:41:53.113 [TRACE] [.LaCrosseTemperatureReadingConverter] - Creating reading from: OK 9 16 1 4 32 106
14:41:53.117 [DEBUG] [sse.LaCrosseTemperatureSensorHandler] - updating states for thing Thermometer Kuehlschrank (16): temp=5.6 (5.6), humidity=106, batteryNew=false, batteryLow=false
14:41:54.222 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 22 176 167 0 2 123 66 0 1 198 15 0 0 1 127 0 15 11 109 4 0
14:41:54.226 [DEBUG] [link.internal.ec3k.Ec3kSensorHandler] - updating states for thing B0A7: currWatt=1.5 (1.5), maxWatt=292.5, consumption=0, secondsOn=116239, secondsTotal=162626
14:41:54.361 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port 192.168.179.4:82: OK 22 188 129 1 89 2 88 0 225 168 159 0 1 229 21 0 69 8 190 2 0
14:41:54.367 [DEBUG] [link.internal.ec3k.Ec3kSensorHandler] - updating states for thing BC81: currWatt=6.9 (6.9), maxWatt=223.8, consumption=124, secondsOn=14788767, secondsTotal=22610520```

vbier · December 1, 2017, 1:53pm

The part you just posted only contains an ongoing connection. Is 192.168.179.4:82 your LGW?

There is no entry at all about the connection being lost. Have you updated to the newest version? I have used ser2net to make the serial port of my Jeelink clone available on my pc. After defining the Jeelink TCP to the PC, the following happens when I kill ser2net and restart it:

2017-12-01 14:51:12.504 [ERROR] [rnal.connection.JeeLinkTcpConnection] - IO exception
java.io.IOException: Got EOF on port 192.168.178.33:6666
at org.openhab.binding.jeelink.internal.connection.JeeLinkTcpConnection$Reader.run(JeeLinkTcpConnection.java:122) [228:org.openhab.binding.jeelink:2.2.0.201712010856]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
2017-12-01 14:51:12.516 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Closing TCP connection to port 192.168.178.33:6666…
2017-12-01 14:51:12.519 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Shutting down reader for TCP port 192.168.178.33:6666…
2017-12-01 14:51:12.545 [DEBUG] [ding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.178.33:6666 aborted (Got EOF on port 192.168.178.33:6666). Reconnect scheduled.
2017-12-01 14:51:12.550 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.178.33:6666 finished…
2017-12-01 14:51:22.546 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.178.33 port 6666…
2017-12-01 14:51:22.549 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.178.33:6666…
2017-12-01 14:51:22.554 [ERROR] [rnal.connection.JeeLinkTcpConnection] - Uncaught exception
java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:?]
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:?]
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:?]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:?]
at java.net.Socket.connect(Socket.java:589) ~[?:?]
at java.net.Socket.connect(Socket.java:538) ~[?:?]
at java.net.Socket.(Socket.java:434) ~[?:?]
at java.net.Socket.(Socket.java:211) ~[?:?]
at org.openhab.binding.jeelink.internal.connection.JeeLinkTcpConnection.openConnection(JeeLinkTcpConnection.java:71) ~[?:?]
at org.openhab.binding.jeelink.internal.JeeLinkHandler.lambda$0(JeeLinkHandler.java:93) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
2017-12-01 14:51:22.581 [DEBUG] [ding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.178.33:6666 aborted (Connection refused (Connection refused)). Reconnect scheduled.
2017-12-01 14:51:32.581 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Opening TCP connection to host 192.168.178.33 port 6666…
2017-12-01 14:51:32.584 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Creating TCP socket to 192.168.178.33:6666…
2017-12-01 14:51:32.588 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - TCP socket created.
2017-12-01 14:51:32.591 [DEBUG] [ding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.178.33:6666 opened.
2017-12-01 14:51:32.592 [DEBUG] [rnal.connection.JeeLinkTcpConnection] - Reader for TCP port 192.168.178.33:6666 starting…
2017-12-01 14:51:32.607 [DEBUG] [ding.jeelink.internal.JeeLinkHandler] - Connection to port 192.168.178.33:6666 established. Reconnect cancelled.
2017-12-01 14:51:32.614 [DEBUG] [.internal.pca301.Pca301SensorHandler] - updating states for thing PCA301 power monitoring wireless socket (1-160-236): state=true, current=0.0, total=170

You can see that the connection has been dropped and re-established. This should be exactly what happens when you reboot the LGW.