Thanks! for me, completely sufficient solution 
Hi @csowada,
I tried the latest version 2.50.10 with the latency setting, but it does not work. I think, I have to test it with a clean setup or do you have any other idea or hint?
Hi,
Just upgraded to OH 3 (docker image tag milestone-debian) and in general, it works!
However, in OH 2.5 in PaperUI, there was a configuration option for:
configurationUrl="file:///openhab/conf/bindings/ebus-controller.json"
configurationUrl1="file:///openhab/conf/bindings/ebus-protherm.json"
Is it possible to use own JSON for my devices in OH 3.0? I tried to edit the code in MainUI for ebus bridge thing, but the keys Url and Url1 do not seem to be allowed.
@Derka If you go to things and press the + to do a scan. Against the ebus binding there is a settings cog & pressing that lets you edit the configuration urlās.
@jpharvey Thanks, that worked!
By the way, I still have a few āNo handler has accepted the commandā¦ā. Is there a way how to show the full raw telegrams within openHAB logs? I tried both
openhab> log:set TRACE org.openhab.binding.ebus
openhab> log:set TRACE de.csdev.ebus
but that did not help. Or do I have to use the ebusd outside of OpenHAB?
EDIT: Ok, forget it. I have found the āAdvanced loggingā hidden under the Advanced settings of eBUS bridge thing.
Hi all,
just as a side information: I just stumbled by chance about a new version 3 of the eBUS adapter, created by some cool guys at the FHEM forum. Newest version, allowing a plethora of connectivy possibilities: direct on RasPi via GPIO, USB, WiFi and now even Ethernet!
Ordering has openend yesterday. Details here:
Documentation:
P.S.: This is not a hidden advertising, I am just a happy user of the previous version. It runs since years with my OpenHabian installation without a single problem. IMHO there is no cheaper way for an eBUS connection.
eBUS binding 3.0.10: it seems that āpollingā must be set individually for each channel of the thing (eBUS device) instead of only in the thingās config itself.
I.e. the option in // Administration // Settings // Things // eBUS Bridge // Some eBUS device // Configuration (show advanced): Polling all chanells (Set to poll all getter channels every n seconds.) is ignored.
I also tried to unlink all channels together with removal of items, to remove the thing and add it again, but to no avail.
@Derka I have it working but when i first tried it i the binding was crashing when trying to access the configuration. It started working later and i have no idea why. So i started adding individual polling but got fed up. Unlink & removed all the items and started again 1 at a time to get the ones i want and somewhere it started working.
Have you checked the log for any exceptions from the ebus binding when you try to set it?
Indeed, there are some parser errors in the logs. I will try again over weekend to find out which actions causes that.
I tried to use eBUS 3.0.10 on opnHAB 3, was able to install and have now eBus bridge in my system, but how to create items?
@wseifert When you select the Ebus Bridge thing in the settings then there are 3 tabs across the top.āThingā, āChannelsā, āCodeā.
If you click on Channels it lists all of them and you can create/link to each to an item individually or select āAdd Points to modeā which will also create the ones you choose and add them to the semantic model.
Found why I did not see any axpected items in Channels: I missed to add eBus Standard. Now I see all expected items there. But I wonder which eBUS master & slave addresses to use to see values read from eBUS, at the moment I do not see any value ā¦
Is the auto discovery not working? Usually you should see several things in your inbox. If you have a valid bridge configured.
No, auto discovery did not work. Bridge is valid, status was immediately after creating and configuring āONLINEā but no things in inbox.
The next issue I have is that no data are received from ebus although eBUS standard channels are linked. I tried multiple csv files in /etc/ebusd for my Ochsner OTE, can see some (not all) decided eBUS data in ebus.log.
Any hint?
I am a little bit irritated: eBUS Bridge reports āONLINEā although ebusd service is stopped so no connection should be possible. Why?
I have removed eBUS things (standard, bridge) and re-created bridge. After saving the bridge configuration error found in events.log:
==> /var/log/openhab/openhab.log <==
2021-01-13 19:57:48.317 [ERROR] [dev.ebus.core.EBusLowLevelController] - error!
java.lang.InterruptedException: null
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2109) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1454) ~[?:?]
at de.csdev.ebus.core.EBusControllerBase.shutdownThreadPool(EBusControllerBase.java:262) ~[bundleFile:?]
at de.csdev.ebus.core.EBusControllerBase.dispose(EBusControllerBase.java:292) ~[bundleFile:?]
at de.csdev.ebus.core.EBusLowLevelController.dispose(EBusLowLevelController.java:462) ~[bundleFile:?]
at de.csdev.ebus.core.EBusLowLevelController.run(EBusLowLevelController.java:245) [bundleFile:?]
OK, I found the reason why no auto discovery: I did not know that the network driver had to be set do ebusd, I left this on raw. After changing to ebusd four ebus Standard items were present in Inbox. I selected the eBUS Standard (15), ebusctl i listed address 15: as slave.
But the only data I can see are from the 5 eBUS bridge channels and 2 eBUS Standard channels (Date/Time of an eBUS Master).
ebusd.log shows more decoded data:
2021-01-14 20:23:26.332 [network debug] [00007] wait for result
2021-01-14 20:23:26.334 [main debug] performing regular tasks
2021-01-14 20:23:26.493 [update info] received MS cmd: 011506210402b50040 / 0a35810000ff0000000000
2021-01-14 20:23:26.496 [update notice] received read heatpump mode QQ=01: 53;1;00;00;255;0;Abgeschaltet
2021-01-14 20:23:27.603 [update info] received MS cmd: 011506210400e00040 / 0a60800d02e80300006901
2021-01-14 20:23:27.605 [update notice] received read temperature buffer QQ=01: 96;0;0d;02;1000;0;36.1
2021-01-14 20:23:28.339 [network debug] [00007] wait for result
2021-01-14 20:23:28.712 [update info] received MS cmd: 011506210400840040 / 0a04800d02e80300004e02
2021-01-14 20:23:28.714 [update notice] received read temperature water QQ=01: 4;0;0d;02;1000;0;59.0
2021-01-14 20:23:29.821 [update info] received MS cmd: 011506210400800040 / 0a00800d02f4010cfe0500
2021-01-14 20:23:29.824 [update notice] received read temperature outside QQ=01: 0;0;0d;02;500;-500;0.5
2021-01-14 20:23:30.343 [network debug] [00007] wait for result
2021-01-14 20:23:30.345 [update info] received MM cmd: 031005030a010000004421ff3f0000
2021-01-14 20:23:30.347 [update notice] received unknown MM cmd: 031005030a010000004421ff3f0000
2021-01-14 20:23:30.916 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-01-14 20:23:30.953 [update info] received MM cmd: 1003050a00
2021-01-14 20:23:30.955 [update notice] received unknown MM cmd: 1003050a00
2021-01-14 20:23:31.058 [update info] received MS cmd: 011506210402c80040 / 0a4841042a9f0500002605
2021-01-14 20:23:31.060 [update notice] received unknown MS cmd: 011506210402c80040 / 0a4841042a9f0500002605
2021-01-14 20:23:31.583 [update info] received MM cmd: 1013050a00
2021-01-14 20:23:31.584 [update notice] received unknown MM cmd: 1013050a00
2021-01-14 20:23:32.151 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-01-14 20:23:32.230 [update info] received BC cmd: 10fe0801081924008000001924
2021-01-14 20:23:32.232 [update notice] received update-read master data1 QQ=10: 36.098;-;0;0;0;0;0;0;0;36.098
2021-01-14 20:23:32.322 [update info] received MS cmd: 011506210402c60040 / 0a46410428ffff0000b1ac
2021-01-14 20:23:32.324 [update notice] received unknown MS cmd: 011506210402c60040 / 0a46410428ffff0000b1ac
2021-01-14 20:23:32.347 [network debug] [00007] wait for resultWhat is the reason why this data are not visible in openHAB?
Werner
The Esera USB eBus coupler is showing me the main information for my Vaillant VRC700 thermostat, but I cannot figure out how to get the individual room readings from the AmbiSense system with VR 50 and VR 51 components. The eBus log shows a lot of unresolved data so I guess the room settings etc. are being sent over the bus but just not resolved. It would be really nice to get some more information and control than the Multimatic App gives for the AmbiSense system.
@csowada Just one question: Is it normal, that the binding in OH3 (after copying the kar file into addons-folder) is not shown in MainUI->Configuration->Bindings?
Why I ask: Where/how should i configure the bundleFileUrl??
BR,
MW
Another question regarding ebus Binding 3.0.10 with OH3:
Does anybody also see a very high number of errors in the log when using this ebus binding? Binding is working quite normal (as far as I can see), but there are a lot of errors like (and many more):
bundle org.openhab.core.model.item:3.0.0.202012201729 (256)[org.openhab.core.model.item.internal.GenericItemProvider(307)] : Error during instantiation of the implementation object - java.lang.IllegalArgumentException: argument type mismatchbundle org.openhab.core.model.thing:3.0.0.202012201733 (266)[org.openhab.core.model.thing.internal.GenericThingProvider(310)] : The activate method has thrown an exceptionbundle org.openhab.core.karaf:3.0.0.202012201715 (255)[org.openhab.core.karafaddons(340)] : Error during instantiation of the implementation object
Also, the API Explorer is not useable (generates an error message in the logs).
openhab_ebus_Erststart.log (923.4 KB)
openhab_ebus_Restart.log (493.9 KB)
openhab_noebus_Erststart.log (2.5 KB)
openhab_noebus_Restart.log (2.5 KB)
Details to my environment:
Fresh installed OH3 via Docker image with 3.1.0-SNAPSHOT (Build #2160)
ebus 3.0.10 kar-file
What could I do to get rid of this?
Thanks,
MW
Mh, looks like a general openhab cache issue !? Iāve tested the binding with 3.0.0 release on windows and linux docker. But you use a SNAPSHOT release, maybe it is currently broken. Please test with the latest openhab release, I canāt help with snapshot releases of openhab.