[eBUS 2.0] New binding - Release Candidate 4

ebus
binding
Tags: #<Tag:0x00007f51e027b558> #<Tag:0x00007f51e027b3c8>

(Allodo) #403

THx a lot bzw., Danke sehr :slight_smile:


(Tom) #404

I can’t install this binding anymore, since everytime I try, the following error occurs: “Binding cannot be installed: Error reading bundle content.”. This is the only binding with this message, all others (including Marketplace bindings) work as expected.

Is there any special procedure to make it work again?


(csowada) #405

No, not really, maybe the file is broken. You should download the file again. Which file do you use? Have you extracted the zip file. Please check the readme file.


(Tom) #406

I used to and am still trying to install the binding via the marketplace (enabled in PaperUI, used to work using this technique).

Manually installing (by copying the jar in the addons-folder) works, but I would like to stick to the Marketplace-way, as it ensures always using the latest version.


(csowada) #407

NEW RELEASE - ALPHA 19

Hello All,

I’ve created a small update to support the newest openhab 2.3 pre-release. This version is not tested in my production, because it is still 2.2. I’m sure that this version is not compatible with openhab 2.2, but also not tested. Also the marketplace should work again (when oh support kar packages!?).

As you can see, all changes are untested from my side, because I’m busy with outdoor projects and holiday preparations.


(Cernon) #408

for me it works fine. Thanks for the great job.


(Witek) #409

hi, can someone guide me in more details how to install from zip file in OH2.3 (fresh upgrade)?
in the “old times :)” I used to just download .jar file and put it under

/usr/share/openhab2/addons/

and my understanding of the guide from release notes was the same. However if I unzipped files and put all of them under the above location, then OH2.3 doesn’t see them.
Or maybe kar way is better (it’s new to me as well as marketplace method, hence I didn’t touch it for the moment)
Edit: stupid me - only now I realized I haven’t checked the logs after install (just after OH2.3 upgrade :)) but they don’t help me either

