1. ComfortClick
  2. bOS Configurator
  3. Tasks
  4. Questions
0

Switch on a scene using movement detector task

Simen Hagen 3 weeks ago in bOS Configurator / Tasks • updated by Ricardo Pinto | visiontech pt 1 week ago • 1

Hi, I tried to use the movement detector task to trigger a scene. The status of the scene updates to ON when the movement detector value is true, but not the actual brightness values of the lights implemented in the scene. Is there a feedback that needs to programmed?

Also I use a KNX switch to actuate the same scene, KNX switch sends a 1byte telegram to trigger the scene, the scene contains both 1byte ''brightness values'' and 1bit ''switching'' group adresses for lights. This works fine.


 What is the best way to integrate a movement detector? I want the scene to work both from the KNX switch and the KNX movement detector.


Regards

Simen 

Ricardo Pinto | visiontech pt 1 week ago

Hello,

I was a little bit confused about the issue, and had to test it out first, before answering.

So here's what's happening:

On the Movement Detector task, the output can't be a "scene". This output only accepts true/false values, and not run values.

If you notice, when you add a scene to the Output Value, when you select the scene it shows the value "State". That's why when the motion is triggered, you're faking and forcing the state to true, rather than running the scene.

Solution:

Create a Boolean value, call it something like "Scene x trigger" or whatever you want to call it;

Go to the scene you want to execute with the Motion Detector task;

Add the Boolean as Trigger of the scene, set it to Condition: Equals(=); Value: True; Select Allow retrigger;

Go to the Motion Detector task, add that Boolean as the Output Value;

This way, when the motion output is true after getting the motion detection input, it sets the Boolean to true, which in this case is a trigger to run the scene.

Just tested, and this workaround works perfectly.

Best regards

Customer support service by UserEcho