possible to ignore triggering lua-script in log?

Moderator: leecollings

Post Reply
BartSr
Posts: 365
Joined: Sunday 03 July 2016 16:16
Target OS: Raspberry Pi / ODroid
Domoticz version: V2024.7
Location: Netherlands
Contact:

possible to ignore triggering lua-script in log?

Post by BartSr »

Hi!
I have LUA script running which is triggered every minute.
It's based on a domoticz example of fan control based upon humidity rise.

The script works fine but I should like to exclude the script from trigger in log.
Is that possible ?

Code: Select all

--[[


    This script controls the humidity in a typical bathroom setting by detecting
    relative rises in humidity in a short period.
    Of course it requires a humidity sensor and a binary switch controlling a fan/ventilator.
    (there is no provision for variable speed ventilators here!)

    How it works (assuming the default constants as defined below):

    Save the script as time triggered!!

    Every 5 minutes a reading is done. Every reading is stored together
    with the previous reading and is stored in two user variables (humidityTmin5 and humidityTmin10).
    So it has two reading over the past 10 minutes.
    It then takes the lowest of the two and compares it with the latest reading and
    calculates a delta.
    If the delta is 3 or higher (see constants) then the fan will be turned
    on, it calculates the target humidity and the 'humidity-decrease program' is started (fanFollowsProgram=1).
    From then on, every 5 minutes the current humidity is compared to the
    stored target humidity. Basically if that target is reached, the fan is turned off
    and the 'program' is ended.
    Of course, it is possible that the target is never reached (might start raining outside
    or whatever). Then there is a failsafe (FAN_MAX_TIME) after which the ventilator
    will be turned off.

    Also, it will detect if the ventilator is manually switched off during a program
    or when it is switched on before the program starts.

    Along the lines it prints to the log and sends notifications
    but of course you can turn that off by removing those lines.

--]]

commandArray = {}

-- adjust to your specific situation

-- devices
local FAN_NAME = 'Badkamer beneden fan'    -- exact device name of the switch turning on/off the ventilator
--local SENSOR_NAME = 'BadkamerBenedenVocht'     -- exact device name of the humidity sensor
local SENSOR_NAME = 'Vochtmeter in badkamer beneden'     -- exact device name of the humidity sensor
--Vochtmeter badkamer beneden
-- script constants
local SAMPLE_INTERVAL = 5                 -- time in minutes when a the script logic will happen
local FAN_DELTA_TRIGGER = 3               -- rise in humidity that will trigger the fan
local FAN_MAX_TIME = 15 -- 30 //15                -- maximum amount of sample cycles the fan can be on, in case we never reach the target humidity
local TARGET_OFFSET = 5                 -- ventilator goes off if target+offset is reached (maybe it takes too long to reach the true target due to wet towels etc)
local LABEL = '- Humidity control - '

-- test / debug
local TEST_MODE = false           -- when true TEST_MODE_HUMVAR is used instead of the real sensor
local TEST_MODE_HUMVAR = 'testHumidity'   -- fake humidity value, give it a test value in domoticz/uservars
--local PRINT_MODE = true                  -- Any other value as false or nil will print output to log and send notifications
local PRINT_MODE = false            -- Any other value as false or nil will print output to log and send notifications

if PRINT_MODE then
    print(LABEL)
end

-- Function added to overcome compatibility problem between Lua version 5.2 an 5.3
local function toInteger(str)
    return math.floor(str)
end

-- get the global variables:
-- this script runs every minute, humCounter is used to create SAMPLE_INTERVAL periods
local current

--print ("humcounter" .. " "..uservariables['humCounter'])
local humCounter = toInteger(uservariables['humCounter'])

-- print ('humidityTmin5' .. " ".. uservariables['humidityTmin5'])
local humidityTmin5 = toInteger(uservariables['humidityTmin5'])                -- youngest reading

-- print ('humidityTmin10' .. " ".. uservariables['humidityTmin10'])
local humidityTmin10 = toInteger(uservariables['humidityTmin10'])              -- oldest reading

-- print ('targetFanOffHumidity' .. " ".. uservariables['targetFanOffHumidity'])
local targetFanOffHumidity = toInteger(uservariables['targetFanOffHumidity'])  -- target humidity

--  print ('fanMaxTimer' .. " ".. uservariables['fanMaxTimer'])
local fanMaxTimer = toInteger(uservariables['fanMaxTimer'])

-- print ( uservariables['fanFollowsProgram'])
local fanFollowsProgram = toInteger(uservariables['fanFollowsProgram'])        -- marker indicating that the decrease program is started

local target = 0 -- will hold the target humidity when the program starts

-- get the current humidity value
if (TEST_MODE) then
     print ('TEST_MODE_HUMVAR' .. uservariables[TEST_MODE_HUMVAR])    
    current = toInteger(uservariables[TEST_MODE_HUMVAR])
    print (current)
else

   current = toInteger(otherdevices_humidity[SENSOR_NAME])
    
--  print ("current".. " "..current)
end

