Domoticz

Last reviewed Sep 13, 2026 · 826 words

The people running Domoticz in 2026 fall into three groups, and if you are not in one of them, Home Assistant is the safer pick and I will not pretend otherwise. Group one: Dutch and Belgian households reading a P1 smart-meter port, which Domoticz has supported natively for over a decade and displays better than most. Group two: anyone whose hub is a Raspberry Pi Zero or an old single-board computer with 256 MB of RAM, where Home Assistant's 2 GB appetite simply does not fit. Group three: existing installs from 2014 that still work, with years of dzVents scripts nobody wants to rewrite. For those three, Domoticz remains a good, stable, boring choice, and boring is a compliment in home automation.

What lightweight actually buys you

Domoticz is a single C++ binary with an embedded SQLite database and a web UI on port 8080 (443 for HTTPS). Idle CPU is near zero, memory sits well under the 256 MB minimum on a typical install, and startup takes a couple of seconds, which matters when your hub is a Pi that reboots after a power cut. The Docker image is straightforward:

services:
  domoticz:
    image: domoticz/domoticz:stable
    ports:
      - "8080:8080"
    volumes:
      - ./config:/opt/domoticz/userdata
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0
    restart: unless-stopped

The device passthrough is for a P1 cable, an RFXcom transceiver or a Zigbee or Z-Wave stick. Bare-metal packages exist for Raspberry Pi OS and Debian, and for the Pi Zero case bare metal is the better route because Docker overhead is a meaningful fraction of the box.

The MQTT auto-discovery bridge is what keeps it current

Domoticz's native hardware list is long but dated, heavy on 433 MHz and early Z-Wave. What keeps it usable with modern devices is that it speaks the same MQTT auto-discovery convention Home Assistant popularised. Run Mosquitto, point Zigbee2MQTT at it for Zigbee and Z-Wave JS UI at it for Z-Wave, add the "MQTT Auto Discovery Client Gateway" hardware in Domoticz, and every bulb, sensor and switch appears as a device without a Domoticz-specific driver. That is the setup I would build today; the older direct Z-Wave integration has been removed and the RFXcom path only matters if you own that hardware.

Automation: three tiers, one that matters

Blockly gives drag-and-drop rules for simple "if this switch then that light" logic. Lua scripts are the middle tier. dzVents is the one to learn: a Lua framework with timers, device events, HTTP calls and persistent variables, written in a few lines each, editable in the web UI. It is not as expressive as Home Assistant's automation editor plus templating, but it is quicker to write for anyone who can read code, and a decade of examples exists in the forum. Python plugins extend the hardware side. There is no visual flow editor of the Node-RED kind built in, though Node-RED can talk to Domoticz over MQTT if you want one.

Where it honestly loses

The interface looks like the year it was designed. The dashboard is functional and the mobile layout works, but there is no equivalent to Home Assistant's dashboard ecosystem or its 2,000-plus integrations, and cloud services (voice assistants, weather providers, energy APIs) need workarounds where HA has a checkbox. The community is smaller, so an obscure device question may sit unanswered. Voice control is possible through third-party bridges but is not a first-class feature. If any of that describes what you want, the Home Assistant versus openHAB comparison is the right reading, and Domoticz is not the third option in it.

Backups and upgrades are refreshingly dull

Everything is in one SQLite file in the userdata folder, and the UI has a backup page that downloads it. Copy that folder nightly and you have a full restore. The stable release channel moves slowly and betas move quickly; stay on stable for a hub you rely on. Upgrades are a binary swap and a restart, with automatic database migration, and in years of running one I have never had a migration fail. That reliability is a real feature for a system that controls the heating.

What I'd do

Smart meter in the Netherlands on a spare Pi: Domoticz, bare metal, with the P1 cable and Mosquitto plus Zigbee2MQTT for everything else, dzVents for rules, nightly copy of the userdata folder. Tiny hardware with no room for HA: the same. Anything else, and especially a first smart home with modern hardware and a voice assistant on the wish list: Home Assistant, which has the momentum, the integrations and the answers. The home automation category lists both and a few others, but in 2026 the honest field is those two, and Domoticz wins only where being small is the point.