put your code in and that works. I get the logs. 2025-05-01 06:53:00.179 dzVents: timertest: Timer event was triggered by every minuteat time : 2025-5-1 6:53:0.52 2025-05-01 06:53:00.179 dzVents: timertest: It works at time :2025-5-1 6:53:0.52 But the trigger is on every minute. My original trigger ...

Hello Walter, Thanks for testing, so it must be in my setup. Domoticz: Version: 2024.7 Build Hash: b317cfab1 Compile Date: 2024-07-13 16:59:31 dzVents Version: 3.1.8 Python Version: 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110] Active User: admin I thought about the summer/winter time ...

I wrote a script for a thermostat that worked fine for 6 months. Suddenly the time function is not executed anymore. Nothing to be shown in the log when a time period is activated. Only when I manually trigger the object where this timer is residing in from OFF to Normaal or vice versa it changes ...

I found out Waaren has past away. :-( In the meantime I worked more on the code and got what I need and works for my purpose. Might need polishing but I am happy. Thanks for all the support who responded with tips and tricks. It now uses two scripts. Script1 for the general settings. As most ...

Thanks Walter,

I will check this evening.

Paco

Hello,

I want to add and change a floorplan but it is not in the top menubar.
I cant select any menu to be active.
Is Domoticz trunkated?
Or do I look in the wrong place?

Paco

Found a solution....by try and error that works. Maybe for others who run also into this basic problem... return { on = { devices = {'Thermostat_Control' }, }, execute = function(dz) local Thermostat = dz.devices('Thermostat_Control') -- =idx69 -- "Boost" mode active, initiated by thermostat ...

Hello Walter, I have a follow up question for what looks to be simple. If I run this script and change the selector value from 10 to 20 by clicking the selector the selector does NOT returns back from boost to normaal after 1 minute. Is this correct script behaviour? Did I missed something? return ...

Got it solved. return { on = { devices = {'Thermostat_Control', 'Heater_Switch', 'Temp_Kamer','Setpoint_Regular' }, timer = {'every minute'}, }, execute = function(dz) --local Vartemp = dz.variables('Vartemp') --declared as float value local Thermostat = dz.devices('Thermostat_Control') -- =idx69 ...

Walter, I got it working. With some try and error.............and implementing checkfirst the correct way. return { on = { devices = {'Thermostat_Control', 'Heater_Switch', 'Temp_Kamer','Setpoint_Regular' }, timer = {'every minute'}, }, execute = function(dz) --local Vartemp = dz.variables('Vartemp ...

Hello Walter, Sorry for me misunderstanding. My DZvents knowledge might be lacking heavily but I am willing to learn if I understand what goes on. OK. You say I created a loop. So now I understand the behaviour shown in the script why it is repeating. I already added the dz.devices(67).switchOff ...

For a proof of concept I made a simple script for switching ON/OFF a relay that works as backup (parallel) when the original thermostat fails. The boiler only works with ON/OFF not Opentherm. The ON/OFF relay is based on a ESPEASY (heater switch) and works fine when toggled when the script does not ...

Hi Walter, As far as my knowledge goes I switched off all logging options as you described. Problem of the filling of the log starts as soon as I start the DZvents script as written below and change the setting manual of a "switch". Without changing the Switch output the logging is regular. When I ...

Hello, When I check my log from the settings menu I see a constant data stream filling the log. But that is a very low fill in. once every 20 seconds or so. No important data. Just scripts starting, weather info data and so on. When I start a Dzvents thermostat script I created the log is filled ...

Hello, three years ago my domoticz went down and corrupted. I am slowly restoring what I have and all works fine and now I am back at debugging the thermostat code. Difference between 3 years ago and now is even if have code snippets I clearly do not know anymore how far I was in the project that is ...

OK, guys thank you for leading me to the working solution. For my general display purpose the Humidity Virtual device needed only a value to be reported from the thermostat data. That is all I needed. But what I learned now from you is this device needs a value and a calculated status number to show ...

The IDX 64 for humidity ESP32 is correct... Paco

Overlooked Domoticz while copying code...>me bad The temperature codeline runs fine as it did before in the old code but the humidity again errors in the same way. 2024-01-28 15:20:00.891 Error: dzVents: Error: (3.1.8) ESP32: No status provided. Humidity not set local scriptVar = 'ESP32' return { on ...

OK thanks for all suggestions I got one step further. Domoticz is replaced with dz where needed. Now the log spits the correct data for the script as HvdW suggested. 2024-01-28 13:07:00.434 Status: dzVents: Info: ESP32: ------ Start internal script: EPS32 T+H+R:, trigger: "every minute" 2024-01-28 ...

If I understanding it correctly by adding it to the script this is the result. 2024-01-27 22:22:00.805 Error: dzVents: Error: (3.1.8) ESP32: No status provided. Humidity not set 2024-01-27 22:22:00.805 Error: dzVents: Error: (3.1.8) ESP32: An error occurred when calling event handler EPS32 T+H+R ...