openHAB
I do not understand why coverage on e.g. opensource.com, fastcompany.com is not considered notable. Likewise, having a press release from Canonical/Ubuntu about openHAB seems to speak for its relevance. Also note that heise.de is the biggest and renowned IT news portal in Germany and has published multiple articles about openHAB.
I strongly disagree with the objections that are being made here. There is enough relevance for openHab as a lemma considering the widespread use and large user community. Th e requirement about 'more coverage' is in my opinion futile. There are plenty of articles in Wikipedia whose relevance can be questioned on the same arguments. Also, this would prevent relevant info to be included in Wikipedia, just because the main stream press has not covered it. The statement that coverage 'beyond reviews or articles by bloggers' seems not to be up with the times of what 'coverage' actually is nowadays and is certainly not applicable for many other Lemmas in wikipedia. I am not sure what sort of 'coverage beyond reviews and articles by bloggers' is expected? A front page on the New York Times perhaps?
Let me just add a more general point of concern. The number of writers for Wikipedia has dropped and is dropping. Frankly, I do not write any articles anymore, which I used to do frequently. That is simply for the way writers are met with criticism. Here is someone who is willing to write and re-write an article about an important subject and instead of any encouragement, appreciation or help, all I see is criticism. That is not the idea behind Wikipedia or any wiki and if I dare say, any info is better than no info.
I see the following comment: " There are some other products in the list that have Wikipedia articles and are also questionably notable, but that isn't a reason for creating one more article of questionable notability." OK, but then can we expect that those other "questionably notable articles" will be removed too now? "it seems to me that this article is created with the desire to see it listed amongst the other products, rather than this product being notable in its own right" Well 'seems' is not a hard argument and completely random, it is just guessing. As far as I know openhab is not a commercial product, no one is selling it, so any presumptions on the author's motives is completely besides the point and lacks 'notable sources'
| File:OpenHABLogo.svg | |
| Original author(s) | Kai Kreuzer |
|---|---|
| Initial release | 2010 |
| Stable release | 2.3
/ May 28, 2018 |
| Written in | Java |
| Engine | |
| Operating system | OS X, Linux, Solaris, FreeBSD, OpenBSD, Microsoft Windows |
| Type | Home automation |
| License | Eclipse Public License |
| Website | www |
Search OpenHAB on Amazon.
openHAB is an open source home automation platform based on the OSGi framework.[1]. It allows the integration and control of home automation systems from different vendors (e.g. Philips Hue, Amazon Echo) and IoT devices (e.g. Chromecast, Sonos, Tesla) within one single environment and is therefore best regarded as playing the role of a central automation hub [2].
The project was founded in 2010 and has evolved into a mature solution consisting of nearly one million lines of code contributed by hundreds of developers [3]. The original code base was merged into the Eclipse SmartHome framework in 2013. The Eclipse SmartHome framework now provides the underlying foundation whereas the openHAB software layer provides the reference implementation for the framework and a production-ready end user system.
Functionality
Integration
One of the main strengths of openHAB is its ability to integrate multiple different home automation technologies under a single umbrella framework. It is particularly effective at acting as a "bridge" from one home automation technology to another - provided someone has implemented a binding to each of the technologies involved.
For example, some electric blinds might operate under mains relay control - perhaps based on KNX technology - whereas others might be controlled using the Somfy RTS radio protocol. Within openHAB these are all just blinds and can be manipulated without regard to the underlying communications technology; instructions like "close all blinds" will apply to them all.
Automation
By the use of rules openHAB is able to automate operations in response to events - across any of the supported home automation technologies. The events can include timer schedules (e.g. 21:00 every Saturday; an hour after sunset), dynamic changes of state (such as someone pressing a switch) or sensor values crossing a threshold. A common use case is the implementation of 'scenes' - for example dimming lights and lowering window shades when starting to watch a movie.
User Interaction
openHAB is often used to provide a unified user interface for a range of different home automation devices based on different technologies, bringing everything together within a single console rather than relying on multiple different apps (one for each technology involved). Lighting, heating, audio control, CCTV feeds, weather forecasts etc. can all be combined on one display - most notably using the HABpanel user interface module in conjunction with a tablet or similar touch-screen device. (TODO - Consider including a HABPanel screenshot)
Rather than relying on a single user interface mechanism, openHAB implements multiple user interface solutions in the form of add-on modules which provide a high degree of flexibility. Graphical user interface options are implemented in WebApp.net, HTML5 or as native apps for iOS, Android or Windows. Command-line and audio-based user interfaces (for Google Speech Engine and Amazon Alexa) are also available.
Persistence
The openHAB architecture allows users to persist data to several types of storage back-end. This supports the visualisation of how sensor values change over time or the recording of device states so they can be restored or compared with previous values. Persistence bindings exist for MySQL, rrd4j and db4o, among others.
Concepts
Items
openHAB items are abstract representations of particular home automation elements such as lights, switches, sensors, media players etc. or virtual elements such as weather forecasts. They are managed separately for each openHAB installation - either based on automated discovery (openHAB 2 onwards) or by manual configuration in .items configuration files.
Sitemaps
openHAB sitemaps define how items should be represented (or not) in a particular user interface on a particular device. Separating the definition of the items from the definition of their visual representation decouples the different aspects and simplifies the construction of different types of user interface - e.g. for simple touch-screens rather than web browsers.
Next to the main configuration interface Paper UI, interfaces are provided specifically for mobile devices like smartphones or tablets. Users are able to adapt these interfaces to their needs via so-called sitemaps[4]
Rules
openHAB rules provide a powerful mechanism to implement automation. (TODO - mention rule language and rule editor GUI)
Bindings
openHAB bindings implement the communication with different types of devices and external systems. They are developed in Java and distributed in the form of plug-in modules, separate from the core openHAB software. Each openHAB installer decides which bindings should be installed and configured, typically by using the management interface.
The bindings can be divided into several main categories:
- Generic communication technologies such as IRTrans, RS-232, TCP, UDP
- Standard TCP/IP protocols such as HTTP, NTP, SNMP
- Standard home automation and IoT protocols such as DMX, KNX, Modbus, MQTT, OneWire, ZWave
- More specialised home automation protocols such as Insteon, Lutron, Miele@home
- Media player solutions such as Chromecast, Kodi, Logitech Squeeezbox, Plex, Sonos
- Specific device APIs such as for LIFX, Nest, Netatmo, Philips Hue, Wemo
- Virtual devices such as RSS feeds, Weather services and the Astro binding which e.g. calculates the position of the sun for a given latitude and longitude
The full list of available bindings is large and continues to evolve as new technologies are brought to market. For an up-to-date list refer to the openHAB website.
Technical Characteristics
Modular Architecture
openHAB is an open-source solution based on the Eclipse SmartHome framework[5]. It is written in Java and uses Apache Karaf together with Eclipse Equinox as an OSGi runtime. Jetty serves as an HTTP server. [6]
The platform's modular architecture allows the flexible extension of the functionality of openHAB through bindings. These bindings provide functionality for different technologies, systems and devices that then can be controlled through the openHAB platform.
The platform is designed to be operated on-premise, i.e. only within a user's home network. This has the advantage that no data is stored in cloud services, where they are potentially vulnerable.
Distribution and Installation
Due to its platform-independent nature, the openHAB runtime can be run on a wide range of systems. Installation packages exist for Windows, macOS, and Linux-based operating systems.[7] [8]. There are also pre-configured images available for Docker, Raspberry Pi, Synology DiskStation, QNAP NAS, and PINE A64 [9]
Development
History
The first version of openHAB was released in August 2012. The last version in the 1.x branch was released in May 2016 (1.9). After that only bugfix releases have been provided. Development for the 2.x branch begun in 2014 and the completely rewritten version 2.0 was released in January 2017. openHAB version 2 is the first one based on the Eclipse SmartHome framework.
From the beginning, the focus was laying on developing modularity, structure and connections (bindings) to the many available hardware systems. During the development process of version 1 the team decided to separate different functions and bring fundamental parts into the Eclipse Smart Home project and keep the specific (hardware) drivers and interface technologies in openHAB. The main focus in version 2 is to improve the usability of configuring the system to also allow non tech-savvy users to set up the system. One aspect is for example the automatic detection of new hardware components within the home network.
Community
The community participates and gives input to other open source initiatives.[10] Kai Kreuzer, who started openHAB in 2010, is leading up the project, and has contributed the core of openHAB to create the Eclipse SmartHome framework. [11]
OpenHAB Foundation
The openHAB Foundation was established in December 2016 with the purpose "to educate the public about the possibilities that Free software offers in the domain of smart homes".
See also
References
- ↑ Raj, Pethuru; Raman, Anupama C. (2017). The Internet of Things: Enabling Technologies, Platforms, and Use Cases. CRC Press. ISBN 978-1-4987-6128-4. Search this book on
- ↑ Porter, Matt (March 2015). Building IoT systems with openHAB (PDF). The Linux Foundation Embedded Linux Conference 2015. San Jose, CA, USA.
- ↑ "Open Hub entry for openHAB".
- ↑ "heise.de: openHAB 2 bringt übersichtlichere User Interfaces". January 2017.
- ↑ "researchgate.net: Standardized framework for integrating domain specific applications into the_IoT" (PDF). August 2014.
- ↑ "finalist.nl: OpenHAB a Java smart home". December 2016.
- ↑ "insights.ubuntu.com: OpenHAB arrives as a snap". February 2017.
- ↑ "OpenHAB on Ubuntu". April 2017.
- ↑ "openHAB documentation - Installation Overview". June 2017.
- ↑ "apache.org: board report". January 2017.
- ↑ "github: Eclipse SmartHome with openHAB" (PDF). October 2016.
External links
Category:Home automation Category:Building automation Category:Internet of things Category:Open hardware and software organizations and companies
This article "OpenHAB" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:OpenHAB. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
|
This page exists already on Wikipedia. |
