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)
    3 hours ago, Rover said:

    {"&tChangeScene","setGlobal","Arm timerArm,600","if {&tVertraagdWeg=Ja}"},

    The timer in this line does not function in AOS, but is accepted by AOS.

    Wat do I wrong?

    AOS version 9.6 does not support that. Just pure timer instead of delay - not supported when on the samel line parameter required.

    However, attached version V10.0 does (will be released soon)

    Please login or register to see this attachment.

     

    In order to keep your configuration, copy/paste new release into your scene from the line

     

    --=============== Copy/Paste form here to the end for a new release ===================

     

    to the end of the code

     

    Let me know if it works

    Please login or register to see this attachment.

     

     

    Edited by cag014
    • Thanks 1
    Posted (edited)

    jM:   {"&XVoorkamer|&XSerre","setGlobal","Stop"},

    result: 

     

    [DEBUG] 15:18:12: Starting AOS - 10.0
    [DEBUG] 15:18:18: [ ] exception: /opt/fibaro/scene/451.jM hash table:19:

    {0,"$blank",{"state"="value=whatever","initAct"={{"&tVoorpoortAlarm","setGlobal","Uit"},{"&tAchterpoortAlarm","setGlobal","Uit"},
    {"&tBeveiliging","setGlobal","Uit"},{"&tAlarmKnipper","setGlobal","Uit"},{"&tAlarmstatus","setGlobal","Uit"},{"&tBlauwKnipper","setGlobal","Uit"},
    {"&tBlauwFlits","setGlobal","Uit"},{"&tChangeScene","setGlobal","Stop"},{"&tHuisstatus","setGlobal","Thuis"},{"&tVertraagdWeg","setGlobal","Nee"},
    {"&XVoorkamer|XSerre","setGlobal","Stop"}}}}
    (33) Global variable &XVoorkamer|XSerre or its value XVoorkamer|XSerre not found as global.
    [

    What is wrong?

     

    In other lines with concatenated globals no problem at all...

    Edited by Rover
    Posted
    17 hours ago, cag014 said:

    AOS version 9.6 does not support that. Just pure timer instead of delay - not supported when on the samel line parameter required.

    However, attached version V10.0 does (will be released soon)

    Please login or register to see this attachment.

     

    In order to keep your configuration, copy/paste new release into your scene from the line

     

    --=============== Copy/Paste form here to the end for a new release ===================

     

    to the end of the code

     

    Let me know if it works

    Please login or register to see this attachment.

     

     

    Hi @cag014,

    The timer works 🙂

    Posted

    [DEBUG] 17:19:18: Starting AOS - 10.0
    [DEBUG] 17:19:28: Arranging data table...
    26-Sep 17:19:17 AOSv10.0 AOS 9.6          sunHours 07:34~19:32    GMT +2

     

    Two versions at a time?

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

    [DEBUG] 17:19:18: Starting AOS - 10.0
    [DEBUG] 17:19:28: Arranging data table...
    26-Sep 17:19:17 AOSv10.0 AOS 9.6          sunHours 07:34~19:32    GMT +2

     

    Two versions at a time?

    Sorry, version in progress... thanks for pointing out on that.

    7 hours ago, Rover said:

    jM:   {"&XVoorkamer|&XSerre","setGlobal","Stop"},

    result: 

     

    [DEBUG] 15:18:12: Starting AOS - 10.0
    [DEBUG] 15:18:18: [ ] exception: /opt/fibaro/scene/451.jM hash table:19:

    {0,"$blank",{"state"="value=whatever","initAct"={{"&tVoorpoortAlarm","setGlobal","Uit"},{"&tAchterpoortAlarm","setGlobal","Uit"},
    {"&tBeveiliging","setGlobal","Uit"},{"&tAlarmKnipper","setGlobal","Uit"},{"&tAlarmstatus","setGlobal","Uit"},{"&tBlauwKnipper","setGlobal","Uit"},
    {"&tBlauwFlits","setGlobal","Uit"},{"&tChangeScene","setGlobal","Stop"},{"&tHuisstatus","setGlobal","Thuis"},{"&tVertraagdWeg","setGlobal","Nee"},
    {"&XVoorkamer|XSerre","setGlobal","Stop"}}}}
    (33) Global variable &XVoorkamer|XSerre or its value XVoorkamer|XSerre not found as global.
    [

    What is wrong?

     

    In other lines with concatenated globals no problem at all...

    AOS does not support number of global variables in one line for setGlobal

    You need to update them one by one.

     

    Edited by cag014
    Posted

    I got the idea that 

    {"$blank",{state="whatever", initAct={

    is not working at all in AOS, I do not see any reporting of execution.

  • Topic Author
  • Posted
    3 hours ago, Rover said:

    I got the idea that 

    {"$blank",{state="whatever", initAct={

    is not working at all in AOS, I do not see any reporting of execution.

    What exactly you attend to do?

     

    $blank is a special placeholder with only one possible value: "blank".

    When you wrap $blank inside a time span definition, it becomes a scheduler:

    Please login or register to see this code.

    • The 20 means every 20 minutes.
    • $blank is used as the “device” to attach the loop to (state="blank" must be defined, any other value won't start the time loop)
    • timeLoopAct will execute on each interval tick.

    If you just declare $blank without a time span, its trueAct or falseAct or initAct will only run once at initialization (when the QA loads).

    If your goal is to run something only once at startup, you could use $initMode as a condition in statements "if{$initMode=true}"

    • Use $blank + time span → recurring interval actions.
    • Use $blank alone → runs once at init.
    • Use $initMode → explicit startup actions.

     

     

    Posted
    2 hours ago, cag014 said:

    What exactly you attend to do?

     

    $blank is a special placeholder with only one possible value: "blank".

    When you wrap $blank inside a time span definition, it becomes a scheduler:

    Please login or register to see this code.

    • The 20 means every 20 minutes.
    • $blank is used as the “device” to attach the loop to (state="blank" must be defined, any other value won't start the time loop)
    • timeLoopAct will execute on each interval tick.

    If you just declare $blank without a time span, its trueAct or falseAct or initAct will only run once at initialization (when the QA loads).

    If your goal is to run something only once at startup, you could use $initMode as a condition in statements "if{$initMode=true}"

    • Use $blank + time span → recurring interval actions.
    • Use $blank alone → runs once at init.
    • Use $initMode → explicit startup actions.

     

     

    I want to use $blank alone for → runs once at init. It was your advice on this forum at 11/15/21:

         The initAct={} has same format as trueAct={} or any other action.

         Since you probably don't have any specific device to set the jM line, so use $blank keyword

         {"$blank",{state="whatever", iniAct={"`sImplant`","<set relay command>"}}},

     

    I suppose that the iniAct commands are to be seen in the debugger text, but there is not one initAct action to be seen.

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

    I want to use $blank alone for → runs once at init. It was your advice on this forum at 11/15/21:

         The initAct={} has same format as trueAct={} or any other action.

         Since you probably don't have any specific device to set the jM line, so use $blank keyword

         {"$blank",{state="whatever", iniAct={"`sImplant`","<set relay command>"}}},

     

    I suppose that the iniAct commands are to be seen in the debugger text, but there is not one initAct action to be seen.

    initAct not iniAct   (should be init with t)

    Have tested that and it works

    Posted
    Just now, cag014 said:

    initAct not iniAct   (should be init with t) : I know, it was your text

    Have tested that and it works : But why is nothing to be seen in the debug part?

     

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

     

    It shown in the debug console. 

    jM line 

    {"$blank",{state="whatever", initAct={"","tts","started"}}},
    debug console

    [TRACE] [AOQ32]: jM{1} $blank[blank]  tts{"started"}

    • Thanks 1
    Posted (edited)
    5 minutes ago, cag014 said:

    It shown in the debug console. 

    jM line 

    {"$blank",{state="whatever", initAct={"","tts","started"}}},
    debug console

    [TRACE] [AOQ32]: jM{1} $blank[blank]  tts{"started"}

    Yes, I see it now.

    TNX cag

    Edited by Rover
    • 3 weeks later...
  • Topic Author
  • Posted (edited)

    New

    Please login or register to see this link.

    has been released.

    Edited by cag014
    • Thanks 1
    Posted

    Hi @cag014,

    I know you have posted once an AOQ or AOS icon, but I cannot find it.

    Could you please post it again?

    Posted
    8 hours ago, cag014 said:

    New

    Please login or register to see this link.

    has been released.

    Works for HC3 in Firefox.

    in Edge:

    Please login or register to see this spoiler.

     

  • Topic Author
  • Posted (edited)

    Did you disable the CORS?

    Please follow instructions in DISBALE CORS user guide

    2 hours ago, Rover said:

    Hi @cag014,

    I know you have posted once an AOQ or AOS icon, but I cannot find it.

    Could you please post it again?

    The icons aoqon and aoqoff are in download section of the AOQ.

    Please login or register to see this attachment.

    Edited by cag014
    • Thanks 1
    Posted
    40 minutes ago, cag014 said:

    Did you disable the CORS?

    Please follow instructions in DISBALE CORS user guide

    The icons aoqon and aoqoff are in download section of the AOQ.

    Please login or register to see this attachment.

    Yes, I have disabled the CORS. The HC3 in 

    Please login or register to see this link.

     on Firefox is working, but not the HC2 ("not implemented"). Maybe the port addition to the IP-address is a problem.

    By the way, with 

    Please login or register to see this link.

     3.0 the HC2 with the same IP-address with port is functioning O.K. on Firefox.

    Posted

    How do I accomplish in

    Please login or register to see this link.

     that the debugging lines are not vanishing after some time, but stay forever or until I want to delete them?

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

    es, I have disabled the CORS. The HC3 in 

    Please login or register to see this link.

     on Firefox is working, but not the HC2 ("not implemented"). Maybe the port addition to the IP-address is a problem.

    By the way, with 

    Please login or register to see this link.

     3.0 the HC2 with the same IP-address with port is functioning O.K. on Firefox.

    If you are forwarding a port, it must be included in the IP address.
    Port 80 is the default HTTP port and does not need to be specified.
    For any other port, append it to the IP address (e.g., http://192.168.1.10:8080).

    Just now, Rover said:

    How do I accomplish in

    Please login or register to see this link.

     that the debugging lines are not vanishing after some time, but stay forever or until I want to delete them?

    Do you mean line like that?

    Please login or register to see this attachment.

    Posted
    8 minutes ago, cag014 said:

     

    If you are forwarding a port, it must be included in the IP address.
    Port 80 is the default HTTP port and does not need to be specified.
    For any other port, append it to the IP address (e.g., http://192.168.1.10:8080).

     

    Do you mean line like that?

    Please login or register to see this attachment.

    Above you can see that I had already added a port number, what is working in Firefix with webeye 3.0, but not with webeye 4.0.

    No, I did not mean this debug information, but all the reporting lines of a working webeye.

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