Domoticz

I just bought a sonoff zigbee 3.0 zbdongle -p.

can this be used in domoticz?
if so which plugin should i use?

i currently using zigate plugin but it seems like the zigbee devices keeps loosing connection, so i thought that i would try this sonoff stick instead.

Yes, you can use the same plugin you used. Only select the correct stick type in the hardware gateway. It is all in the plugin wiki. You have to redo the device pairing to the stick for all zigbee devices but all Domoticz devices will stay the same as they are recognized on zigbee ID.

I did the same a year ago and do not regret it. Much more stable zigbee network.

thank you for your quick reply.

i have tried the same plugins as i use for the zigate, but it doesnt seem to work, i get these error messages:

2023-12-09 00:16:44.073 Error: Sonoff: - unplug/plug the zigate
2023-12-09 00:16:49.055 Error: Sonoff: Plugin is not started ...
2023-12-09 00:16:49.055 Error: Sonoff: - Communication issue with the Zigate
2023-12-09 00:16:49.055 Error: Sonoff: - restart once the plugin, and if this remain the same

i never replaced the zigate plugin with the newer zigbeefordomoticz plugin, can that be the problem?
can i runt both the old zigate lugin and the zigbeefordomoticz plugin at the same time?
just to see if i can get the sonoff stick to work vefore i delete the zigate plugin?

i tried to install according to the installation process and i get this error message nwhen i try to install : sudo pip3 install -r requirements.txt


sudo pip3 install -r requirements.txt
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting zigpy==0.59.0 (from -r requirements.txt (line 1))
Could not find a version that satisfies the requirement zigpy==0.59.0 (from -r requirements.txt (line 1)) (from versions: 0.0.1, 0.0.2, 0.0.3, 0.1.0, 0.2.0, 0.20.0a1, 0.20a2, 0.20.0, 0.20.1a1, 0.20.1a2, 0.20.1a3, 0.20.1, 0.20.2, 0.20.3, 0.20.4, 0.21.0, 0.22.0, 0.22.1, 0.22.2, 0.23.0, 0.23.1, 0.23.2, 0.24.0, 0.24.1, 0.24.2, 0.24.3, 0.25.0, 0.26.0, 0.27.0, 0.27.1, 0.28.0, 0.28.1, 0.28.2, 0.29.0, 0.30.0, 0.30.1, 0.31.0, 0.32.0, 0.33.0, 0.34.0, 0.35.0, 0.35.1, 0.35.2, 0.36.0, 0.36.1, 0.36.2, 0.37.0, 0.37.1, 0.37.2, 0.38.0, 0.39.0, 0.40.0, 0.41.0, 0.42.0, 0.43.0, 0.44.1, 0.44.2, 0.45.0.dev0, 0.45.0, 0.45.1, 0.46.0, 0.47.0, 0.47.1, 0.47.2, 0.50.1, 0.50.2, 0.50.3, 0.51.0, 0.51.1, 0.51.2, 0.51.3, 0.51.4, 0.51.5, 0.51.6)
No matching distribution found for zigpy==0.59.0 (from -r requirements.txt (line 1))



what should i do?

Yes, you should be on the newest zigbee for Domoticz plugin version (now version 7).
Perhaps @pipiche can assist for the zigpy install error.

The error is strange as there is already even an newer zigpy module.
Did you update your system with
sudo apt update
sudo apt upgrade

tjabas wrote: ↑Saturday 09 December 2023 0:27 i have tried the same plugins as i use for the zigate, but it doesnt seem to work, i get these error messages:
2023-12-09 00:16:44.073 Error: Sonoff: - unplug/plug the zigate
2023-12-09 00:16:49.055 Error: Sonoff: Plugin is not started ...
2023-12-09 00:16:49.055 Error: Sonoff: - Communication issue with the Zigate
2023-12-09 00:16:49.055 Error: Sonoff: - restart once the plugin, and if this remain the same

Did you replace the coordinator model in the DomoticZ plugins parameters page ?

