Can the database used v2025.1 be used by v2025.2?

[bearjoost]

Got a Raspberry Pi 4b (Bullseye) running Domoticz V2025.1. Upgrade to V2025.2....... CRASH! Yes..... V2025.2 needs Bookworm.
Made a different approach. Domoticz on my Synology NAS. It has Docker (Container Manager) under the hood. Domoticz V2025.2 is running in a container but it is totally empty. Is it possible to copy the database from V2025.1 on the RPi4 to my Synology Domoticz V2025.2?

[jannl]

A database is automatically upgraded when used in a higher version. For going back you need a backup.

Backwards compatibility is not always possibkle with the database.

Why not install docker on your Pi?

Should be no problem using the database from you Pi on the NAS

[bearjoost]

Thanks for the reply "janni". The reason to move from RPi4B to Synology is to get rid of the OS updates on my RPi4B. But nevertheless it is going to be tough job to copy the whole directory structure to my NAS for I don't yet know where to put it. I have some digging to do! Let you know if i have succeeded or not.

[waltervl]

You can better run Domoticz in Docker om your RPi then on the NAS. Keep those applications separate....

[bearjoost]

Well...... I managed to get Domoticz running on my Synology. It came with problems!
I used the "Container Manager" to register the "Domoticz/Domoticz" image and launched it. I could open Domoticz in the browser, created a dummy switch and so far it worked. Next: Setup >> Hardware >> More Options >> Events. A incomplete window popped up. I couldn't create events at all. Templates...... No where. I discovered that the installation was far from complete in contrast to what I was used to on a Raspberry Pi. The next thing I did, I made a <.yml> file:
---------------------------------------------------------------------
version: '3.8'
services:
domoticz:
image: domoticz/domoticz:stable
container_name: domoticz
restart: unless-stopped
# Pass devices to container
# devices:
# - "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0"
ports:
- "XXXX:XXXX"
- "ZZZZ:ZZZZ"
volumes:
- /volume1/docker/domoticz/config:/opt/domoticz/userdata
- /volume1/docker/domoticz/www:/opt/domoticz/userdata/www
- /volume1/docker/domoticz/scripts:/opt/domoticz/userdata/scripts
- /volume1/docker/domoticz/plugins:/opt/domoticz/userdata/plugins
environment:
- TZ=Europe/Amsterdam
- LOG_PATH=/opt/domoticz/userdata/domoticz.log
- WWW_PORT="XXXX"
- SSL_PORT="ZZZZ"
- EXTRA_CMD_ARG=-nowwwpwd
---------------------------------------------------------------------
The next step was to copy more or less the directory structure installed on the Raspberry Pi, did a <docker-compose> in the directory where the <.yml>-file was stored, opened the browser again en YES!!! I could create dzVents scripts with the build-in editor of Domoticz. The templates are available!

By the way...... the domoticz.db (2025.v1) was used with the Domoticz 2025.v2 on my Synology. All my devices where visible! I have to do some more checks and make a decision to go over to Domoticz on my Synology. For now Domoticz 2025.v1 is still active on my Raspberry Pi.
ZWave-JS-UI is already running in a container on my Synology and works perfect with a Aeotec Z-Stick Pro 10 (Zwave an Zigbee). Also for the ZWave container I used a <.yml>-file. With the provided image it was not possible to map the internal USB-device to an external device.

The reason to move to Synology is that if you want to keep up with the Raspberry OS it is a lot of work to do that. I also saw that Debian 13 (Trixie) was out. Maybe there will come a time that I regret that a went over but for now I'll go for it.