Domoticz Community Forum - Support & Discussion

Join 16,000+ members discussing home automation with Domoticz. Get help with Zigbee, ZWave, MQTT, scripting, and 150+ integrations
https://forum.domoticz.com/

DZVents/LUA LOG disabled but still flooding in LOG

https://forum.domoticz.com/viewtopic.php?t=45206

Page 1 of 1

DZVents/LUA LOG disabled but still flooding in LOG

Posted: Wednesday 16 September 2026 16:20
by BarryT
{336D2FC0-EF7B-4BD8-8768-94FA8FFAA453}.png
{336D2FC0-EF7B-4BD8-8768-94FA8FFAA453}.png (10.99 KiB) Viewed 178 times
Domoticz V2026.3
Build Hash b57fc4687
Compile Date 2026-09-07 16:35:47
dzVents Version 3.1.11
Python Version 3.13.5 (main, Jul 15 2026, 20:25:40) [GCC 14.2.0]

As the title say, we disabled the LOG function of DZvents / LUA, but these messages are still flooding our log.

Code: Select all

2026-09-16 14:14:00.302  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:14:00.508  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 14:14:34.483  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:14:34.720  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 14:18:53.321  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:18:53.525  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 14:22:49.251  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:22:49.490  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 14:31:46.461  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:31:46.684  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 14:33:36.363  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:33:36.588  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 14:43:52.434  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:43:52.650  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 14:53:16.095  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:53:16.322  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 14:56:23.045  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:56:23.276  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:05:38.605  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:05:38.838  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:07:01.956  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:07:02.183  Status: setcolbrightnessvalue: ID: d6d, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:15:44.957  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:15:45.189  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 15:15:59.606  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:15:59.817  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:29:04.125  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:29:04.353  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:29:59.729  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:29:59.942  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 15:30:05.484  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:30:05.691  Status: setcolbrightnessvalue: ID: d6d, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:35:14.511  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:35:14.731  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:37:38.748  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:37:38.953  Status: setcolbrightnessvalue: ID: 13f3, bri: 100, color: '{m: 4, RGB: 000000, CWWW: 00ff, CT: 0}'
2026-09-16 15:40:55.319  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:40:55.528  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
How can we disabled these messages?
Thanks.

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Wednesday 16 September 2026 17:06
by waltervl
What logging definition is used in the script?

Edit: This logs probably also popup because dzvents uses a Domoticz API URL to set the color. Setting color is not supported by the normal dzvents itegration so the developer took a detour over the API.....

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Wednesday 16 September 2026 17:09
by BarryT
waltervl wrote: Wednesday 16 September 2026 17:06 What logging definition is used in the script?
None, there is no extra logging activated in every scripts.

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Wednesday 16 September 2026 17:12
by waltervl
waltervl wrote: Wednesday 16 September 2026 17:06 Edit: This logs probably also popup because dzvents uses a Domoticz API URL to set the color. Setting color is not supported by the normal dzvents integration so the developer took a detour over the API.....

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Thursday 17 September 2026 8:22
by BarryT
waltervl wrote: Wednesday 16 September 2026 17:12
waltervl wrote: Wednesday 16 September 2026 17:06 Edit: This logs probably also popup because dzvents uses a Domoticz API URL to set the color. Setting color is not supported by the normal dzvents integration so the developer took a detour over the API.....
Aha... Okay, thanks.
Is there any way to disable or hide these messages, often it is really annoying :-(

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Thursday 17 September 2026 13:27
by waltervl
Perhaps make your scripts so that it only changes the color when it really needs so. Looking at a snippet of your log you for example send the same command 3 times.

Code: Select all

2026-09-16 14:56:23.045  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 14:56:23.276  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:05:38.605  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:05:38.838  Status: setcolbrightnessvalue: ID: d87, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'
2026-09-16 15:07:01.956  Status: EventSystem: Opening a URL after 0.2 seconds...
2026-09-16 15:07:02.183  Status: setcolbrightnessvalue: ID: d6d, bri: 100, color: '{m: 2, RGB: 000000, CWWW: 0000, CT: 150}'

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Thursday 17 September 2026 19:09
by BarryT
I tried that as well, but all that dzVents "openURL" keeps flooding our log.
It's really a pain in the ass, especially since we have a lot of them — 103 Zigbee/Shelly/Tasmota/other light bulbs as well — that can only be RGBWW-controlled by using JSON in dzVents.
We have a lot of motion sensors all around the house, and every time you walk past a sensor, we see that OpenURL message in the log.
Since we have a lot of individual bulbs that are not part of any group or scene, we need to send the color and ON state to every device, for example when motion is detected.
There is simply no other easy way to turn the bulbs ON with the exact color we need/want for each individual lamp/device.
I was very happy using Domoticz for over 14 years, but for reasons like this alone, I'm finding myself more and more tempted to switch to Home Assistant instead of continuing to use Domoticz.

The reason is simple:
Every bulb has its on color, its timebased (day=daylight/night=smooth romantic / cleaning house=all bright 100% on, etc) and that to every bulb.
It works perfectly, but only the log is not funny.

I also tried a very simple piece of code like this, but I still get the exact same message in the log:

Status: setcolbrightnessvalue: ID: d30, bri: 100, color: '{m: 3, RGB: 00ff00, CWWW: ff00, CT: 0}'

Code: Select all

return {
    on = {
        timer = {'every minute'}
    },
    execute = function(domoticz)
        local lamp = domoticz.devices('HueBureauLampLinks')
        lamp.setColor(0, 255, 0)
        lamp.switchOn().forSec(45)
    end
}
I simply do NOT want messages like these in the log, because they are completely useless to us.
I really hope there is, or will be, an option to disable or hide these "EventSystem"/"OpenURL" messages in the log, and have them appear only when I explicitly request them from the script, for example:

Code: Select all

local function log(msg)
    print("Verlichting: " .. msg)
-- OR
    print("EventSystem: " .. msg)
end
Nothing more, nothing less. :-)

Re: DZVents/LUA LOG disabled but still flooding in LOG

Posted: Thursday 17 September 2026 22:49
by waltervl
You could try to not set the color first but only switch on/off. Normally the color will be memorised (at least with my zigbee bulbs).

End the best option would be to have dzvents have an integrated setColor function.
All times are UTC+02:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited