I have posted a link to a test version in the other thread.
Changes have just been merged for 2.4 that add units to the channels. A side-effect of this is that channels âcurrentWattâ and âmaxWattâ have been renamed to âcurrentPowerâ and âmaxPowerâ. So in case you update your 2.4 snapshot version make sure to re-discover all ec3k and pc301 things.
Continuing the discussion from New Jeelink Openhab2 Binding:
Hey there!
Iâve updated to openhab 2.3.0 and jeelink addon 2.3.0 and tried to configure the pca301 like the wiki says with
Number:Power SocketWattage {channel="jeelink:pca301:1-160-236:currentPower"}
but it doesânt work
So i tried
âcurrentWattâ instead of âcurrentPowerâ
now it works
Is there a fault in the wiki?
And the consumptionTotal puts out (example) 430,0 kWh instead of 0,4 kWh.
Is there a fix and can we use the reset function of pca301 to reset the statistics?
Thanks!
edit: if you are on 2.3.0, then use the old stuff
from 2.4.0 you have the new stuff
during an upgrade from 2.3 to 2.4, apt shows me:
Warning: Jeelink Binding: The 'currentWatt' and 'maxWatt' channels have been replaced with 'currentPower' and 'maxPower' channels
here? Jeelink - Bindings | openHAB (thatâs for 2.4)
To see the docs for 2.3, use: https://www.openhab.org/v2.3/addons/bindings/jeelink/ (there is a version menu to the top right)
Is there a new version again?
Did the 2.3 update 5 days agoâŚ
no, not yet
the 2.4 is in testing (but includes many goodies )
see more here: [OH 2.4.0 M6] Testing Results
Dear all
Sorry if this question was already answered, I was not following this topic for a while.
After the latest openhab update I get the following error during startup.
2018-12-01 14:06:04.951 [ERROR] [org.openhab.binding.jeelink ] - FrameworkEvent ERROR - org.openhab.binding.jeelink
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.jeelink
Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.3.0.201803081647"; osgi.identity="org.openhab.binding.jeelink"; singleton:="true"
Could somebody help me to fix this.
Thank you in advance.
BR
Matze
Sounds like you have two versions of the plugin installed.
Yes, I know, it looks like this.
But I do not know where this comes from?
I have no jar file any more and just installed the binding via PaperUI.
Any hint what could be wrong?
Should I uninstall the binding? How to do that?
Thank you in advance.
I got it.
I found that there are two JeeLink Bindings installed, via the karaf console.
I unistalled one and everything is ok now.
BR
Matthias
Unfortunately it is not solved.
When I try to install a new binding I get this error.
2018-12-07 16:27:09.652 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-astro': Error restarting bundles:
Could not resolve module: org.openhab.binding.jeelink [219]
Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.3.0.201803081647"; osgi.identity="org.openhab.binding.jeelink"; singleton:="true"
Any hint how to resolve this?
Thank you in advance.
you should try to clean tmp & cache
if you have 2 versions of the same binding and remove one from the console it doesnât clean all the stuff and it may reload it.
See: Clear the Cache
Thank you very much!
That did it!
@vbier Are you still using your JeeLink stick with ser2net?
I also tried to get it running but something is not working as it should. My JeeLink thing of openHAB has the state online but it doesnât receive any information from any of my sensors. It doesnât finds any sensors (auto discovery & manual thing config). I tried switching the baud rate (56700 as used by jeelinkUsb and 115200) in the ser2net config file but this doesnât help either and the information on the internet about JeeLinks via ser2net are quite thin.
I also use ser2net to share my zwave stick via tcp and that works fine.
Can you tell me which settings are working for your case on the side of openHAB and ser2net?
I think the important part is to simulate the version string the Jeelink sends on connect. This is from my ser2net.conf:
BANNER:jeelink:\r\n[LaCrosseITPlusReader whatever]\r\n
6666:raw:600:/dev/ttyUSB0:57600 8DATABITS NONE 1STOPBIT
This allows me to connect to the PC that has the ser2net running on port 6666.
I had a strange behavior when i inserted these lines in my ser2net.conf. At first it looked like it would work. My sensor things were online but after about ten seconds they were unknown/offline again. I also tried without a timeout.
BANNER:jeelink:\r\n[LaCrosseITPlusReader whatever]\r\n
3333:raw:0:/dev/zwave:115200 8DATABITS NONE 1STOPBIT
3334:raw:0:/dev/jeelink:57600 8DATABITS NONE 1STOPBIT
3335:raw:0:/dev/zigbee:115200 8DATABITS NONE 1STOPBIT
/dev/jeelink is my static udev link of the port from the jeelink which leads to /dev/ttyUSB0
I also tried mentioning the banner after the jeelink line like in the examples of the config file.
BANNER:jeelink:\r\n[LaCrosseITPlusReader whatever]\r\n
3333:raw:0:/dev/zwave:115200 8DATABITS NONE 1STOPBIT
3334:raw:0:/dev/jeelink:57600 8DATABITS NONE 1STOPBIT jeelink
3335:raw:0:/dev/zigbee:115200 8DATABITS NONE 1STOPBIT
Do I have to modify the banner e.g. so the whatever
meets some id or something else?
Did you find any good instructions on how to create those banners or is there a special way to find out what banners might work?
I shutdown the server over night and now in the morning the jeelink stick seems to work alongside the zwave stick. Strange behavior.
Hello Volker,
thank you for this great JeeLink Binding. Works flawless for here with a few of LaCrosse Sensors.
may i ask you about the BatterNEW and LOWBattery logics ?
Yesterday around 21 o´clock i put new Batterys (Eneloop) in my Sensors.
And the switch Battery NEW goes to "ON"State. Works great.
But this morning 6 o´clock the Switch Battery NEW was in âOFFâ State.
How come ?
Br Peter
Because it was no longer new? I have no idea as I did neither invent the protocol nor manufacture the HW. I have only written the binding that displays the values.
Ok, letâs see. Because i setup another additional Lacrosse.
I fired it up around 20:30. Now I will keep an eye at witch time the BatteryNew went off.