Scene with multiple triggers treats AND as OR

[lurendrejer 0]

Hi.

Please take a look at the attached scene.

 

Why does the 'then = Turn ON' fire when the variable changes?

 

I only want to 'ON' the garagedoor when the button is pressed AND the position is "Åben".

I can recreate this with every thinkable device, variable, etc. All scenes with (If Var1/Device1 and Var2/Device2 Then Device3) will fire when the last device or variable (Var2/Device2) is triggered via another scene.

 

 

Please login or register to see this attachment.

Edited June 19, 2017 by lurendrejer

[Torbjorn 6]

Hi,

 

I think you have the variable as a "releasing variable" and then it will trigger the scene by itself.....

 

Untick   the box at the red arrow (my example only) and save scene

 

I learned this trick today as having the same problem...

 

OK ??

Please login or register to see this attachment.

[lurendrejer 0]

You are my hero! Thank you.

 

 

Can somebody explain why we have 'or' as and option? And+the mentioned checkmark does exactly the same as 'or'

 

/From my mobile phone

 

[lurendrejer 0]

This is still not "solved".

There is still something fishy going on if you have a scene with two triggers. My garage will keep rolling up and down if I initiate the "up" scene once, via the keypress.

After going up, the variable change ($garage=open) will then trigger the down-scene, in turn triggering the variable ($garage=closed) and so forth.

 

 

[Torbjorn 6]

Hi,

 

Can you please temporarily turn on the LUA code (not permanent), copy the code and post here.....

[lurendrejer 0]

Sorry, i only have an HCL. 

No lua.

 

Anything else i can do?

The problem/bug os easily replicatable.

 

[Torbjorn 6]

Aaaahh, I see.

 

Sorry, but my knowledge is not so good in this case, we have to wait for some experts to reply....

 

Good luck !

[lurendrejer 0]

Thank you anyways

[Sankotronic 2,370]

21 hours ago, lurendrejer said:

This is still not "solved".

There is still something fishy going on if you have a scene with two triggers. My garage will keep rolling up and down if I initiate the "up" scene once, via the keypress.

After going up, the variable change ($garage=open) will then trigger the down-scene, in turn triggering the variable ($garage=closed) and so forth.

 

 

 

@lurendrejer,

 

There is nothing strange going on except that you need to understand how scenes and triggers work. You can't trigger scene that is used to control garage door with global variable which value is change with same scene! You just need to remove global variable not to trigger scenes to open and close garage door and they will stop opening and closing all the time.

 

So, the question is what you want to achieve with this scenes for garage door?

[lurendrejer 0]

Hi.

 

Let us forget the variables. I wan't two conditions to be true, before an action is performed.

 

The reasoning:

I have a garagedoor, which has one fibaro relay installed which both opens and closes.

I have a LED light by the front door, which is controlled by a sensor on the garagedoor.

 

What i want is a button that always closes the door, hence:

IF Door-button pressed, and garagedoorLED=ON then OPEN/CLOSE garage ELSE NOTHING.

 

I don't want the garagedoor to react, if it's already closed.

What happens is: IF any CONDITION = TRUE then OPEN/CLOSE.

 

I have to control the LED via scenes triggered by the battery-powered sensor. 

 

The variable was just because is was trying to figure out what the hell happened, and i thought it would be easier to understand for the person reading.

Edited June 21, 2017 by lurendrejer

[lurendrejer 0]

Just tried something completely different.

IF "Sunrise+20min" 

AND "Kids night light" DIM = 1%

Then "Kids night light" = OFF

 

What happens is: If i dim the lights to 1% (at any time via a scene) it will turn off.

 

That can't be the way it was ment to behave, can it?

Edited June 21, 2017 by lurendrejer

[kunoch 27]

@lurendrejer: try to set the scene to manual and not automatic in the general tab, Then select the button as the trigger in the details tab. This would then only start the scene if the button is pressed.

Same annoying behavior if the scene is run manually in the scene overview. independently of the IF conditions the THEN is executed.

Sorry to say with all the other bugs and the daily crashes, the system is getting somewhat useless for me as well. Especially the daily crashes are for me the point for not going further into bugaro and most likely to change over to openhab.

Edited June 22, 2017 by kunoch

[lurendrejer 0]

@kunoch

Hi, and thank you - I have tried that before, but as far as i can remember the scene just didn't fire. I'll try again later today to doublecheck.

I've actually been looking at both homeseer and openHAB - both of which would do this sort of thing with ease. I used HS3 as a secondary controller to update firmware on my devices that fibaro wouldn't/couldn't update.

 

The thing is, these types of scenes did work once, but recreating them on the latest firmwares just doesn't.

 

I'll be looking at Athom Homey in the near future.

Edited June 23, 2017 by lurendrejer

[lurendrejer 0]

Nope, when the scene is manual, it doesn't fire when the button is pressed.

The thing you mention with fibaro not evaluating IF statements when scenes are run manually was posted about before - I always found it strange.

 

Thank you your input though..

[lurendrejer 0]

What i'm doing is exactly this (that last picture in the article): 

Please login or register to see this link.

And it doesn't work. (AND is treated as OR)

 

 

[kunoch 27]

@lurendrejer: yes you are right (sorry), manual does not wait for something from a sensor, only the play within the interface runs it

[lurendrejer 0]

I tried a few things and if i recreate the scenes, from scratch and copy the scenes and change the devices/variables it doesn't work. (It must maintain some info from the copied scene).

If I recreate every single scene by hand, from scratch - it actually works as intended.

 

nice fibaro....

[kunoch 27]

That copy scene does not work is unfortunately a known issue. I faced the same with scenes, so every scene to be written from scratch

can take a few hours easily

[Jamie mccrostie 82]

16 hours ago, kunoch said:

That copy scene does not work is unfortunately a known issue. I faced the same with scenes, so every scene to be written from scratch

can take a few hours easily

 

Agreed copy scenes doesnt work