Upgrading from VERY old beta version of Domoticz

[JonathanLondon]

Hi

I am trying to update from a very old beta release

Version: 2022.1 (build 14525)
Build Hash: 8733c84c9
Compile Date: 2022-10-02 10:00:00
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0]

running on a Raspberry Pi 3b with the very old Debian 10.13 to the latest stable Domoticz release running on the lastest Raspberry Pi OS (64-bit) Debian Trixie.

I have two USB devices:

Bus 001 Device 004: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC

ZWave OpenZWave USB Version: 1.6-1911-gc6a420ef /dev/serial/by-id/usb-0658_0200-if00
RFXtrx433 RFXCOM - RFXtrx433 USB 433.92MHz Transceiver Version: Ext2/1025 /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A120OBEE-if00-port0

I built a brand new Pi installation, and installed the latest Domoticz (curl -L install.domoticz.com | bash)

I then copied over the SSL certificates, LUA scripts, and domoticz.db file from my old installation, and in the settings, told it to use stable releases.

At start-up everything seems OK, with the following exceptions:

1. One of my ZWave devices had disappeared
2. The dashboard tab only had scenes, but no lights/switches (but they were easily added back)

However, in the Setup>Hardware tab, there are no devices showing. But ZWave and RF entities work just fine. I tried adding the USB devices, but they do not appear.

After a short period, the ZWave entities drop offline. RF devices continue to work

I have reverted to the old hardware, and everything is back to normal, including the missing ZWave entity.

Is there something else I should be doing instead? Should I restore the complete domoticz installation directory onto the new OS/hardware, and attempt the Domoticz update there?

I noticed in the log file there was an error about OpenZWave versus a newer ZWave subsystem.

Advice (or HOW TO pointers) gratefully received.

Thank you.

[globetrotter]

Maybe something because of this: https://raspberrypi.stackexchange.com/q ... i-domoticz

I installed Raspberry Pi OS 11. And downgraded the kernel to 6.1. After that it worked for me. In Pi OS 12 I got errors while downgrading kernel.

I also blocked updating for kernel:
sudo apt-mark hold raspberrypi-kernel raspberrypi-bootloader

[jannl]

Running bookworm, with kernel 6.12 and zwave-js-ui without problems on a Pi 5.
Remember to have the zwave usb in a asb 2 slot and that a pi5 handles usb boot differently, resulting in usb communication errors because of timing issues. lsusb -v solves when issued before starting the usb stichs (zwave and zigbee) in my case. Timing issues could be related to the use of an usb hub. Google gives a lot of info on this.

[JonathanLondon]

Thanks folks, you've given me some routes to explore.

I see references to Docker and ZWave JS UI, which don't apply, but also to Aeotic sticks hanging Pi 3Bs. What I noticed was that access to entities hanging off the Aeotec fail, but accesses to devices hanging off the RFXtrx433 continue to work.

I'll try the

Raspberry pi file
/boot/firmware/config.txt
add last line under [all] :

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Zwave Stick USB hang
[all]
dtoverlay=dwc2

fix and report back.

[JonathanLondon]

So it's been quite a journey but I hope I'm there now.

Some of these things might seem obvious, but I found out the hard way!

Along the way...

• The old version was on a 32-bit operating system, and importing the database into a 64-bit operating system didn't work

• When using the Raspberry Pi OS Lite 32-bit distro, there's a missing USB library which needed

  Code: Select all

  apt-get install libusb-0.1-4

• I ended up installing the new Domoticz (hence systemd/rc-scripts etc), then replaced /home/pi/domoticz with the old version (which wouldn't run due to a missing ssl library) and then updated to the latest current release. That had the advantage of preserving certificates for HSTS etc.

• My Domoticz dashboard was lost in the process (easy to recreate, just "favourite" the devices in the Switch screen)

• One of my ZWave TKBs has gone walkies - not a big surprise, but it reappears if I revert to the old system. I'll do a "replace hardware" and deal with any fallout

• The way Raspberry Pi OS sets a static IP has changed (bloomin' network manager, previously dhcpcd.conf) resulting in no IP address at all

• I have set dtoverlay=dwc2 in the firmware config

I hope this is of use to someone.

[Thorgal789]

The old version was on a 32-bit operating system, and importing the database into a 64-bit operating system didn't work

Seriously ? But by definition it's just data, SQL data, why the OS architecture have an impact on it ?

[JonathanLondon]

I am guessing some data (might even be an SQLlite issue) is stored in binary blobs. I didn't try dumping out the contents of the database from the old 32 bit version, and importing it to the new 64 bit. I just transferred the file.

But that's a guess. Once I found a working solution, I patched up a few bits around the edges (dashboard, and blind delay timers) and it's job done.

[gizmocuz]

As mentioned above, the database has nothing to do with 32 or 64 bit. it is just a database.
If you have issues, you could edit the database in SQLite Expert Personal Edition, go to the hardware tab, disable all hardware and exit
Next start Domoticz, it should just start, next enabling hardware one by one to see it that is the issue