I think you're absolutely right! I patched the code and a new beta 1(6330) is (shortly) available Hope this solves your issue... but you are sending lots of notifications if this is causing issues... :mrgreen: Thank you very much! It happens after a while so it's not that many notifications in 2 ...

Sorry, can't help you with this as I'm not the author of this class, and don't use Kodi (and this hardware) I had a small look at the code, and it seems there is only one place where a new socket is made: "CKodiNode::handleConnect()" All looks ok... but I believe you found an issue! Maybe that is ...

Ha! I think I've found the issue, every time a notification (or test message via settings) is sent to Kodi Media Player (whether online or offline) a new UDP entry appears: sudo lsof -p 3467223 | grep UDP domoticz 3467223 domoticz 33u IPv4 21305033 0t0 UDP all-systems.mcast.net:9777 domoticz 3467223 ...

Version: 2024.7 Platform: Ubuntu 22.04 LTS VM on ESXi 7 Plugin/Hardware: SolarEdge Web API, P1 meter (USB), RFXCOM433E (USB), OpenZWave via ZMEEUZB1 (disabled), MQTT Auto Discovery Client Gateway ZWave-JS-UI, Philips Hue bridge, Kodi Media server, Panasonic TV, OWM (disabled), BuienRadar, two Dahua ...

Then it seems perhaps an issue with blocky. I don't use that. But as the Camara wiki states you can link a (dummy) switch to a camera so when that switch is switched a screenshot can be sent. If that works it is a blockly issue. https://www.domoticz.com/wiki/Camera_Setup#Connect_to_Switch.2FLight ...

Technically sending snapshots is working with a Gmail account. I use it too. But perhaps there is some local storage going wrong?As you seem to have Ubuntu running as a VM? As a test you can also use a dummy switch and attach it to the camera to have a snapshot sent. You are able to see the camera ...

Version 2024.7 Platform Ubuntu 22.04 LTS VM on ESXi 7 Description: Hi, I'm trying to set up the following blockly. blockly2.png What is working: doorbell button is pressed (connected to my fibaro smart implant) both chimes ring. What is not working: 1. the time is ignored for one of the chimes. I ...

seismic.png I'm trying to migrate to zwave-js-ui and doing replacement of devices in Domoticz 2024.7. However I have a FGMS001 Multi Sensor (protocol version 4.5 chip fw 3.2) where "seismic intensity" isn't reported as "percentage" like before but as a "custom sensor". So I cannot replace it at the ...

Not sure this is the right place but I want to share my successfull addition of HomeWizard Watermeter in Domoticz. First start by looking up the IP address the Watermeter is using. Then add hardware type HTTP/HTTPS poller in domoticz using the url with IP address including the API: http://your-ip ...

I think I've figured it out what is causing some migration problems for people like sincze, Eugene and me! The problem seems to be Z-Wave SDK related and thus a tutorial issue! What I did to solve my problem was; I moved the "S2 Unauthenticated key" (which was my Domoticz Z-Wave Security Network Key ...

Could it be that I should have left out a key for S2 authenticated and S2 access control? I've generated them like I did with S0 legacy.

An update from my side. I"ve upgraded my zwave.me zme_uzb1 stick to FW 5.39 and SDK 6.82.1 after spinning up a Z-Way container. I've just started my Zwave-js-ui container. Currently 5 devices are recognized. I still see "error: invalid auth code" messages appearing in the log unfortunately..

Hello all, Yesterday I've tried jumping on the train called zwave-js-ui. I'm running Domoticz 2024.4 on a Ubuntu 22.04 LTS VM on ESXI7. I have like 30 ZWave devices hooked up on my zwave.me zme-uzb1 USB device which is running: fw 5.5 (aka 5.05?) sdk 6.51.6 (aka 6.51.06?) Most, if not all, are zwave ...

I'm looking forward into migrating to Domoticz 2021.1 in a Docker container preferably. Currently I'm running 2020.2 on Ubuntu 18.04 LTS. The best way, I think, is to upgrade Ubuntu 18.04 to 20.04 first and then upgrade Domoticz 2021.1. Then export database/settings from Domoticz 2021.1 VM to ...

So it's specifically json.htm?... that might have an issue? No it is by design. When you check other JSON's you will see some will work and some will return a 401 UNAUTHORIZED message based on the perceived risk/impact. Maybe a stupid question, but why isn't just simply everything: 401 UNAUTHORIZED ...

DAEMON_ARGS="$DAEMON_ARGS -www 0" Thanks for pointing that one out, waaren. It seems that worked out. Regarding the "local network (no network password)" that one is empty. I'm accessing domoticz on my local network, yes. To point it a little bit more out. "I still can access https://domoticz/json ...

I have two questions regarding my installation of Domoticz 2020.2 on Ubuntu 18.04. I'm trying to get my domoticz more secure. 1. How can I completely disable HTTP ? I want to use HTTPS only. I have searched the internet but couldn't find it. 2. I've set: website security with a password in settings ...

I think I've figured it out, I've copied the contents of the zwcfg_0x......xml file from the x32 VM to the x64 VM. Now Z-Wave seems to be fully working!

I've fixed a Python error based on the log file: But still the zwave sensors aren't adopted.. are there any other (OZW) requirements?

Btw, these are my tty settings on both x32 and x64 VMs. RFXCOM: /dev/ttyUSB0 P1 meter: /dev/ttyUSB1 Zwave.me: /dev/ttyACM0 I did "sudo usermod -a -G dialout domoticz" Is ttyACM0 also a "dialout" device? I found myself an answer: domoticz2:~$ ls -l /dev/ttyACM0 crw-rw---- 1 root dialout 166, 0 Oct ...