Thats really interesting. I have now checked my addon.cfg and recognized that also with an update to #1088 this file is empty. Everything is commented out.
Maybe thats the point where all of those issues coming from?
I don’t know if this is helping, but I just checked my /var/lib/openhab2/etc/org.openhab.addons.cfg and it looks exactly like @houz one, I’ve also got the B"true". I’m running build 1073 (didn’t dare upgrading last few days because of the known problems) and everything is working like a charm here.
@benjy, you work a lot with the upgrade scripts and such, do you have any ideas? To summarize, people are upgrading to recent builds and their addons.cfg are becoming corrupted. See Daniel’s posting for an example.
For how long have they been untouched? I mean, this might very well have been in my config for a while, I seldom check the contents of that file. And everything seems to work fine anyway until OH is upgrading to 1083+.
In the meantime i made a reinstallation of OH2 and restored the backup (without tmp and cache). Now it works like a charm and better than ever bevor. The /opt/openhab2/userdata/etc/org.openhab.addons.cfg file is now “clean”, without “B” and and quotiation marks. I don’t know what the problem was, but it doesn’t matter. Best OH2 till now.
It is definitely not related to the upgrade scripts. My assumption is that this is due to an changed behavior of Felix FileInstall which has been updated to a more recent version in Karaf 4.1.3.
FileInstall writes such files as well, if configs are edited through Config Admin (e.g. by the Paper UI).
I’ll try to figure out what causes the file to be written by FileInstall here in the first place and also what goes wrong when parsing such a file. I have entered an issue for it.
yes. Bevor reinstalling OH i’ve modified the /opt/openhab2/userdata/etc/org.openhab.addons.cfg, since it was also wrong formatted as described here in this thread. Unfortunately i’ve not checked, how the file looks like directly after unpacking the new version.