A calm comparison of the four paths most Just Smart Homes readers actually consider, so you can pick one as the "spine" of a home rather than installing all of them and debugging the overlaps. It points at the existing getting-started threads rather than repeating them: Home Assistant, openHAB, SmartThings.
Complexity
Beginner as a reading guide. Migrating a live house between platforms is a project of its own.
1. The vendor app — start here, do not always stay here
Every air conditioner, irrigation controller, lighting bridge and inverter ships with an app. Strengths: it is supported by the manufacturer, it usually works on day one, and it is the right place to do firmware and warranty tasks. Limits: each brand is a silo, automations stop at that brand's cloud, and you have little control when the vendor changes an API or retires a server (MELCloud vs a local Daikin path is a current example in the air-conditioning forum).
Use the vendor app for setup and firmware even if you later drive the device from a hub.
2. Home Assistant — local-first, integration-heavy
Home Assistant (docs current at research time: the 2026.11 series, including 2026.11.1) is a self-hosted hub with a very large official integration list, a companion app, and first-class energy, Matter, KNX, MQTT and backup tooling.
- Choose it if you want one dashboard and automations across many brands, and you are willing to run and back up a small always-on host.
- Official core integrations (Daikin, Hydrawise, KNX, Matter, Lunatone, ChirpStack, ONVIF, and so on) are the comfortable path.
- Community / HACS components (common for OpenSprinkler, C-Bus after C-Gate, some inverters) are possible, but they are not the same as official support — see the day-two FAQ in the Home Assistant forum.
- You own the backup, the VLAN design and the update cadence.
openHAB is the other major open, self-hosted platform. Official install pages at research time showed stable 5.2.4 and latest 5.3.0. Choose it if you already know it, or if you prefer its bindings and rules style, not because it is "more professional" or "more hobby" than Home Assistant — they solve a similar job with a different flavour.
You still run a host, still take backups, and still need official binding docs for each protocol. The existing openHAB thread is the on-forum starting point.
4. SmartThings — a vendor-hosted hub, with a phone-first workflow
Samsung SmartThings is a cloud-backed ecosystem (with local execution for some devices and hubs). Choose it if you want a supported consumer product, a phone app, and a shorter list of officially compatible devices, and you accept that some automations and features depend on Samsung's service. See t=104. It is a weaker fit if your core world is C-Bus, KNX, DALI or a SunSpec inverter — those usually want a local integration hub.
5. A practical way to decide
- If almost everything you own already works in one vendor app and you do not need cross-brand automations, stay there until the pain is real.
- If you have (or will have) lighting on a real bus, a local energy dashboard, or mixed HVAC and irrigation, pick one self-hosted hub — in this community that is usually Home Assistant — and add official integrations first.
- If the household wants a supported retail product and Matter accessories, SmartThings or a similar consumer hub can be enough; you can still use vendor apps alongside it.
- Do not run two hubs that both try to own the same Matter fabric, the same MQTT broker, or the same Modbus TCP connection "just to compare". Compare in a lab, then choose.
Official starting points
Home Assistant (2026.11 docs)
openHAB installation
SmartThings
HA getting started · openHAB · SmartThings
Researched from official documentation on 15 November 2026 (Australia/Sydney). This is a planning and how-to guide, not a claim that the exact hardware combination was assembled and tested on a live site. Please correct anything that has moved on.