Jump to content

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


  • 0

HC3 - Scene Trigger


moltos

Question

Hi, 

 

this f***ing new "scene declaration" is driving me crazy. Nearly no trigger works as expected in my case:

 

Example (1) Device "LUX" LightSensor: (Trigger: Every Value Change of Light Sensor)

{
    conditions = {
        { type = "device",
        id = 490,
        property = "value",
        operator = "anyvalue",
        isTrigger = true
        }},
    operator = "all"
}
 
 
 
 

 

Nothing happend when value is changed (checked via API "value" and Dashboard), everything works fine when "push: run action".

 

Example (2) Intervall (Trigger: Between 10:00-18:00 every 60 Seconds)

{
conditions = {
    { type = "date",
      property = "cron",
      operator = "matchInterval",
      value = {
         date = { "0", "10", "*", "*", "*", "*" },
         interval = 60
              },
    isTrigger = true
    },
    { type = "date",
      property = "cron",
      operator = "match<=",
      value = {"00", "18", "*", "*", "*","*"}
     } },
  operator = "all"
}

 

Example (3) QuickApp or Device (Trigger: if device is on "true")

{
    conditions = {
        { type = "device",
        id = 490,
        property = "value",
        operator = "==",
        value = true,
        isTrigger = true
        }},
    operator = "all"
}

 

The only scene which works as expected is a simple cron Job to start a scene everyday to same time (same to workaround creating QuickApps).

For me in the current state the scene triggers is a mess.

 

Anyone out here who can help me out in this mess. Is there something wrong in my interpretation?

 

 

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

conditions = {
        { type = "device",
        id = 490,
        property = "value",
        operator = "!=",

        value = -1
        isTrigger = true
        }},
    operator = "all"

Link to comment
Share on other sites

  • 0
23 hours ago, moltos said:

 operator = "anyvalue",

it is anyValue

 

 

Link to comment
Share on other sites

  • 0
  • Inquirer
  • 1 hour ago, Momos said:

    it is anyValue

     

     

     

    If I check the documentation than this is not the case:

    Devices

    For devices, the interpretation of conditions fields is as follows:

    • type – takes value "device".
    • id – takes the ID of the device for which to check if the given property has the given value.
    • property – the name of the property to check.
    • value – value of the property to compare the current value to.
    • operator – depending on type:
      • text type:
        • "==" – are the texts the same
        • "!=" – are the texts different
        • "anyvalue" – match any value
      • numeric type:
        • "==" – are the values the same
        • "!=" – are the values different
        • ">" – is the current value greater than the one in the condition
        • ">=" – is the current value greater than or equal to the one in the condition
        • "<" – is the current value lesser than the one in the condition
        • "<=" – is the current value lesser than or equal to the one in the condition
        • "anyvalue" – match any value
      • logical type:
        • "==" – are the values the same
        • "!=" – are the values different
          rigger the scene if value of device with ID 30
    • isTrigger – is the condition also a trigger:
      • true – is a trigger
      • false – is only a condition (default)

    Examples:

    Link to comment
    Share on other sites

    • 0

    I know.  but what can i say... anyValue works for me ?

    Link to comment
    Share on other sites

    • 0
  • Inquirer
  • On 7/7/2020 at 1:10 PM, Momos said:

    I know.  but what can i say... anyValue works for me ?

     

    Your are right, the documentation is wrong.

    I have sent that information towards the Fibaro support, hopefully they change it and save time of their customers in future.

    • Thanks 1
    Link to comment
    Share on other sites

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...