Where Does Domoticz Store Data and Config?
Domoticz anchors state to its install folder with flags deciding the base: database, scripts, plugins and backups beneath it.
Last updated
Domoticz refuses one true path because flags decide everything. Database file, userdata tree, web root and logs all arrive as launch arguments with defaults varying by install method. Curl installs, packages and Docker each anchor differently.
Find the effective flags first through processes or service files, then back up what they name. The database with scripts and plugins carries the smart home. Versioned backup tarballs appear beside the database on default layouts.
Where Domoticz stores this, by platform
/home/<user>/domoticz/domoticz.db
SQLite state with journal companions at the curl-install default. Packaged variants relocate to opt or var trees and Docker to mounted config, so confirm flags first. Copy with the service stopped.
/home/<user>/domoticz/scripts
Automation scripts with lua, dzVents and python children plus plugins beside them under the install folder. Versioned backup tarballs land in the backups sibling. Same flag-decided base as the database.
Frequently asked questions
How do I back up Domoticz?
Copy the database file with scripts and plugins from the install folder, found through the process flags or service definition. Defaults differ between curl installs, packages and Docker mounts. The database plus scripts carry the home.
Where is my Domoticz install?
Read the effective flags from the running process or unit file. Database, userdata, www root and log paths all arrive as flags with different defaults per install method. Guessing absolute paths without checking misleads more than it helps.
How do I persist Domoticz in Docker?
Mount a host folder over the container config path with USB devices passed through. Database, scripts and plugins then persist outside the image. Windows runs take explicit database and userdata flags the same way.
Notice an outdated path? Let us know.