Upgrade to 2025.1 miserably failed

[Toulon7559]

Have 9 RPIs running in a variety of Raspberries of types3A, 3B and 02W with OS= Buster or BullsEye.
1 RPI4B with Bookworm, reporting

Code: Select all

OpenSSL 3.0.16 11 Feb 2025 (Library: OpenSSL 3.0.16 11 Feb 2025)

Paid attention to the warning to have OpenSSL3 fitted prior to trying upgrade, but (in hindsight) apparently made a mistake.
Yesterday upgrade for 2025.1 seemed to progress quit smoothly, with all Domoticz-instances reappearing.
However after programmed reboot today, desaster stroke:
first reporting that no devices choosen, and now only black screens on all upgraded Raspberries (incl. RPI4B).

Helping hint needed,
howto rollback to earlier version 2024.7, and then try Docker-approach ....
At a Raspberry3A (when still with display) tried to restore the database,
but Domoticz did not recognize any database, neither from own backup, nor from folder /home/pi/domoticz/backups
All RPIs can still be accessed by means of PuttySSH, by WinSCP etc.

[waltervl]

Luckily Domoticz creates a full backup when updating so you can restore to the old situation. See the wiki for instructions: https://wiki.domoticz.com/Raspberry_Pi# ... ect_update

[Toulon7559]

Due to the failed upgrade you may doubt the value, but when testing & trying this morning, the following observations related to browser versus processortype and OS-version:
- upgraded Raspberry3A_Buster called with GoogleChrome shows Domoticz-window telling that no favorite devices defined etc.
- upgraded Raspberry3B_Buster called with GoogleChrome shows black Domoticz-windows, but if called by Firefoz at other PC, the display is quite normal
- upgraded Raspberries3B_BullsEye called with GoogleChrome show black Domoticz-window, and have timeout when called by Firefox
- upgraded Raspberries02W called with either GoogleChrome or Firefox have timeout.

That the upgraded Raspberry4B_Bookworm refuses access by both browsers seems strange, because (without any extra effort) that configuration meets all requirements for successful, faultless upgrade to Domoticz2025.1:
fortunately this Raspberry4B not yet filled with applications beyond Domoticz and some testing functions, and therefore minor trouble to freshly reinstall. Just small setback for introduction of this device in the LAN.

Thanks for the hint to the instructions for rollback from tar-file made as first step at upgrade: that really is a lifesaver!
Would suggest to accompany each update with a weblink to these instructions, for less work for the moderation as well as for less headache at user-side.
Or put a related weblink as fixed head in the 'Problem'-section ......

[waltervl]

Try with browser in incognito /private mode.
From what version did you upgrade? 2024.7?
Or way older so before 2023.2? As in that version some security changes were performed that could give similar issues.

[Toulon7559]

Only tried upgrade from machines running Domotic_2024.7, first with few Testers running 'beta', and then 'Production'-kernel running 'stable':
now (re)learned the hard way that testing must be done over some extended time to catch effects of load, timing, reboot etc. .......
In my configuration Domoticz_2023.1 is strictly used with Raspberries0W_1.1 as legacy setup.
Present experience gives reason to further stay with Domoticz_2024.7 for all machines older than Raspberry4.
Why not? If running jobs without problems, do not touch ......
Just some precautions required for repair/restauration in case of accidents, such as availability of file/images for restore.

Leftover Raspberry1B is fading out for jobs without Domoticz.

[waltervl]

If OS Bookworm (with openssl3) is running on the machine it should also run Domoticz 2025.1 beta (on Bookworm) as it is build on that OS.