This has been a blockly glitch since a few generations. Opening and closing the event and refreshing the page should fix it.

On further examination, "Set Level" also doesn't work in Blockly either, only "Open" and "Close".

I also use this device and I recently had to change a module for exactly the same device using the replace function. The new device doesn't respond to commands in dzVents and throws an error, wether using "open()" , "close()" or "setLevel(50)". 2025-05-24 14:46:31.417 Error: dzVents: There is no ...

What about installing openssl 3 on bullseye/buster ?

Be aware that with Bookworm there is a missing library (libssl?) so Domoticz needs that installed separately beforehand. I happily use zigbee2mqtt in a docker which was easy to move over so I can't help with your other question.

I remember when I started moving from Blockly to dzvents it seemed like my cpu use went up. However dzvents is much much more powerful and I found I came up against Blockly's limits pretty quickly.

Nothing in the logs but while I was asleep the solution came to me ; the newer devices needed to be added in "Set Devices" as they didn't exist when I created the remote user.

Thanks for your help Walter.

Yeah, did that and it was working before and created a test virtual device which still works. services: domoticz: image: domoticz/domoticz:stable container_name: domoticz restart: unless-stopped # Pass devices to container # devices: # - "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyACM0 ...

Is there any reason new devices created on the slave aren't visible on the main Domoticz instance ? I have a previously set up test virtual switch that is working so the basic connection is fine but new devices aren't appearing. I have "allow new devices" enabled and I have tried starting and ...

Thanks walter, I managed to get something working with a python gpio2mqttAD script, still a work in progress but functional. import paho.mqtt.client as mqtt import RPi.GPIO as GPIO import time import json # GPIO setup GPIO.setmode(GPIO.BCM) GPIO.setwarnings(False) # Define relay GPIO pins (BCM ...

I have been trying to follow the GPIO guide on the wiki, however I tried installing "generic sysfs GPIO" but no devices were created. I tried using the command echo 11 > /sys/class/gpio/export but got this error -bash: echo: write error: Invalid argument At this point I tried the second method ...

Bingo, all up and running, thanks a lot jvdz.

Ah , no, I used the standard docker-compose.yml from hub.docker.com/r/domoticz/domoticz.

Good catch !

I am still getting Can not connect to: 192.168.2.34:6144 (Connection refused) in the "Main" domoticz log. I set the trusted network to "192.168.2.*" and enabled "Allow Basic Auth" and still no luck. Otherwise I followed the wiki. The new server is a brand new docker version of domoticz on a ...

Brilliant, thank you jvdz !

In the wiki page for the domoticz remote server there is this line : Configuration Remote1 and Remote2 1. Specify the shared port (6144 by default) where the Main will connect to. But it is not specified where this is to be entered. In the log of the main I get this repeated ; Can not connect to ...

It's been like that since the big roller shutter shake up crisis. I rarely see it because I don't control my shutters directly usually.

jvdz wrote: ↑Sunday 06 April 2025 17:52 Show the whole script so we can check what the reason might be as sunriseInMinutes & sunsetInMinutes functions do exist.

Apologies, discovered a typo, all good now.

I am trying to get a time value for sunset or time until sunset but I can't find anything documented. "domoticz.time.sunset" and "domoticz.time.sunsetInMinutes" do not work. Is there anywhere this is written down ? (I did check the dzVents wiki but found nothing) sunsetInMinutes gave this error ...

Excellent, thank you, shall try it now.