Domoticz

Open-source home automation, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Free, open-source (GPL-3.0) home automation platform written in C++ — monitors and controls lights, switches, sensors, energy meters, and 150+ smart home devices [website][2].
• Who it’s for: Privacy-conscious homeowners, Raspberry Pi tinkerers, and anyone who wants rock-solid home automation without a cloud subscription, a monthly bill, or a beefy server to run it [website].
• Cost savings: Competing hubs like Homey Pro cost ~$399 upfront. Smartthings requires Samsung hardware. Domoticz runs for $0 on hardware you probably already own — a Pi Zero counts [website][4].
• Key strength: Absurdly lightweight. Under 50 MB of RAM, runs on a Pi Zero, written in C++ rather than Python or Java. It’s been reliably stable since 2012 [website].
• Key weakness: The UI looks like it was designed in 2013, because a lot of it was. Home Assistant has lapped Domoticz on polish, integrations, and community momentum. Domoticz’s 3,720 GitHub stars vs Home Assistant’s 70,000+ tells the story [GitHub].

---

What is Domoticz

Domoticz is a home automation server that runs on your own hardware and stays entirely local. You point it at your Z-Wave stick, Zigbee coordinator, or RFXCOM transceiver, and it discovers your sensors and switches. From there you set up automations using a visual scheduler, dzVents (a Lua scripting engine), Python plugins, or Blockly visual scripting. The dashboard shows live readings from temperature sensors, energy meters, rain gauges, wind sensors, and anything else you’ve connected [website][2].

The elevator pitch the project itself uses: “Free open source home automation system for Linux, Windows, Raspberry Pi. Supports Z-Wave, Zigbee, MQTT, and 150+ devices.” That’s accurate and unembellished — which is more than you can say for most software homepages [website].

What makes it practically distinct: it’s written in C++ rather than Python or Java, which is why it can genuinely run on a Pi Zero with 512MB of RAM and still respond quickly [website][4]. A CNX Software tutorial from 2017 documented installing it on a NanoPi NEO — a board with 256MB RAM — and having it run fine [4]. Nearly a decade later, the same low-resource story holds. That’s not a common claim in the home automation space, where Home Assistant now recommends 4GB RAM for comfortable operation.

The project is community-run and has been running since 2012 — over 14 years. There’s no company behind it, no VC backing, no SaaS pivot risk. Donations keep the lights on. The tradeoffs that come with that model are real and worth understanding before you commit.

---

Why people choose it

The community forums and reviews paint a consistent picture: people land on Domoticz because they want local-only home automation on minimal hardware without cloud accounts, and they stay because it’s stable and doesn’t break.

The lightweight argument is real. Under 50MB of RAM is not marketing copy — it’s a consequence of the C++ implementation [website]. For someone running a Pi 3B as a NAS and media server simultaneously, the ability to run a home automation controller in the remaining headroom matters. No other mainstream open-source home automation system can make this claim honestly.

Privacy and local control. The website leads with “All data stays on your hardware. All automations run locally. No cloud accounts, no monthly fees, no vendor lock-in. Your home keeps working even without internet.” [website] This isn’t niche paranoia — it’s a real selling point when you’re connecting occupancy sensors, door locks, and energy usage data to a single system. The Norwegian home automation community (hjemmeautomasjon.no) has an active Domoticz subforum where users discuss Python plugins and Domoticz API integrations that keep all processing on-premises [3].

Hardware support breadth. 150+ supported hardware types, including protocols that newer platforms have deprioritized: RFXCOM RF433, P1 Smart Meters (common in Dutch homes), YouLess energy meters, Davis Vantage weather stations, 1-Wire sensors, Eco Devices, and various European-specific devices [2]. If you have older RF hardware that modern hubs ignore, Domoticz is often the last platform that still supports it cleanly.

Alexa integration exists — with caveats. As of Domoticz beta 2025.2, there’s native Alexa Smart Home API v3 support with a built-in OAuth2 server. The catch: you still need an AWS Lambda function to bridge Alexa to your local instance, and your Domoticz must be publicly accessible with a valid SSL certificate (self-signed certificates won’t work) [1]. It’s functional but it requires more AWS setup than most non-technical users will want to do.

