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


Recommended Posts

Posted

Jan, getting error

Please login or register to see this code.

 

  • Topic Author
  • Posted
    On 6/24/2026 at 9:21 PM, Sjakie said:

    Jan how to write in ER7?

    Please login or register to see this code.

     

    Fixed in latest version.
    Now ID:msg will use fibaro.alert('simplePush',{id},...)
    The push push method can be changed by setting 
    fibaro._pushMethod = 'simplePush'
    to ex. 'push'. However, I have only made it work for me with 'simplePush'

     

  • Topic Author
  • Posted
    1 hour ago, Sjakie said:

    Jan, getting error

    Please login or register to see this code.

     

    I had spelled it vnum...
    pushed new version with the correct wnum variable defined. (v0.1.47)

  • Topic Author
  • Posted (edited)

    Yes, it looks ok.
    You could do

    Please login or register to see this code.

    You may also want to check that there is a Morning,Day,Event,Night field in p.

    Edited by jgab
  • Topic Author
  • Posted

    A note about time check t1..t2.

    rule("10:00..11:00 => ... ")

    will trigger the rule at 10:00, and it will also trigger the rule at 11:00:01,

    e.g. 1 second after the second bound.

    However, that last trigger will usually fail as 11:00:01 is not within 10:00..11.00
    The reason that ER will anyway generate a trigger for 11:00:01 is that we may have a rule like
    rule("!(10:00..11:00) => ...")
    meaning if we are not in the interval, the condition should be true.

    Now because we trigger at 11:00:01 that is outside the interval, the test is false, but the not version is true and the condition becomes true... what we want. 

    Posted

    Jan any progress to be informed about new version update? Subscribe for e-mail notification?

    Join the conversation

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

    Guest
    Reply to this topic...

    ×   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...