-- check if the sensor is on or has some weird reading
if (current == 0 or current == nil) then
    print(LABEL .. 'current is 0 or nil. Skipping this reading')
    return commandArray
end

if PRINT_MODE then
    print(LABEL .. 'Current humidity:' .. current)
    print(LABEL .. 'targetFanOffHumidity:' .. targetFanOffHumidity)
    print(LABEL .. 'humidityTmin5: ' .. humidityTmin5)
    print(LABEL .. 'humidityTmin10: ' .. humidityTmin10)
    print(LABEL .. 'fanMaxTimer: ' .. fanMaxTimer)
    print(LABEL .. 'humCounter:' .. humCounter)
    print(LABEL .. 'fanFollowsProgram:' .. fanFollowsProgram)
end

-- increase cycle counter
humCounter = humCounter + 1

if (humCounter >= SAMPLE_INTERVAL) then

    if (humidityTmin5 == 0) then
        -- initialization, assume this is the first time
        humidityTmin5 = current
        humidityTmin10 = current
    end

    humCounter = 0 -- reset the cycle counter

    -- pick the lowest history value to calculate the delta
    -- this also makes sure that two relative small deltas in the past 2*interval minutes are treated as one larger rise
    -- and therefore will still trigger the ventilator
    -- I don't want to use a longer interval instead because I want the ventilator to start as soon as possible
    -- (so rather after 5 minutes instead of after 15 minutes because the mirrors in the bathroom become kinda useless ;-)
    delta = current - math.min(humidityTmin10, humidityTmin5)
--print (delta)
    if PRINT_MODE then
        print(LABEL .. 'Delta: ' .. delta)
    end

    -- pick the lowest history value
    target = math.min(humidityTmin10, humidityTmin5) + TARGET_OFFSET

    -- shift the previous measurements
    humidityTmin10 = humidityTmin5
    -- and store the current
    humidityTmin5 = current

    if (otherdevices[FAN_NAME]=='Off' or (otherdevices[FAN_NAME]=='On' and fanFollowsProgram==0)) then
        -- either the fan is off or it is on but the decrease program has not started
        -- in that latter case we start the program anyway. This could happen if someone turns on the ventilator
        -- manually because he/she is about to take a shower and doesn't like damp mirrors.
        -- I don't do this because the ventilator removes heat from the bathroom and I want this to happen
        -- as late as possible ;-)

        if (fanFollowsProgram == 1 and otherdevices[FAN_NAME]=='Off') then
            -- likely someone turned off the ventilator while the program was running
            fanFollowsProgram = 1
        end

        -- see if we have to turn it on
        if (delta >= FAN_DELTA_TRIGGER) then
            -- time to start the fan
--            commandArray[FAN_NAME] = 'Set Level 99'            
            commandArray[FAN_NAME] = 'On'
            targetFanOffHumidity = target

            if (fanFollowsProgram == 1) then
                print('Ventilator was already on but we start the de-humidifying program')
            end

            fanFollowsProgram = 1

            -- set the safety stop
            fanMaxTimer = FAN_MAX_TIME

            if PRINT_MODE then
                print(LABEL .. 'Rise in humidity. Turning on the vents. Delta: ' .. delta)
                print(LABEL .. 'Target humidity for turning the ventilator: ' ..targetFanOffHumidity)
                commandArray['SendNotification'] = LABEL .. 'Ventilator is on#The ventilator was activated at humidity level ' .. current .. '#0'
            end
        end

    else
        if (fanMaxTimer > 0) then
            -- possible that someone started the ventilator manually
            fanMaxTimer = fanMaxTimer - 1
        end


        if (fanFollowsProgram == 1) then -- not manually started

            if (delta >= FAN_DELTA_TRIGGER) then
                -- ok, there is another FAN_DELTA_TRIGGER rise in humidity
                -- when this happen we reset the fanMaxTimer to a new count down
                -- because we have to ventilate a bit longer due to the extra humidity
                if PRINT_MODE then
                    print(LABEL .. 'Another large increase detected, resetting max timer. Delta: ' .. delta)
                end
                fanMaxTimer = FAN_MAX_TIME
            end

            -- first see if it can be turned off
            if (current <= targetFanOffHumidity or fanMaxTimer==0) then
                commandArray[FAN_NAME] = 'Off'

                msg = ''

                if (fanMaxTimer == 0 and current > targetFanOffHumidity) then
                    msg = 'Target not reached but safety time-out is triggered.'
                    if PRINT_MODE == true then
                    print(msg)
                    end
                else
                    msg = 'Target humidity reached'
                    if PRINT_MODE then
                        print(LABEL .. msg)
                    end
                end

                if PRINT_MODE then
                    print(LABEL .. 'Turning off the ventilator')
                    msg = msg .. '\nTurning off the ventilator'
                end

                targetFanOffHumidity = 0
                fanMaxTimer = 0
                fanFollowsProgram = 0
                -- reset history in this case.. we start all over
                -- Tmin10 is still in the 'ventilator=On'-zone
                humidityTmin10 = humidityTmin5
                 if PRINT_MODE == true then
                commandArray['SendNotification'] = 'Ventilator is off#' .. msg .. '#0'
                end

            else
                -- we haven't reached the target yet
                if PRINT_MODE then
                    print(LABEL .. 'Humidity delta: ' .. delta)
                end
            end
        end
    end

