Thanks for the information. I have also upgraded to 2.5.0 and did not have any problems. So it does not seem to be a general problem. Anybody else having problems with the jeelink binding after upgrading to 2.5?
Hi Volker,
many thanks for the binding. I have a question regarding LaCrosse Gateway. I use some of them with a directly connected Temp/Hum Sensor. These sensors are not visible within the binding and can not configured manually. So I think this option is not supported by the binding until now. Is it possible to add the support for this setup?
Many thanks in advanced
Christian
Adding support is possible as long as the LGW writes the values of the connected sensors to the serial/TCP port as it does for the other sensors. Set debug level trace using the openhab console and post a relevant part of rthe openhab logv containing ouput for the directly connected sensors. I can then add support when I find the time.
Hi Volker,
currently I use two LGWs with the ‘Internal sensors ID’ 71 and 75 which can be configured manually within LGW setup. Here are the traces for both:
22:08:46.155 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 10.10.16.71:82: OK WS 71 4 4 203 53 255 255 255 255 255 255 255 255 0 3 219 255 255 255 255 255 255 255 255 255
22:08:48.318 [TRACE] [.connection.AbstractJeeLinkConnection] - Read line from port 10.10.16.75:82: OK WS 75 4 4 195 61 255 255 255 255 255 255 255 255 0 255 255 255 255 255 255 255 255 255 255 255
Hopefully that helps.
Many thanks
Christian
Now i only need to find a description of the format of the internal sensors. I will have to check the LGW source code and keep you posted on the progress.
Thanks for the pointer to the docs, that helped.
I am wondering why the LGW reports values for two different connected sensors. Reading the LGE docs, it states:
Wenn ein BME280 vorhanden ist, wird dieser verwendet und sonst nichts, da man dann bereits Temperatur, Feuchte und Druck hat.
Your first sensor (id71) has temperature, humidity and pressure, so should be a BME280. According to the docs, all other sensors should be ignored. Your second sensor (id75) has temperature and humidity, so should be a DHT22, correct? I would like to understand what is happening so the binding supports everything correctly.
You are right. In my setup the 71 has a BME280 connected, the 75 a DHT22. So far documented, a BMP180 or LM75 sensors also possible, but I think with the BME280 the max. supported values available.
Many thanks for the fast replies and support.
You can try this jar file, which should support internal LGW sensors. If it works I can create a pull request to have it officially added. Remove the currently installed add-on and copy the jar to the add-ons directory.
Many thanks Volker … works as expected 
22:28:43.257 [DEBUG] [nk.internal.lacrosse.LgwSensorHandler] - updating states for thing lgw75 (75): sensorId=75: temp=22.2, hum=62
22:28:43.291 [INFO ] [smarthome.event.ItemStateChangedEvent] - Temp_lgw_id75 changed from NULL to 22.2 °C
22:28:43.300 [INFO ] [smarthome.event.ItemStateChangedEvent] - Hum_lgw_id75 changed from NULL to 62 %
22:28:44.201 [DEBUG] [nk.internal.lacrosse.LgwSensorHandler] - updating states for thing lgw71 (71): sensorId=71: temp=23.2, hum=56, pressure=1010
22:28:44.236 [INFO ] [smarthome.event.ItemStateChangedEvent] - Temp_lgw_id71 changed from NULL to 23.2 °C
22:28:44.253 [INFO ] [smarthome.event.ItemStateChangedEvent] - Hum_lgw_id71 changed from NULL to 56 %
22:28:44.262 [INFO ] [smarthome.event.ItemStateChangedEvent] - Pres_lgw_id71 changed from NULL to 1010 hPa
Only to bring up the pressure value to PaperUI should not work so far, I will check my config tomorrow.
Many thanks again for the really great support to add it so quickly.
Hi Volker, it works fine for my since 10 or 12 days. So i’m happy with the changes … many thanks again.
Would it available in the official release some day?
I have created a pull request: https://github.com/openhab/openhab-addons/pull/7153. I have to make some changed to get it merged. After that it will take one or two days for it to show up in the official distribution.
After updating from 2.4.x to 2.5.3 jeelink doesn’t work anymore.
This is my bridge configuration:
Thing jeelink:jeelinkTcp:lacrosse "Jeelink lacrosse" @ "home" [ ipAddress="192.168.3.1", port=5002, sketchName="LaCrosseITPlusReader", initCommands="0a v" ]
I can telnet to the server and the jeelink stick sends data but the binding throws errors:
2020-03-25 09:58:22.133 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lacrosse' changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR): Socket closed
2020-03-25 09:58:32.101 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lacrosse' changed from OFFLINE (COMMUNICATION_ERROR): Socket closed to ONLINE
2020-03-25 09:58:32.480 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lacrosse' changed from ONLINE to OFFLINE
2020-03-25 09:58:32.509 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkTcp:lacrosse' changed from OFFLINE to OFFLINE (COMMUNICATION_ERROR): Socket closed
I tried to reinstall or restart the binding but that did not help.
Is this the same problem as tried here?
It is definitively similar. Removing the init command solves the problem. In which thread would you like to continue the discussion?
Let us use the other thread.
I just updated to OH 2.5.8-1 (Release Build).
Everything is working, but the lacrosse sensors get offline every minute and come back online.
2020-08-27 10:21:44.845 [hingStatusInfoChangedEvent] - 'jeelink:lacrosse:36' changed from ONLINE to UNINITIALIZED
2020-08-27 10:21:44.870 [hingStatusInfoChangedEvent] - 'jeelink:lacrosse:36' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-08-27 10:21:46.134 [hingStatusInfoChangedEvent] - 'jeelink:lacrosse:36' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2020-08-27 10:21:46.155 [hingStatusInfoChangedEvent] - 'jeelink:lacrosse:36' changed from INITIALIZING to UNKNOWN
2020-08-27 10:21:47.871 [hingStatusInfoChangedEvent] - 'jeelink:lacrosse:36' changed from UNKNOWN to ONLINE
Does the binding initiate the reconnect by itself? Anything I can do to avoid that behavior?
242 │ Active │ 80 │ 2.5.8 │ openHAB Add-ons :: Bundles :: JeeLink Binding
Kinds
Christian
I have not changed anything since March. Can you turn on DEBUG logging and send me a two minute excerpt of your log?
I assume that this has something to do with the openhab maintainers replacing the serial communication library.
Sorry, I restored to 2.4 due to not working rules.
I have one issue which is more of a feature request:
I’m using my jeelink with several temperature sensor and the values are filtered by the jeelink addon (default setting). Unfortunately one of the sensors is quite far away and sometimes no values are received for up to several hours. When new values arrive the filtering leads to grossly wrong values as the temperature has changed quite a bit.
So instead of filtering with a constant amount of old values I would love to have the option to filter with values from a constant time range or at least an option to discard all values from the buffer which are older than a certain time range.