Page 1 of 1
Updating from RasPI/D2022.1 to thin-client/D2024.7
Posted: Friday 25 April 2025 12:43
by costo
I'm updating to a completely new setup.
My old setup:
Raspberry Pi3b with Raspbian 10 (buster)
Domoticz 2022.1 (build 14498)
RFLink433 and a lot of virtual devices on ESPEasy.
My new setup:
thin client HP-t530 (4Gbmem/128GbSSD) with extra wifi module
Linux Mint Cinnamon 22.1
Installed Domoticz 2024.7 , mosquitto-clients , python3.12-dev , monit , fail2ban.
I tested this setup with some spare hardware-sensors and everything seems to work fine
Are there precautions to take or any issues to expect when I import my 2022.1 database into the 2024.7
Re: Updating from RasPI/D2022.1 to thin-client/D2024.7
Posted: Saturday 26 April 2025 14:17
by costo
As no one mentioned any issues/problems i did the swap,.
Restore the old 2022.1 database into Domoticz 2024.7
I got 3 dB errors which give me a headache, Can this become a problem later ?
----------------------------
I got this in the logfile:
2025-04-26 13:38:47.161 Status: Restore Database: Starting...
2025-04-26 13:38:47.273 Error: SQL Query("ALTER TABLE UserVariables RENAME TO tmp_UserVariables") : error in trigger shareddevicesupdate: no such column: Order
2025-04-26 13:38:47.273 Error: SQL Query("INSERT INTO UserVariables ([ID],[Name],[ValueType],[Value],[LastUpdate]) SELECT [ID],[Name],[ValueType],[Value],[LastUpdate] FROM tmp_UserVariables") : no such table: tmp_UserVariables
2025-04-26 13:38:47.273 Error: SQL Query("DROP TABLE tmp_UserVariables;") : no such table: tmp_UserVariables
2025-04-26 13:38:47.297 Error: Default admin password has NOT been changed! Change it asap!
2025-04-26 13:38:47.557 Status: Restore Database: Succeeded!
2025-04-26 13:38:48.780 Status: PiBoard: System: ODroid/Raspberry
2025-04-26 13:38:48.780 Status: PiBoard: Hardware Monitor: Started (OStype Linux)
2025-04-26 13:38:48.781 Status: norway: Using Domoticz default location from Settings as Location.
2025-04-26 13:38:48.781 Status: norway: Started...
2025-04-26 13:38:48.782 Status: NotificationSystem: thread stopped...
2025-04-26 13:38:48.782 Status: NotificationSystem: thread started...
2025-04-26 13:38:48.782 Status: EventSystem: Queue thread stopped...
2025-04-26 13:38:48.783 Status: EventSystem: Stopped...
2025-04-26 13:38:48.907 Status: EventSystem - Python stopped...
2025-04-26 13:38:48.907 Status: EventSystem: reset all events...
2025-04-26 13:38:48.907 Status: EventSystem: reset all device statuses...
2025-04-26 13:38:48.976 Status: Python EventSystem: Initializing event module.
2025-04-26 13:38:48.976 Status: EventSystem: Started
2025-04-26 13:38:48.976 Status: EventSystem: Queue thread started...
2025-04-26 13:38:48.992 Status: RFLink433: Using serial port: /dev/ttyUSB0
2025-04-26 13:38:49.782 Status: MQTT: Connecting to 127.0.0.1:1883
2025-04-26 13:38:49.920 Status: RFLink433: Controller Initialized!...
Re: Updating from RasPI/D2022.1 to thin-client/D2024.7
Posted: Saturday 26 April 2025 16:30
by waltervl
Could be a problem if you use user variables. Do you have them in your database? And are the same user variables also in your new environment?
Re: Updating from RasPI/D2022.1 to thin-client/D2024.7
Posted: Saturday 26 April 2025 18:20
by costo
Yes I have several user variables defined.
Only one is active at the moment in a small script and there is no problem with that.
6 other user variables are defined for in-active scripts, i can delete them .