2018-05-30 15:37:05.298 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.ebus-2.3.0-230518.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.ebus [255]
  Unresolved requirement: Import-Package: de.csdev.ebus.client
    -> Export-Package: de.csdev.ebus.client; bundle-symbolic-name="de.cs-dev.ebus.ebus-core"; bundle-version="0.9.18.SNAPSHOT"; version="0.0.0"; uses:="de.csdev.ebus.command,de.csdev.ebus.service.metrics,de.csdev.ebus.service.device,org.slf4j,de.csdev.ebus.core,de.csdev.ebus.command.datatypes,de.csdev.ebus.service.parser"
       de.cs-dev.ebus.ebus-core [253]
         Unresolved requirement: Import-Package: gnu.io; version="3.12.0"
  Unresolved requirement: Import-Package: de.csdev.ebus.command
    -> Export-Package: de.csdev.ebus.command; bundle-symbolic-name="de.cs-dev.ebus.ebus-core"; bundle-version="0.9.18.SNAPSHOT"; version="0.0.0"; uses:="de.csdev.ebus.cfg,org.slf4j,de.csdev.ebus.utils,de.csdev.ebus.core,de.csdev.ebus.command.datatypes.ext,de.csdev.ebus.command.datatypes,org.apache.commons.lang"

        at org.eclipse.osgi.container.Module.start(Module.java:444) [?:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [?:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [9:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [9:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [9:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [9:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [9:org.apache.felix.fileinstall:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [9:org.apache.felix.fileinstall:3.6.4]
2018-05-30 15:37:05.310 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/ebus-configuration-0.9.18-070518.jar
org.osgi.framework.BundleException: Could not resolve module: de.cs-dev.ebus.ebus-configuration [254]
  Unresolved requirement: Import-Package: de.csdev.ebus.cfg.std
    -> Export-Package: de.csdev.ebus.cfg.std; bundle-symbolic-name="de.cs-dev.ebus.ebus-core"; bundle-version="0.9.18.SNAPSHOT"; version="0.0.0"; uses:="de.csdev.ebus.command,de.csdev.ebus.cfg,org.slf4j,de.csdev.ebus.utils,de.csdev.ebus.cfg.std.dto,de.csdev.ebus.command.datatypes.ext,de.csdev.ebus.command.datatypes,org.apache.commons.lang,com.google.gson,com.google.gson.annotations,com.google.gson.reflect"
       de.cs-dev.ebus.ebus-core [253]
         Unresolved requirement: Import-Package: gnu.io; version="3.12.0"


hint how to install it will be still needed. I tried trough marketplace as well but also getting some errors (don’t want to paste them here not to open too many threads)


(csowada) #410

You need to install the serial bundle.


(Witek) #411

Thanks! this indeed helped. I didn’t think of it as I used transport serial since last summer and I didn’t expect to have it reinstalled after 2.3 upgrade.


(Witek) #412

My general observation is that perfectly stable configuration I had with Alpha 14 (from Nov) and OH2.2 works only partially now. I need some more time to debug whether this is because of OH2.3 or Alpha 19 (also, because I haven’t updated for a while I don’t know whether it stopped working in v19 or between some other version - also - maybe some of it was intentional by changing the format of items, etc). Will keep you posted.


(Witek) #413

I’ve spent some time debugging it and collecting logs and without hint from @csowada I doubt I can come to a solution.
To summarize environment:

  • platform was perfectly stable with OH2.2 and Alpha 14 (from Nov) hence I didn’t upgrade it to anything newer for some time. All items were immediately read from eBus as well as set where relevant.
  • yesterday I upgrade OH to 2.3 and therefore used latest Alpha 19. I installed it using zip file and installed transport-serial as suggested by @csowada above
  • eBus bridge became operational and I recreated everything (bridge, things from autodiscovery). I used existing items but without success I even recreted most of them (by native OH mechanism to create item from channel)
  • Obviously I haven’t touched anything in the HW part

General result is that apart from time from eBus and outside temperature (from vrc430/470 thing) all other items don’t work (maybe one more would work as well - depending on different test cycles and different channels enables I was able to get also VR81 temperature item to work). But I think this is not important what exactly works what not, because problem looks like being broader. Interestingly the items which I could see in the ebus log were not moved to PaperUI to monitor them neither to events.log. Only time was passed properly in both places. So I sticked to collecting logs for just couple of items configured.

I put platform in debug (even in TRACE for some time but I don’t think these details now are so important). I hope this sample is enough to conclude on reasons, if not I’m happy to send the whole log file with TRACE if it helps.

2018-05-31 11:47:05.652 [INFO ] [ding.ebus.thing.EBusTypeProviderImpl] - Loading eBUS Type Provider ...
2018-05-31 11:47:05.656 [WARN ] [ding.ebus.thing.EBusTypeProviderImpl] - EBusTypeProviderImpl.updated()
2018-05-31 11:47:05.659 [WARN ] [ding.ebus.thing.EBusTypeProviderImpl] - Update eBUS configuration ...
2018-05-31 11:47:06.818 [INFO ] [ding.ebus.thing.EBusTypeProviderImpl] - Load custom configuration file 'file:///home/pi/ebus-vaillant_vc206.json' ...
2018-05-31 11:47:06.841 [INFO ] [ding.ebus.thing.EBusTypeProviderImpl] - Load custom configuration file 'file:///home/pi/ebus-vaillant_vr61.json' ...
2018-05-31 11:47:07.327 [INFO ] [ding.ebus.thing.EBusTypeProviderImpl] - Generated all eBUS command collections ...
2018-05-31 11:47:39.175 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Initialize eBUS pollings for ebus:vr81:d43117b1:75 ...
2018-05-31 11:47:39.209 [INFO ] [hab.binding.ebus.handler.EBusHandler] - Initialize eBUS pollings for ebus:vrc430:d43117b1:15 ...
2018-05-31 11:47:40.817 [INFO ] [.binding.ebus.internal.EBusDiscovery] - Discovered device vrc430 ...
2018-05-31 11:47:41.073 [INFO ] [.binding.ebus.internal.EBusDiscovery] - Discovered device bai ...
2018-05-31 11:47:41.884 [INFO ] [.binding.ebus.internal.EBusDiscovery] - Discovered device vr81 ...
2018-05-31 11:48:49.175 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:48:49.180 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:48:51.749 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.datetime
2018-05-31 11:48:51.754 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 08 ...
2018-05-31 11:48:54.402 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:48:54.405 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:48:55.281 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:48:55.284 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:48:59.381 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:48:59.383 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:49:04.134 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:49:04.136 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:49:05.429 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:49:05.431 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:49:09.469 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:49:09.470 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:49:11.525 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]
2018-05-31 11:49:11.765 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]
2018-05-31 11:49:12.019 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 A0 07 04 00 2F]
2018-05-31 11:49:12.526 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command gen.bc_datetime
2018-05-31 11:49:12.528 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command gen.bc_datetime from 10 to FE ...
2018-05-31 11:49:12.532 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.datetime
2018-05-31 11:49:12.536 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) (15) with id ebus:vrc430:d43117b1:15 ...
2018-05-31 11:49:12.541 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Key datetime with value 31.05.2018 11:48:28
2018-05-31 11:49:13.789 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:49:13.791 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:49:16.719 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 03 64 B5 12 02 02 FE 98]
2018-05-31 11:49:19.637 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:49:19.657 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:49:21.577 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: 00 AA]
2018-05-31 11:49:22.297 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 03 64 B5 12 02 02 FE 98]
2018-05-31 11:49:22.434 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
2018-05-31 11:49:22.436 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
2018-05-31 11:49:23.520 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:49:23.522 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:49:23.951 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:49:23.954 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:49:27.460 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 03 64 B5 12 02 02 FE 98]
2018-05-31 11:49:29.834 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:49:29.837 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:49:32.295 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command gen.bc_temp_outside
2018-05-31 11:49:32.297 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command gen.bc_temp_outside from 10 to FE ...
2018-05-31 11:49:32.300 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.temp_outside
2018-05-31 11:49:32.303 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) (15) with id ebus:vrc430:d43117b1:15 ...
2018-05-31 11:49:32.305 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Key temp_outside with value 34.4375
2018-05-31 11:49:33.270 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:49:33.288 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:49:34.037 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:49:34.039 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:49:39.887 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:49:39.889 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:49:42.747 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
2018-05-31 11:49:42.750 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
2018-05-31 11:49:42.972 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:49:42.975 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:49:44.218 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:49:44.220 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:49:50.084 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:49:50.087 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:49:52.608 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.datetime
2018-05-31 11:49:52.612 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 08 ...
2018-05-31 11:49:54.383 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:49:54.387 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:00.245 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:00.247 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:50:02.407 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:50:02.411 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:50:04.533 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:50:04.536 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:10.361 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:11.043 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:50:12.129 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:50:12.131 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:50:12.404 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]
2018-05-31 11:50:12.660 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]
2018-05-31 11:50:12.900 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 35 07 04 00 A2]
2018-05-31 11:50:13.420 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command gen.bc_datetime
2018-05-31 11:50:13.423 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command gen.bc_datetime from 10 to FE ...
2018-05-31 11:50:13.426 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.datetime
2018-05-31 11:50:13.428 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) (15) with id ebus:vrc430:d43117b1:15 ...
2018-05-31 11:50:13.483 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Key datetime with value 31.05.2018 11:49:29
2018-05-31 11:50:14.665 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:50:17.674 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:18.535 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:18.537 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:50:20.548 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.datetime
2018-05-31 11:50:20.550 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 08 ...
2018-05-31 11:50:20.803 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
2018-05-31 11:50:20.806 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
2018-05-31 11:50:21.812 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:50:21.814 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:50:24.608 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:50:24.611 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:28.620 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:28.622 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:50:31.162 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command gen.bc_temp_outside
2018-05-31 11:50:31.164 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command gen.bc_temp_outside from 10 to FE ...
2018-05-31 11:50:31.167 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.temp_outside
2018-05-31 11:50:31.170 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) (15) with id ebus:vrc430:d43117b1:15 ...
2018-05-31 11:50:31.171 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Key temp_outside with value 34.4375
2018-05-31 11:50:31.514 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:50:31.516 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:50:34.727 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:50:34.730 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:38.772 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:38.774 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:50:41.234 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:50:41.236 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:50:41.617 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
2018-05-31 11:50:41.620 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
2018-05-31 11:50:44.911 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:50:44.913 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:48.971 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:48.974 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:50:51.544 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.datetime
2018-05-31 11:50:51.548 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 08 ...
2018-05-31 11:50:55.076 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:50:55.079 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:50:59.041 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:50:59.044 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:51:00.683 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:00.685 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:05.131 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:51:05.133 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:51:09.238 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:51:09.241 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:51:10.406 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:10.409 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:11.237 [INFO ] [.binding.ebus.internal.EBusDiscovery] - Discovered device vr81 ...
2018-05-31 11:51:11.246 [INFO ] [ervice.device.EBusDeviceTableService] - DATA TABLE UPDATE EBusDevice [masterAddress=0x70, slaveAddress=0x75, lastActivity=1527760271231, manufacturer=-75(Joh. Vaillant GmbH & Co.), deviceId=56 38 31 30 30, softwareVersion=2.02, hardwareVersion=25.02]
2018-05-31 11:51:11.247 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 75 with command common.identification
2018-05-31 11:51:11.249 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.identification from 10 to 75 ...
2018-05-31 11:51:11.251 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 75 with command controller.identification
2018-05-31 11:51:11.252 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command controller.identification from 10 to 75 ...
2018-05-31 11:51:11.254 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 75 with command pmw.identification
2018-05-31 11:51:11.256 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command pmw.identification from 10 to 75 ...
2018-05-31 11:51:11.728 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command gen.bc_datetime
2018-05-31 11:51:11.729 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command gen.bc_datetime from 10 to FE ...
2018-05-31 11:51:11.732 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.datetime
2018-05-31 11:51:11.733 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) (15) with id ebus:vrc430:d43117b1:15 ...
2018-05-31 11:51:11.735 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Key datetime with value 31.05.2018 11:50:28
2018-05-31 11:51:19.420 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:51:19.422 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:51:20.124 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:20.140 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:21.418 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.datetime
2018-05-31 11:51:21.420 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 08 ...
2018-05-31 11:51:21.689 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
2018-05-31 11:51:21.692 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
2018-05-31 11:51:25.510 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:51:25.512 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:51:29.523 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:51:29.525 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:51:29.826 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:29.829 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:32.116 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command gen.bc_temp_outside
2018-05-31 11:51:32.120 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command gen.bc_temp_outside from 10 to FE ...
2018-05-31 11:51:32.124 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.bc.temp_outside
2018-05-31 11:51:32.128 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Handle received command by thing Vaillant VRC 430(f)/470(f) (15) with id ebus:vrc430:d43117b1:15 ...
2018-05-31 11:51:32.131 [DEBUG] [hab.binding.ebus.handler.EBusHandler] - Key temp_outside with value 34.25
2018-05-31 11:51:33.818 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:51:33.820 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:51:39.514 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:39.518 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:39.705 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:51:39.708 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:51:42.437 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
2018-05-31 11:51:42.440 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
2018-05-31 11:51:44.019 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:51:44.023 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:51:49.232 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:49.235 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:49.854 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:51:49.858 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
2018-05-31 11:51:52.380 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.datetime
2018-05-31 11:51:52.950 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.datetime from 10 to 08 ...
2018-05-31 11:51:54.093 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.setopdata
2018-05-31 11:51:54.097 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.setopdata from 10 to 08 ...
2018-05-31 11:51:58.965 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 70 to 08 with command boiler.control.getopdata
2018-05-31 11:51:58.968 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 70 to 08 ...
2018-05-31 11:51:59.957 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
2018-05-31 11:51:59.960 [DEBUG] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...


