New Jeelink Openhab2 Binding

vbier · March 7, 2018, 7:58pm

The log does not show that discovery has been started?

5tift · March 7, 2018, 8:04pm

I deleted the stick and run it again

2018-03-07 20:59:24.664 [DEBUG] [l.connection.JeeLinkSerialConnection] - Closing serial connection to port /dev/ttyUSB0...
2018-03-07 20:59:24.758 [DEBUG] [org.openhab.binding.jeelink         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=324, service.bundleid=188, service.scope=singleton} - org.openhab.binding.jeelink
2018-03-07 20:59:34.334 [DEBUG] [core.karaf.internal.FeatureInstaller] - Running scheduled sync job
2018-03-07 20:59:52.138 [DEBUG] [elink.internal.JeeLinkHandlerFactory] - creating JeeLinkHandler for thing 70432608...
2018-03-07 20:59:52.139 [DEBUG] [elink.internal.JeeLinkHandlerFactory] - registering sensor discovery service...
2018-03-07 20:59:52.143 [DEBUG] [org.openhab.binding.jeelink         ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=325, service.bundleid=188, service.scope=singleton} - org.openhab.binding.jeelink
2018-03-07 20:59:52.160 [DEBUG] [l.connection.JeeLinkSerialConnection] - Creating serial connection for port /dev/ttyUSB0 with baud rate 57600...
2018-03-07 20:59:52.163 [DEBUG] [l.connection.JeeLinkSerialConnection] - Opening serial connection to port /dev/ttyUSB0 with baud rate 57600...
2018-03-07 20:59:52.492 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 8 4 5 86 62 1 2 131 68 76
2018-03-07 20:59:52.883 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 6 4 6 200 255 1 2 4 60 154
2018-03-07 20:59:53.075 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 7 4 5 64 16 1 0 0 0 0
2018-03-07 21:00:09.369 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 7 5 5 64 16 1 170 170 170 170
2018-03-07 21:00:09.977 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 7 4 5 64 16 0 0 0 0 0
2018-03-07 21:00:11.560 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 7 5 5 64 16 0 170 170 170 170

vbier · March 7, 2018, 8:10pm

Did you start discovery for the jeelink binding in the inbox of the paper ui?

5tift · March 7, 2018, 8:12pm

Inbox > JeeLink Binding > Search

vbier · March 7, 2018, 8:17pm

Did you paste the wrong part of the log? A discovery should look like this:

2018-03-06 19:55:49.601 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery started for bridge jeelink:jeelinkUsb:4c6d16fd
2018-03-06 19:55:50.410 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 30
2018-03-06 19:55:54.151 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 58
2018-03-06 19:55:54.642 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 30
2018-03-06 19:55:57.894 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 38
2018-03-06 19:56:02.411 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found unknown sensor of type jeelink:pca301 with id 1-160-236
2018-03-06 19:56:02.445 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘jeelink:pca301:1-160-236’ to inbox.
2018-03-06 19:56:03.059 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 58
2018-03-06 19:56:06.487 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 38
2018-03-06 19:56:11.582 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 30
2018-03-06 19:56:11.963 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 58
2018-03-06 19:56:15.082 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:4c6d16fd found already known sensor id 38
2018-03-06 19:56:19.600 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery stopped for bridge jeelink:jeelinkUsb:4c6d16fd

It should at least contain the discovery started and stopped messages.

5tift · March 7, 2018, 8:23pm

Hm,
openhab> log:get
Logger │ Level
───────────────────────────────────────────────────┼──────
ROOT │ INFO
javax.jmdns │ ERROR
org.apache.karaf.jaas.modules.audit │ INFO
org.apache.karaf.kar.internal.KarServiceImpl │ ERROR
org.apache.karaf.shell.support │ OFF
org.eclipse.smarthome │ INFO
org.jupnp │ ERROR
org.openhab │ TRACE
org.openhab.binding.jeelink │ TRACE
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime │ OFF
smarthome.event │ DEBUG
smarthome.event.InboxUpdatedEvent │ ERROR
smarthome.event.ItemAddedEvent │ ERROR
smarthome.event.ItemRemovedEvent │ ERROR
smarthome.event.ItemStateEvent │ ERROR
smarthome.event.ThingAddedEvent │ ERROR
smarthome.event.ThingRemovedEvent │ ERROR
smarthome.event.ThingStatusInfoEvent │ ERROR

