RESOLVED: it was only necessary to move from raw to ebusd protocol.
I fell into error as “ebusd” did not appear in the list of suggested values
Thanks Chiuaua79, I didn’t know there was an ebus.config.
Hallo
I have updated to Openhab 3.3.0.M2 and now the ebus binding
does not work: “Status uninitialized”, binding release 3.2.14
Hallo
After update to Openhab 3.3.0.M3 the ebus binding works, but with many errors.
After 5 hours stop the binding and is offline, manually restart work for the next 5-6 hours.
Hi, did someone upgrade to the final Openhab 3.3 version and is eBUS working there?
Remarks later on. I updated my Rasperry from openhab 3.2 to 3.3: do NOT work. Restarts all 15 Min. I am still in analysis. Have two buendle witch access to usb/serial (smartmeter and ebus). Seems if one of them is active, the restarts are there. Little bit difficult to have the short time between restarts to change the config via karaf.
Maybe I will find the root cause - but if another one have an idea: please give a statement!
Maybe helpful to find the root-Cause … have the impression the issue is the integrated bundle ‘jSerialComm’ (version 2.5.3) which comes with the ebus-bundle.
If I unplug the USB-Plugger, I can install ebus-binding without restarts (OK, and it cant find the unplugged bridge). If I ask via bundle:list only jSerialComm is not active.
csowada - good to read from you. Hope you can find and fix the issue 
Hi,
You can use ebusd without the binding and transfer the values via mqtt. It works very well and is also very stable.
https://github.com/john30/ebusd
Hello All,
I’ll work on a new release next days. But my own system is not on 3.3 at the moment.
Thanks for info. But if I am right this means to use john30/ebusd instead of ebus-binding. And to go in all the details again to find out the value of interest (for me) and map them ?!
Those would be a quite hard way… So I hope csowada could fix the root issue…
@Roland62 I’ve commited a first test version on github. You can try this download
https://github.com/csowada/openhab-ebus-binding/suites/7189033507/artifacts/287073182
https://github.com/csowada/openhab-ebus-binding/pull/10
I was able to install the version on a fresh windows oh3.3 Installation. but it was not tested yet. I guess you need a github account to access the artifacts.
Hi @csowada I have a github account and could download it. Even after a (manual) system restart it stay on ‘2022-07-02 12:37:43.345 [INFO ] [ng.ebus.internal.handler.EBusHandler] - Bridge is not online yet …’.
If I try to go in the configuration of the bridge via UI openhab restarts. Still without error messages - but if I am in the karaf-console I see it there - Connection is lost. Some minutes later the system messages come up starting of openhab.
Don’t know if it is helpful. Hat switched log for ebus from info to debug. Also here no entry when I go in UI for configuration of ebus bridge. Here the whole log+event messages after new boot of openhab
220702-log+event.txt (90.6 KB)
Found out, that in /var/log/daemon.log are created entries. Here from the last crash (where I try to go in UI-Configuration)
Jul 2 22:29:14 openHABianPi karaf[3061]: #
Jul 2 22:29:14 openHABianPi karaf[3061]: # A fatal error has been detected by the Java Runtime Environment:
Jul 2 22:29:14 openHABianPi karaf[3061]: #
Jul 2 22:29:14 openHABianPi karaf[3061]: # SIGILL (0x4) at pc=0xaa306e80, pid=3061, tid=3790
Jul 2 22:29:14 openHABianPi karaf[3061]: #
Jul 2 22:29:14 openHABianPi karaf[3061]: # JRE version: OpenJDK Runtime Environment Zulu11.52+13-CA (11.0.13+8) (build 11.0.13+8-LTS)
Jul 2 22:29:14 openHABianPi karaf[3061]: # Java VM: OpenJDK Client VM Zulu11.52+13-CA (11.0.13+8-LTS, mixed mode, serial gc, linux-arm)
Jul 2 22:29:14 openHABianPi karaf[3061]: # Problematic frame:
Jul 2 22:29:14 openHABianPi karaf[3061]: # C [libNRJavaSerialv8_HF.so+0x2e80]
Jul 2 22:29:14 openHABianPi karaf[3061]: #
Jul 2 22:29:14 openHABianPi karaf[3061]: # No core dump will be written. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again
Jul 2 22:29:14 openHABianPi karaf[3061]: #
Jul 2 22:29:14 openHABianPi karaf[3061]: # An error report file with more information is saved as:
Jul 2 22:29:14 openHABianPi karaf[3061]: # /var/lib/openhab/hs_err_pid3061.log
Jul 2 22:29:15 openHABianPi karaf[3061]: [thread 5824 also had an error]
Jul 2 22:29:15 openHABianPi karaf[3061]: [thread 6041 also had an error]
Jul 2 22:29:16 openHABianPi karaf[3061]: #
Jul 2 22:29:16 openHABianPi karaf[3061]: # If you would like to submit a bug report, please visit:
Jul 2 22:29:16 openHABianPi karaf[3061]: # Customer Support for Platform Core & Platform Prime | Azul
Jul 2 22:29:16 openHABianPi karaf[3061]: # The crash happened outside the Java Virtual Machine in native code.
Jul 2 22:29:16 openHABianPi karaf[3061]: # See problematic frame for where to report the bug.
Jul 2 22:29:16 openHABianPi karaf[3061]: #
Jul 2 22:29:16 openHABianPi systemd[1]: openhab.service: Main process exited, code=killed, status=6/ABRT
Jul 2 22:29:16 openHABianPi systemd[1]: openhab.service: Failed with result ‘signal’.
Jul 2 22:29:21 openHABianPi systemd[1]: openhab.service: Service RestartSec=5s expired, scheduling restart.
Jul 2 22:29:21 openHABianPi systemd[1]: openhab.service: Scheduled restart job, restart counter is at 1.
Jul 2 22:29:21 openHABianPi systemd[1]: Stopped openHAB - empowering the smart home.
Jul 2 22:29:21 openHABianPi systemd[1]: Started openHAB - empowering the smart home.
The named file ‘/var/lib/openhab/hs_err_pid3061.log’ contains only the text: hs_err_pid3061.log
Could you check which serial driver do you use. Sounds like a incompatible library for the pi. Can you switch to the buildin driver?
Hello @Roland62 ,
I’ve now update my productive system and the version old 3.1.13 and the new 3.3.16 are working without any issues. I use the build-in driver. My system is x64 Docker. S
Jul 2 22:29:14 openHABianPi karaf[3061]: # C [libNRJavaSerialv8_HF.so+0x2e80]
This line shows an low level issue with the serial library.
Hi @csowada if you could tell me, what I should have to do i will try it…
What I have done when the issue came up:
Only updated to openhab3.3 via cli openhabian-config.
Why I come a little bit later on here. Tried somewhat, but not helpful…
-
installed OpenJDK-11 as java provider via openhabian-config:
Nothing worked any more. cli java --version got the information will not run on this machine -
installend Zulu-11 32-bit via openhabian-config:
now same issue like before, only with zulu instead of OpenJDK -
Upgraded raspberry to bullseye
Have taken me longer time to get network-access again. But good to find hints on the internet…
But even issue stay -
Last step: reinstall openhab and openhab-addons.
Even error stay.
Checked again … only part, what outside of openhab was installed is librxtx-java have removed it - but same result.
And sarched in file-system for those libNRJavaSerialv8_HF - must come from openhab. Found it here:
var/lib/openhab/tmp/libNRJavaSerialv8_HF_openhab_0
var/lib/openhab/tmp/libNRJavaSerialv8_HF_openhab_0/libNRJavaSerialv8_HF.so
Maybe my environment
installed packed via apt:
aptlist-installed-220703.txt (42.3 KB)
activated feature of openhab:
feature-list-220703.txt (83.2 KB)
bundle-list:
bundle-list-220703.txt (14.8 KB)
Hello @Roland62 ,
one option is to change the Serial Driver in the Bridge thing to “jserialcomm”. But it will not solve the issue with the open hab driver in general.
Hello,
i will get a VC 15 CS/1-7 with VWL BM 270/5 and VRC 720 controller
Is it possible to use the VRC720 with this binding?
Hi @csowada could you give me an hint, how I could change it via cli ?
Problem: I cant use the Browser-UI. Latest by try to access the system crashes.
In the meantime I think I have the issue. But don’t know how let use openhab the right file.
See issue of nrjavaserial:
https://github.com/NeuronRobotics/nrjavaserial/issues/224
And I do not find a way to let use openhab the hopefully right file. See also another tread:
Here an example for a *.thing file
Bridge ebus:bridge:home “eBUS Bridge” @ “Heizung” [ serialPortDriver =“jserialcomm”, serialPort=“/dev/ttyUSB_EB”, masterAddress=“00”, advancedLogging=false ]
Have not found one file which on the whole SD-Card which ends with thing. Don’t know, where the config is stored which comes via UI…
But - I use the idea of the issue of this problem. Let start java with an own short script in the middel which gives the info for dedicated driver via
/usr/lib/jvm/java-17-openjdk-armhf/bin/java -DlibNRJavaSerial.userlib=/home/openhabian/libNR/libNRJavaSerialv5.so $*
First try was to use v5. Here the system do not crash, but ebus is not working
And I could see, that it was already set to jserialcomm. Have changed it - no success.
Now I can try with the different versions of libNRJavaSerial… will latest report, when it work (or when all of the variants not working)
And here is the result. The archive nrjavaserial-5.2.1.jar contains different native driver:
libNRJavaSerialv6_HF.so libNRJavaSerialv7_HF.so libNRJavaSerialv8_HF.so
libNRJavaSerialv5.so libNRJavaSerialv6.so libNRJavaSerialv7.so libNRJavaSerialv8.so
With all *HF.so driver the system crashed. With the other not - but serial interface do not work with NRJavaSerial. Only with jserialcomm with a but…
The but:
jserialcomm works only with ebus till version 3.1.13.
Seems those was the reason, why I went not to 3.2.14. The file was copied, but not in use. Do not really remember - but think it was not working.
Even ebus 3.3.16 is not working with jserialcomm.
So I have gone back to 3.1.3. Here ebus is working by using jserialcomm.
If I try to use NRJavaSerial with a … not restarting lib those messages come up:
2022-07-05 14:31:57.945 [WARN ] [s.internal.handler.EBusBridgeHandler] - Enable advanced logging for eBUS commands!
2022-07-05 14:31:58.158 [ERROR] [ion.EBusSerialNRJavaSerialConnection] - Unable to connect to serial port /dev/ttyUSB0
2022-07-05 14:31:58.243 [WARN ] [dev.ebus.core.EBusLowLevelController] - Retry to connect to eBUS adapter in 5 seconds …
Hello @Roland62, have you also tried the driver buildin? I could create a version with an older jserialcomm driver. But do you have a log that shows the issue with jserialcomm?