Is there a minimal breach time required to trigger a scene ?

[fel-x 7]

Hello

I'm having trouble for a few weeks now, with several scenes that do not execute when the condition is met.

They execute in manual mode, but not in automatic mode.

 

I tried quite everything, from resetting the HCL, excluding and including the devices, erasing and rewriting scenes.

Since nothing works, I was monitoring the event panel, and noticed the triggering devices are actually only breached for 1 second.

 

like in this case :

Please login or register to see this image.

/monthly_2020_06/image.png.6d6137f02f37990e3b2ab09ed4d806ca.png" />

 

Is the fact that it is breached @ 18:15:32 and goes back to normal state @ 18:15:33, causing the following scene to be ignored :

 

(This is french for "if Alarme" == "breached" then)

And I could put anything after the "THEN" condition, it will NOT execute in automatic mode. ?

 

The scene is indeed in automatic mode :

 

I have plenty of scenes that work just fine.

This problem only occurs with a smart implant whose inputs are breached briefly (=<1 second). Typically a doorbell.

 

I suppose it should work, since the breach event is recorded in the event panel ?

 

so what's wrong ?

 

 

thanks

 

Edited June 25, 2020 by fel-x

[Flash 103]

Hello @fel-x,

Did you had a look at parameter 150?

Parameter 150:

Input 1 - sensitivity

This parameter defines the inertia time of IN1 input in alarm modes. Adjust this parameter to prevent bouncing or signal disruptions. Parameter is relevant only if parameter 20 is set to 0 or 1 (alarm mode).

[fel-x 7]

Hi @Flash

Thanks for your idea.

However parameter 150 (and 151 for that matter, as both inputs have the same kind of purpose and still fail activating scenes) are set to 10 milliseconds (default was 100 ms).

It never triggers the scene anyway.

 

Technically, if the event panel tells me the input was breached, it should only be logical that any scene that depends on it would be triggered, right?

So I should consider this a Fibaro bug and report it ??

[Flash 103]

26 minutes ago, fel-x said:

So I should consider this a Fibaro bug and report it ??

 

Don't know if it's a real bug, maybe you can ask Fibaro support for an explanation for this behaviour. They can also tell you if you found a bug.