eBus binding OH2 RPi3 USB Koppler - solved

Hello all,

I’ve already spent a couple of hours trying to get the eBus binding working. My config:

  • RPi 3
  • OpenHAB 2 build 600 + eBus binding
  • USB eBus Koppler
  • Protherm Gepard (compatible with Vaillant BAI00)

I get no errors nor warnings during startup, everything looks ok. But it doesn’t receive any telegrams. I configured the binding to log all telegrams but this log is empty.

When I configure one of the items to do polling I get this error message from time to time:

Send queue is full! The eBUS service will reset the queue to ensure proper operation.

When I disable eBus binding and try to communicate with the bus using the ebusd utility, it works like a charm - I can read the values from the boiler. So it’s not a hardware problem.

Is there any special configuration that has to be done or something else that I am missing? I’m really out of ideas… Thanks for any help!

Does the openhab user have permission to read/write to the /dev/tty device where the eBus dongle resides? This is often accomplished by adding the openhab user to the dialout group. This assumes you installed using apt-get.

Thanks for your answer. Yes, I already gone through this. When I started ebus binding for the first time there was an error message that it can’t open the serial port. So I added the openhab user to the dialout group and the error disappeared.

Yes, I installed using apt-get (openhab-offline).

Well, I can’t see anything generic that could be wrong. I don’t know this technology so can’t help.

Could you attach your ebus.cfg and the start log? You could also increase the log level to get more information.

ebus.cfg:

serialPort=/dev/ttyUSB0
parsers=common,vaillant-bai00
record=all
senderId=FF

log (ebus related entries only):

2016-11-22 13:12:56.843 [DEBUG] [org.openhab.binding.ebus            ] - BundleEvent [unknown:512] - org.openhab.binding.ebus
2016-11-22 13:12:57.043 [DEBUG] [org.openhab.binding.ebus            ] - ServiceEvent REGISTERED - {org.openhab.model.item.binding.BindingConfigReader, org.openhab.binding.ebus.EBusBindingProvider}={component.name=org.openhab.binding.ebus.genericbindingprovider, component.id=1, service.id=106, service.bundleid=204, service.scope=bundle} - org.openhab.binding.ebus
2016-11-22 13:12:57.537 [DEBUG] [org.openhab.binding.ebus            ] - BundleEvent STARTING - org.openhab.binding.ebus
2016-11-22 13:12:57.539 [DEBUG] [org.openhab.binding.ebus            ] - BundleEvent STARTED - org.openhab.binding.ebus
2016-11-22 13:13:06.854 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'ebus.items'
2016-11-22 13:13:24.865 [DEBUG] [rnal.connection.EBusCommandProcessor] - Remove all polling items for this provider from scheduler ...
2016-11-22 13:13:24.866 [DEBUG] [ab.binding.ebus.internal.EBusBinding] - eBus binding has been started.
2016-11-22 13:13:24.871 [DEBUG] [org.openhab.binding.ebus            ] - ServiceEvent REGISTERED - {org.osgi.service.cm.ManagedService, org.osgi.service.event.EventHand
ler}={event.topics=openhab/ *, service.pid=org.openhab.ebus, component.name=org.openhab.binding.ebus, component.id=0, service.id=297, service.bundleid=204, service.scope
=bundle} - org.openhab.binding.ebus
2016-11-22 13:13:24.873 [INFO ] [ab.binding.ebus.internal.EBusBinding] - Update eBus Binding configuration ...
2016-11-22 13:13:24.881 [DEBUG] [ab.binding.ebus.internal.EBusBinding] - Load eBus Parser Configuration "common" ...
2016-11-22 13:13:24.926 [DEBUG] [.internal.EBusGenericBindingProvider] - Process binding cfg for ebus_test with settings id:boiler.pressure, refresh:10 [Context:ebus.it
ems]
2016-11-22 13:13:24.928 [DEBUG] [rnal.connection.EBusCommandProcessor] - Binding changed for item ebus_test
2016-11-22 13:13:24.932 [DEBUG] [rnal.connection.EBusCommandProcessor] - Add polling item ebus_test with refresh rate 10 to scheduler ...
2016-11-22 13:13:26.353 [DEBUG] [ab.binding.ebus.internal.EBusBinding] - Load eBus Parser Configuration "vaillant-bai00" ...
2016-11-22 13:13:26.548 [INFO ] [ab.binding.ebus.internal.EBusBinding] - Enable CSV writer for eBUS all
2016-11-22 13:17:13.944 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:20:33.957 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:23:53.967 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:27:13.978 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:30:33.988 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:33:54.000 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:37:14.010 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:40:34.022 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:43:54.034 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-22 13:47:14.044 [ERROR] [onnection.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.

I finally found the solution.

feature:install openhab-transport-serial

This installs nrjavaserial and the serial port can then be successfully opened by the ebud binding.

1 Like

Wow, this was new to me that the serial library is missing. Thank you for you information.

Hi,

Could you give me a hint how you used the ebusd utility to communicate directly with ebus coupler.
I am having trouble of configuring the ether ebus coupler of the same manufacturer. I am not sure if I am getting the ebus connected the right way, especially the level adjustment.
Would be great I I would see some terminal output of traffic going over the ebus.