Installation of openHAB2 (v2.5.5) as a prototype component within EATSv5.2020 is a follow-on to a trial implementation of openHAB 2.4 which was accomplished in 2017-18.
openHAB is implemented locally on a home intranet as a home automation controller. In order to access the local controller from outside the home openHAB maintains and operates the openHAB Cloud Service as a gateway facility to provide an internet interaction network facility for the local server.
- Selection of an administrative user interface. Home Builder is one option, but is insufficient to the task. It is useful for setting up the relationship between devices to be managed and their contextual placement in the home or office, but it is not as functional for elements which constitute the infrastructure of the automation system. Paper UI is recommended.
Automation with openHAB uses a number of key concepts.
Configuration revolves around Things. When you wish to add a new element to the system, you always start by defining a Thing. Once a Thing has been defined and configured, you are done setting up the connection to the physical layer. From then on, everything else is configured at the application layer for that entity. From start to finish, the process for fully configuring a physical entity represented by a Thing looks like this:
- Identify the binding required for the Thing
- Install the binding if it has not already been installed
- Define and configure the Thing
- Identify the Channels provided by the Thing
- Add Items and link them to the Thing’s Channels
- At this point Items can be used to control the Thing or consume its information in e.g. Sitemaps or Rules
There are two methods for defining Things provided by the various bindings: through discovery or by manual definition in configuration text files.
Some elements are only capable of definition via discovery; and some things can not be discovered and therefore must be manually configured via the text files. Things defined through discovery are not reflected in the configuration text files, rather they are defined in undocumented internal files. If things of both types are required for the configuration of a site, there is currently no full description of the site configuration available for ease of administration other than the operational site.
- 148Avenida Configuration
- Security Configuration