eBUS Binding 5.x [5.0.0.0;6.0.0.0)

[dk8pn (Willi Konrath)]

I have my ebusd adapter disabled in openHAB because my production coupler is an Esera LAN eBUS adapter. There are two ways of connecting to the ebusd adapter:

1. Directly via WiFi, port and using network driver “raw”.
2. To a computer which already runs the ebus daemon using the computers IP and port and then the the ebusd network driver. For this, some environment settings are required (see below).

Onyl way 2. enables the full advantage of ebusd (zero roundtrip time).

See also here:

@dk8pn

Just switched over from my Esera LAN bridge to the “ebusd adapter 3” WiFi bridge. Cor was right and the network driver needs to be raw and not ebusd.

But this configuration does of course not have the advantages of ebusd w.r.t. a zero roundtrip time.

If i apply the “ebusd” network driver, i need to start the daemon within the Windows docker desktop first. Then, within the openhab ebus bridge, i connect to the computers IP (here 192.168.1.100) and port (here 8888) where the docker desktop with ebusd is running. IP and port are now not those of the ebusd adapter 3. This setup takes now full advantage of ebusd. Its a bit complicated because i am a Windows10 user. Using a Pi, this should be much simpler because docker is not needed and openhab can run on the same Unix computer than ebusd.

In docker, the ebusd image needs environment variable settings. Here i have EBUSD_OPTS (see the screenshot below) where i use the “ens:” acc. to John30’s descriptions. But the openhab binding bridge requires “naked” IP and port.