Balboa based Whirlpools: old jar won't load into list of extensions

Add-ons Bindings
1

I’m running vanilla OH5.1.4 on docker.

As I tried to refactor my installation I just dropped the org.openhab.binding.balboa-3.2.0-SNAPSHOT.jar from that Balboa Binding thread into the AddOns folder, but the binding won’t show up in “Add-On Store” overview of installed bindings. And also not, if I try to install the thing via Web-UI.

Nevertheless I can drop a things-file into the conf/things folder and it will show up and work. is there any way to configure OH5, so that this “old” jar works with Web-UI?

the console shows:

openhab> bundle:list | grep -i balboa
342 │ Active │  80 │ 3.2.0.202108270027    │ openHAB Add-ons :: Bundles :: Balboa Binding
openhab> openhab:addons list | grep balboa
2

The short answer is no. Any add-on “installed” by dropping a jar fil into the addons folder will not show up in MainUI like other add-ons do.

I’m very surprised that an add-on this old works at all. There have been two Java versions and untold API changes made since OH 3.2. Keep an eye on future updates as any one of them is likely to break this binding.

3

hmm… I also have org.openhab.binding.amazonechocontrol-5.0.3-SNAPSHOT.jar and org.openhab.binding.mideaac-5.0.3-SNAPSHOT.jar, which both appear in the “Add-On Store” as installed bindings and I do have both to chose from while adding a thing…?

I will do…, but I think ‘clinophobic’ (the one who ported the binding last time) isn’t actively around here anymore.

4

The something must have changed. But it changed after OH 3.2.