DzVents: next generation Lua scripting - Revision history

Walter vl: /* Thermostat 6 3.1.11 */ Layout

2026-08-09T12:38:32Z

Thermostat 6 3.1.11: Layout

@@ Line 1,384: / Line 1,384: @@
 ==== Thermostat 6 <sup>3.1.11</sup> ====
-Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint. - '''setPoint''': ''Number''. The current set point. - '''humidityStatusValue''': ''Number''. Mapped humidity status value (only for subtypes with humidity). - '''updateSetPoint(setPoint)''': ''Function''. Update the set point. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29|command options]]. - '''updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)''': ''Function''. Update thermostat values. Parameters depend on the subtype: - ''Temp/Setpoint'': <code>updateThermostat(temperature, setPoint)</code> - ''Temp/Hum/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus)</code> - ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code> - ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code> - <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value. - <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.
+Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint.
 <span id="uv-sensor"></span>

Gizmocuz at 10:25, 9 August 2026

2026-08-09T10:25:13Z

← Older revision		Revision as of 10:25, 9 August 2026
Line 357:		Line 357:
	* '''marker''': A string that is prefixed before each log message. That way you can easily create a filter in the Domoticz log to see just these messages. '''marker''' defaults to scriptname		* '''marker''': A string that is prefixed before each log message. That way you can easily create a filter in the Domoticz log to see just these messages. '''marker''' defaults to scriptname

	\*LOG_DEBUG will also cause Execution Info to be displayed (start/finished)		<nowiki></nowiki>*LOG_DEBUG will also cause Execution Info to be displayed (start/finished)

	Example:		Example:
Line 909:		Line 909:
	* '''HUM_COMFORTABLE, HUM_DRY, HUM_NORMAL, HUM_WET, HUM_COMPUTE''' <sup>3.0.15</sup>: constant for humidity status.		* '''HUM_COMFORTABLE, HUM_DRY, HUM_NORMAL, HUM_WET, HUM_COMPUTE''' <sup>3.0.15</sup>: constant for humidity status.
	* '''INTEGER, FLOAT, STRING, DATE, TIME''': variable types.		* '''INTEGER, FLOAT, STRING, DATE, TIME''': variable types.
	* \**LOG_INFO, LOG_STATUS, LOG_ERROR, LOG_DEBUG, LOG_FORCE: for logging messages. LOG_FORCE will always be displayed.		* <nowiki></nowiki>**LOG_INFO, LOG_STATUS, LOG_ERROR, LOG_DEBUG, LOG_FORCE: for logging messages. LOG_FORCE will always be displayed.
	* '''NSS_CLICKATELL''' <sup>3.1.3</sup>, '''NSS_FIREBASE, NSS_FIREBASE_CLOUD_MESSAGING, NSS_GOOGLE_DEVICES,''' <sup>3.0.10</sup> <sup>Only with installed casting plugin</sup>, '''NSS_HTTP, NSS_KODI, NSS_LOGITECH_MEDIASERVER, NSS_NMA,NSS_PROWL, NSS_PUSHALOT, NSS_PUSHBULLET, NSS_PUSHOVER, NSS_PUSHSAFER, NSS_TELEGRAM, NSS_GOOGLE_CLOUD_MESSAGING''' <sup>deprecated by Google and replaced by firebase</sup>: for notification subsystem		* '''NSS_CLICKATELL''' <sup>3.1.3</sup>, '''NSS_FIREBASE, NSS_FIREBASE_CLOUD_MESSAGING, NSS_GOOGLE_DEVICES,''' <sup>3.0.10</sup> <sup>Only with installed casting plugin</sup>, '''NSS_HTTP, NSS_KODI, NSS_LOGITECH_MEDIASERVER, NSS_NMA,NSS_PROWL, NSS_PUSHALOT, NSS_PUSHBULLET, NSS_PUSHOVER, NSS_PUSHSAFER, NSS_TELEGRAM, NSS_GOOGLE_CLOUD_MESSAGING''' <sup>deprecated by Google and replaced by firebase</sup>: for notification subsystem
	* '''PRIORITY_LOW, PRIORITY_MODERATE, PRIORITY_NORMAL, PRIORITY_HIGH, PRIORITY_EMERGENCY''': for notification priority.		* '''PRIORITY_LOW, PRIORITY_MODERATE, PRIORITY_NORMAL, PRIORITY_HIGH, PRIORITY_EMERGENCY''': for notification priority.
