Trigger based on global variable

[jnathalia 0]

I'm reprogramming scenes after implementing a second house with a HC2 and trying to follow a different approach.

 

The approach is driven on global variables. If the value is changed the trigger should start. But it doesn't.

 

I have a global variable "avondverlAan" and after changing the value via the admin panel nothing is being triggered. What am I doing wrong? I did the same before with "properties" based on the value of a PIR from Satel which is also a device in HC2. But nothing happens. It only works if an original device from Fibaro is declared at properties, like "5 value", then the scene is triggered as it should be.

 

--[[

%% properties

5 value

 

%% globals

avondverlAan

--]]

 

local trigger = fibaro:getSourceTrigger()

 

if (trigger['type'] == 'property') then

  fibaro:debug('Source device = ' .. trigger['deviceID'])

elseif (trigger['type'] == 'global') then

  fibaro:debug('Global variable source = ' .. trigger['name'])

elseif (trigger['type'] == 'other') then

  fibaro:debug('Other source.')

end

  

[jnathalia 0]

seems like it does work when one of the scripts is changing the variable. It is NOT being triggered when the value is changed via the admin panel/variables. Weird...! How do you see this?

[boomx 43]

Yes, thats right. You have to change the value with a scene. It doesn't work if you change it manually 

[XanderF 8]

I noticed that too. I also made a script to turn on garden lights based on the change of a global variable. I spend a lot of time debugging what was wrong, because nothing happened when I changed the global variable manually. But when I used a script to update the variable it did work. Unfortunately Fibaro hasn't implemented this correctly.