Hi, I ran into trouble updating the Z4D module. Updating from the web page did not work. Git pull and hard reset etc succeeded but I got an error
Backend error - unknown error.
I updated de Venv with the requirements. but it still gives the error. The log file states:
2026-02-10 19:00:29.621 Error: for Domoticz: Looks like zigpy==0.83.0 Python module is not installed or does not meet the required version. Requires 0.83.0, Installed 0.80.0.Make sure to install the required Python3 module with the correct version.
I think the venV is showing 0.82
Could it be that zigpy versions are out of sync?
Z4D upgrade failing - zigpy version conflict?
Moderator: leecollings
-
lost
- Posts: 699
- Joined: Thursday 10 November 2016 9:30
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Z4D upgrade failing - zigpy version conflict?
I did update from 7.1.025 to 027 from Z4D webUI on 08 feb and got nothing printed in the process on the webUI. As it seemed a bit long without any prints, I ssh'ed on the PI to see some processes from the upgrade where still ongoing so I did wait until there was no more and disabled then re-enabled the plugin from Domoticz.
After that, the plugin pages showed "Plugin: 7.1.027 [7.525]"...
So looks it finally succeded...
After 1 day, I had an unexpected PI restart (no log to understand why, unfortunately, but most probably not linked to Z4D upgrade) and after restart, a python service linked to Domoticz (not a plugin, only using the HTTP/Json API) using serial could not start.
The error message was about serial.Serial() not present but turned out that this was the serial module that was updated at the date of Z4D with permissions that prevented loading by my own python code. After changing permissions to a+rx for directory and a+r recursively for anything under my own service was able to start again:
Extract (ls -alrt) of my /usr/local/lib/python3.9/dist-packages/ (may vary with your python version), shows serial did have same permissions as other modules updated on 08/02 before changing this on par with others/not updated by Z4D:
Looking at /usr/local/lib/pythonX.Y/dist-packages/ will show what was changed at the date of upgrade... if you are not already on a more recent version of raspbian that requires to install using a venv, in such case this'll be in the venv...
After that, the plugin pages showed "Plugin: 7.1.027 [7.525]"...
So looks it finally succeded...
After 1 day, I had an unexpected PI restart (no log to understand why, unfortunately, but most probably not linked to Z4D upgrade) and after restart, a python service linked to Domoticz (not a plugin, only using the HTTP/Json API) using serial could not start.
The error message was about serial.Serial() not present but turned out that this was the serial module that was updated at the date of Z4D with permissions that prevented loading by my own python code. After changing permissions to a+rx for directory and a+r recursively for anything under my own service was able to start again:
Extract (ls -alrt) of my /usr/local/lib/python3.9/dist-packages/ (may vary with your python version), shows serial did have same permissions as other modules updated on 08/02 before changing this on par with others/not updated by Z4D:
Code: Select all
drwxr-x--- 4 root root 4096 Feb 8 20:23 z4d_certified_devices
drwxr-x--- 3 root root 4096 Feb 8 20:23 z4d_certified_devices-7.525.dist-info
drwxr-xr-x 6 root root 4096 Feb 8 20:23 serial
drwxr-x--- 2 root root 4096 Feb 8 20:23 pyserial-3.5.dist-info-
hyeronimo
- Posts: 68
- Joined: Saturday 11 March 2023 8:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Z4D upgrade failing - zigpy version conflict?
Thanks, I will look into that. Anyway, probably I will have to find a way to update Zigpy 0.82 to 0.83 first
-
hyeronimo
- Posts: 68
- Joined: Saturday 11 March 2023 8:33
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Z4D upgrade failing - zigpy version conflict?
Ok, after a lot of effort I have it working again. version 7.1.027
Even deleting and uninstalling did not work. So to document what worked for me:
I have VenV installed according to:
cd /home/pi
mkdir Domoticz_Python_Environment
python3 -m venv Domoticz_Python_Environment
source Domoticz_Python_Environment/bin/activate
pip install --upgrade pip
And of course, update Z4D for the Domoticz-Zigbee folder with: git pull
Then Install the required python3 modules:
source Domoticz_Python_Environment/bin/activate
cd /home/pi/domoticz/plugins/Domoticz-Zigbee
python3 -m pip install -r requirements.txt --upgrade
Then edit domoticz.sh in etc/init.d:
to include
export VIRTUAL_ENV=/home/pi/Domoticz_Python_Environment
export PATH="/home/pi/Domoticz_Python_Environment/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
! Note that the command in the
https://zigbeefordomoticz.github.io/wik ... to-stable8
contains an additional " that breaks the domoticz startup
Even deleting and uninstalling did not work. So to document what worked for me:
I have VenV installed according to:
cd /home/pi
mkdir Domoticz_Python_Environment
python3 -m venv Domoticz_Python_Environment
source Domoticz_Python_Environment/bin/activate
pip install --upgrade pip
And of course, update Z4D for the Domoticz-Zigbee folder with: git pull
Then Install the required python3 modules:
source Domoticz_Python_Environment/bin/activate
cd /home/pi/domoticz/plugins/Domoticz-Zigbee
python3 -m pip install -r requirements.txt --upgrade
Then edit domoticz.sh in etc/init.d:
to include
export VIRTUAL_ENV=/home/pi/Domoticz_Python_Environment
export PATH="/home/pi/Domoticz_Python_Environment/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
! Note that the command in the
https://zigbeefordomoticz.github.io/wik ... to-stable8
contains an additional " that breaks the domoticz startup
Who is online
Users browsing this forum: No registered users and 1 guest