Varazir wrote: Monday 13 April 2020 14:29
Updated the gist with the dump
Please post the information here in code windows. Over time the information on external sides will be updated or removed and then the posts on this forum does no longer make sense for other members if they search for solutions for their problems. Thx !
I looked at your dump but it only shows a limited number of lines. If you log to an os file you can grab all.
It looks like dzVents is sending the right command to domoticz but domoticz cannot identify any active hardware for the device. No idea why and can be many things.
You could try to send a switchOff when the state == 'On' and vice vesrsa. Maybe that will help you identifying what is happening.
Other things you can try is switch on debug mode in dzVents and domoticz. For dzVents you can do that inside the GUI. For domoticz wide in /etc/init.d/domoticz,sh
The domoticz logfile location and other settings are defined in /etc/init.d/domoticz.sh
the relevant settings are in set to the DAEMON_ARGS var.
with an editor of choice
Code: Select all
DAEMON_ARGS="$DAEMON_ARGS -log /var/log/domoticz.log" # or any other OS file
DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error, debug" # debug disabled for now
#DAEMON_ARGS="$DAEMON_ARGS -loglevel normal,status,error" # these loglevels will make it to the logfile
DAEMON_ARGS="$DAEMON_ARGS -debuglevel normal,hardware,received,webserver,eventsystem,python,thread_id"
sudo systemctl daemon-reload
sudo service domoticz stop
sudo service domoticz start
sudo tail -f /var/log/domoticz.log
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>>
dzVents wiki