Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Do
Self-host Domoticz
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A home automation system written in C++ that talks to lights, switches, temperature, power and water meters and other sensors through hardware plugins and protocols such as Z-Wave, MQTT, Matter and 433 MHz radios. It has a web interface with dashboards, floor plans, charts and a scene and timer system, event scripting in Lua, dzVents and Python, notifications and an API. Settings, device data and history are kept in a SQLite database in the user data folder. In the Docker image the admin account can be created at first start from environment variables, otherwise a web setup wizard creates it.
Pick Domoticz when you want a lightweight, self-contained home automation server that you configure from a web interface rather than YAML files: add hardware, let it create devices for your switches, sensors and meters, and build timers, scenes and scripts in Lua, dzVents or Python. It handles power, gas and water metering with charts, and supports Z-Wave, MQTT, Matter, 433 MHz radios and many other integrations through hardware plugins. It is GPL-3.0 (the repository's licence file is the GPLv3 text), C++ with a SQLite database. Our snippet adapts the compose file in the domoticz-docker README, pins `domoticz/domoticz:2026.4` (Domoticz 2026.4, released 2026-10-01, amd64, arm64 and arm) instead of the `stable` tag the README uses, keeps the user data in a named volume, and creates the administrator from a generated `DOMOTICZ_ADMIN_PASSWORD` in `.env`. Look elsewhere if you want the largest ecosystem of integrations and community add-ons: Home Assistant is far larger.
What you need
Any VPS with at least 256 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Domoticz — home automation server — adapted from the domoticz-docker README compose file, pinned to domoticz/domoticz:2026.4 (the image README's examples use the floating stable tag); the admin account is created from a generated DOMOTICZ_ADMIN_PASSWORD in .envecho "DOMOTICZ_ADMIN_PASSWORD=$(openssl rand -hex 12)" > .envcat > docker-compose.yml <<'EOF'services: domoticz: image: domoticz/domoticz:2026.4 restart: unless-stopped env_file: .env environment: TZ: UTC ports: - "8080:8080" volumes: - domoticz-data:/opt/domoticz/userdatavolumes: domoticz-data:EOFdocker compose up -dtimeout 300 bash -c 'until curl -fsSL -o /dev/null http://localhost:8080/; do sleep 3; done'# → http://SERVER_IP:8080 — the Domoticz web interface; sign in as admin with the DOMOTICZ_ADMIN_PASSWORD line in .env (grep DOMOTICZ_ADMIN_PASSWORD .env)
Domoticz's README, SECURITY_SETUP.md and the image README flag these before you rely on it:
non-negotiableThe image has no preset password. The administrator is created at first start from DOMOTICZ_ADMIN_PASSWORD (and optionally DOMOTICZ_ADMIN_USERNAME, default admin), and only when the database has no admin user yet; changing the variable later is ignored and the log says so. Without the variable, the first visit to the web interface runs a setup wizard to create the account, so do not publish the port before that is done.
non-negotiableSECURITY_SETUP.md says it is a bad idea to connect a Domoticz installation directly to the internet, since anyone could then control the connected devices. Put it behind a VPN or an authenticating TLS reverse proxy, and note that addresses listed under Setup, Settings, Security, Trusted Networks skip authentication altogether, so keep that list short.
non-negotiableThe settings and the SQLite database live in the userdata folder, which our snippet mounts as the domoticz-data volume. The image entrypoint copies bundled plugins and templates into it and recursively chowns it to uid 1000 on every start, so a bind mount is rewritten by the container and removing the volume deletes the whole configuration.
non-negotiableRadio and serial hardware attached to the host (an RFXtrx or another USB stick) needs the device passed through with a devices: entry in the compose file. The snippet leaves that out, so the container starts with only network-based hardware and the internal virtual devices. For Z-Wave, the release history points to Z-Wave JS UI with MQTT Auto Discovery and marks OpenZWave as unsupported.
non-negotiableThe image is built from Domoticz's release archive at build time, and Domoticz has shipped a stable release about every two months this year (2026.1 on 2026-03-25, 2026.2 on 2026-05-31, 2026.3 on 2026-08-02, 2026.4 on 2026-10-01). The 2026.4 notes call the web server, API and MCP server security fixes important, so do not stay on an old tag; back up the data volume before each bump because the database schema is upgraded on start.
non-negotiableThe container serves plain HTTP on 8080 (and HTTPS on 443 inside the container, not published here). The administrator password is in .env in clear text, so keep that file readable only by you.
Domoticz used 11 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 256 MB.
Is the Domoticz install snippet verified?
The Domoticz install snippet is marked verified on Ubuntu 26.04 (Nov 2026).