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
Search the Community
Showing results for tags 'condition'.
Found 3 results
-
Would it be possible to add a Description Field in the Conditions / Triggers : This would be very useful in scene creation and debugging. Example: { operator = "any" conditions = { { type = "device", id = 25, property = "value", operator = "==", value = true, duration = 20, isTrigger = true description = "MyDescription1" },{ type = "device", id = 26, property = "value", operator = "==", value = true, isTrigger = true description = "MyDescription2" } } Example code: local triggerDescription = json.encode(sourceTrigger.description) if triggerDescription == "MyDescription1" then print("Action 1 Triggered scene") elseif triggerDescription == "MyDescription2" then print("Action 2 Triggered Scene") else print("Something else triggered the scene") end
-
Global variable as trigger, is there a better way than mine?
jimicr posted a question in Home Center 3
Hi all, I am building our first room using the HC3. Beining used to the HC2 it requires some thinking out of the box for me. My question: I'm building a scene for the ventilation in the new bathroom. I have a MS6 for RH and this part works. Now my challenge: In the future I want all extraction fans turn on when there is a CO alarm. I made an enumerated with 2 "states": Safe and Breached. To get the scene to act on the var change (now by a test scene) I am checking the variable in the condition/ trigger part as a non existing state: "off". Is there a better/ cleaner way to do this? { conditions = { { id = 50, isTrigger = true, operator = ">=", property = "value", type = "device", value = 60 }, { isTrigger = true, operator = "!=", property = "CoAlarm", type = "global-variable", value = "off" }}, operator = "all" } If I add a condition for "Safe" and "Breached" the scene isn't triggered. This works, but it is a weird way to check variables for what you want to do IMHO. Jim -
Hello! I'm new here and I am just building my smart home. I want to install air conditioning in my flat, and here comes the question - can you recomend me any ac system interactiong with Fibaro? How ac unit is connected to Fibaro? Thank you very much for your answers!
