***CORRECTION*** I rebooted, still the same error. Then I thought that it might be better to copy domoticz from the ~/domoticz/bin directory to the ~/domoticz directory. It worked straight away ! I would have been using it now, f Open ZWave wasn't removed from this build :( So I will start ...

Thank you. I tried this before, and recieved errors. This time I took some more time out for that. Loads of cmake errors, but google was my friend this time and I could fix all the missing dependencies. Finally I could start to run Domoticz $ sudo ./domoticz -www 8088 -sslwww 0 2023-02-27 20:30:31 ...

I am now trying for toooo long to get Domoticz even started on Ubuntu 22.04.1. Docker does not work, so I went back to the normal version. The Domoticz dir structure looks as all is proper, but I run into: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such ...

2023-02-24 07:46:48.495 Error: Tuya: ModuleNotFoundError: No module named 'tuyaha' The module tuyaha is missing from your installation. Thank you for trying to help me. However, as stated - the plugin was installed in ./setup/plugins and domoticz finds these plugins but running the various plugins ...

I removed the docker version again, and am back to the normal version. This gets stuck with: # sudo service domoticz.sh status domoticz.service - domoticz_service Loaded: loaded (/etc/systemd/system/domoticz.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit ...

My appologies for being unclear on that @gizmocuz. My infrastructure is set to consist out of: - The Z-Wave protocol Consisting out of an Aeontec ZWave 500 stick and loads of Fibaro switches and Coolcam sensors and powerplugs - The Zigbee protocol Consisting out of a Dresden Technology Conbee stick ...

This morning I tried to install Tuya once more. It gives the error notification that shows the issue. The plugin directory Domoticz is looking at in it's plugin list (and where I had to install the plugin) is /opt/domoticz/config/plugins. But the plugin itself looks for /opt/domoticz/userdata ...

As expected. Back in Docker, the issue is the same: cd /opt/domoticz ls -al config/ totaal 1492 drwxr-xr-x 3 root root 4096 feb 23 23:06 . drwxr-xr-x 4 root root 4096 feb 23 23:17 .. -rw-r--r-- 1 root root 341 feb 23 23:05 domocookie.txt -rw-r--r-- 1 root root 405504 feb 23 23:20 domoticz.db -rw-r ...

PS. As I read enough people not being able to run Domoticz on Ubuntu, and more people run Domoticz succesfully in Docker, I will already start to deinstall the normal Domoticz and reinstall the docker version. Hoping somebody can tell me a single file to alter to get things running. (and it gives me ...

THIS TOPIC IS SNOWED UNDER BY THE AMOUNT OF MY TRIES TO GET ANY DOMOTICZ WORKING. I AM THEREFOR STARTING A NEW TOPIC. PLEASE DELETE THIS TOPIC. I have uses Domoticz on Pi, but as the SD memory card kept crashing over the years. I now got myself a Intel NUC, running on Ubuntu 22.04.2. (do not read ...

Ok, thank you for that insight.

Thank you. Taking it from level did indeed do the trick in regards to the brightness. However, I still have the issue: - When selecting an RGB color and press ON, all spots now switch on in this color - Altering the brightness also works - When I then select a WW color and press the ON button, all ...

I have a virtual RGBWWZ switch to set all my RGBWWZ-LEDs (Zigbee) with one action. This is my DZvents script: return { on = { devices = { 63, } }, execute = function(domoticz, device) local lightIds = {} for i=1,#domoticz.helpers.SpotsRight do lightIds[#lightIds+1] = domoticz.helpers.SpotsRight[i ...

Good (morning/afternoon/evening), After my domoticz system kept on failing, I decided to start from scratch. However, that was easier said then done. - Install instructions say I have to download raspbian stretch, but I can only download raspbian buster. - After installing the buster version (full ...

Ok, as nobody was able to help me on this, I have expiremented myself and in the end got myself a working program. As others may have the same issues, I add my script code here local setdelay = 10 -- ADD DEVICES JUST ABOVE THE PROGRAM EXECUTION WITH return { -- NO MORE CONFIGURING UNTIL THAT BLOCK ...

Thank you Waaren, but I must have more active fields. This was just an attempt for the proof of concept. The first real life implementation will need 3 parameters per array item, and will be something along the lines of: PSEUDO CODE listgroup : { {RealDeviceID1, VirtualDeviceID1, CorrectionAction ...

At the top of any dzvents script, I can insert some variables, which I for instance use to set up the device list that is used in the "on = {" section. But now I want to go one step further. I want the device array to be set up as a result of other variables. But my proof of concept fails: local ...

pi@raspberrypi:~ $ sudo find /home/pi/domoticz/scripts/dz* -type d -ls 525639 4 drwxr-xr-x 6 pi pi 4096 mei 17 17:51 /home/pi/domoticz/scripts/dzVents 525696 4 drwxr-xr-x 2 pi pi 4096 mei 10 13:18 /home/pi/domoticz/scripts/dzVents/scripts 525666 4 drwxr-xr-x 3 pi pi 4096 mei 10 13:18 /home/pi ...

I had a problem with Domoticz, which turned out to be a full disk. Upon reboot raspbian did not even start anymore. It was due to the log file of OpenZWave that accumulated to about 2GB. Finally I managed to remove that file and reboot the pi. I then used Pi's SD Card Copier to move all from a 8GB ...

2019-05-17 16:20:00.618 Error: EventSystem: in /home/pi/domoticz/dzVents/runtime/dzVents.lua: /home/pi/domoticz/dzVents/runtime/EventHelpers.lua:96: attempt to index local 'fileStorage' (a boolean value) My log is full of this now. Before my raspberry pi SD card was full, so I now copied all to a ...