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


All-in-One Scene: How to do it Better


cag014

Recommended Posts

2 hours ago, Rover said:

{"PortSwitch","sendEmail,2","1 1x"}, {"`DimmerLeeslamp`","turnOn;else;turnOff","if {`DimmerLeeslamp`:value=0}"} }}},

"works", but:

  • time between push button and reaction dimmer with SlaveRemote_centralScene-v2.fqa first edition: 9, 19, 8, 41 seconds.
  • very strange that toggling dimmer is not assured: 

    Please login or register to see this spoiler.

Why can the response time so bizar (while it is so continuously bizar, that there cannot be a relation with table updates)?

Link to comment
Share on other sites

  • Topic Author
  • 51 minutes ago, Rover said:

     

    Where can I find "CPU & Scan elapsed time " popup menu?

    How does user function looks like?

    No, my network has no issues. I am the only moderate user of the LAN, no Netflix, etc.

    You can see that in hcWebEye by hovering over Z-wave traffic  statistics

    Please login or register to see this spoiler.

     

    Link to comment
    Share on other sites

    13 minutes ago, cag014 said:

    You can see that in hcWebEye by hovering over Z-wave traffic  statistics

    Please login or register to see this spoiler.

    ???

     

    [26.10.2020] [21:20:01] [DEBUG] [AOQ66]: onAction: {"args":[],"deviceId":66,"actionName":"turnOff"}

    After a webEye Toggle, together with the famous email from Fibaro...

    Edited by Rover
    Link to comment
    Share on other sites

  • Topic Author
  • 1 hour ago, Rover said:

    Please login or register to see this spoiler.

    Could you please to reduce number of jM lines, just to verify that's the problem

    Link to comment
    Share on other sites

    2 hours ago, cag014 said:

    Could you please to reduce number of jM lines, just to verify that's the problem

    jM lines from more than 100 to 53 lines:

    Toggle webEye: [27.10.2020] [00:24:16] [DEBUG] [AOQ66]: onAction: {"actionName":"turnOff","deviceId":66,"args":[]}

    but no email from Fibaro.

    deviceID:66 is AOQ

    Edited by Rover
    Link to comment
    Share on other sites

  • Topic Author
  • 33 minutes ago, Rover said:

    jM lines from more than 100 to 53 lines:

    Toggle webEye: [27.10.2020] [00:24:16] [DEBUG] [AOQ66]: onAction: {"actionName":"turnOff","deviceId":66,"args":[]}

    but no email from Fibaro.

    deviceID:66 is AOQ

    So hcWebEye updated normally

    Link to comment
    Share on other sites

    2 minutes ago, cag014 said:

    So hcWebEye updated normally

    [DEBUG] [AOQ66]: onAction: {"actionName":"turnOff","deviceId":66,"args":[]} means webEye update?

    Link to comment
    Share on other sites

  • Topic Author
  • 2 minutes ago, Rover said:

    [DEBUG] [AOQ66]: onAction: {"actionName":"turnOff","deviceId":66,"args":[]} means webEye update?

    Yes... but do you see that on hcWebEye the data has been updated?

    Link to comment
    Share on other sites

    2 minutes ago, cag014 said:

    Yes... but do you see that on hcWebEye the data has been updated?

    That is hard to say, the last modified date left above is getting updated.

    Link to comment
    Share on other sites

    Everything set back to 122 lines: webEye Toggle: again email from Fibaro. Further nothing special to be seen in webEye (except the two "Uit" GV's that should be &Alarmststatus). And the yellow detail rectangles work!

     

    Edited by Rover
    Link to comment
    Share on other sites

  • Topic Author
  • 1 hour ago, Rover said:

    Everything set back to 122 lines: webEye Toggle: again email from Fibaro. Further nothing special to be seen in webEye (except the two "Uit" GV's that should be &Alarmststatus). And the yellow detail rectangles work!

     

    OK, found it... it's just wrong table arrangement (shifted by using same global name "Alarmstatus"  in HC3 and Hc2). FIXED.

    Attached version includes also verification for "alarm" property on slave controller devices.

     

     

     

     

    Please login or register to see this attachment.

    Edited by cag014
    Link to comment
    Share on other sites

  • Topic Author
  • 1 hour ago, Rover said:

    Everything set back to 122 lines: webEye Toggle: again email from Fibaro. Further nothing special to be seen in webEye (except the two "Uit" GV's that should be &Alarmststatus). And the yellow detail rectangles work!

     

    I'm curious about that, is it means HC3 always reports to Fibaro?

    What will happen if no internet to outside?

    Just for testing, could you please turn off remote access?

    Please login or register to see this spoiler.

     

    Link to comment
    Share on other sites

    I have catched the mysterious GV "Uit".

    At the moment there are 5 GV's  "Uit", that should be GV &Alarmstatus: 

    Please login or register to see this spoiler.

     

    If a delete the line with &Alarmstatus'hc2 then the Uit GV's has been changed to GV &Alarmstatus, like it should!

    Link to comment
    Share on other sites

    7 hours ago, cag014 said:

    I'm curious about that, is it means HC3 always reports to Fibaro?

    What will happen if no internet to outside?

    Just for testing, could you please turn off remote access?

    Please login or register to see this spoiler.

    Also with remote access turned off, the Fibaro email comes when Toggle webEye.

    Link to comment
    Share on other sites

  • Topic Author
  • 2 hours ago, Rover said:

    I have catched the mysterious GV "Uit".

    At the moment there are 5 GV's  "Uit", that should be GV &Alarmstatus: 

    Please login or register to see this spoiler.

    Yes, you're correct, did you try v6.1 - it should be fixed

    Link to comment
    Share on other sites

  • Topic Author
  • 4 hours ago, Rover said:

    Also with remote access turned off, the Fibaro email comes when Toggle webEye.

    It could be a good idea to split the AOQ to two.

    One will control all alarm actions and other all the rest.

    That's what I do on HC2 - two AOS. To synchronize between them,  I use global variables.

     

    Edited by cag014
    Link to comment
    Share on other sites

  • Topic Author
  • To all,

    I'm trying to speed up command execution and to keep CPU low as much as possible.

    Please try attached version and report if it's faster and CPU load still low.

     

     

    Please login or register to see this attachment.

    Edited by cag014
    Link to comment
    Share on other sites

    7 minutes ago, cag014 said:

    It could be a good idea to split the AOQ to two.

    One will control all alarm actions and other all the rest.

    That's what I do on HC2 - two AOS. To synchronize between them,  I use global variables.

     

    Before I am going to split, I should like to comprehence what is going on here.

    What is the HC3 problem with AOQ with a CPU load of 20%?

    Why is Fibaro send email to AOQ has been turned off? What means turned off here, while AOQ is still working?

    Could it be the fact that almost all devices are still HC2 devices? If yes, then the problem is temporary until migration of devices to HC3.

    What is the effect of splitting AOQ to HC3?

    Link to comment
    Share on other sites

  • Topic Author
  • 1 minute ago, Rover said:

    Before I am going to split, I should like to comprehence what is going on here.

    What is the HC3 problem with AOQ with a CPU load of 20%?

    Why is Fibaro send email to AOQ has been turned off? What means turned off here, while AOQ is still working?

    Could it be the fact that almost all devices are still HC2 devices? If yes, then the problem is temporary until migration of devices to HC3.

    What is the effect of splitting AOQ to HC3?

    Regarding the email from Fibaro, I think the best option is to submit ticket to Fibaro support.

    To verify the effect on CPU while two AOQ run, you can just run another instance of your AOQ and to see the effect.

     

     

    Link to comment
    Share on other sites

    3 minutes ago, cag014 said:

    Regarding the email from Fibaro, I think the best option is to submit ticket to Fibaro support.

    To verify the effect on CPU while two AOQ run, you can just run another instance of your AOQ and to see the effect.

     

     

    My HC3 CPU load is not a problem (20%). The only problems now are the response times of (HC2-)devices.

    So why do you do it yourself on HC2? 

    What should be the advantage of splitting?

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