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

  • Topic Author
  • 5 minutes ago, Sjakie said:

     

     

    That it takes 10s to turn off something is a sign that there is something wrong...

    Could it be that the z-wave network is behaving strange due to some device being faulty and spamming?

    One could try to do a turnOff, check if it came through and if not try again.

    Something like

    Please login or register to see this code.

    ...but it's a bit messy and not a sustainable fix.

    Link to comment
    Share on other sites

    If I switch on/off manual from my laptop all zwave devices responding directly.

    Link to comment
    Share on other sites

    3 hours ago, Sjakie said:

    How to check or monitor the Zwave network?

    Did you try Z-Wave monitor... I mean it should monitor dead traffic.

    Another tool that I think could help you is All-in-One Scene... just download it and run it without any changes.

    You should see Dead traffic table that shows all NACK/dead traffic.

    Edited by cag014
    Link to comment
    Share on other sites

  • Topic Author
  • 7 hours ago, cag014 said:

    Did you try Z-Wave monitor... I mean it should monitor dead traffic.

    Another tool that I think could help you is All-in-One Scene... just download it and run it without any changes.

    You should see Dead traffic table that shows all NACK/dead traffic.

    Yep, I was about to suggest something like @cag014 z-wave monitor. Haven't used it myself but there should be a thread on it in the forum.

     

    Link to comment
    Share on other sites

    Installed and running we will see latertoday what pops up.

    Thanks guys

    Link to comment
    Share on other sites

    Hello Jan,

     

    Is this in ER scenes also a good practice?

    If yes how to write this rule?

     

    Rule.eval([[#eveninglightOn =>  
            zijkant.spotfietsenstalling:on; serre.spotenkel:on; log('TRIGGER:%s',tjson(env.event)); log('spot fietsenstalling en serre spotenkel - aan');
                    log('TRIGGER:%s',tjson(env.event)); log('Evening light on Post flaglightOn - aan')
                            ]])

    Please login or register to see this attachment.

    Link to comment
    Share on other sites

  • Topic Author
  • 1 hour ago, Sjakie said:

    Hello Jan,

     

    Is this in ER scenes also a good practice?

    If yes how to write this rule?

     

    Rule.eval([[#eveninglightOn =>  
            zijkant.spotfietsenstalling:on; serre.spotenkel:on; log('TRIGGER:%s',tjson(env.event)); log('spot fietsenstalling en serre spotenkel - aan');
                    log('TRIGGER:%s',tjson(env.event)); log('Evening light on Post flaglightOn - aan')
                            ]])

    Please login or register to see this attachment.

    In theory this should be a method to limit zwave traffic. In practice I see limited use for this kind of precautions in turning on/off things at specific moments where in 99% of the case you do want to set the opposite state. Put another way, in ER you tend to write rules that follow the state off the device and seldom apply rules to devices with unknown state.

    For a routine that turns off all lights in a house it could make sense to check before as you will probably turn off many devices that are already off.

    However if you try to turn off a device and it doesn’t turn off it’s another matter...

     

    anyway, to check before turning on to make sure you don’t turn if already on would look like (id:isOff&id:on)

    Please login or register to see this code.

    Link to comment
    Share on other sites

    Jan,

    Thanks its clear!

    Yeah in some cases the state of the device is clearly of for example in the mornig if I switch light on.

    Indeed if I turn off all lights they will be turned off all independent off they are on or not.

    Specially for the HUE it can help.

    Will review all my scenes

    //Sjakie

     

    Link to comment
    Share on other sites

  • Topic Author
  • 7 minutes ago, Sjakie said:

    Jan,

    Thanks its clear!

    Yeah in some cases the state of the device is clearly of for example in the mornig if I switch light on.

    Indeed if I turn off all lights they will be turned off all independent off they are on or not.

    Specially for the HUE it can help.

    Will review all my scenes

    //Sjakie

     

     

    Wait a minute. I can easily add that check to ER as I already patch fibaro:call anyway. When I come home this evening I will release a version of ER where you can set a flag if you want fibaro:call to check the value before. It will apply to turnOn/turnOff/setValue.

     

    Link to comment
    Share on other sites

    Wowww Jan that is very convenience.

    To change  with --55:isOff&55:on is a long time job.

    btw I thought & was only to use on the trigger side?

    Thanksssssssssssss

    //Sjakie

    Link to comment
    Share on other sites

  • Topic Author
  • 28 minutes ago, Sjakie said:

    Wowww Jan that is very convenience.

    To change  with --55:isOff&55:on is a long time job.

    btw I thought & was only to use on the trigger side?

    Thanksssssssssssss

    //Sjakie

    Turned out to be an easy fix (I think). I pushed B69.

    Somewhere in the beginning of main() do

    Please login or register to see this code.

    ... to enable the checks.

    Let me know if there are any issues.

    Link to comment
    Share on other sites

    Hi Jan,

    In all scenes implemented no extra error(s) came up.

    The result is not direct visible for me but perhaps will Cag's Zwave monitor shows good numbers.

    Thank you very much for this outstanding service excellence!!!

    //Sjakie

    Link to comment
    Share on other sites

    Hello Jan,

    What is the syntax for;

     

    Rule.eval([[trueFor(>00:05, woonkamer.gordijnvoor:value==0) =>

     

    thanks in advance

    //Sjakie

    Link to comment
    Share on other sites

  • Topic Author
  • 15 minutes ago, Sjakie said:

    Hello Jan,

    What is the syntax for;

     

    Rule.eval([[trueFor(>00:05, woonkamer.gordijnvoor:value==0) =>

     

    thanks in advance

    //Sjakie

     

    Please login or register to see this code.

    This will log when the woonkamer.gordijnvoor:value been 0 for 5 minutes

    (it can't be more than 5min without being passing 5min)

     

    Or was it something else you wanted to achieve?

    Link to comment
    Share on other sites

    Jan,

    All curtains will be closed.

    If the curtain in the living is closed it can take to max 2 hour if the curtain  back side will be closed when the back door closes.

    I have now this rule:

        Rule.eval([[woonkamer.gordijnvoor:value==0 & eetkamer.gordijnachter:isOpen & once(eetkamer.deur:safe) & sunset-00:30..sunrise-00:30 =>
            1740:start; wait(00:00:20); eetkamer.gordijnachter:close; log('TRIGGER:%s',tjson(env.event)); log('Serre deur dicht gordijnachter - sluiten')
                           ]])

    It works good  when the back door stays open even if curtains house are closed.

    Now you hope fully understand the problem if the back door is already closed as all curtains closes it will start also the message,

    1740:start is to start the announcement curtain back will be closed.

     

    So I thought if woonkamer.gordijnvoor:value==0 is longer than lets say 5min  closed and ....

    //Sjakie


     

     

    Link to comment
    Share on other sites

  • Topic Author
  • 14 minutes ago, Sjakie said:

    Jan,

    All curtains will be closed.

    If the curtain in the living is closed it can take to max 2 hour if the curtain  back side will be closed when the back door closes.

    I have now this rule:

        Rule.eval([[woonkamer.gordijnvoor:value==0 & eetkamer.gordijnachter:isOpen & once(eetkamer.deur:safe) & sunset-00:30..sunrise-00:30 =>
            1740:start; wait(00:00:20); eetkamer.gordijnachter:close; log('TRIGGER:%s',tjson(env.event)); log('Serre deur dicht gordijnachter - sluiten')
                           ]])

    It works good  when the back door stays open even if curtains house are closed.

    Now you hope fully understand the problem if the back door is already closed as all curtains closes it will start also the message,

    1740:start is to start the announcement curtain back will be closed.

     

    So I thought if woonkamer.gordijnvoor:value==0 is longer than lets say 5min  closed and ....

    //Sjakie

     

    Sorry, it's late so I'm not sure I still understand (and I haven't learned dutch yet to decipher the variable names :-) )

    However, you can get the time since the device changed state with deviceID:last

    So maybe this works?

    Please login or register to see this code.

    Btw, woonkamer.gordijnvoor:value==0. could be woonkamer.gordijnvoor:isClosed

    Link to comment
    Share on other sites

    Sorry Jan,

    Curtain switch

    Please login or register to see this image.

    /monthly_2019_10/image.png.ae26bef22689f41904f68c7acf9aab46.png" />

    //Sjakie

    Link to comment
    Share on other sites

  • Topic Author
  • 4 hours ago, Sjakie said:

    Sorry Jan,

    Curtain switch

    Please login or register to see this link.

    //Sjakie

    :isClosed, not :isClose...

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