The stability argument has weight. “Set it up once and it just works — for years. No monthly breaking changes, no forced updates that break your automations,” says the website [website]. Home Assistant users who’ve had Saturday morning integrations break after an auto-update will recognize what this is pointing at. Domoticz does not ship changes fast, which is a bug or a feature depending on your perspective.

---

Features

Core device support:

• 150+ hardware types including Z-Wave (OpenZWave + Aeon ZStick), Zigbee, MQTT, RFXCOM RF433, P1 Smart Meter, YouLess, Philips Hue, 1-Wire, EnOcean, and more [website][2]
• Auto-discovery of sensors and switches when hardware is connected [website]
• Temperature, humidity, rain, wind, UV, electricity, gas, and water monitoring [website][2]
• Energy monitoring and smart meter support with graphing and cost tracking [website]

Automation and scripting:

• dzVents — a Lua-based event scripting system with a cleaner syntax than raw Lua [website]
• Python plugin framework for custom hardware integrations [website][3]
• Blockly visual scripting for non-coders [website]
• Timers and schedules [2]
• Sensor and switch triggers [website]

Interfaces and notifications:

• HTML5 scalable web frontend, adapts to desktop and mobile [website][2]
• iOS and Android push notifications [website][2]
• Extended data logging and historical charts [website][2]

Connectivity:

• REST API for external integrations [features canonical]
• MQTT broker support (inbound and outbound) [website]
• Alexa Smart Home API (beta 2025.2+, requires AWS Lambda) [1]
• Docker deployment supported [features canonical]

Platform support:

• Linux (x86, ARM), Windows, macOS, FreeBSD
• Raspberry Pi, NanoPi, Cubieboard, and other ARM boards [website][4]
• Minimum viable setup: 256MB RAM, 200MB storage [4]

What it notably lacks compared to Home Assistant: a polished integration marketplace, native Matter/Thread support, a mobile app with rich controls (the third-party Domoticz apps are functional but spartan), and any kind of visual automation builder that a non-technical user would find approachable.

---

Pricing: SaaS vs self-hosted math

Domoticz: $0. GPL-3.0 license. No cloud tier, no commercial edition, no paid features [website].

What it actually costs to run:

• Raspberry Pi 3B or 4 (if you don’t already have one): $35–75 one-time
• Power consumption: ~3–5W on a Pi 3B — roughly $2–4/year in electricity at US average rates
• Storage: any microSD card, 16GB is plenty
• Domain + SSL certificate: Let’s Encrypt is free; only needed if you want remote access or Alexa integration [1]

For comparison:

Home Assistant:

• Software: free (Apache 2.0)
• HA Cloud (Nabu Casa): $6.50/month — adds remote access, Alexa/Google integration without port forwarding
• HA Green hardware: ~$99 one-time
• HA Yellow (with Zigbee + Z-Wave): ~$139 + modules

Homey Pro (2023):

• Hardware + software: ~$399 one-time
• No subscription required after purchase

Samsung SmartThings:

• Hub hardware: ~$70–130
• No subscription for basic use, some features cloud-dependent

Philips Hue ecosystem (for comparison):

• Hub: ~$60, then per-bulb costs ($15–50 each)
• Free app, but entirely cloud-dependent until you run your own bridge API

For someone who already owns a Raspberry Pi or a spare mini-PC, Domoticz has a meaningful cost advantage over hardware-bundled alternatives. The real cost is time — setup, learning dzVents for automations, and troubleshooting when things break.

---

Deployment reality check

The one-liner install path: curl -sSL install.domoticz.com | sudo bash. On a fresh Raspberry Pi OS install, this actually works and produces a running Domoticz instance in under 5 minutes [website]. There’s also a Windows installer and Docker support for those who prefer containers.

What you need before you start:

• A Raspberry Pi (any model with 256MB+ RAM), Linux VPS, or Windows machine [4]
• Physical smart home hardware — a Z-Wave USB stick, Zigbee coordinator (Sonoff Zigbee Dongle Plus is commonly used), or RFXCOM transceiver
• A network to connect the Pi to

What can go sideways:

The Alexa integration requires a publicly accessible Domoticz instance with a valid CA-signed SSL certificate, plus an AWS Lambda function and Amazon Developer account setup [1]. This is not beginner territory. The wiki documents it thoroughly, but the word count of the Alexa setup guide alone should tell you something about the complexity involved [1].

The community is primarily forum-based (forum.domoticz.com and language-specific communities like hjemmeautomasjon.no [3]) rather than Discord or Slack. Answers exist but require searching. The GitHub issue tracker is explicitly not for end-user support [website README].

The UI is functional but dated. If you’re coming from Home Assistant’s Lovelace dashboards, the visual step down is significant. Domoticz’s interface looks like an early-2010s responsive web app, because that’s roughly when the core design was set. It works, but you don’t show it to house guests.

Realistic time estimates:

• Technical user with a Pi already set up: 30–60 minutes to a working instance with one hardware device configured
• Technical user adding Alexa integration: add another 2–4 hours for AWS setup and SSL cert [1]
• Non-technical user: budget a full day, and seriously consider whether Home Assistant’s more guided setup experience might save you frustration

---

Pros and Cons

Pros

• Genuinely free, forever. GPL-3.0, community-run, no commercial tier to upsell you into. Donations keep it alive, not investor expectations [website].
• Absurdly lightweight. Under 50MB RAM, runs on a Pi Zero, written in C++. No other mature home automation platform makes this claim credibly [website][4].
• 14+ years of stability. Since 2012, with no forced breaking updates. If you configure it and it works, it will probably keep working [website].
• 150+ hardware devices including legacy ones. RFXCOM, P1 Smart Meters, older RF protocols, Davis weather stations — hardware that newer platforms have dropped [2].
• Fully local and private. Zero cloud dependency required. Works without internet. No vendor lock-in [website].
• Active community for hardware-specific integrations. The Python plugin system means someone has probably already written a plugin for your obscure sensor [3].
• Energy monitoring is a first-class feature. P1 Smart Meter support, graphing, cost calculations — not bolted on as an afterthought [website][2].
• Alexa integration added in 2025. Native Smart Home API v3, OAuth2 built-in — though setup still requires AWS [1].

Cons

• UI is dated. The web frontend works on all browsers, but it looks like 2013. No visual automation builder that a non-technical user would find intuitive [website].
• Automation scripting requires code. dzVents (Lua) and Python plugins are powerful but not beginner-friendly. Blockly helps, but it’s limited [website]. Home Assistant has significantly better no-code automation tooling.
• Smaller community than Home Assistant. 3,720 GitHub stars vs Home Assistant’s 70,000+. Fewer integrations, fewer tutorials, slower development pace [GitHub].
• Alexa requires AWS Lambda. Even with native OAuth2 support, you still need an AWS account, a Lambda function, and a public-facing SSL endpoint [1]. Not a one-click setup.
• No native Matter/Thread support as of this writing. Newer smart home devices adopting these protocols will require workarounds.
• No polished mobile app. Third-party apps exist but are basic. Compare to Home Assistant Companion, which has location awareness, widgets, and full device control.
• Community-run = no guaranteed roadmap. No company means no SLA, no committed feature timeline, no enterprise support contract. The project could slow down if key maintainers move on.
• Remote access requires work. Tailscale, VPN, or port forwarding — none of it is configured for you. HA Cloud makes this a $6.50/month solved problem; Domoticz requires DIY networking [1].

---

Who should use this / who shouldn’t

Use Domoticz if:

• You’re running on a Pi Zero, Pi 2, or any low-RAM device and Home Assistant won’t fit.
• You have older RF hardware (RFXCOM, P1 meters, legacy Z-Wave devices) that newer platforms have dropped.
• You want a zero-cost, zero-cloud home automation system that you set up once and leave alone.
• You’re comfortable with Lua or Python for automation scripting.
• You’re in the Netherlands, Belgium, or Norway where P1 Smart Meters and specific European hardware are the norm — Domoticz has deeper support here than most alternatives [3].
• Stability matters more than features. You don’t want a Saturday morning update breaking your heating schedule.

Skip it (pick Home Assistant instead) if:

• You want a polished UI and visual automation builder that non-technical family members can actually use.
• You need Matter, Thread, or modern cloud integrations (Google Home, Apple Home, Spotify, etc.) with one-click setup.
• You have a Pi 4 or better with 4GB RAM — there’s no resource reason to accept Domoticz’s limitations.
• You want a mobile app that feels like a product, not a port of the web interface.
• You’re not comfortable with command-line setup and occasional debugging.

Skip it (pick openHAB instead) if:

• You’re in an enterprise or commercial building automation context and need Java-based extensibility and formal rule engines.

Skip it (stay with Homey Pro) if:

• You want everything in one physical hub with a polished consumer UI and don’t mind paying $399 upfront to skip all configuration complexity.

---

Alternatives worth considering

• Home Assistant — the dominant open-source home automation platform. 70,000+ GitHub stars, 3,000+ integrations, polished Lovelace UI, active development. Requires more RAM (2–4GB recommended) and accepts more update-related breakage risk. For most users making this decision today, Home Assistant is the right answer unless the resource constraints are real.
• openHAB — Java-based, enterprise-oriented, extremely flexible. Harder learning curve than either Domoticz or Home Assistant. Better fit for commercial buildings than homes.
• Gladys Assistant — privacy-first, lighter than Home Assistant, more polished than Domoticz. Smaller community but actively developed.
• ioBroker — popular in German-speaking markets, JavaScript-based, strong industrial integration support. More technical than Home Assistant.
• FHEM — Perl-based, long-running, strong German community. Similar vintage and philosophy to Domoticz but with different hardware strengths.
• Homey Pro — commercial product (~$399), all-in-one hardware hub with no setup complexity. Not open source, but genuinely plug-and-play for non-technical users.

For the specific audience of non-technical founders who self-host tools: the realistic choice is Home Assistant vs Domoticz. If your hardware is modest (Pi 2/Zero, old ARM board) or you have specific older hardware, pick Domoticz. Otherwise, Home Assistant’s setup experience and integration breadth are worth the extra RAM requirements.

---

Bottom line

Domoticz is the home automation system for people who want their smart home to run the way a smoke detector runs — install it, forget it’s there, and have it still work ten years later. It won’t impress you with a slick dashboard or a one-click integration catalog. What it will do is run on genuinely minimal hardware, support legacy RF protocols that everyone else dropped, stay entirely local with zero cloud dependency, and not break when you don’t update it.

The honest caveat: Home Assistant has won the open-source home automation category on nearly every dimension that matters to most users in 2026. If you have a Pi 4 and want a polished experience, Home Assistant is the answer. Domoticz’s niche is real but specific — constrained hardware, European smart meter protocols, users who prioritize stability over features, and anyone who’s had enough of platforms that update themselves into brokenness.

If the self-hosting setup is the blocker regardless of which platform you choose, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients. One-time fee, done, you own the infrastructure.

---

Sources

1. Domoticz Wiki — Alexa Smart Home Integration (Domoticz Wiki, 2025). https://wiki.domoticz.com/Alexa_Smart_Home_Integration
2. LinuxLinks — Domoticz: control at your fingertips (linuxlinks.com). https://www.linuxlinks.com/domoticz/
3. Hjemmeautomasjon.no — deve87 community posts on Domoticz API and Python plugins (hjemmeautomasjon.no). https://www.hjemmeautomasjon.no/profile/969-deve87/content/
4. Jean-Luc Aufranc, CNX Software — “How to Install Domoticz Home Automation System in NanoPi NEO and Other ARM Linux Boards” (January 19, 2017). https://www.cnx-software.com/2017/01/19/how-to-install-domoticz-home-automation-system-in-nanopi-neo-and-other-arm-linux-boards/
5. IOTDomotica.nl — “Domoticz – App voor het beheren van je home domotica” (October 23, 2015). https://iotdomotica.nl/category/app

Primary sources:

• GitHub repository: https://github.com/domoticz/domoticz (3,720 stars, GPL-3.0)
• Official website: https://www.domoticz.com/
• Wiki: https://wiki.domoticz.com/
• Community forum: https://forum.domoticz.com/