Line 1,384:		Line 1,384:
	==== Thermostat 6 <sup>3.1.11</sup> ====		==== Thermostat 6 <sup>3.1.11</sup> ====

	Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint.		Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint. - '''setPoint''': ''Number''. The current set point. - '''humidityStatusValue''': ''Number''. Mapped humidity status value (only for subtypes with humidity). - '''updateSetPoint(setPoint)''': ''Function''. Update the set point. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]]. - '''updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)''': ''Function''. Update thermostat values. Parameters depend on the subtype: - ''Temp/Setpoint'': <code>updateThermostat(temperature, setPoint)</code> - ''Temp/Hum/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus)</code> - ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code> - ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code> - <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value. - <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.

	* '''setPoint''': ''Number''. The current set point.
	* '''humidityStatusValue''': ''Number''. Mapped humidity status value (only for subtypes with humidity).
	* '''updateSetPoint(setPoint)''': ''Function''. Update the set point. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]].
	* '''updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)''': ''Function''. Update thermostat values. Parameters depend on the subtype:
	** ''Temp/Setpoint'': <code>updateThermostat(temperature, setPoint)</code>
	** ''Temp/Hum/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus)</code>
	** ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code>
	** ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code>
	~~***~~ <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value.
	~~***~~ <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.

	<span id="uv-sensor"></span>		<span id="uv-sensor"></span>

	==== UV sensor ====		==== UV sensor ====

Line 1,644:		Line 1,632:

	If your device is not recognized by dzVents, you can still operate it using the generic device attributes and methods. It is much nicer, however, to have device specific attributes and methods. Existing recognized adapters are in <code>/path/to/domoticz/dzVents/runtime/device-adapters</code>. Copy an existing adapter and adapt it to your needs. You can turn debug logging on and inspect the file <code>domoticzData.lua</code> in the dzVents folder. There you will find the unique signature for your device type. Usually it is a combination of deviceType and deviceSubType, but you can use any of the device attributes in the <code>matches</code> function. The matches function checks if the device type is suitable for your adapter and the <code>process</code> function actually creates your specific attributes and methods. Also, if you call <code>myDevice.dump()</code> you will see all attributes and methods and the attribute <code>_adapters</code> shows you a list of applied adapters for that device. Finally, register your adapter in <code>Adapters.lua</code>. Please share your adapter when it is ready and working.		If your device is not recognized by dzVents, you can still operate it using the generic device attributes and methods. It is much nicer, however, to have device specific attributes and methods. Existing recognized adapters are in <code>/path/to/domoticz/dzVents/runtime/device-adapters</code>. Copy an existing adapter and adapt it to your needs. You can turn debug logging on and inspect the file <code>domoticzData.lua</code> in the dzVents folder. There you will find the unique signature for your device type. Usually it is a combination of deviceType and deviceSubType, but you can use any of the device attributes in the <code>matches</code> function. The matches function checks if the device type is suitable for your adapter and the <code>process</code> function actually creates your specific attributes and methods. Also, if you call <code>myDevice.dump()</code> you will see all attributes and methods and the attribute <code>_adapters</code> shows you a list of applied adapters for that device. Finally, register your adapter in <code>Adapters.lua</code>. Please share your adapter when it is ready and working.

			'''Note''': dzVents only runs when there is at least one active dzVents script, either created in the internal web editor or placed as a <code>.lua</code> file in <code>/path/to/domoticz/scripts/dzVents/scripts</code>. Without such a script, Domoticz never starts the dzVents Lua engine, so the device adapters are not loaded, <code>domoticzData.lua</code> is not written and any logging you add to your adapter stays silent whatever the log level is. When you develop an adapter before you have a script that uses it, add a minimal placeholder script to activate the engine.

	<span id="variable-object-api-user-variables"></span>		<span id="variable-object-api-user-variables"></span>
Line 1,664:		Line 1,654:
	* '''value''': ''String\|Number\|Date\|Time''. Value of the variable.		* '''value''': ''String\|Number\|Date\|Time''. Value of the variable.

	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">return
	return
	{		{
	on =		on =
	{		{
	timer = {'Every 10 minutes on mon,tue,wed,thu,fri'}		timer = {'Every 10 minutes on mon,tue,wed,thu,fri'}
	},		},

	~~execute = function(domoticz)~~
	~~-- check time of the day~~
	~~if (domoticz.time.isDayTime and domoticz.variables('myVar').value == 10) then~~
	~~domoticz.variables('anotherVar').set(15)~~
	~~end~~
	~~end~~
	}
	~~</syntaxhighlight>~~

			execute = function(domoticz)
			-- check time of the day
			if (domoticz.time.isDayTime and domoticz.variables('myVar').value == 10) then
			domoticz.variables('anotherVar').set(15)
			end
			end
			}</syntaxhighlight>
			<span id="time-object"></span>
	== Time object ==		== Time object ==

Line 2,636:		Line 2,624:

	Make sure the active section in your script is set to <code>true</code>: <code>active = true</code>. And, on top of that, if you are using the internal web editor to write your script, make sure that your script is active there and you have clicked Save! “Event active” is a separate checkbox that must be ticked for every active script. When not active, the script name will be red in the list on the right.		Make sure the active section in your script is set to <code>true</code>: <code>active = true</code>. And, on top of that, if you are using the internal web editor to write your script, make sure that your script is active there and you have clicked Save! “Event active” is a separate checkbox that must be ticked for every active script. When not active, the script name will be red in the list on the right.

			<span id="do-you-have-at-least-one-active-script"></span>
			=== Do you have at least one active script? ===

			dzVents only starts its Lua engine when there is at least one active dzVents script, either created in the internal web editor or placed as a <code>.lua</code> file in <code>/path/to/domoticz/scripts/dzVents/scripts</code>. With no active script at all, Domoticz skips dzVents completely: nothing is logged whatever the log level is, <code>domoticzData.lua</code> and <code>module.log</code> are not created, and the code in the device adapters never runs. Adding a minimal script is enough to activate the engine.

	<span id="turn-on-debug-logging"></span>		<span id="turn-on-debug-logging"></span>

Walter vl: /* Thermostat 6 3.1.11 */

2026-08-02T17:07:02Z

Thermostat 6 3.1.11

← Older revision		Revision as of 17:07, 2 August 2026
Line 1,394:		Line 1,394:
	** ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code>		** ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code>
	** ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code>		** ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code>
	** <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value.		*** <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value.
	** <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.		*** <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.

	<span id="uv-sensor"></span>		<span id="uv-sensor"></span>

	==== UV sensor ====		==== UV sensor ====

Walter vl: /* Thermostat 6 3.1.11 */

2026-08-02T17:06:17Z

Thermostat 6 3.1.11

← Older revision		Revision as of 17:06, 2 August 2026
Line 1,386:		Line 1,386:
	Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint.		Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint.

	- '''setPoint''': ''Number''. The current set point.		* '''setPoint''': ''Number''. The current set point.
			* '''humidityStatusValue''': ''Number''. Mapped humidity status value (only for subtypes with humidity).
	- '''humidityStatusValue''': ''Number''. Mapped humidity status value (only for subtypes with humidity).		* '''updateSetPoint(setPoint)''': ''Function''. Update the set point. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]].
			* '''updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)''': ''Function''. Update thermostat values. Parameters depend on the subtype:
	- '''updateSetPoint(setPoint)''': ''Function''. Update the set point. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]].		** ''Temp/Setpoint'': <code>updateThermostat(temperature, setPoint)</code>
			** ''Temp/Hum/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus)</code>
	- '''updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)''': ''Function''. Update thermostat values. Parameters depend on the subtype:		** ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code>
			** ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code>
	- ''Temp/Setpoint'': <code>updateThermostat(temperature, setPoint)</code>		** <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value.
			** <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.
	- ''Temp/Hum/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus)</code>

	- ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code>

	- ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code>

	- <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value. - <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.

	<span id="uv-sensor"></span>		<span id="uv-sensor"></span>

Walter vl: /* Thermostat 6 3.1.11 */ layout

2026-08-02T17:03:39Z

Thermostat 6 3.1.11: layout

@@ Line 1,384: / Line 1,384: @@
 ==== Thermostat 6 <sup>3.1.11</sup> ====
-Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint. - '''setPoint''': ''Number''. The current set point. - '''humidityStatusValue''': ''Number''. Mapped humidity status value (only for subtypes with humidity). - '''updateSetPoint(setPoint)''': ''Function''. Update the set point. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29|command options]]. - '''updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)''': ''Function''. Update thermostat values. Parameters depend on the subtype: - ''Temp/Setpoint'': <code>updateThermostat(temperature, setPoint)</code> - ''Temp/Hum/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus)</code> - ''Temp/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, nil, nil, barometer, forecast)</code> - ''Temp/Hum/Baro/Setpoint'': <code>updateThermostat(temperature, setPoint, humidity, humidityStatus, barometer, forecast)</code> - <code>forecast</code> can be a string: <code>'noinfo'</code>, <code>'sunny'</code>, <code>'partlycloudy'</code>, <code>'cloudy'</code>, <code>'rain'</code> or a numeric value. - <code>humidityStatus</code> can be a string: <code>'dry'</code>, <code>'normal'</code>, <code>'comfortable'</code>, <code>'wet'</code> or a numeric value. If omitted with humidity provided, it is auto-calculated.
+Thermostat 6 devices come in several subtypes: Temp/Setpoint, Temp/Hum/Setpoint, Temp/Baro/Setpoint and Temp/Hum/Baro/Setpoint.
 <span id="uv-sensor"></span>

