eBUS Binding 4.x [4.0.0;5.0.0)

[csowada]

Here the new marketplace link for the 5.x binding.

eBUS Binding 5.x [5.0.0;6.0.0)

[ebus] With this binding, heating and ventilation systems that have an eBUS can be addressed. The corresponding hardware is required. Connections are possible via serial, TCP and ebusd. Requirements openHAB 5.x eBUS Hardware Interface (Serial, Ethernet, ebusd) eBUS protocol compatible Heating System Changelog or just check GitHub Releases for the latest or older versions. Resources Release 5.0.0 or just check GitHub Releases for the latest or older versions.

[Trainer (Hannes)]

Hi,
is there a way to deactivate the logs from ebus?

[Chiuaua79 (Cor)]

In your ebus Bridge Thing you have the option to enable or disable “advanced logging”, which is basically logging all the ebus messages in separate csv files (unresolved.csv and resolved.csv).

The regular logging to your openhab.log of INFO or WARN or other messages can be done via the openhab-cli. See the openhab Logging page. It can be turned OFF as well via openhab-cli.

[Trainer (Hannes)]

i still got this warnings
´´´

21:47:00.751 [WARN ] [sdev.ebus.core.EBusLowLevelController] - Received byte 0xAA is not equal to send byte 0x15! Stop send attempt …
21:47:14.163 [WARN ] [sdev.ebus.core.EBusLowLevelController] - Received byte 0x11 is not equal to send byte 0x15! Stop send attempt …
21:47:15.758 [WARN ] [sdev.ebus.core.EBusLowLevelController] - Received byte 0xD0 is not equal to send byte 0xB5! Stop send attempt …
21:47:16.856 [WARN ] [sdev.ebus.core.EBusLowLevelController] - Received byte 0xF5 is not equal to send byte 0x15! Stop send attempt …
21:47:17.913 [WARN ] [sdev.ebus.core.EBusLowLevelController] - Received byte 0x2A is not equal to send byte 0x15! Stop send attempt …
21:47:20.717 [WARN ] [sdev.ebus.core.EBusLowLevelController] - Received byte 0x00 is not equal to send byte 0x15! Stop send attempt …```

advanced logging is not active.

also in openhab-cli all ebus relevant addons are OFF

Logger │ Level
─────────────────────────────────────────────────────────┼──────
ESPHOMEDEVICE │ WARN
ROOT │ WARN
core.auth │ TRACE
de.sdev.ebus.core.EBusLowLevelController │ off
ebu │ WARN
ebus │ WARN
ebusd │ OFF
org.openhab.binding.ebus │ OFF
org.openhab.binding.ebus.internal.EBusLowLevelController │ OFF

[Chiuaua79 (Cor)]

When using “list -s” in openhab-cli console, I see the package “de.cs-dev.ebus.ebus-core”.

I suppose that is the one you need to silence and not “de.sdev.ebus.core.EBusLowLevelController”.

[dk8pn (Willibald Konrath)]

Have upgraded from OH 3.4.5 to OH 4.3.8 today. Use ebus binding 4.0.20 (jar file in addons folder).

Get now mass errors like this:

Exception in thread "ebus-receiver-557" java.lang.NoSuchMethodError: 'void org.openhab.core.library.types.DecimalType.<init>(java.math.BigDecimal)'

Has anybody a hint for me. Seems to have to do with Java and BigDecimal but i didn’t find the trick yet.

Edit: I have used the official upgrade tool for Windows. Beside this issue with ebus everything else worked quite well.

[dk8pn (Willibald Konrath)]

Deleting the folders “cache” and “tmp” did the trick.

Edit 28.11.2025:

The “send queue is full” error disappeared, this is great. On OH 3.4.5 i restarted the eBUS binding every 30 minutes. This is not longer necessary now. The binding works out perfectly.