Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team
Question
dcspock 17
Hi,
Over the last years I have tried many Motion Sensor Scenes to turn on lights after motion is detected (I have 4 Merten outside and around 10 Fibaro inside the house installed).
The problem with the Fibaro sensors is the reliability to update the “last breached” value and the value itself - so either I am still in the room and the light turns off (so the last breached value was not updated) or I am leaving the room and the light is still on (the value is kept to breached)... very unreliable und unpredictable - with one Motion Sensor it worked (most of the time) with two sensors for the same room it drives me crazy.
now the Merten sensors do not have a “last breached” value by default, the only set the “value” to 1 and directly back to 0 when there is motion detected. That forced me to come up with two scenes: one is used to set a global variable to the current time stamp in case of a breach and it starts the second scene turning on the lights and then comparing the current time with the global variabele - if threshold (ie 60sec) is gut, turn off the lights. This way, I (at least believe) to have one very short and efficient scene to set the global variable to the new value every time there is motion and one scene continuously running to check and turn off the lights...
As I have ten motion sensors - and this is my actual question for your comments, thoughts and feedback - would it make sense to have like 10 (less if I use two sensors in one room of course) slim scenes to update the global variables / turn on the light and then have ONE scene continuously running (all the time like a scheduler) checking to turn them off?
Does that make scenes at all? Would it be more efficient? The scenes would be independent (currently one starts the other), the “trigger” scenes very very slim...
thanks for feedback
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.