Walter vl: /* Variable attributes and methods */

2026-08-02T17:01:11Z

Variable attributes and methods

@@ Line 1,652: / Line 1,652: @@
 * '''value''': ''String|Number|Date|Time''. Value of the variable.
-<span id="time-object"></span>
+<syntaxhighlight lang="lua">
 == Time object ==

Gizmocuz at 09:48, 20 April 2026

2026-04-20T09:48:02Z

Show changes

Gizmocuz at 05:21, 20 April 2026

2026-04-20T05:21:13Z

← Older revision		Revision as of 05:21, 20 April 2026
Line 756:		Line 756:
	<ul>		<ul>
	<li><p>'''switchTimerPlan(idx)''': ''Function''. Switch the active timer plan to the plan with the given database ID. <code>idx</code> must be a positive integer matching an existing timer plan ID (as shown in '''Settings → Timer Plans'''). Invalid or non-existent plan IDs are silently ignored. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]].</p></li>		<li><p>'''switchTimerPlan(idx)''': ''Function''. Switch the active timer plan to the plan with the given database ID. <code>idx</code> must be a positive integer matching an existing timer plan ID (as shown in '''Settings → Timer Plans'''). Invalid or non-existent plan IDs are silently ignored. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]].</p></li>
			<li><p>'''resumeTimerPlan(deviceOrIdx)''': ''Function''. Finds the most recent timer that should have fired today (before now) for the given device or scene and executes it immediately. Useful for restoring the correct device state after a Domoticz restart or power cut. Pass a device or scene object (recommended) or a raw integer ID (always treated as a device). Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]]. ```lua – Replay last timer for a device object domoticz.resumeTimerPlan(domoticz.devices(‘My Light’))</p>
			<p>– Replay last timer for a scene domoticz.resumeTimerPlan(domoticz.scenes(‘Evening Scene’))</p>
			<p>– By raw device ID domoticz.resumeTimerPlan(42) ```</p></li>
	<li><p>'''startTime''': ''[[#Time_object\|Time Object]]''. Returns the startup time of the Domoticz service.</p></li>		<li><p>'''startTime''': ''[[#Time_object\|Time Object]]''. Returns the startup time of the Domoticz service.</p></li>
	<li><p>'''systemUptime''': ''Number''. Number of seconds the system is up.</p></li>		<li><p>'''systemUptime''': ''Number''. Number of seconds the system is up.</p></li>

Gizmocuz at 09:34, 19 April 2026

2026-04-19T09:34:38Z

← Older revision		Revision as of 09:34, 19 April 2026
Line 1:		Line 1:
			'''Note''': This document is maintained on [https://github.com/domoticz/domoticz/blob/development/dzVents/documentation/README.md github], and the wiki version is automatically generated. Edits should be performed on github, or they may be suggested on the wiki article’s [https://wiki.domoticz.com/Talk:DzVents:_next_generation_Lua_scripting Discussion page]. Editing can be done by any editor but if you are looking for a specialized markDown editor; [https://stackedit.io/app# stackedit.io] would be a good choice.

	<span id="about-dzvents"></span>		<span id="about-dzvents"></span>
	= About dzVents =		= About dzVents =
Line 753:		Line 755:
	dz.snapshot({'test', 'test2'}) -- table</syntaxhighlight>		dz.snapshot({'test', 'test2'}) -- table</syntaxhighlight>
	<ul>		<ul>
			<li><p>'''switchTimerPlan(idx)''': ''Function''. Switch the active timer plan to the plan with the given database ID. <code>idx</code> must be a positive integer matching an existing timer plan ID (as shown in '''Settings → Timer Plans'''). Invalid or non-existent plan IDs are silently ignored. Supports [[#Command_options_.28delay.2C_duration.2C_event_triggering.29\|command options]].</p></li>
	<li><p>'''startTime''': ''[[#Time_object\|Time Object]]''. Returns the startup time of the Domoticz service.</p></li>		<li><p>'''startTime''': ''[[#Time_object\|Time Object]]''. Returns the startup time of the Domoticz service.</p></li>
	<li><p>'''systemUptime''': ''Number''. Number of seconds the system is up.</p></li>		<li><p>'''systemUptime''': ''Number''. Number of seconds the system is up.</p></li>

Gizmocuz at 06:09, 1 March 2026

2026-03-01T06:09:28Z

Show changes