I have been experimenting with using openHAB to control my home automation devices. I am mainly using it as a user interface to existing capability.
It is very easy to set up, and install, and is very portable. Its default user interfaces for the web and Android are very usable, if a bit limited. Here is the web page I set up for my living room:
It was trivial to move it between running on a Windows PC and on a Raspberry Pi.
openHAB supports a huge number of devices, but unfortunately not all the ones I use. It has no support Jeenode devices (other than the OpenEnergyMonitor devices), and no support for my EDF (Current Cost) Individual Appliance monitors.
It does support Wemo plugs, but unfortunately not the Wemo Insight until the next release.
It does, however, have excellent support for MQTT, so I added extra MQTT support to my HouseControl system, including publishing the sensor readings from all my sensors including the Jeenode ones, and I added the ability to control my EDF IAM devices by MQTT.
openHAB does have support for LightwaveRF devices, but only via UDP and the Wifi link, which I do not own. My solution to this was to add LightewaveRF UDP support to HouseControl, so that it emulates the Wifi Link. This works well and lets me control my sockets and lights. There is no support for LightwaveRF contact devices, however. I am probably best supporting those via MQTT. (Althogh they don’t work very well, and I prefer EnOcean ones).
openHAB does have EnOcean support, and I could probably get it to drive my Raspberry Pi EnOcean interface, but it was easier to pick up the sensor values and button presses via MQTT, as I was already publishing them.
I don’t have my TV, TiVO and AV receiver controlled by openHAB yet. The simplest way to do that is probably to add emulation of a supported TV (like Samsung or LG) to HouseControl. These use UDP, and my HouseControl emulation would read the UDP packets and convert them to messages to my Jeenode IR blaster.
openHABs TCP/IP support does not seem to be compatible with the way that HouseControl TCP/IP sockets work, but I am moving away from using the TCP/IP interface so heavily as using MQTT or UDP is more lightweight.
openHAB does support camera streams from my IP camera, but the way I am currently doing is a bit slow.
I am currently configuring openHAB by editing the text files, which is very easy. I have not tried their designer product yet.
openHAB seems to have a good rules system, but I have not used it much yet. Currently I prefer to use node-red for rules.
openHAB lacks a natural language interface that can be used for speech and chat interfaces, so HouseControl remains an essential part of my infrastructure.
Overall, I think I prefer openHAB to OpenRemote, but I am not sure if I will use it much.
I now have a wide variety of user interfaces to control and monitor my house, but none of them is ideal. Getting the combination of immediate accessibility and usability is hard.