Domoticz update, reinstall or upgrade

kris · Post by **kris** » Saturday 01 January 2022 16:29

Hi. I've been running my Domoticz setup since 2015 and lately it's been crashing almost daily.
I'm using a Raspberry Pi2B+ and I'm still on Raspbian Wheezy. My Domoticz installation can't be updated past 4.11083 (2019-08-11).
I have a ZiPigate, a RFLink and a Z-Stick, some plugins and 147 devices.

Is it reasonable to update the OS and then Domoticz, I figure the best way is to do a new install, possibly on a Raspberry Pi 3B or 4? If I do, will I be able to restore my database or do I have to start all over again?

Also, is there really any major benefit of moving to a newer Pi or should I keep the 2B+?

Thanks

Sjonnie2017 · Post by **Sjonnie2017** » Saturday 01 January 2022 18:06

I would suggest updating your hardware to an Rpi 4 with at least 2 GB RAM. Install the system and update. Create a backup of Domoticz on your 2B+. Install Domoticz on your new Pi and add the ZiPiGate, TFLink and Z-stick. Switch of the 2B+, launch the 4, restore your database and check if all is working. If not you can always revert to the 2B+

EDIT: If you use plugins you'd best install them before restoring the backup.

mgugu · Post by **mgugu** » Saturday 01 January 2022 18:08

Like you I've been running domoticz since 2015 with a Pi2B+ and I have now a very large number of devices. In addition I run some nodejs and python programs.
I can confirm that 2B+ is totally sufficient for that purpose.
Concerning OS upgrade, I did it 2 years ago and I remember it was a long process (several steps). So I would recommand a fresh install since with domoticz only one folder has to be moved (no specific dependancy).
May be legacy debian 10 is preferable. Check the forum for incompatiblities issues between domoticz and bullseye (debian 11).

kiddigital · Post by **kiddigital** » Saturday 01 January 2022 18:37

Performance wise a Pi 2B+ is up for the task.

Upgrading to a 3B+ is nice giving you more performance room for other/new things. Pi 4 could bring some small challenges but is future proof.

But upgrading is not mandatory. Better to get some idea about what causes the instability. SD card issues are common after running a while, so replace the SD card with a new one is a good first option.

Second, the powersupply of your Pi could be causing issues. A good, reliable and powerful enough powersupply is mandatory for good long running operations. Even more important if/when you upgrade to a more power hungry model 3 or 4.

A migration is not a walk-in-the-park but it is doable. Make sure you have good backups of Domoticz (database) and your z-stick config.

Special attention for your Z-wave environment as the newer versions of Domoticz are using Openzwave 1.6 and not the 1.4 your current Domoticz version uses. This change is significant and potentially could cause some headaches especially when your current (1.4) z-wave network runs smoothly. Several people reported that the (initially) regretted the upgrade.

A clean install with Buster is your best option as there are some issues with compatibility running Bullseye.

Running the latest stable or beta from Domoticz can bring nice new feature and options (if needed of course).

My suggestion: verify that SD and/or powersupply are not causing issues. As they will keep causing issues when you decide to upgrade/migrate. Once you are sure that neither the SD card nor the powersupply give any issues, then it is a good moment to (re)consider your options.

But upgrading makes sense as there will come a time that for whatever other reason upgrading becomes mandatory

That

needs to swallowed sometime

MaikelK · Post by **MaikelK** » Wednesday 05 January 2022 22:27

kiddigital wrote: ↑Saturday 01 January 2022 18:37
A clean install with Buster is your best option as there are some issues with compatibility running Bullseye.

Hi,

Would you think this is fixed with the last two commits?
The one from 30-12-21 and 4-1-22?

Doubting if I will reinstall Buster or go for Bullseye now.

kiddigital · Post by **kiddigital** » Thursday 06 January 2022 7:08

MaikelK wrote:
kiddigital wrote: ↑Saturday 01 January 2022 18:37
A clean install with Buster is your best option as there are some issues with compatibility running Bullseye.

Hi,

Would you think this is fixed with the last two commits?
The one from 30-12-21 and 4-1-22?

