4 ms·
I have tried both OpenHAB and HomeAssistant extensively. My recommendation: use HomeAssistant, do not bother with OpenHAB Rationale: . OpenHab is very po
by ur-whale 5y ago
I have tried both OpenHAB and HomeAssistant extensively.
My recommendation: use HomeAssistant, do not bother with OpenHAB
Rationale:
. OpenHab is very powerful but requires the user to invest a lot of time to configure it properly
. OpenHab data model is very, very (and in my opinion unnecessarily) convoluted and it takes a lots of work/time to wrap your head around it
. OpenHab is implemented in Java and drags along with it all the heaviness/unwieldiness of the Java world. In particular, if you want to do anything a little complex, that implies writing a Java plugin.
. Home Assistant is Python. For simple, code-based changes to the system, YMMV but I personally think that Java vs. Python ... Python wins hands down.
. Home Assistant works "out of the box" for most things, and is also very flexible when you want to
. The Home Assistant community is much larger, and if you are doing exotic stuff, you'll find a ton more support online
- armistace 5y agoagree with most points, recently upgraded to OH 3.x though and I have to say they have abstracted a lot of their complexity (particulary like the new semantic model) HomeAssistant I found harder to use for a very very specific reason, it didn't have a MySensors binding. thats it :/ so yes in general HomeAssistant is better, until it doesn't support what you want.
- theshrike79 5y agoI concur. The data model was what finally turned me off to OpenHab. I just couldn't wrap my head around the weird terms and ways stuff is configured. I would pick OH if I was getting paid to do automation and the system had to be super reliable for years. But for my home, where I'm always tinkering with stuff I'll go with Home Assistant + NodeRED with a MQTT backend.