help

[davidneale 0]

I have the scene but its not notifying me on my phone why 

 

 

--[[
%% properties
308 value
426 value
%% events
DayNight
%% globals
--]]

local sensordrive = fibaro:getValue(308,'value') --Drive 
local sensor = fibaro:getValue(426,'value') --test
local startSource = fibaro:getSourceTrigger();
local DayNight = fibaro:getGlobal("DayNight")

fibaro:debug(sensor)
fibaro:debug(sensordrive)

if (sensordrive =='1')
     then 
      print (" one has been set")    
  
      if (sensor =='1')
          then
            print (" both has been set")
    
               if fibaro:getModificationTime(308, "value")< fibaro:getModificationTime(426, "value")
                then 
                    print ("time thing is right")
                    fibaro:call(152,'sendPush','Drive Breached IN') -- a Phone
                      fibaro:call(135,'sendPush','Drive Breached IN') -- d Phone
    --  fibaro:sleep(9000)
     
if (
    (sensordrive == '1') and (DayNight == 'Night')
    ) then
 fibaro:call(527, "turnOn")

  fibaro:sleep(3 * 60 * 1000)
 fibaro:call(527, "turnOff")

  end    
  
    end 
    
                 
          end
      end

[T.Konopka 8]

Could you please change the topic so that it specifies what kind of problem you have?

Also, you can try switching places between DayNight and %%globals.

[cag014 731]

First of all variable DayNight should be under %%globals. Honestly i don't see any reason to trigger this scene by global variable.

The scene looks OK, so the question is:

How far one sensor from other... I mean if there is any chance that the time that takes to trigger second "sensor"  is longer than time interval return to safe of first sensordrive. In this case it won't work ever.

[T.Konopka 8]

16 hours ago, cag014 said:

First of all variable DayNight should be under %%globals.

Indeed then why is it the other way around in your code?

 

[davidneale 0]

ok will change that around I will have a play with the sensor and see if that works