With this binding, heating and ventilation systems that have an eBUS can be addressed. The corresponding hardware is required. Connections are possible via serial, TCP and ebusd.
or just check GitHub Releases for the latest or older versions.
or just check GitHub Releases for the latest or older versions.
Thanks, I replaced the old binding with the new version and so far it looks good.
Have upgraded to OH 5.0.3 today and your binding remains being my favorite. It works out really great and provides me full insight into my Vaillant aroTherm plus (overall >80 eBUS parameters). Many thanks for all your work. And have a nice Advent time.
In the meantime i have upgraded to 5.1.0 and 5.2.0-SNAPSHOT #5090. An issue is that the eBUS binding from the OH marketplace is deinstalled automatically during each upgrade procedure.
Normally not a problem if the marketplace is available for reinstallation of the binding. But there is a bug, present since many weeks, where the marketplace disappears temporarily. Then it only helps to wait until it is back by accident.
Also tested the .kar file within the addon folder. This works for eBUS but the MainUI actually only handles .jar files properly but not .kar files. A .kar installation is not shown in MainUI as installed and the custom file setup screen is missing then. The actual eBUS .jar doesn’t work out due to missing dependecies.
It would be nice to have the binding being part of the OH core to overcome these issues.
I have the same problem with the automatic uninstallation;
I already observed this problem in version 4.
Yes, the availability issue of the marketplace is pretty old. I also have seen posts which describe the root cause but the maintainers don’t get it solved.