I searched a lot, but I can’t find an instruction how to install the ebusd on an PI4 with openhabian.
Please tell me how to do it or where I can find an instruction. Unfortunately I don’t know much about linux.
@rqxrqx here you can find a instruction:
Thank you very much. I looked there already, but which package (Debian 8/9/10) could I use for openhabian?
You can find the Release in your console, like this:
Hi there, can anybody help me ? Any hints how to deal with it ?
I have the same release an installed the ebusd with the following commands:
sudo -s
wget -qO - https://raw.githubusercontent.com/john30/ebusd-debian/master/ebusd.gpg.key|apt-key add -
wget -O /etc/apt/sources.list.d/ebusd.list https://raw.githubusercontent.com/john30/ebusd-debian/master/ebusd-default-buster.list`
apt-get install ebusd
in /etc/default/ebusd I added: -d enh:192.168.8.162:9999
With this the adapter status is now:
ebusd connected: yes (inactive)
eBUS signal: no signal
eBUS initial signal: echo
Who can I activate the ebusd und receive the eBUS signal?
In the binding the eBUS Master Address is set to FF. Is this correct or where can I find the address?
@rqxrqx check the logs /var/log/ebusd.log and the service status ebusctl info & systemctl status ebusd.
Currently I use mqtt to transfer the values without binding.
The results look good to me:
[20:37:50] root@openhab:/home/openhabian# ebusctl info
version: ebusd 21.2.v21.2
access: *
signal: acquired
symbol rate: 71
max symbol rate: 128
reconnects: 0
masters: 1
messages: 11
conditional: 0
poll: 0
update: 4
address 04: slave #25, ebusd
address ff: master #25, ebusd
[20:37:53] root@openhab:/home/openhabian# systemctl status ebusd
● ebusd.service - LSB: controls ebusd, the daemon for communication with eBUS heating systems.
Loaded: loaded (/etc/init.d/ebusd; generated)
Active: active (running) since Sat 2021-05-15 20:36:48 CEST; 1min 57s ago
Docs: man:systemd-sysv-generator(8)
Process: 19760 ExecStart=/etc/init.d/ebusd start (code=exited, status=0/SUCCESS)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/ebusd.service
└─19766 /usr/bin/ebusd --pidfile /var/run/ebusd.pid --scanconfig --accesslevel=* --latency=100 -d enh:192.168.8.162:9999 --address=ff
Mai 15 20:36:48 openhab systemd[1]: Starting LSB: controls ebusd, the daemon for communication with eBUS heating systems…
Mai 15 20:36:48 openhab ebusd[19760]: Starting ebusd: ebusd.
Mai 15 20:36:48 openhab systemd[1]: Started LSB: controls ebusd, the daemon for communication with eBUS heating systems…
But the ebusd.log has errors. Any idea what could be wrong?
2021-05-15 20:36:48.972 [main notice] ebusd 21.2.v21.2 started with auto scan on enhanced device 192.168.8.162:9999
2021-05-15 20:36:49.387 [bus notice] bus started with own address ff/04
2021-05-15 20:36:49.395 [bus notice] device status: reset
2021-05-15 20:36:49.399 [bus notice] signal acquired
2021-05-15 20:36:49.903 [bus error] device status: unexpected available enhanced byte 2
2021-05-15 20:36:49.948 [bus error] device status: unexpected enhanced command 0x0e
2021-05-15 20:36:49.988 [bus error] device status: unexpected enhanced command 0x0e
2021-05-15 20:36:50.035 [bus error] device status: unexpected enhanced command 0x0e
2021-05-15 20:36:50.036 [bus error] device status: unexpected available enhanced following byte 1
2021-05-15 20:36:50.048 [bus error] device status: unexpected available enhanced byte 2
2021-05-15 20:36:50.052 [bus error] device status: unexpected available enhanced byte 2
2021-05-15 20:36:50.053 [bus error] device status: unexpected available enhanced byte 2
2021-05-15 20:36:50.056 [bus error] device status: unexpected available enhanced following byte 1
2021-05-15 20:36:50.057 [bus error] device status: unexpected available enhanced following byte 1
2021-05-15 20:36:50.078 [bus error] device status: unexpected available enhanced following byte 1
2021-05-15 20:36:50.112 [bus error] device status: unexpected available enhanced following byte 1
2021-05-15 20:36:50.113 [bus error] device status: unexpected available enhanced byte 2
2021-05-15 20:36:50.113 [bus error] device status: unexpected available enhanced byte 2
Finally the adapter works:
ebusctl info
version: ebusd 21.2.v21.2
update check: OK
access: *
signal: acquired
symbol rate: 23
max symbol rate: 258
min arbitration micros: 2
max arbitration micros: 100
min symbol latency: 9
max symbol latency: 195
reconnects: 2
masters: 6
messages: 497
conditional: 12
poll: 1
update: 10
address 04: slave #25, ebusd
address 10: master #2
address 15: slave #2, scanned “MF=Vaillant;ID=UI ;SW=0508;HW=6201”, loaded “vaillant/15.ui.csv”
address 23: slave, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”, loaded “vaillant/23.vr630.cc.csv”
address 25: slave, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”
address 26: slave, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”, loaded “vaillant/26.vr630.hc.csv”
address 3f: master #23
address 44: slave #23, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”
address 50: slave, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”, loaded “vaillant/50.vr630.mc.csv”
address 51: slave, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”, loaded “vaillant/51.vr630.mc.3.csv”
address 70: master #4
address 75: slave #4, scanned “MF=Vaillant;ID=RC C ;SW=0508;HW=6201”, loaded “vaillant/75.rcc.csv”
address 7f: master #24
address 84: slave #24, scanned “MF=Vaillant;ID=VR630;SW=0500;HW=6301”
address f0: master #5
address f5: slave #5, scanned “MF=Vaillant;ID=RC C ;SW=0318;HW=6201”
address ff: master #25, ebusd
But the ebus bindings receives no telegrams:
Any idea what could be the reason?
is that in the works?
still not working!
Hi all,
I get an error message
2021-06-18 12:53:22.635 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.ebus.internal.handler.EBusHandler@4baf9796': can't parse argument number:
java.lang.IllegalArgumentException: can't parse argument number:
at java.text.MessageFormat.makeFormat(MessageFormat.java:1451) ~[?:?]
at java.text.MessageFormat.applyPattern(MessageFormat.java:491) ~[?:?]
at java.text.MessageFormat.<init>(MessageFormat.java:370) ~[?:?]
at java.text.MessageFormat.format(MessageFormat.java:859) ~[?:?]
at de.csdev.ebus.command.EBusCommandException.<init>(EBusCommandException.java:34) ~[?:?]
at org.openhab.binding.ebus.internal.utils.EBusClientBridge.generatePollingTelegram(EBusClientBridge.java:259) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.getChannelTelegram(EBusHandler.java:276) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.initializeChannelPolling(EBusHandler.java:417) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.updateChannelPolling(EBusHandler.java:613) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.updateHandler(EBusHandler.java:624) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.initialize(EBusHandler.java:383) ~[?:?]
at jdk.internal.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:662) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:770) ~[?:?]
at java.text.MessageFormat.makeFormat(MessageFormat.java:1449) ~[?:?]
... 19 more
2021-06-18 12:53:22.640 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while initializing handler of thing 'ebus:vrc700_general:52d3004b:15': can't parse argument number:
java.lang.IllegalArgumentException: can't parse argument number:
at java.text.MessageFormat.makeFormat(MessageFormat.java:1451) ~[?:?]
at java.text.MessageFormat.applyPattern(MessageFormat.java:491) ~[?:?]
at java.text.MessageFormat.<init>(MessageFormat.java:370) ~[?:?]
at java.text.MessageFormat.format(MessageFormat.java:859) ~[?:?]
at de.csdev.ebus.command.EBusCommandException.<init>(EBusCommandException.java:34) ~[?:?]
at org.openhab.binding.ebus.internal.utils.EBusClientBridge.generatePollingTelegram(EBusClientBridge.java:259) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.getChannelTelegram(EBusHandler.java:276) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.initializeChannelPolling(EBusHandler.java:417) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.updateChannelPolling(EBusHandler.java:613) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.updateHandler(EBusHandler.java:624) ~[?:?]
at org.openhab.binding.ebus.internal.handler.EBusHandler.initialize(EBusHandler.java:383) ~[?:?]
at jdk.internal.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.openhab.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:154) [bundleFile:?]
at org.openhab.core.internal.common.Invocation.call(Invocation.java:52) [bundleFile:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:662) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:770) ~[?:?]
at java.text.MessageFormat.makeFormat(MessageFormat.java:1449) ~[?:?]
... 19 more
and I don’t know why. My thing for the VR700_gerneral looks like every other VR700 module
Thing ebus:vrc700_general:52d3004b:15 "VR700 general" [slaveAddress="15", polling=60]
{}
Thing ebus:vrc700_hc1:52d3004b:15 "VRC 700 heating circuit 1" [slaveAddress="15", polling=10]
but only the VR700_general says error. But I can receive values from the thing like the outside temperatur.
I understood that ebus is not available since 3.1.M4. Any way how I could help to make it available?
I think this should work or? At the moment I not spend any free time on my computer. I’ll work on it if the weather is colder. For me it is a winter project.
1 Like
Not working for me, csowada. I have the following files in the add-on folder:
-rw-r--r-- 1 pi pi 284220 Jun 21 23:02 commons-lang-2.6.jar
-rw-r--r-- 1 pi pi 734398 Jun 21 23:44 org.openhab.binding.ebus-3.0.12-SNAPSHOT.kar
However, I only tried for a couple of minutes. Maybe I have overseen something.
I am noticing user and group “pi”. Supposedly your user “openhab” is also member of group “pi”? I need to have files in my addons folder being group “openhab” and owner “openhab”.
Hi Chiuaua79,
no that does not make a difference, because everyone can read. However, I changed user and group to openhab - which anyway did not make a difference:
-rw-r--r-- 1 openhab openhab 284220 Jun 21 23:02 commons-lang-2.6.jar
-rw-r--r-- 1 openhab openhab 734398 Jun 21 23:44 org.openhab.binding.ebus-3.0.12-SNAPSHOT.kar
It still does not work after a reboot.
Could you please create an issue on GitHub and attach a log? I was not aware of an additional issue with the Milestone build.