It also seems not to be possible to install new bindings. Just tried it again, after I had fully rebooted my machine to fix that already installed Bindings are shown as not installed, it won’t install a new binding … or at least doesn’t show it as installed.
The installed field is not part of AddonInfo, so cannot be the reason.
1 Like
Have checked how it is working in my environment. All add-ons, which I had installed via the store are shown correctly. One exception - I have installed my eBus addon via placing the kar-file in the openhab-addons folder. The eBus addon is shown in the store as not installed.
Could it be, that the add-ons which are named here are even not installed via the store?
Exactly the other way on my side… All installed from the marked will not shown. And installed via jar file are be shown as installed in the market. And one more this one they are installed from SmarthomeJ, are shown as installed either.
It uses a version range that states it doesn’t work with OH 4:
Which ones specifically?
That is the reason, why I am not using the version of the store. Currently I have running eBus 4.0.19. It is perfectly running with OH 4.1.0.
For me it makes sense, that it is not listed as installed in the overview of the store. Cause I have running another version.
SmartHomeJ/ Alexa Binding is installed and show as installed.
Following are installed and shown as not installed:
MQTT , iCalender, AVM, tankekönig, denonmaranz, network, wled, networking… and so on. Transformations like Regex or JSONPath and other things like InfluxDB… all of them show install button. If i go via things to try to add new things nothing of them will show.
I’cant install new devices at the moment, but I have new one to add… That isn’t pretty cool.
BTW: Blink and ConnectedCar were installed before I remove them, cause for new updates and they were present in add-ons as installed.
For me everything is missing…
Did you already try to clear the cache?
Yes sir I do. After an update like this to 4.1.0 I clear cache always. Openhab-CLI clean cache cmd was executed.
Does it work better if you only install the official “openHAB Distribution” add-ons?
It could be third-party add-ons confuse your installation somehow.
Looks good now! Thanks for your support.
I remove all third party add-ons, stop openhab, clean-cache and restart openhab. Now all bindings are back!
To dive a little bit deeper into this issue: SmartHomeJ didn’t update automatically. You must uninstall and install manual to get the new version. Maybe the old version can interrupt openhab?! Dunno, but now it’s working.
@lfs_alp5 can you fix this also in this kind of way and confirm that openhab is working again?
1 Like
I just tried with the amazonechocontrol binding you had installed (SmartHome/J 4.0.x) on a 4.2.0-SNAPSHOT and it does not cause any issues.
I had made the update from 4.1.0-M3. There were no issues before and it start after update to 4.1.0 stable. Thereafter I cleared cash but nothing was OK. I removed two jar Bindings manually installed. Cleared cache nothing happens. After remove Amazon Binding clear cache and then all Bindings are shown as installed. Thereafter I installed Amazon Binding again and everything was fine… So dunno…
But there some guys more in this thread with this issue. Would be great to hear their findings.
Did you all have bindings in the addons folder? As .jar or as .kar? If still available, do you have the exact files?
First question confuses me a little bit. I had only two bindings in this folder. Blink and ConnectedCar. I delete both and there is no backup. Openhab backup script ignore the folder and my personal weekly backup doesn’t contain the files any more. So i can only say no… Sorry for that. And at this point, I forgotten to add them. At the moment there is only one standard file openhab addons 4.1.0.
I reinstalled OH to resolve this since I never figured out the problem. I don’t think I have any 3rd party addons installed (atleast for the time being) but will check if I do install one.
(Sorry for slow reply, haven’t had much time to look at this, just needed to get it working again asap).
1 Like
I had same issue.
The problem was I had old version of 3rd party binding installed. Tuya Binding
I uninstalled the binding thru karaf and removed the cache.
Everything works fine after restart.
1 Like
I doubt that is the issue. I have a test instance that shows the same behavior and has only distribution add-ons installed. It is more likely related to timing during start-up.