You just list the bindings by name in services/addons.cfg. Here is my current one:
# The base installation package of this openHAB instance (default is "standard")
# Valid options:
# - minimal : Installation only with dashboard, but no UIs or other addons
# - standard : Typical installation with all standards UIs
# - demo : A demo setup which includes UIs, a few bindings, config files etc.
#
#package = standard
# Access Remote Add-on Repositories
# Defines whether the remote openHAB add-on repository should be used for browsing and installing add-ons.
# This not only makes latest snapshots of add-ons available, it is also required for the installation of
# any legacy 1.x add-on and all experimental features. (default is false for offline distro, true for online distro)
#
remote = true
# Include legacy 1.x bindings. If set to true, it also allows the installation of 1.x bindings for which there is
# already a 2.x version available (requires remote repo access, see above). (default is false)
#
legacy = true
# Include experimental add-ons. If set to true, it also allows the installation of extensions that are not (yet) part
# of the official distribution and need further testing (requires remote repo access, see above). (default is false)
#
experimental = true
# A comma-separated list of bindings to install (e.g. "sonos,knx,zwave")
binding = zwave,astro1,http,mqtt,nest,networkhealth
# A comma-separated list of UIs to install (e.g. "basic,paper")
ui = paper,classic,habmin,habpanel
# A comma-separated list of persistence services to install (e.g. "rrd4j,jpa")
persistence = influxdb,rrd4j,mapdb
# A comma-separated list of actions to install (e.g. "mail,pushover")
action = nma,mail
# A comma-separated list of transformation services to install (e.g. "map,jsonpath")
transformation = xslt,map,regex,javascript
# A comma-separated list of voice services to install (e.g. "marytts,freetts")
voice =
# A comma-separated list of miscellaneous services to install (e.g. "myopenhab")
misc = myopenhab
An add-on is an extension to openHAB. A binding is one such type of add-on among others (UIs, transformations, actions, voice, persistence, etc). Services is just the name of the folder where the .cfg file for each add-on that needs it goes.
It isn’t lost on a reboot but it is lost when you upgrade openHAB 2 to a new version.
You don’t have to reboot. As soon as it is added to addsons.cfg and the file is saved OH will see the change and immediately install the add-on.
For 1.9 add-ons, look at the Configuration section of the binding’s wiki page. If an example .cfg file was not created for the binding create one using the name of the binding. Populate it with the parameters defined on the wiki page but omit the name. For example, the wiki page for Nest says there should be, among others, a nest:refresh=6000 property. So you would create a services/nest.cfg file (if one isn’t created for you) and populate it with all the parameters minus their name (i.e. nest:refresh=6000 becomes refresh=6000).
To test the 1.9 binding that isn’t listed follow the instructions I linked to above and see if the binding works as described. If it does what it is supposed to to then it works. If you get errors in the logs, particularly errors about missing classes, it may not work. Report this results either way.
) to the .cfg, if the add-on is installed via Paper UI and is only active for the actual instance and lost somehow after reboot… Most add-ons don’t come with example cfgs, but I’ll try your hint with the addons.cfg, I’ll list them there and look whats happening after a reboot.
)