Variable triggering scene when it shouldn't

[perjar 7]

I can't get my head around a problem I am having with variables triggering scenes. So, turning to the forum to see if anyone has any idea.

 

The problem I am having is that a scene is triggered by a variable even if the variable is not named in the LUA trigger section.

 

I created a scene with the following trigger definition:

1. --[[
2. %% autostart
3. %% properties
4. %% globals
5. Var1
6. Var2
7. --]]

 

The scene worked fine. It is triggered by changes in Var1 and Var2 as should be and the LUA code is executed. My debug code verfies it. I can see that both Var1 and Var2 are triggering the scene.

 

Next, I wanted to change the logic a little and no longer wanted Var2 to trigger the scene, only Var1. I still used Var2 in the code however, just not as scene trigger.

 

The new trigger definition looked as follows:

1. --[[
2. %% autostart
3. %% properties
4. %% globals
5. Var1
6. --]]

 

But, to my surprise, the scene is still triggered by Var2! My debug code reports that Var2 is indeed the trigger source. I am confused! 

 

Restarting the HC2 does the trick though. After restarting, the scene works as designed and Var2 no longer triggers the scene. 

 

The same behaviour also applies to block scenes. I have created a  block scene  using Var1 and Var2 in the if-statement and then unchecked Var2 it in the "Triggering variables" list. Same thing happens - Var2 keeps triggering the scene despite the fact that I have unchecked it. If I convert the block scene to LUA code I can see that Var2 is not in trigger definition and hence should not trigger the scene. But it still does!

 

Surely this must be a bug in the system right? Or I am missing something?

 

Thanks

 

Software version 4.160

 

 

[I.Srodka 3]

Hi @perjar!

 

Did you restart (stopped and played) the scene you've edited?

[BOT 0]

The topic has been moved from "Home Center 2" to "Scenes and Interface".

 

Temat został przeniesiony z "Home Center 2" do "Scenes and Interface".

[perjar 7]

48 minutes ago, I.Srodka said:

Hi @perjar!

 

Did you restart (stopped and played) the scene you've edited?

Hi,

 

No, not explicitly. I saved the scene of course after I edited it. But I did not stop it, disable/enable it or similar.

Are you saying the scene needs to be reset or something before some edits take effect?

 

Thanks

 

 

[wpeeters 30]

Hi all, I can confirm the same behavior since some versions ago.
It happens on both HC2 and HCL. In block and Lua. Restarting HC is the only solution.
Unless you delete the scene and create it again, first time wright.
According to me, it happens if you save a scene in between too much.

[perjar 7]

20 hours ago, wpeeters said:

Hi all, I can confirm the same behavior since some versions ago.
It happens on both HC2 and HCL. In block and Lua. Restarting HC is the only solution.
Unless you delete the scene and create it again, first time wright.
According to me, it happens if you save a scene in between too much.

 

Thanks wpeeters, good to know that I am not the only one having this problem.

Let's hope the Fibaro team can fix it in the next release.

 

[I.Srodka 3]

On 30.01.2018 at 4:04 PM, perjar said:

Are you saying the scene needs to be reset or something before some edits take effect?

Did you test it? Did you changed something in the scene and you stopped and resumed it?