The question is: Why is the bundle in “Installed” state. This could be the cause of the issues. Can you do diag 246 on the console?
As I was testing the new release I have uninstalled this kar few days ago and replaced a few times with newer versions. Can’t easily go back to check.
^
Can you please tell us what you have in Main UI | Settings | Add-on Management | Include (Potentially) Incompatible Add-ons … and if enabling/disabling the setting causes any improvement?
It was disabled in my case.
Same for me. Upgraded from 4.1.0 to 4.1.1 and then restored a backup from 4.1.0 as no binding installed and all my things were offline. After restore (downgrade) all my things are online but now I cannot add a new thing as my bindings are not listed on UI.
Is there a known working method (workaround) till this is fixed? 4 times cache clear and restart works? Should I go this way? I’m on docker controller. Do I need to stay at 4.1.0 or upgrade to 4.1.1?
Some have reported problems with (old) custom bindings (jar’s dropped in the addons folder) , check if you have any of them. I ended up reinstalling it all 
Is this problem fixed?
I have same issue. All my bindings works … but i miss all installed bindings in ui.
Had the same problem. In my case the log showed an exception pointing to an old binding.
I deleted the old .jar and restarted openHAB. Now everything seems fine.
2024-05-23 10:08:48.996 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/openhab/addons/org.openhab.binding.broadlink-3.2.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.broadlink [27]
Unresolved requirement: Import-Package: org.openhab.core
at org.eclipse.osgi.container.Module.start(Module.java:463) ~[org.eclipse.osgi-3.18.0.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:445) ~[org.eclipse.osgi-3.18.0.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.7.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.7.4]