(Roland Hartmann) #414

Hi Witek,
ebus 2.0 seems not to be ready for OH 2.3 even not Alpha 19. For me it helps to donwgerade to OH 2.2 (apt-get install openhab2=2.2.0-1).
I had contact with @csowada - he will have time to have a look earliest in 3 weeks.
Hope it is helpful for you.
Maybe also a symtom: Latest after reboot no of the items is going to status online. Only eBus Bridge.


(csowada) #415

But Alpha18 running fine in oh2.2 ? I habe issue with Alpha18. The difference to Alpha 19 is not that big. Someone tried Alpha 19 in oh 2.2?


(Roland Hartmann) #416

I have Alpha 18 running on OH 2.2 without issues.
On detail used: org.openhab.binding.ebus-2.3.0-070518 / ebus-core-0.9.18-070518 / ebus-configuration-0.9.18-070518
… I had a view on the versions. I thougt before I had Alpha-19. But it seems I have Alpha-18 what is running…

Have upgraded to OH 2.3 again with realy ebus Alpha 19. Now no errors are comming, eBus components are going online. Only what I have found poll seems not to work. Only values are set, where no poll is needed. Also in DEBUG I do not see them. But this seems to be a smaller issue…

What I have find out in addition: poll is not working, if link item is set.
What do help as workaround: unset link item, set poll every x seconds, wait a minute and set link item again.


