Remote debugging is always difficult if hardware is involved. I would try the following steps:
- Hardware: Is the adapter properly powered and does it receive eBus signals? To check this the adapter has a couple of LEDs, e.g. yellow=power, green=eBus data received. Just look at Willkommen zum eBUS Adapter 3!. Looking at the circuit diagram, the eBus inputs are fed into a rectifier diode circuitry. Means: The eBus wiring works both ways. I don’t think that you have to tinker with the eBus addresses. If the green LED is blinking I would guess that the adapter properly receives data.
- Wifi: Is Wifi properly enabled? The blue LED gives some hints (see LED meaning above)
- Communication: Does the Raspberry Pi receive data? From here on I cannot help anymore I don’t have experience with the Wifi mode. I would try to get support from the FHEM community (eBUS Adapter 3.0)
- eBUS Binding: Does the eBUS openHAB binding is set correctly? There, I would continue the discussion in the respective forum ([eBUS 2.0,3.0] Binding - Release 2.50.11 & 3.0.11)
Hope this gives you at least some debugging direction.