3 ms·
I have had an openhab install running in a rpi without any issues for several years now. Everything in the home is MQTT-based (Tasmota firmware on the switches)
by mattlondon 5y ago
I have had an openhab install running in a rpi without any issues for several years now. Everything in the home is MQTT-based (Tasmota firmware on the switches) and it sends messages to the broker to control stuff. The local reliability is rock solid and cannot be faulted.
However the initial config is quite a learning curve though, and is pretty user-hostile IMHO (they appear to have basically just put a web UI on their java inheritance tree with zero thought given to making it understandable, at least in the 2.x version), and the documentation is usually wrong/out-of-date so it is a challenge. Some stuff could not be configured in the Web UI and needs to be done in the CLI which is fine (if frustrating) but the docs for the CLI didn't exist or were wrong (at least when I was setting it up). Perhaps their newest version is better - I don't know. I have not upgraded for fear if having to configure everything again.
The Google/Alexa integration however is free and works, but has occasional outages (perhaps 5 or 6 times a year, sometimes several days at once). I have a local web server that runs a tiny UI to manually turn things on and off (sends MQTT to the switches/bulbs etc) that I have to rely on more frequently than I'd like.
I chose openhab over homeassistant because the Google/Alexa integration is (was?) $5/month for homeassistant. I wanted to be able to shout out loud to turn things on and off and openhab does that well with its integration (apart from the mentioned outages)
- imglorp 5y ago> appear to have basically just put a web UI on their java inheritance tree with zero thought given to making it understandable Exactly my impression. I used to work for Thingworx, more industrially oriented, and that's what was done there (also a java object astronautical culture), with an additional layer of generics to double complexity. They had some great ideas but any user would need a training class to be productive.
- musingsole 5y ago> with an additional layer of generics to double complexity In 2022, I just don't understand Java development. It feels like a whole ecosystem just insisting on itself as everything else moves on.