Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build #4410: Bindings whose Jars are in /addons folder not shown in manual Add Things screen #4494

Open
andrewfg opened this issue Dec 12, 2024 · 5 comments
Labels
bug An unexpected problem or unintended behavior of the Core

Comments

@andrewfg
Copy link
Contributor

When you drop a binding Jar in the /addons folder, the binding does install. And the binding does find respective things via background discovery. HOWEVER the respective bindings do NOT show up in the manual Add Things screen.

OH Snapshot Build #4410

Two bindings in `/addons' folder

image

The bindings DO find Things via background discovery

image

The bindings are NOT available for adding Things via manual discovery

image

@andrewfg andrewfg added the bug An unexpected problem or unintended behavior of the Core label Dec 12, 2024
@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/openhab-4-3-milestone-discussion/158139/101

@holgerfriedrich
Copy link
Member

Hm, for KNX, it seems to work.
Snapshot 4411 on RPI5(64).
Started w/o knx addon. Dropped the jar. Binding gets installed. Under Addon-Store, there is still the suggestion for knx binding from the distro. But it is listed under "Installed Bindings".
When I select "Addon-Store, Bindings", it is listed under "Other Add-ons", see
grafik
Things can be added manually (at least is shows like this, did not test):
grafik
bundle:list only shows my jar version of the addon.

@andrewfg
Copy link
Contributor Author

In my case it seems that the bindings did finally appear on the add manually screen after some time (30 or more minutes). Maybe there is an overlap between the OH server's cache-control expire time and the time when the addon is dropped in the folder? Or something like that. Such Jar drops ought to force an immediate browser cache expire IMHO.

@morph166955
Copy link

My govee ended up finally showing up. Days later. After multiple OH restarts. Not sure why. To note, the other 4 addons I have as jars seem to work without issue.

@andrewfg
Copy link
Contributor Author

.. ended up finally showing up. Days later.
Not sure why

Indeed. A mystery.

{ PS the Govee now does auto discovery so you don't really need the add manually scan anymore.. }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of the Core
Projects
None yet
Development

No branches or pull requests

4 participants