dzVents domoticz.time object is completely nil (isWeekend, weekday, etc. all nil)

[gomsoo]

Hello everyone,

I'm facing a critical issue where my dzVents event system is not executing any time-based scripts or conditions. Device-triggered scripts work, but anything relying on the domoticz.time object fails because all its properties are returning nil.

My System:

Domoticz Version: 2025.1

Platform: Debian 11.7 X86_64

The Definitive Proof:
I created a minimal diagnostic script to inspect the domoticz.time object:


return {
on = {
timer = { 'every minute' }
},
execute = function(domoticz, item)
domoticz.log(
'[Time-Diagnose] isWeekend = ' .. tostring(domoticz.time.isWeekend) ..
', weekday = ' .. tostring(domoticz.time.weekday) ..
', weekDayName = ' .. tostring(domoticz.time.weekDayName),
domoticz.LOG_INFO
)
end
}

This script produces the following output in my Domoticz log every minute:
[Time-Diagnose] isWeekend = nil, weekday = nil, weekDayName = nil

This proves that the core dzVents time functionality is completely broken in my installation.

Troubleshooting Steps Already Taken:

Confirmed "dzVents enabled" is checked in Setup -> Settings -> Other.

Confirmed Latitude and Longitude are correctly set in settings.

Confirmed the system timezone is correctly set to my location (Europe/Zurich) using timedatectl.

Performed a full system reboot (power cycle).

Verified that device-triggered scripts work, but timer-triggered scripts do not.

The minimal test script above fails, even when all other scripts are disabled.

What could cause the domoticz.time object to be completely uninitialized when all system settings appear to be correct? Is this a known bug, or could it point to a corrupt installation?

Thank you for your help!

[boum]

maybe stop using ai generated code and read the doc?
https://wiki.domoticz.com/DzVents:_next ... nd_methods

none of that attributes you are reading exist…