if PRINT_MODE then
    print(LABEL .. 'New values >>>>>>>>>>>')
    print(LABEL .. 'humidityTmin5: ' .. humidityTmin5)
    print(LABEL .. 'humidityTmin10: ' .. humidityTmin10)
    print(LABEL .. 'fanMaxTimer: ' .. fanMaxTimer)
    print(LABEL .. 'humCounter:' .. humCounter)
    print(LABEL .. 'fanFollowsProgram:' .. fanFollowsProgram)
    print(LABEL .. '------ target: ' .. targetFanOffHumidity)
end

end

-- save the globals
commandArray['Variable:humCounter'] = tostring(humCounter)
commandArray['Variable:humidityTmin10'] = tostring(humidityTmin10)
commandArray['Variable:humidityTmin5'] = tostring(humidityTmin5)
commandArray['Variable:targetFanOffHumidity'] = tostring(targetFanOffHumidity)
commandArray['Variable:fanMaxTimer'] = tostring(fanMaxTimer)
commandArray['Variable:fanFollowsProgram'] = tostring(fanFollowsProgram)

xdelta =humidityTmin10 -humidityTmin5
-- commandArray['UpdateDevice'] ='1554|0|humidityTmin5:'..tostring(humidityTmin5) -- werkt!
commandArray['UpdateDevice'] ='1554|0|humCounter: '..tostring(humCounter)..'\n humidityTmin5: '..tostring(humidityTmin5)..'\n humidityTmin10: '..tostring(humidityTmin10) .. '\n Humidity current: ' .. tostring(current) .. '\n Humidity delta: ' .. tostring(xdelta) .. '\n targetFanOffHumidity: ' .. tostring(targetFanOffHumidity) .. '\n fanFollowsProgram: ' .. tostring(fanFollowsProgram)

return commandArray
Raspberry pi 3b
Arduino
KAKU
RfxCom
Zwave2MQTT
OTGW
Chinese sensors temp (Dallas),movement
Tasmota
Esp8266 / 32 espeasy
Zigbee2MQTT
User avatar
psubiaco
Posts: 205
Joined: Monday 20 August 2018 9:38
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Italy
Contact:

Re: possible to ignore triggering lua-script in log?

Post by psubiaco »

You can replace print() with log() and define in the begin of script:

Code: Select all

debug=0		-- 1 to enable debugging
function log(msg) 
  if (debug>0) then print(msg) end	-- print info in the log only if debug variable is not zero
end
Paolo
--
I use DomBus modules to charge EV car, get a full alarm system, control heat pump, fire alarm detection, lights and much more. Video
Facebook page - Youtube channel
BartSr
Posts: 365
Joined: Sunday 03 July 2016 16:16
Target OS: Raspberry Pi / ODroid
Domoticz version: V2024.7
Location: Netherlands
Contact:

Re: possible to ignore triggering lua-script in log?

Post by BartSr »

thanks for your reply.
I didnot test as in normal nothing will be printed to log because there are flags which don't allow printing.
The problem is that every mintute next is in status tab of log.

Code: Select all

2024-11-13 18:17:56.660 Status: EventSystem: Script event triggered: /home/bart/domoticz/dzVents/runtime/dzVents.lu   
Raspberry pi 3b
Arduino
KAKU
RfxCom
Zwave2MQTT
OTGW
Chinese sensors temp (Dallas),movement
Tasmota
Esp8266 / 32 espeasy
Zigbee2MQTT
User avatar
psubiaco
Posts: 205
Joined: Monday 20 August 2018 9:38
Target OS: Raspberry Pi / ODroid
Domoticz version: Beta
Location: Italy
Contact:

Re: possible to ignore triggering lua-script in log?

Post by psubiaco »

on Setup -> Settings -> Other do as indicated in the screenshot:
Istantanea_2024-11-13_18-38-47.png
Istantanea_2024-11-13_18-38-47.png (13.4 KiB) Viewed 1145 times
Paolo
--
I use DomBus modules to charge EV car, get a full alarm system, control heat pump, fire alarm detection, lights and much more. Video
Facebook page - Youtube channel
BartSr
Posts: 365
Joined: Sunday 03 July 2016 16:16
Target OS: Raspberry Pi / ODroid
Domoticz version: V2024.7
Location: Netherlands
Contact:

Re: possible to ignore triggering lua-script in log?

Post by BartSr »

thanks
was not aware of this setting
problem solved
Raspberry pi 3b
Arduino
KAKU
RfxCom
Zwave2MQTT
OTGW
Chinese sensors temp (Dallas),movement
Tasmota
Esp8266 / 32 espeasy
Zigbee2MQTT
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest