So, Autodiscovery finds nothing or only not your Vaillant device. This binding has only a subset of devices compared to to ebusd. Can give us the device type ?
I’ve released a new version, you should try it with this version. But you defined the thing by hand, a VRCxxx device with slave address 08, but your ebusd log shows 15. Could you try this, if auto discovery fails. Slave address 08 is for BAI things as far as I know.
I’ve now stopped ebusd on my FHEM-RPi so that ebus-adapter will be free and rebooted my other RPi with OH2 over VPN. When I will be at home I could send you the complete log file.
EDIT:
It’s really crazy, after I deleted now the ebus-bridge an added new, now something was found automatically und I get data
@csowada,
What do you mean exactly with “But you defined the thing by hand” ? I disabled the .thing file and followed the configuration instructions the github readme. Is there another way ?
Right now, there is only the Vaillant bai and the Tado extension kit on the ebus (also the ebus bridge of course).
I will try to install the newer version, see if that helps.
In meantime, I got some more error logs. Maybe this gives you more insight
@csowada,
I get below error messages in the log after installing the latest version 18 and creating a bridge thing, before adding the bai thing.
06:38:25.422 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
06:38:25.507 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
06:38:25.808 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:26.367 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
06:38:26.414 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
06:38:26.803 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:27.812 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:30.849 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:32.828 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:33.814 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:34.319 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]
06:38:34.844 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:38:35.414 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
06:38:35.468 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
06:38:35.806 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
After creating the bai thing from the inbox in PaperUI and creating two items, I get the below logs
06:48:34.386 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 1C 07 04 00 4E]
06:48:34.865 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:48:35.445 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
06:48:35.491 [TRACE] [nhab.binding.ebus.handler.EBusHandler] - eBUS node handler ebus:std:71c1289c:08 use collectionId std, not bai ...
06:48:35.534 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
06:48:35.875 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:48:36.435 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
06:48:36.481 [TRACE] [nhab.binding.ebus.handler.EBusHandler] - eBUS node handler ebus:std:71c1289c:08 use collectionId std, not bai ...
06:48:36.525 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
06:48:36.874 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
06:48:37.884 [TRACE] [de.csdev.ebus.core.EBusController ] - waiting for slave answer ...
None of the items is getting any value, they remain ‘Nan’.
Hello there, does anyone knows how to order the board for the ebus adapter, please?
The FHEM forum is in German and not very friendly with the translator
Thanks
I Try out your binding since December. It works fine. Now my openhab crash and I have to install everything new. I upgrade to Openhab 2.3 unstable Build 1268. Now I get in Papier UI an error:
UNINITIALIZED - HANDLER_INITIALIZING_ERROR linkRegistry
and nothing works.
How can I solve this? I read some discussion about removing “linkRegistry”?!?
Since my ebus binding is working I now wanna see some values. But there are a lot of Items who don’t delivers any values. So my first step, get Item an wait if there is an value. But this method isn’t really nice.
Is there a possibility to list all values? So I can pick them up and make not try & error?
in PaperUI you can use the Simple mode for Items in den system-config. Then all items of a new thing where automatically aktiv and you can see the value in “control”