Doubting if I will reinstall Buster or go for Bullseye now.

Possibly, but needs more testing to be sure.

Give it a go and let us know

Post by **waltervl** » Thursday 06 January 2022 9:21

You have to build it yourself as they are not yet built by automated builds. Currently only available for Windows machines only: https://www.domoticz.com/downloads/

Post by **waltervl** » Saturday 08 January 2022 14:28

Fix is now in latest automated Beta builds so if someone can test on Bullseye?

MaikelK · Post by **MaikelK** » Saturday 08 January 2022 14:38

Maybe I can find some time for that tomorrow!
I was using a python plugin which caused Domoticz too crash.
That should be fixed too, am I right?

Mike70 · Post by **Mike70** » Saturday 08 January 2022 14:43

One clean installed RPI 3B+ with Bullseye And Domoticz build 13994.
Using Tuya plugin.
Error:

: Knipsel.PNG (5.38 KiB) Viewed 5688 times

Unfortunately the same problem as I had in december.

Post by **waltervl** » Saturday 08 January 2022 15:40

Sorry to hear that, thanks for testing!
We will have to wait a little bit longer.

Toulon7559 · Post by **Toulon7559** » Sunday 20 February 2022 21:18

Reading about issues with Bullseye as OS-platform, reluctantly decided to equip 2 more Raspberries with Raspian_Buster, to avoid confusion & risk of 'unclear' effects: wait with general upgrade of all my RPIs till Bullseye is reported as stable.

Long time ago for fresh install, used same Buster base-version as applied for other Raspberries (and [to ensure availability] kept in backup).
Surprise that usual CLI-inputs sudo apt-get update and sudo apt-get upgrade did not do the normal upgrade-job towards latest version,
but instead with sudo apt update and sudo apt upgrade seem to have arrived at fresh & complete Buster setup.

Next is Domoticz-installation with recommended CLI-command

Code: Select all

curl -sSL install.domoticz.com | sudo bash

Installation starts running, but does not reach the finish, because the ssl-certificates not being trusted: see spoiler for error report.

Spoiler: show: --2022-02-20 21:08:17-- http://www.domoticz.com/download.php?ch ... ine=armv7l
Herleiden van www.domoticz.com (www.domoticz.com)... 188.114.96.0, 188.114.97.0, 2a06:98c1:, ...
Verbinding maken met www.domoticz.com (www.domoticz.com)|188.114.96.0|:80... verbonden.
HTTP-verzoek is verzonden; wachten op antwoord... 301 Moved Permanently
Locatie: https://www.domoticz.com/download.php?c ... ine=armv7l [volgen...]
--2022-02-20 21:08:17-- https://www.domoticz.com/download.php?c ... ine=armv7l
Verbinding maken met www.domoticz.com (www.domoticz.com)|188.114.96.0|:443... verbonden.
HTTP-verzoek is verzonden; wachten op antwoord... 302 Found
Locatie: https://releases.domoticz.com/releases/ ... armv7l.tgz [volgen...]
--2022-02-20 21:08:17-- https://releases.domoticz.com/releases/ ... armv7l.tgz
Herleiden van releases.domoticz.com (releases.domoticz.com)... 146.185.159.228, 2a03:b0c0:0:480:1001
Verbinding maken met releases.domoticz.com (releases.domoticz.com)|146.185.159.228|:443... verbonden.
FOUT: Het certificaat van '‘releases.domoticz.com’' wordt niet vertrouwd.
FOUT: Het certificaat van '‘releases.domoticz.com’' is verlopen.

What solution to pass that certificate-hurdle?

Post by **waltervl** » Sunday 20 February 2022 23:50

See topic viewtopic.php?t=37880

Toulon7559 · Post by **Toulon7559** » Monday 21 February 2022 12:08

Thanks for the hint,
but surprising that it happens at fresh installation of Domoticz, and that 'cleaning' seems so difficult/hidden and mandatorily at client-side.
In the manual method for update of certificates, instead of vi used sudo nano, being more familiar from earlier Raspian setup.
After the update of certificates now Domoticz could be installed 'as usual'.

