Ebus binding

Thanks, looks better now, however I only receive 3 results out of all the ones I use.

This is my log:

2016-11-01 17:54:18.661 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 15 B5 09 03 0D 34 00 1E 00 01 00 9B 00 AA
2016-11-01 17:54:20.172 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d67RemainingBoilerBlockTime! Check your item configuration.
2016-11-01 17:54:22.254 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:22.254 [DEBUG] [.ebus.internal.parser.Analyses] - FF 15 B5 09 03 0D 34 00 1E 00 01 00 9B 00 AA
2016-11-01 17:54:22.262 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:22.265 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:22.263 [DEBUG] [.ebus.internal.parser.Analyses] - >>> VRT 350 HC1 modulating status
2016-11-01 17:54:25.545 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:25.548 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:26.667 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:26.803 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:27.716 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 54 00 AC AA
2016-11-01 17:54:28.188 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d13CirPump! Check your item configuration.
2016-11-01 17:54:28.472 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 08 B5 09 03 0D 54 00 AC 00 00 00 00 AA
2016-11-01 17:54:28.479 [DEBUG] [.ebus.internal.parser.Analyses] - FF 08 B5 09 03 0D 54 00 AC 00 00 00 00 AA
2016-11-01 17:54:28.480 [DEBUG] [.ebus.internal.parser.Analyses] - >>> BAI00 - d.35 Position of diverter valve (combination boilers only)
2016-11-01 17:54:32.876 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:37.183 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:38.165 [ERROR] [i.c.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-01 17:54:39.195 [ERROR] [o.b.e.i.c.EBusCommandProcessor] - Error while running runnable …
java.lang.NullPointerException: null
at org.openhab.binding.ebus.internal.parser.EBusConfigurationProvider.getCommandById(EBusConfigurationProvider.java:259) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeEBusTelegram(EBusCommandProcessor.java:170) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeSendData(EBusCommandProcessor.java:311) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor$1.run(EBusCommandProcessor.java:102) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
2016-11-01 17:54:41.171 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d47OutsideTemperature! Check your item configuration.
2016-11-01 17:54:44.076 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 15 B5 09 03 0D 80 00 82 00 02 52 01 7A 00 AA
2016-11-01 17:54:47.685 [DEBUG] [.ebus.internal.parser.Analyses] - FF 15 B5 09 03 0D 80 00 82 00 02 52 01 7A 00 AA
2016-11-01 17:54:47.686 [DEBUG] [.ebus.internal.parser.Analyses] - >>> VRT 350 current room temperature
2016-11-01 17:54:50.688 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 08 B5 09 03 0D 3F 00 2F 00 01 01 9A 00 AA
2016-11-01 17:54:55.077 [DEBUG] [.ebus.internal.parser.Analyses] - FF 08 B5 09 03 0D 3F 00 2F 00 01 01 9A 00 AA
2016-11-01 17:54:55.079 [DEBUG] [.ebus.internal.parser.Analyses] - >>> BAI00 - d.11 Status external heating pump
2016-11-01 17:54:55.087 [DEBUG] [.ebus.internal.parser.Analyses] - 03 64 B5 12 02 02 32 54 00 06 32 01 00 80 FF FF B9 00 AA
2016-11-01 17:54:55.090 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-11-01 17:54:55.094 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:58.154 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:09.471 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 17 00 52 AA
2016-11-01 17:55:09.472 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:55:10.386 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:12.431 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 17 00 52 AA
2016-11-01 17:55:15.514 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:15.868 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:17.297 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:22.236 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d67RemainingBoilerBlockTime! Check your item configuration.
2016-11-01 17:55:22.237 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:23.237 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:25.256 [DEBUG] [i.c.AbstractEBusWriteConnector] - Received wrong telegram: FF 08 B5 09 03 0D 17 00 52 E6
2016-11-01 17:55:26.176 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 17 00 52 AA
2016-11-01 17:55:28.169 [ERROR] [i.c.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-01 17:55:28.190 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d13CirPump! Check your item configuration.
2016-11-01 17:55:33.704 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:36.564 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 15 B5 09 03 0D 4B 00 6E AA
2016-11-01 17:55:39.205 [ERROR] [o.b.e.i.c.EBusCommandProcessor] - Error while running runnable …
java.lang.NullPointerException: null
at org.openhab.binding.ebus.internal.parser.EBusConfigurationProvider.getCommandById(EBusConfigurationProvider.java:259) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeEBusTelegram(EBusCommandProcessor.java:170) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeSendData(EBusCommandProcessor.java:311) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor$1.run(EBusCommandProcessor.java:102) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
2016-11-01 17:55:39.730 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:41.173 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d47OutsideTemperature! Check your item configuration.
2016-11-01 17:55:42.021 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:43.021 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:43.167 [ERROR] [i.c.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-01 17:55:52.018 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:54.223 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!

My 12 year old boiler has been replaced with a new one as the main heat echanger failed :frowning: with the same model name (completely new PCB and burner). The controls are still the same (350) so should still respond and many still work over ebusctl, but not through openhab.

Did you had the same problems with the 1.7 binding?

I haven’t used it in a while but I remember those error messages occurring back then.

I think you have a problem with the delay of your connection. So you often run in sync collisions. How is your openhab connected to the ebus coupler? Via Wifi?

Maybe the C/C++ implementation of ebusd is faster than a Java implementation. Or the garbage collector causes delays.

I personally use a usb coupler, so no tcp network overhead in my setup.

The technical problem is the ebus byte collision check. The binding must react on the read bytes within microseconds. This is critical!

Hi,

I use the USB eService Coupler connected via a Raspberry Pi 3, so the faster one without the underpowered USB port.

I have to restart openhab when it happens. Sometimes restarting the Raspberry Pi fixes it.

This is the device ID:

E-Service_GmbH_eBus_Coupler_USB_A6YLL9V6-if00-port0.

Openhab is installed locally on the Raspberry Pi 3.

Um, could you send the link again for the new binding version? I can’t seem to find it on your github, only an old one from 2015 and I can’t find it through the OH page either…
Thank you!

There is no newer version available. You can download the current version from the OH web site.

I have tested with another tool that runs off of ebusd and is based on nodejs, and yes unfortunately it does seem that because Openhab is based on Java, it might be too much for the RPi. I have no issues with the nodejs software combined with ebusd.

I will try this next weeks with my usb coupler based on a TDI chip. Maybe it is helpful for you?

https://projectgus.com/2011/10/notes-on-ftdi-latency-with-arduino/

It’s already there on the Rpi :frowning:

cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
1

It looks like the used RXTX version has a build-in delay of 20ms.

Is that relevant to my eService Coupler too?

This is maybe the reason why the java version has a higher delay. I will try another serial library.

Here is a test version with RXTX and JSSC as serial port driver. On my device the timings a bit better with JSSC.
You must add ebus:useJSSC=true to the openhab.cfg to use JSSC.

Warning: This version is only for test !!!

https://drive.google.com/open?id=0B5Vjy5Qe0CabdDlYZGI0QzI1Vlk

Here my results from a Odroid U3 on Arch Linux

21:17:58.730 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 26 us
21:17:58.736 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:221] - read delay 4584 us
21:17:58.737 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 56 us
21:17:58.738 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 66 us
21:17:58.739 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 37 us
21:17:58.740 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 32 us
21:17:58.741 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 26 us
21:17:58.741 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 45 us
21:17:58.742 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 25 us
21:17:58.743 INFO  o.o.b.e.i.c.AbstractEBusWriteConnector[:209] - write delay 24 us

Hi csowada,

Thanks for the test release, it did to magic! I’m only running a test OH1.8.3 with the ebus items now and it got MUCH faster, and it has lost all the SYN collision problems, thank you very much!!

I have one issue left, but that is independent from your binding - but maybe you or someone could help… My thermostat is a Vaillant VRC470 and I can’t seem to catch any communication between it and the boiler. I’m looking for ID 15, but there’s not a single telegram with it.
I have also tried to send something to it, but to no avail.

Number	TOutside		"Temperature outside [%.1f]"	<temperature>	(All, gGroundFloor)	{     ebus="id:burner_v.temp_outside" }
Number	THeatingOut		"Heating TOut [%.1f °C]"	<temperature>   (All, gGroundFloor)	{ ebus="id:burner_v.temp_vessel" }
Number	THeatingReturn	"Heating T [%.1f °C]"			<temperature>   (All, gGroundFloor)	{ ebus="id:burner_v.temp_return" }
Switch  Ebusc 	"Heating" 							(All, gGroundFloor) { ebus="id:burner_v.heating_on" }
Switch  Ebuse 	"Switch it to auto " 						(All, gGroundFloor) { ebus=ON:"id:heating.set_program_heating_circuit_program2" }

I use these parsers:
ebus:parsers=_vaillant,vaillant-vrc470,vaillant-bai00

Without _vaillant, most of the telegrams are unknown… The ebus coupler is connected to the boiler directly, not to the thermostat.

Curiously if I add this line it goes crazy:
Number Ebusf "Temperature room [%.2f]" <temperature> (All, gGroundFloor) { ebus="id:controller.temp_room_disp, refresh:30"}

2016-11-12 23:17:43.591 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 460 us
2016-11-12 23:17:43.600 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 6904 us
2016-11-12 23:17:43.601 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.642 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 103 us
2016-11-12 23:17:43.651 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7428 us
2016-11-12 23:17:43.653 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.695 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 80 us
2016-11-12 23:17:43.704 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7930 us
2016-11-12 23:17:43.705 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.748 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 100 us
2016-11-12 23:17:43.757 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7539 us
2016-11-12 23:17:43.758 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.801 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 106 us
2016-11-12 23:17:43.810 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7493 us
2016-11-12 23:17:43.811 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.853 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 72 us
2016-11-12 23:17:43.863 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7818 us
2016-11-12 23:17:43.864 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.906 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 103 us
2016-11-12 23:17:43.915 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7706 us
2016-11-12 23:17:43.917 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:43.959 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 75 us
2016-11-12 23:17:43.968 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7454 us
2016-11-12 23:17:43.970 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:44.420 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 118 us
2016-11-12 23:17:44.429 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7321 us
2016-11-12 23:17:44.430 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-12 23:17:52.256 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 80 us
2016-11-12 23:17:52.265 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 8061 us
2016-11-12 23:17:52.266 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision detected! 0x10
2016-11-12 23:18:20.876 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 99 us
2016-11-12 23:18:20.885 [INFO ] [i.c.AbstractEBusWriteConnector] - read delay 7636 us
2016-11-12 23:18:20.886 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 219 us
2016-11-12 23:18:20.888 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 187 us
2016-11-12 23:18:20.889 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 271 us
2016-11-12 23:18:20.890 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 178 us
2016-11-12 23:18:20.891 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 174 us
2016-11-12 23:18:20.892 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 166 us
2016-11-12 23:18:20.893 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 164 us
2016-11-12 23:18:20.894 [INFO ] [i.c.AbstractEBusWriteConnector] - write delay 203 us
2016-11-12 23:18:20.934 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 15 B5 09 03 0D 80 00 82 AA

Any ideas? Thanks!

Dear guys,

I have a problem which is maybe easy to solve but I have no ideas anymore what to do…

It seems that openHAB will not connect to the eBus coupler at the startup.

In principle I have the same configuration like Jagohou:

  • eService Online Ethernet eBus Coupler (configured like discribed above)
  • Vaillant geoTherm heatpump connected to the bus (but it is not that important at the moment…)
  • eBus level adjusted
  • I’m able to ping the coupler
C:\Users\Server>ping 192.168.1.201

Ping wird ausgeführt für 192.168.1.201 mit 32 Bytes Daten:
Antwort von 192.168.1.201: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.1.201: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.1.201: Bytes=32 Zeit<1ms TTL=128
Antwort von 192.168.1.201: Bytes=32 Zeit<1ms TTL=128

Ping-Statistik für 192.168.1.201:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

openHAB startup log:

Launching the openHAB runtime...
osgi> 2016-11-16 09:57:57.612 [INFO ] [.o.core.internal.CoreActivator] - openHAB runtime has been started (v1.8.3).
2016-11-16 09:57:58.456 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - mDNS service has been started
2016-11-16 09:57:58.534 [INFO ] [o.o.i.s.i.DiscoveryServiceImpl] - Service Discovery initialization completed.
2016-11-16 09:57:58.534 [INFO ] [.io.transport.mqtt.MqttService] - MQTT Service initialization completed.
2016-11-16 09:57:58.534 [INFO ] [o.i.t.m.i.MqttBrokerConnection] - Starting MQTT broker connection 'mosquitto'
2016-11-16 09:58:00.422 [INFO ] [penhab.io.rest.RESTApplication] - Started REST API at /rest
2016-11-16 09:58:08.207 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'myhouse.sitemap'
2016-11-16 09:58:08.411 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'db4o.persist'
2016-11-16 09:58:08.426 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'exec.persist'
2016-11-16 09:58:08.442 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'logging.persist'
2016-11-16 09:58:08.442 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'mysql.persist'
2016-11-16 09:58:08.442 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'rrd4j.persist'
2016-11-16 09:58:08.458 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'myhome.items'
2016-11-16 09:58:08.936 [INFO ] [.o.u.w.i.servlet.WebAppServlet] - Started Classic UI at /classicui/openhab.app
2016-11-16 09:58:12.139 [INFO ] [b.k.i.connection.KNXConnection] - Established connection to KNX bus on 192.168.1.200:3671 in mode TUNNEL.
2016-11-16 09:58:12.514 [INFO ] [.p.rrd4j.internal.RRD4jService] - Removing invalid defintion component = null heartbeat = 0 min/max = 0.0/0.0 step = 0 0 archives(s) = [] 0 items(s) = []
2016-11-16 09:58:12.686 [INFO ] [.service.AbstractActiveService] - HTTP Refresh Service has been started
2016-11-16 09:58:12.686 [INFO ] [.service.AbstractActiveService] - NTP Refresh Service has been started
2016-11-16 09:58:12.733 [INFO ] [runtime.busevents             ] - Date state updated to 2016-11-16T09:58:12
2016-11-16 09:58:18.534 [INFO ] [c.internal.ModelRepositoryImpl] - Loading model 'myhouse.rules'
2016-11-16 09:58:56.728 [INFO ] [runtime.busevents             ] - Temperatur_Bar state updated to 17.80
2016-11-16 09:58:56.728 [INFO ] [runtime.busevents             ] - Humidity_Bar state updated to 40.70
2016-11-16 09:59:00.329 [INFO ] [m.script.Thermostat_Badezimmer] - Wochenende: nein

My .cfg file looks like:

############################## eBus Binding ###########################################
#

# Serial port of eBus interface
# Valid values are e.g. COM1 for Windows and /dev/ttyS0 or /dev/ttyUSB0 for Linux
#ebus:serialPort=COM2

# TCP Hostname and Port
# Warning: Only use ebus.hostname or ebus.serialPort
ebus:hostname=192.168.1.201
ebus:port=5000

# Custom parser configuration file
# This example tries to load a configuration ${openhab_home}/configurations/ebus-config.json
ebus:parserUrl=platform:/base/../configurations/ebus-config.json

# Load different parser, currently supported
# >> common - All telegrams defined by eBus interest group
# >> wolf - All telegrams specified by Wolf/Kromschröder
# >> vaillant - All telegrams specified by Vaillant
# >> testing -  All unknown or test telegrams
# >> custom - Use configuration defined by ebus:parserUrl
# default uses common and all vendor specified telegrams
ebus:parsers=custom

# Set the sender id of this binding, default is "FF"
#ebus:senderId=FF

my ebus-config.json

[
	{
"comment": "HeatSource->Heater",
"device": "VWP",

"id": "HeatSource",
"class": "controller",

"command": "B5 09",
"data": "(0D) 0F 00",

"values":   {
    "temp1": {"type": "data2c", "pos": 1, "label": "SourceTemperature"},
    "temp2": {"type": "data2c", "pos": 2, "label": "SourceTemperature"},
    "temp3": {"type": "data2c", "pos": 3, "label": "SourceTemperature"},
    "temp4": {"type": "data2c", "pos": 4, "label": "SourceTemperature"},
    "temp5": {"type": "data2c", "pos": 5, "label": "SourceTemperature"},
    "temp6": {"type": "data2c", "pos": 6, "label": "SourceTemperature"},
    "temp7": {"type": "data2c", "pos": 7, "label": "SourceTemperature"},
    "temp8": {"type": "data2c", "pos": 8, "label": "SourceTemperature"},
    "temp9": {"type": "data2c", "pos": 9, "label": "SourceTemperature"},
    "temp10": {"type": "data2c", "pos": 10, "label": "SourceTemperature"},
    "temp11": {"type": "data2c", "pos": 11, "label": "SourceTemperature"},
    "temp12": {"type": "data2c", "pos": 12, "label": "SourceTemperature"},
    "temp13": {"type": "data2c", "pos": 13, "label": "SourceTemperature"},
    "temp14": {"type": "data2c", "pos": 14, "label": "SourceTemperature"}        
            }
},
{
"comment": "OutsideTemperature",
"device": "VWP",

"id": "TempOut",
"class": "controller",

"command": "B5 09",
"data": "(0D) 06 00",

"values":   {
    "temp1": {"type": "data2c", "pos": 1, "label": "SourceTemperature"},
    "temp2": {"type": "data2c", "pos": 2, "label": "SourceTemperature"},
    "temp3": {"type": "data2c", "pos": 3, "label": "SourceTemperature"},
    "temp4": {"type": "data2c", "pos": 4, "label": "SourceTemperature"},
    "temp5": {"type": "data2c", "pos": 5, "label": "SourceTemperature"},
    "temp6": {"type": "data2c", "pos": 6, "label": "SourceTemperature"},
    "temp7": {"type": "data2c", "pos": 7, "label": "SourceTemperature"},
    "temp8": {"type": "data2c", "pos": 8, "label": "SourceTemperature"},
    "temp9": {"type": "data2c", "pos": 9, "label": "SourceTemperature"},
    "temp10": {"type": "data2c", "pos": 10, "label": "SourceTemperature"},
    "temp11": {"type": "data2c", "pos": 11, "label": "SourceTemperature"},
    "temp12": {"type": "data2c", "pos": 12, "label": "SourceTemperature"},
    "temp13": {"type": "data2c", "pos": 13, "label": "SourceTemperature"},
    "temp14": {"type": "data2c", "pos": 14, "label": "SourceTemperature"}        
            }
},      
{
"comment": "HeatSinkTemperatur",
"device": "VWP",

"id": "HeatSink",
"class": "controller",

"command": "B5 09",
"data": "(0D) 03 00",

"values":   {
    "temp1": {"type": "data2c", "pos": 1, "label": "SourceTemperature"},
    "temp2": {"type": "data2c", "pos": 2, "label": "SourceTemperature"},
    "temp3": {"type": "data2c", "pos": 3, "label": "SourceTemperature"},
    "temp4": {"type": "data2c", "pos": 4, "label": "SourceTemperature"},
    "temp5": {"type": "data2c", "pos": 5, "label": "SourceTemperature"},
    "temp6": {"type": "data2c", "pos": 6, "label": "SourceTemperature"},
    "temp7": {"type": "data2c", "pos": 7, "label": "SourceTemperature"},
    "temp8": {"type": "data2c", "pos": 8, "label": "SourceTemperature"},
    "temp9": {"type": "data2c", "pos": 9, "label": "SourceTemperature"},
    "temp10": {"type": "data2c", "pos": 10, "label": "SourceTemperature"},
    "temp11": {"type": "data2c", "pos": 11, "label": "SourceTemperature"},
    "temp12": {"type": "data2c", "pos": 12, "label": "SourceTemperature"},
    "temp13": {"type": "data2c", "pos": 13, "label": "SourceTemperature"},
    "temp14": {"type": "data2c", "pos": 14, "label": "SourceTemperature"}        
            }
}
]

Is there any other file which needs to be placed in the openHAB runtime folder? Did I forget anything else?

Thank you in advance for your help!

  • Have you copied the binding .jar to openhab?
  • You should start with ebus:parser=common

I’m such a stupid idiot! I was 100% sure I took the binding.jar into the folder…that was the mistake. :rolling_eyes:

Thank you very much csowada!

But what do you mean with your second sentence? Now I get some values from the eBus, is your second sentence still relevant?

Thanks

No, I was not sure if the binding loads if the configuration is incorrect or empty.

Ah ok, thanks a lot again!