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
Neo Andersson 177
Hello Jan, i am moving the discussion here..
In a rule like this
Please login or register to see this code.
i can understand, that 'once' statement is good for cases like this..when ext_lux_sensor value drops under 720, we don't want the action to be triggered every time, this is clear to me. But we don't want to use this lux checking part as a trigger!!! That is the problem. I want it to be a condition and not a trigger. Thats why i asked how to use it.
So i don't want the light to be turned on at all whatever the ext_lux_sensor value is, i just want it to be controlled in case of office_sensor is breached. So how to do that? How to make a condition (NOT a trigger). I checked the logs you mentioned, and it says
Please login or register to see this code.
, meaning that the lux sensor changing will be used as trigger also.
And if using the 'once' statement, should i use it for the entire left part of the rule e,g,.
Please login or register to see this code.
or just for the sensor part e.g.
Please login or register to see this code.
Link to comment
Share on other sites
9 answers 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.