You do not need to create a new instance of the plugin, otherwise you'll have to start for the beginning. By keeping the same plugin instance, you'll just need to pair again all the devices : the plugin will be able to recognize the object you already add.

The ZiGate plugin has only be renamed in ZigBeeForDomoticZ when we opened it to other coordinator than ZiGate. There are no changes to do.

Please give us all the starting logs.

What type of Coordinator Model did you select in plugin ?

Silicon Labs EZSP - for dongle-E
Texas Instruments - ZNP for dongle-P

thank you for your help, i use a dongel-P

i will try to get this running later in the evening.

keros wrote: ↑Sunday 10 December 2023 1:04

tjabas wrote: ↑Saturday 09 December 2023 0:27 i have tried the same plugins as i use for the zigate, but it doesnt seem to work, i get these error messages:
2023-12-09 00:16:44.073 Error: Sonoff: - unplug/plug the zigate
2023-12-09 00:16:49.055 Error: Sonoff: Plugin is not started ...
2023-12-09 00:16:49.055 Error: Sonoff: - Communication issue with the Zigate
2023-12-09 00:16:49.055 Error: Sonoff: - restart once the plugin, and if this remain the same

Did you replace the coordinator model in the DomoticZ plugins parameters page ?

You do not need to create a new instance of the plugin, otherwise you'll have to start for the beginning. By keeping the same plugin instance, you'll just need to pair again all the devices : the plugin will be able to recognize the object you already add.

The ZiGate plugin has only be renamed in ZigBeeForDomoticZ when we opened it to other coordinator than ZiGate. There are no changes to do.

Please give us all the starting logs.

yes i did choose the right model in the cordinator page,
but when i save the config in the hardware page the name still are zigate, not zigbeefordomoticz. thats kind of strange.

Can you put a screenshot of your DomoticZ plugins parameters page with the plugin selected in order for us to see the parameters ?

waltervl wrote: ↑Saturday 09 December 2023 11:03 Yes, you should be on the newest zigbee for Domoticz plugin version (now version 7).
Perhaps @pipiche can assist for the zigpy install error.

should i remove the old zigate plugin first?

im currently running buster and i guess that this can be the problem, should i upgrade to the latest , i think its called bookworm?
or should i upgrade to bullseye?

trying to upgrade from buster to bullseye wasnt easy at all, and i still havent figured it out, i found a script that seems to automize the installation, but i cant figure out how to run this script, could anyone help me?

#!/bin/bash

errexit()
{
echo ""
echo "$1"
echo ""
exit 1
}

if [ $(id -u) -ne 0 ]; then
errexit "Must be run as root user: sudo $0"
fi
OSVER="$(sed -n 's|^VERSION=".*(\(.*\))"|\1|p' /etc/os-release)"
if [ "${OSVER}" != "buster" ]; then
errexit "Unsupported operating system: ${OSVER}"
fi
echo ""
echo -n "Ok to upgrade Buster to Bullseye (y/n)? "
while read -r -n 1 -s answer; do
if [[ ${answer} = [yYnN] ]]; then
echo "${answer}"
if [[ ${answer} = [yY] ]]; then
break
else
errexit "Aborted"
fi
fi
done
echo ""

if [ -e /etc/apt/listchanges.conf ]; then
sed -i 's/frontend=pager/frontend=text/' /etc/apt/listchanges.conf
fi
apt-get -y update
apt-get -y upgrade
apt-get -y dist-upgrade
apt-get -y update
apt-get -y autoremove
apt-get -y clean
if [ -e /etc/apt/listchanges.conf ]; then
sed -i 's/frontend=text/frontend=pager/' /etc/apt/listchanges.conf
fi