Just guessing that the older/invalid certificate appeared because I used from backup an older package for installation of Raspian_Buster: correct?
;-( Is this happening to everybody walking this route for fresh installation of Raspian&Domoticz?
Then would hope for more public, general & easier plan of attack as part of installation-procedure for Domoticz.
Or at least a hint as warning.

joaquinmaroto · Post by **joaquinmaroto** » Monday 28 March 2022 22:11

Hello everyone
I have a zwave network running on version: 4.9700. within a RPI3.
I would like to update to the new version of Domoticz.
The idea is to have a fresh install on RPI 4 with Buster.
I will install the operating system and the last stable version of domoticz.
Then I will copy my zwave config file and domoticz database.
It is a good option?, would it be preferable to upgrade?
Did I forget any step?
Best Regards

Post by **waltervl** » Tuesday 29 March 2022 9:41

This seems correct.
Also do not forget to copy your event scripts (lua, python etc) that are not stored in the database with the events manager.

Toulon7559 · Post by **Toulon7559** » Thursday 31 March 2022 18:37

A small sidestep from Domoticz, but in line with previous question, related to runup to get a full installation.

Now for revival of a broken down Raspberry, decided to use the latest SD-card-imager.
Successful 'burning' of the OS-image, added an empty file called ssh to enable link with SSH-clients and a preconfigured file wpa_supplicant.conf to ease connection to the WLAN. Connection to WLAN went smooth.
All seems OK for further operation, and programs like WINSCP and Core FTP LE happily communicate with this 'new' RPI in SSH-mode,
but PuttySSH 'refuses' with complaint as shown in the attached picture.
.

: PuttySSH: reporting certificate-problem; 2022-03-31_PuttyError.png (19.15 KiB) Viewed 4588 times

.
;-( Another 'certificate-problem'?
Remedy or alternative available?

elzorrovega · Post by **elzorrovega** » Monday 04 July 2022 23:34

Hello All,

Yesterday afternoon I decided to take the plunge and upgrade both RPI to Bullseye and Domoticz to Version: 2022.1. Made sure to backup the data base and kept an old SD card in the event that I needed to go back. Used another USB ext4 memory stick to store Documents, Scripts, and things ..

Used the imager from another Raspberry to burn Bullseye image on to a 32 GB SD card. For some reason, the imager makes four partition and which left the ext4 with 300 Mb of free space while the the last one is unallocated ~ 27 GB. Disaster in the making!

Used Gparted to resize ext4 to use all free space.

Configured new installation and transferred all Documents and Scripts. Installed Domoticz and restored the last backup. Some devices did not respond to master Z-STICK GEN5 CONTROLLER ZZW090-C(868.42 MHz) but within the hour all was connected.

The curious thing was that both Safari and Chromium browsers could not properly access the Domoticz server while Firefox could. I tried looking at the security settings in both browsers and Domoticz but could not find anything out of the ordinary.

Today all browsers seem to be happy! The wonders of science. Something changed, I just need to figure what did. I remember that the wise words from my first computer science teacher in high school: Computers are not intelligent they just do exactly what we tell them and not what we want!

Please note that Bullseye uses Debian crontab which involves directories where one stores scripts to be executed at least that one possible way to use this tool. Please refer to https://wiki.debian.org/cron for more details.

Domoticz runs some diagnostics scripts tracking load and memory usage. Note that memory load is now around 36 %.

So far so good!

I hope this helps anyone who procrastinates with doing the wild move.

Code: Select all

RPI in Bullseye (64-bit OS) & Domoticz Version: 2022.1
Build Hash: c9526851b
Compile Date: 2022-01-31 09:34:32

RPI Information

Code: Select all

Linux version 5.15.32-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022

Hardware	: BCM2835
Revision	: a020d3
Serial		: 00000000cc7e2232
Model		: Raspberry Pi 3 Model B Plus Rev 1.3
H264:	H264=enabled
MPG2:	MPG2=disabled
WVC1:	WVC1=disabled
MPG4:	MPG4=enabled
MJPG:	MJPG=enabled
WMV9:	WMV9=disabled