OK, logging is running.
The system uptime is 42 days, while it happend atleast 2 times in de last 3 weeks.
In my opinion shutdown/poweroutages/etc can't be the problem.

Will post as much as possible when it happens again.

Thanks!

It happend a couple of times now, the storage is a brand new (2,5 month old) Crucial MX500 250GB SSD with ~10% used.
I dare to say its not the storage.

I'm running the last Beta version .10732 before going to OZW 1.6 Since a couple of weeks now and then I get this error; Error: EventSystem: in /home/XXX/dev-domoticz/dzVents/runtime/dzVents.lua: /home/XXX/dev-domoticz/dzVents/runtime/EventHelpers.lua:90: attempt to index local 'fileStorage' (a ...

I'm running LUbuntu 19.04 with 12 docker containers on a NUC with 256g ssd and 8g mem. Performance is totally no issue. The high Python number is caused by Home-Assistant. The high Java number is caused by the Ubiquiti Unifi-Controller. The high Domoticz number is caused by.... xx@xx:~$ [b]sudo lsof ...

Ok, this evening another "to many files..": 2019-06-14 22:03:35.260 Error: EventSystem: in /home/marco/dev-domoticz/dzVents/runtime/dzVents.lua: cannot open /home/marco/dev-domoticz/dzVents/runtime/dzVents.lua: Too many open files Here the output of the above commands; xx@dxx:~$ echo Top 20 ...

OK, had Home-Assistant for testing running in a Docker container. Stopped HA and Python is of the list. That keeps Java all alone on top, thinking that the Ubiquiti Unifi Controller container is the next potential point to look at. 31046 2910 java 9546 3141 mongod 4002 27237 domoticz 3432 1150 ...

ok will do! you having this prepare/ready, means it happens more often? monitoring the top20 for about 10mins and don't see any changing figures. What are the figures saying? Here's a first report; 30666 2910 java 17425 1844 python 7067 3141 mongod 3696 1150 dockerd 3625 27237 domoticz 2635 1738 ...

Since a few weeks my domoticz "randomly" isn't reachable on its webserver and all LUA scripts aren't working. Looking at the Domoticz Logfile i see this message constantly showing up: 2019-06-10 11:47:43.548 Error: EventSystem: in /home/XXXX/dev-domoticz/dzVents/runtime/dzVents.lua: cannot open ...

Does any body has found a weather service which provides the expected outside temperature for the next day? Looked at some services, installed a couple of them, but non I found expose the value and only some have it in a prediction text string. Hopefully someone already found one or is using/getting ...

Any idea what's causing it?

Don't known if its matter, but thats a virtual/dummy device and i'm using a Z-Wave device. When I use a dummy device with the name "Badkamer verlichting3", then it's also working fine; Screenshot - 31_01_2019 , 19_22_27.png And the strange thing is... When I add a * the the "on" trigger in the ...

Looks like it has something to do with the lenght of the devicename;
Devicename "Badkamer verlichtin" is working is expected
Devicename "Badkamer verlichting" is not working as expected

Here's the script I use to test the UserVariables, no rocket science.: return { on = { variables = {'BadkVerwarmingOffTime','BadkVerwarmingOnTime'} }, logging = { level = domoticz.LOG_DEBUG, -- change to LOG_ERROR after you tested the script marker = "Return::on::variables::" }, execute = function ...

Did some testing with the Z-Wave device and created an secundary script which triggers on the 2 UserVariable changes. The original script to set the UserVariables send an email notification and the UserVariable change script also send a notification; Screenshot - 30_01_2019 , 21_15_43.png The On ...

In de case of the Z-wave Off command, no change.

log: 2019-01-30 08:38:04.143 OpenZWave: Domoticz has send a Switch command! NodeID: 8 (0x08) 2019-01-30 08:38:04.162 (Zwave) Light/Switch (Badkamer verlichting) 2019-01-30 08:38:04.186 (Zwave) General/Voltage (Voltage) 2019-01-30 08:38:04.497 Status: dzVents: Info: isDevice check: ------ Start ...

Ah ok, had to look 3 times.....

Strange... I now see three difference in my case with your's; 1. I'm using a Z-Wave device, yours is a virtual device, on which I switch from the Domoticz main dashboard view, 2. Not the same device name, 3. The length of the device name, mine is "Badkamer verlichting" (20 chars), your "isDevice ...

OK, used your log script. First tried with an ON/OFF cycle with device "237" Then tried with an ON/OFF cycle with device "Badkamer verlichting" Also waited for the 1 minute timed trigger. The log shows that Here the log; ------------------------------------------------------- - 237/ON, uservariables ...

That's not the case; Screenshot - 28_01_2019 , 16_44_15.png Tried to remove the space from the devicename, so I changed the name from "Badkamer verlichting" to "Badkamerverlichting" and that solved the problem. So it looks like the device name is the problem and most likely its something to do with ...