ARCH="$(file -b /bin/bash | sed -n 's|^.*, \(ARM\s*\S*\),.*$|\1|p')"
if [ "${ARCH}" = "ARM" ]; then
sed -i 's|^deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi$|deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi|' /etc/apt/sources.list
sed -i 's|^deb http://archive.raspberrypi.org/debian/ buster main$|deb http://archive.raspberrypi.org/debian/ bullseye main|' /etc/apt/sources.list.d/raspi.list
elif [ "${ARCH}" = "ARM aarch64" ]; then
sed -i 's|^deb http://deb.debian.org/debian buster main contrib non-free$|deb http://deb.debian.org/debian bullseye main contrib non-free|' /etc/apt/sources.list
sed -i 's|^deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free$|# deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free|' /etc/apt/sources.list
sed -i 's|^deb http://deb.debian.org/debian buster-updates main contrib non-free$|deb http://deb.debian.org/debian bullseye-updates main contrib non-free|' /etc/apt/sources.list
sed -i 's|^deb http://archive.raspberrypi.org/debian/ buster main$|deb http://archive.raspberrypi.org/debian/ bullseye main|' /etc/apt/sources.list.d/raspi.list
else
errexit "Unsupported architecture: ${ARCH}"
fi

if [ -e /etc/apt/listchanges.conf ]; then
sed -i 's/frontend=pager/frontend=text/' /etc/apt/listchanges.conf
fi
apt-get -y update
apt-get -y upgrade
apt-get -y install gcc-8-base
apt-get -y dist-upgrade
apt-get -y autoremove
dpkg --configure -a
apt -y update
apt -y full-upgrade
apt -y autoremove
apt -y clean
if [ -e /etc/apt/listchanges.conf ]; then
sed -i 's/frontend=text/frontend=pager/' /etc/apt/listchanges.conf
fi

echo ""
echo "Reboot required"
echo ""
echo -n "Reboot now (y/n)? "
while read -r -n 1 -s answer; do
if [[ ${answer} = [yYnN] ]]; then
echo "${answer}"
if [[ ${answer} = [yY] ]]; then
shutdown -r now
fi
break
fi
done
echo ""

I've just done the upgrade from buster to bullseye by following this, worked first time
https://www.tomshardware.com/how-to/upg ... rom-buster

I also did the upgrade after from bullseye to bookworkby following this
https://dev.blues.io/blog/easiest-upgra ... -bookworm/

I used the easy option, you have to do buster - bullseye - bookworm though, you can't just miss out bullseye, and they can take a while so be prepared to sit back and wait, just for the record I also went with the default options when asked.

Dave21w wrote: ↑Monday 11 December 2023 8:47 I've just done the upgrade from buster to bullseye by following this, worked first time
https://www.tomshardware.com/how-to/upg ... rom-buster

I also did the upgrade after from bullseye to bookworkby following this
https://dev.blues.io/blog/easiest-upgra ... -bookworm/

I used the easy option, you have to do buster - bullseye - bookworm though, you can't just miss out bullseye, and they can take a while so be prepared to sit back and wait, just for the record I also went with the default options when asked.

Thanks for your reply.

I tried that first conversion to bullseye but it didn't work for me.
At one instance the update told me to reboot the rpi, but in the guide a reboot wasn't mentioned so I didn't reboot and just followed the guide, after everything was installed I rebooted but I still was on buster.
Should I have rebooted when the putty installation told me to do so?

There is no putty installation in the manual, but if a computer asks you to reboot it is better to do so. Seems as your current system was not up to date on Buster already.

And sometimes it easier to buy a new SD card and start with a fresh install of Bookworm.

waltervl wrote: ↑Monday 11 December 2023 11:45 And sometimes it easier to buy a new SD card and start with a fresh install of Bookworm.

But I also have alot of scripts and other programmes installed on the sd card, can these be copied over to the new one or do I have to install everything again?

Ideally you should be able to copy the complete domoticz folder including your scripts to the new server after installing the same version of Domoticz.
You perhaps have to set some exec access rights again for your scripts.

If you have a lot of other programs (not domoticz related) then you have to check for those too.
But as said: Sometimes it is easier, sometimes it is not....

For safety it as also wise to make a backup of your current SD in case things are failing during update.