I haven’t read thru the issue on git but it may help to delete /var/lib/openhab2/config/org/openhab/addons.config so it is regenerated with correct content. Please note that by deleting this file you will have to reinstall all your binding again (b/c they were installed via PaperUI). FYI If you have them installed in the addons.cfg file then after a restart OH will automatically reinstall the listed bindings.
I had the same problems after OH2 build #1518 upgrade - no addons and scheduler errors on startup. I’ve stopped OH2, removed /var/lib/openhab2/config/org/openhab/addons.config and upgraded OH2 (yesterday #1521) with no issues and additional commands.
Firstly this is my first post so I would like to say thank you to all that contribute, it has helped me immensely. I have been playing around as a noob for some time now, I have a very limited coding background and wanted to put something here as someone starting out might trip up where I did.
This all started when I updated my network adaptor (/etc/network/interfaces) and failed to add dns-nameservers. The Pi was fine on my network internally but obviously was powerless when trying to discover the outside world, page 1 mistake on my part for not checking this 1st when noticing my cloud service had gone wonky. Anyway before I discovered this I had managed to break everything else and couldn’t install any releases. Once I fixed the DNS I could roll version and restore a backup.
If using ZRAM, RTFM! I didn’t and it cost me a day. When rolling back/upgrading/cleaning the cache on ZRAM.
My file system was forced to Read-Only in the end “EXT4-fs error (device zram1): ext4_journal_check_start:61: Detected aborted journal” but you can still follow these steps to recover.
stop openHAB2: sudo systemctl stop openhab2
clear the cache from ZRAM: sudo rm -rf /var/lib/openhab2/tmp/* /var/lib/openhab2/tmp/.??* /var/lib/openhab2/cache/*
stop ZRAM to make it sync to disk (notably the Karaf-generated files in /var/lib/openhab2/cache and …/tmp): sudo systemctl stop zram-config
upgrade OH. Don’t reboot (remember automatic startup of ZRAM and OH at boot time). The upgrade process clears the cache so you don’t need step 5. Then again, to double check does not hurt.
clear the cache from disk: `sudo rm -rf /var/lib/openhab2/tmp/* /var/lib/openhab2/tmp/.??* /var/lib/openhab2/cache/*.
I also had this read-only filesystem error and failures from core.karaf saying it wouldn’t install bindings and Paper UI wouldn’t start, etc…all kinds of problems. Was going to revert to backup but turns out the overall OS update I did via openhab-config turned ZRAM OFF. Simple fix to turn it back on and reboot but damn, took me a few hours to play around until i realized in the release notes ZRAM is OPTIONAL by default.
Version I use
I use Openhab 2.5.12.-1 and all was working perfectly but now my error log is full of
Error I have
[ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-snmp1, openhab-action-mqtt, openhab-binding-mqtt1’
And MQTT binding is not working any longer…
=> I still see on the Panel that my mqtt-devices are turned on/off but no MQTT message is sent out
Also homematic binding is not working
What I tried
restart OH2 5x
deleded addon.cfg as proposed somewhere…
restart raspi pi4 several times
red everywhere , saw that I need to add in addons openhab-addons-2.5.12.kar
changed ownership to openhab, gave rw access to all and even execution access
went to the homepage and ```
wget -qO - ‘https://openhab.jfrog.io/artifactory/api/gpg/key/public’ | sudo apt-key add -
`` Please HELP
I do not want to go to version 3 as I need and want mqtt binding 1.1. The hole installation became useless as no mqtt comands are sent out. It seems that the addons are no longer available for download? But why?
What is remote = set to in addons.cfg in /etc/openhab2/services/ is it set to false resp. put into a comment ? As far as I can see version 1 bindings are not included in the openhab-addons-2.5.12.kar file.