And the content from the openhab.log
(you see the removed jeelink and the rest of entries above"

vbier · March 7, 2018, 8:26pm

It is not a logging configuration problem. It looks like the discovery is not started, but I have no idea why.

Can you check that you only have one version of the binding installed? Type

bundle:list |grep Jeelink

Into the console.

5tift · March 7, 2018, 8:40pm

I found 2 entries
188 │ Active │ 80 │ 2.3.0.201802111802 │ JeeLink Binding
199 │ Installed │ 80 │ 2.3.0.201803022259 │ JeeLink Binding

vbier · March 7, 2018, 8:52pm

That might be the reason. Try uninstalling the older one. Have you installed the binding through paper ui? Then try uninstalling from there.
Or try

bundle:remove 188

In the console. The command might be different, I am currently not in front of my PC.

5tift · March 7, 2018, 9:11pm

Ahh,
now i have under
Inbox > JeeLink Binding > Choose Thing
Jeelink USB Receiver and PCA301

For PCA301 i should input a sensor ID??

vbier · March 7, 2018, 9:20pm

Do not create the things manually, use the discovery.

5tift · March 7, 2018, 9:46pm

Thx Volker for your help
Now my sockets were found

2018-03-07 22:31:38.815 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery started for bridge jeelink:jeelinkUsb:92155c70
2018-03-07 22:31:41.348 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 7 5 5 64 16 1 170 170 170 170
2018-03-07 22:31:41.972 [TRACE] [connection.AbstractJeeLinkConnection] - Read line from port /dev/ttyUSB0: OK 24 7 4 5 64 16 0 0 0 0 0
2018-03-07 22:31:41.974 [TRACE] [ternal.pca301.Pca301ReadingConverter] - Creating reading from: OK 24 7 4 5 64 16 0 0 0 0 0
2018-03-07 22:31:41.980 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery for bridge jeelink:jeelinkUsb:92155c70 found unknown sensor of type jeelink:pca301 with id 5-64-16
2018-03-07 22:31:41.989 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'jeelink:pca301:5-64-16' to inbox.

But i cant switch the sockets.
Under
Configuration > Things
I see JeeLink USB Receiver and my sockets as UNINITIALIZED

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

EDIT:
First Day User Post reached so:

Thx for your time & help

vbier · March 7, 2018, 9:49pm

They will stay uninitialised until the first reading has been received and then should come online. At that point you should be able to switch them.
I am not sure what the polling interval is, but if my memory serves me right it can be configured with an init command. You can specify an init command in the stick configuration.
That’s it for today. More tomorrow.

vbier · March 8, 2018, 3:47pm

I have updated the jar once again. I forgot one file yesterday, have now created dedicated thing types for LaCrosseGateways and also updated the README to reflect the changes:

https://github.com/vbier/openhab2-addons/raw/jars/addons/binding/org.openhab.binding.jeelink/org.openhab.binding.jeelink-2.3.0-SNAPSHOT.jar

5tift · March 8, 2018, 6:26pm

Hi Volker,
after your last Update the sockets works perfect.
Thx for intensiv help

Now it´s time for the 2nd Jeelink & Lacrosse

64matze · March 11, 2018, 10:50am

Dear Volker
I just installed the latest jar you published in this thread.
I just copied it into /usr/share/openhab2/addons/
Now I got the following error in the openhab log:

2018-03-11 11:45:12.871 [ERROR] [org.openhab.binding.jeelink         ] - FrameworkEvent ERROR - org.openhab.binding.jeelink
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.jeelink [217]
  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.2.0"; osgi.identity="org.openhab.binding.jeelink"; singleton:="true"
	at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1600) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514) [?:?]
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) [?:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [?:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [?:?]

Do I need to unsintall the “old” 2.2.0 binding that was installed via PaperUI?

Thank you in advance.
Best regards,
Matthias

vbier · March 11, 2018, 11:10am

Yes.

habpower · March 24, 2018, 4:05pm

Dear volker!

Thank you for that advice! i was not aware about this possibility! After doing that everything works fine again! Thank you again!

best regards
Walter

julcaron · April 23, 2018, 9:57am

Hello Everybody,
I’ve my openhab system working for more than one year on raspebrry pi 3 and openhabian config, with the zwave binding. i bought a jeelink stick in order to collect the data from my lacrosse weather station. in order to make the both stick working together, i used Symlinks for the Zwave Stick and the JeeLink stick. now the both are recognised and online.
unfortunately it seems that i can’t discover any lacrosse sensors (TX29DTH-IT). i followed this topic others and try to solve the problem by my self. but for the moment it still do not work for me.

below you have the log for the jeelink binding:

2018-04-23 11:08:27.304 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkUsb:1dbffc92' changed from ONLINE to OFFLINE

2018-04-23 11:08:27.310 [me.event.ThingUpdatedEvent] - Thing 'jeelink:jeelinkUsb:1dbffc92' has been updated.

2018-04-23 11:08:27.320 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkUsb:1dbffc92' changed from OFFLINE to ONLINE

2018-04-23 11:11:18.646 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkUsb:1dbffc92' changed from ONLINE to OFFLINE

2018-04-23 11:11:18.668 [me.event.ThingUpdatedEvent] - Thing 'jeelink:jeelinkUsb:1dbffc92' has been updated.

2018-04-23 11:11:18.688 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkUsb:1dbffc92' changed from OFFLINE to ONLINE

2018-04-23 11:13:45.498 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkUsb:1dbffc92' changed from ONLINE to OFFLINE

2018-04-23 11:13:45.506 [me.event.ThingUpdatedEvent] - Thing 'jeelink:jeelinkUsb:1dbffc92' has been updated.

2018-04-23 11:13:45.523 [hingStatusInfoChangedEvent] - 'jeelink:jeelinkUsb:1dbffc92' changed from OFFLINE to ONLINE

2018-04-23 11:36:11.596 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery started for bridge jeelink:jeelinkUsb:1dbffc92

2018-04-23 11:36:41.595 [DEBUG] [nal.discovery.SensorDiscoveryService] - discovery stopped for bridge jeelink:jeelinkUsb:1dbffc92

log list:

openhab> log:list
Logger                                             │ Level
───────────────────────────────────────────────────┼────────
ROOT                                               │ WARN
javax.jmdns                                        │ ERROR
org.apache.karaf.jaas.modules.audit                │ INFO
org.apache.karaf.kar.internal.KarServiceImpl       │ ERROR
org.apache.karaf.shell.support                     │ OFF
org.eclipse.smarthome                              │ INFO
org.jupnp                                          │ ERROR
org.openhab                                        │ INFO
org.openhab.binding.jeelink                        │ TRACE
org.openhab.binding.zwave                          │ DEFAULT
org.oprnhab.binding.jeelink                        │
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime                  │ OFF
smarthome.event                                    │ INFO
smarthome.event.InboxUpdatedEvent                  │ ERROR
smarthome.event.ItemAddedEvent                     │ ERROR
smarthome.event.ItemRemovedEvent                   │ ERROR
smarthome.event.ItemStateEvent                     │ ERROR
smarthome.event.ThingAddedEvent                    │ ERROR
smarthome.event.ThingRemovedEvent                  │ ERROR
smarthome.event.ThingStatusInfoEvent               │ ERROR

and binding version:

bundle:list|grep -i jeeLink
>
220 │ Active   │  80 │ 2.3.0.201803081647     │ JeeLink Binding

does anyone of you already face this issue, or can help me to solve it?

thanks

vbier · April 23, 2018, 10:42am

Have you flashed the sketch onto the stick? If yes, are you sure you configured the stick thing with the correct usb device? You logs show that nothing at all can be read from the stick, not even the line identifying the sketch.