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
  • Posted (edited)
    12 hours ago, Rover said:

    In order to be able to optimize jM lines, I have two wishes that are familiair to each other:

    1.   state="condition-a" or state="condition-b" or state="condition-c",
      • The number of lines with the same action tables could be diminished.
      • Alternative trigAll with conditions in the action lines is not so elegant.
    2.   If lineState is correct and delayed command initiated, after delay before command execution should the lineState to be verified again.
      • After delay things could be changed so that the actions could be not desired anymore to execute.
      • Necessary conditions in the action lines to accomplish the same effect are not so elegant.

    1. It will reduce the number of jM lines, but same number of lines will appear in table. Every or state... or state... creates a line in table.

    Could you please a post an example of such a line.

    Edited by cag014
    Posted

    Have downloaded the latest version and all my delays with remote HCL (not in the same LAN) are gone!!!!

    I had a huge delays (sometime over 2 minutes) with HCL which is located at other home...

    Thank you 

    Posted (edited)
    13 hours ago, Rover said:

      If lineState is correct and delayed command initiated, after delay before command execution should the lineState to be verified again.

    • After delay things could be changed so that the actions could be not desired anymore to execute.
    • Necessary conditions in the action lines to accomplish the same effect are not so elegant.

     

    I saw today that you possibly changed the Linestate behaviour already after version 7.1, because 

    Please login or register to see this spoiler.

    if the Linestate condition changes in jM(9) after armAlarm verifying in the okAct, then you see Se and not Ok and then the errAct is executed. It looks like the execution of the verify has been interrupted by the change in Linestate. In version 7.1 that was not the case.

    Removing the Linestate has brought a normal execution.

    Conclusion: I do not know whether I should continue my advice to verify again the lineState after delay before command execution.

    Edited by Rover
  • Topic Author
  • Posted (edited)
    1 hour ago, Rover said:

    I saw today that you possibly changed the Linestate behaviour already after version 7.1, because 

    Please login or register to see this spoiler.

    Oops, my bad... forgot to mention that someone have asked if okAct and errAct could be executed according to lineState as well.

    Did that as a trial to see if it works....

    The problem is when the line have verify condition also.

    What do you think about that? I can disable okAct and errAct execution for lineState when verify defined, but keep it in use if not.

    Could you post the line where you have both  lineState and verification defined.

    Edited by cag014
    Posted
    49 minutes ago, cag014 said:

    Oops, my bad... forgot to mention that someone have asked if okAct and errAct could be executed according to lineState as well.

    Did that as a trial to see if it works....

    The problem is when the line have verify condition also.

    What do you think about that? I can disable okAct and errAct execution for lineState when verify defined, but keep it in use if not.

    Could you post the line where you have both  lineState and verification defined.

    Yes it "works" ?‍♂️

    Why interrupt a running verify on armAlarm so that it is misfunctioning?

    Please disable okAct and errAct execution for lineState when verify defined, but keep it in use if not.

    I used the lineState to avoid running this line twice after each other.

    Please login or register to see this spoiler.

     

  • Topic Author
  • Posted
    12 minutes ago, Rover said:

    Yes it "works" ?‍♂️

    Why interrupt a running verify on armAlarm so that it is misfunctioning?

    Please disable okAct and errAct execution for lineState when verify defined, but keep it in use if not.

    I used the lineState to avoid running this line twice after each other.

    Please login or register to see this spoiler.

    lineState errAct and okAct disable when verify define...

     

    Please login or register to see this attachment.

    Posted (edited)
    31 minutes ago, cag014 said:

    lineState errAct and okAct disable when verify define...

     

    Please login or register to see this attachment.

    Sorry for the misunderstanding. I think I did not make myself clear enough: errAct and okAct should not be disabled at all! 

    Edited by Rover
  • Topic Author
  • Posted
    7 minutes ago, Rover said:

    Sorry for the misunderstanding. I think I did not make myself clear enough: errAct and okAct should not be disabled at all! 

    They are not disabled... the priority is for verification process, that's all.

    I mean when lineState defined - errAct and okAct are executed (if defined).

    If verification defined, errAct and okAct executed as well.

    When lineState and verification booth defined, verification process will execute errAct or okAct.

     

    Posted
    3 minutes ago, cag014 said:

    They are not disabled... the priority is for verification process, that's all.

    I mean when lineState defined - errAct and okAct are executed (if defined).

    If verification defined, errAct and okAct executed as well.

    When lineState and verification booth defined, verification process will execute errAct or okAct.

     

    ? That is what it should be, TNX!

    Posted

    It's normal that when initialized aoq force global vars to false?

    I have some gvars ( true/false) and every time i restart aoq those vars are forced to false except the one that is calculated on sunset-sunrise.

    Posted

    I completed a small amount of tests on delay in zwave action and for now aoq 7.7 introduces a very small delay compared to block scene. I'll make a more extensive test on week end but it looks like aoq act now as the old beloved aos on hc2 :-)

     

    Just to be clear delay isn't noticeable ( to my wife too) so it's just a matter of 100-200ms compared to block scene.

    Cag014 it's what you expected?

    Cpu load is very low with some spikes when a lot of actions are executed same time.

    Tnx for your hard work and i'll send you feedback in a few days

  • Topic Author
  • Posted
    12 hours ago, gggizmo said:

    It's normal that when initialized aoq force global vars to false?

    I have some gvars ( true/false) and every time i restart aoq those vars are forced to false except the one that is calculated on sunset-sunrise.

    if we're talking about AOQ internal GVs then yes it is normal if you don't use system global variable to store the values.

    global4local= {false,gVarName="",varArray={...}}

    please define and assign system global variable to save the value and then on startup values will be retrieved to their last settings.

    global4local= {true,gVarName="AOQgv",varArray={..}}

    Posted
    16 hours ago, SmartLifeSystems said:

    @cag014,

     

    The restart problem back again.

     

    This problem is only on my HC3?

    Posted
    11 minutes ago, cag014 said:

    if we're talking about AOQ internal GVs then yes it is normal if you don't use system global variable to store the values.

    global4local= {false,gVarName="",varArray={...}}

    please define and assign system global variable to save the value and then on startup values will be retrieved to their last settings.

    global4local= {true,gVarName="AOQgv",varArray={..}}

    No i'm talking about system global vars. Every system global var returns to false when i restart aoq, except the one calculated in oninit stage...

    Posted

    Please login or register to see this spoiler.

    Is it a serious problem?

  • Topic Author
  • Posted (edited)
    2 hours ago, Rover said:

    Please login or register to see this spoiler.

    Don't know if it's serious, but I have same behavior... internet on -off

    By the way please remove RAM,Internet and HC3online lines from one of the AOQs... it's good enought that just one AOQ will follow  the status.

    Or you can remove it at all.

     

    Edited by cag014
    Posted

    Hi Cag,

    If I want to use

    jSlave={ 
        hc2={user=.........
    What to write in the j2Sn table?
    If I use HC2 ID's it give an error
     
    //Sjakie
    Posted

    How to stop a rptAction before all defined repetitions have been finished?

    Posted (edited)
    3 hours ago, Sjakie said:

    Hi Cag,

    If I want to use

    jSlave={ 
        hc2={user=.........
    What to write in the j2Sn table?
    If I use HC2 ID's it give an error
     
    //Sjakie

    Aap="<deviceID>'hc2",

    Edited by Rover

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