I’m currently trying out HA just to get an alternative view, my setup allows that if disabling corresponding rules. Im using in OH not many bindings, Zigbee via Zigbee2MQTT (by adding the required channels for devices by hand), icalendar and shelly. So far, i can see following advantages in OH:
- If getting more advanced, you are required to script very quickly, but have more powerful possibilities
- Access to historic data is much easier in OH
- The architecture is much cleaner as there are different types of plugins
- HA seems only to know integrations, which is quite universal, but somehow also not clear
- The docs are more clear
On the other hand HA has some advantages:
- Automations (= rules in OH) can be triggered by a state + time
- Triggers for rules in OH are only a point in time. To implement something similar, i had to write some code and i’m using it in multiple rules. The rule itself would be much easier when OH had a similar mechanism
- The android app is a very well integrated into HA, there is no break because there are multiple UIs as in OH (at least i think so)
- The development pace seems to be much higher
- my PR to icalendar is now some months old without review, that a little bit frustrating, but it seems not relevant enough, i’m pretty sure i would have to rebase again (!) because of the age
- in HA you have to review another PR before getting your own merged, maybe that would help, too
I have no long-time experience yet, currently i’m driving both at same time.
One thing i saw here simply not true: HA can also run without internet and completely free. It’s cloud connection is just not free. That’s a little difference. I can run my HA instance the same way like OH beind a reverse proxy. This is neither pro nor con.