If you use the addons.cfg then it precedes what you have installed in PaperUI and on the next restart it will ONLY load the add-ons specified in addons.cfg and your paperUI loaded ones will disappear.
If you want yo use addons.cfg put ALL the bindings you are currently using
eg.:
# A comma-separated list of bindings to install (e.g. "binding = sonos,knx,zwave")
binding = http1,exec,nest,network,caldav-command1,mqtt1,astro,expire1,systeminfo,samsungtv,openweathermap,mqtt,gpstracker,groheondus
If I install a binding by paperUI (for testing) then it will not survive a restart. If it works well, I add it to the addons.cfg BEFORE restarting.
with everything what I have learned, since, I do think that the documentation should the name to be used in the addons.cfg .
Now it’s assumed to use paperUI to figure out the name, yet it’s bad to combine them.
Sounds very confusing to first time users.
jwiseman
(Mr. Wiseman (OH 4.2 Snapshot on Pi4))
45
Hi yves,
Here’s my addons.cfg line for the Synology for OH 2.3.
I don’t have/use the bosesoundtouch binding BUT I put it in there for some reason many months ago because certain bindings I needed loaded kept going away after I rebooted also.
It may have been the HTTP1 or SERIAL1 binding since it’s between them.
On top of that entry list; I have the following additional bindings manually put ADDON’s folder.