(Cernon) #417

For me it Works Fine with alpha19 and oh 2.3. But i have to change the items. The Bridge-ID changed and the item-String changed for „bridge-ID:Slave-Adresse“ to only Bridge-ID. After edit it Manuel it works.


(csowada) #418

MH, sounds not correct. I have to check this after holiday. I think it is only a small change to the code to work again.


(Witek) #419

@Roland62, @Cernon, @csowada, thanks for your comments, I came back from long weekend now and didn’t touch it since initial try.
Regarding items changes - I know ID of bridge changed so I not only recreated it but also items (and also to make sure there is proper routing, I removed manually from json files configuration which assigns items to channels which normally keeps all config from the past).
I’m fine to wait couple of weeks for code fix from @csowada (given how stable and mature were previous version already, I guess it is something minor here).
I don’t want to downgrade OH yet as it fixed one major logging problem for me unless waiting would be truly long till next version.


(Rolf) #420

Dear Csowada

After some further testing and trying to interpret telegrams I guess I have to get ready for a custom parser. However I have not much of an idea how to program that. One example of telegram I would like to get implemented: It is a master/slave construct: When I send

 smarthome:ebus send "FF 08 50 22 03 78 82 30 D3"

which is a request to WPM-1 (SA 08) to send the temperature of the boiler I get (in log:tail)

Successful send: FF 08 50 22 03 78 82 30 D3 00 02 DF 00 33 00

In the Slave part Temperature of DF 00 (low byte first) is received, which has to be scaled by 0.1 and results in 22.3 degree Celsius.

Question now: How can that be implemented with a custom parser?

I would be very thankful for some hints.

Best regard Rolf


(csowada) #421

Hello All,
I’m back from holiday tomorrow. So I can help at the end of this week. I will update my productive system to 2.3 first, to check a new alpha release.


(Roland Hartmann) #422

Hope you had have a good relaxation - and wellcome back :wink: