openhab-core
openhab-core copied to clipboard
openhab
Build #4410: Bindings whose Jars are in /addons folder not shown in manual Add Things screen
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
The bindings DO find Things via background discovery
The bindings are NOT available for adding Things via manual discovery
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
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
Things can be added manually (at least is shows like this, did not test):
bundle:list only shows my jar version of the addon.
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.
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.
.. 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.. }
Also works for me with the matter binding in 4.3 milestone 5:
But to be honest, I remember one time it did not appear and I was surprised.
This has annoyed me as well. One thing I noticed is that if I click another binding and manually change the binding id in the URL, it works. So it seems the issue is only about binding missing in the list. Maybe there is some cache not being updated?
Maybe there is some cache not being updated?
Yes that is also my hypothesis. However I did try clearing the browser cache, both using Chrome and Edge, so my guess is that it is not a client side cache issue..
This issue has been mentioned on openHAB Community. There might be relevant details there:
https://community.openhab.org/t/esphome-binding-for-the-native-api/146849/345