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


Quick Apps

The category contains Quick Apps submitted by users.
Downloading and submission terms have to be accepted.

Quick Apps have to be described properly, screen shots are optional.
Support topics are created automatically here Quick Apps

Report topics and files that are no longer supported by authors.
All the files submitted have to be approved by administrators.

2 files

  1. HC3: All-in-One QA

    If you've found yourself with too many Lua and Block scenes and need more automation, this QA is the right solution for you.
    The QA is designated to control and monitor your home system. QA automatically identifies the type of elements in the system. (Z-wave device, QA device, scene, automatic scene (Block and Lua). Any valid Z-wave device property and his value could be monitored, controlled and execute commands accordingly
    All-in-One QA supports custom events, active profile setup and controls alarm zones while every breached zone or sensor in the zone could be identified and execute actions accordingly.
     
    The first time you use All-in-One QA, jM {} hash table must be defined. Each line in the table has two mandatory and two optional fields.
    jM={ {      15,              "137|630",       {timeSlot={“12:00~18:00”},state="value=true",     trueAct={“|230|”, “turnOn”,””}}}   }
               Time span      IDs list                                   Criteria & Rules                                               Action tables
     
    Time span   a period of time (in minutes) within which some activity must be performed by device or scene. Additional two options could be defined:
    time span = 0   defines the line as activity only. time span = ‘negative number’   line is suspended (remarked) IDs list   given list of devices/scenes/QA/global/keywords. Use under score for scene IDs. (“_45”).
    global variable – add an ampersand sign & to System, QA and Local variable names: &varName keyword – add a dollar sign $ to keyword variable: $name Note: To use & and $ characters for other purpose , add % after the character.
    Criteria & Rules  (optional) property, state, time slot, active rules…
    Action tables      (optional) tables of commands to be executed.
     
    To avoid using device IDs  jS2n{} array could be defined. If device ID changed because of re-inclusion it requires to change ID in one place only.
    for example:
    jS2n= {boiler=137, dryer=630, light=230} device name must be included within back apostrophe sign in jM{} hash table.
    Now jM{} hash table above will look like that:
    jM={ { 15,  "`boiler`|`dryer`",{timeSlot={“12:00~18:00”},state="value=true",     trueAct={“`light`”, “turnOn”,””}}}   }
     
    1. Monitor option
    Some time the scenes or QA devices are stuck w/o any understandable reason. Some devices suddenly stop to send reports or don’t change state. In most of the cases we don’t aware about the problem till something goes very wrong.  The monitor option will send an alert in case of defined states are timed out.
    Example to set watchdog timer for devices, scenes, QA devices, global variables and keywords
    jM={     
    {8, "_17|_545",{timeSlot=”10:00~22:00”}},  -- within every 8 min.  between 10am to 10pm, scenes 17, 545 must be active. If not alert sent.
    {3,"134|618|_556|_588"},  -- within  every 3 min. devices 134,618 and scenes 556,588 must be active. If not auto-alert sent.
    {10,”132|145”,{property=”power”}}, -- within every 10 min. devices in list must to report new power value. If not auto-alert sent.
    {30,”470”,{state=”power>10”}}, -- if device’s power greater than 10 over 30 minutes, auto-alert sent.
    {20,”&HomeStatus|$iDoor”}} -- if global variable HomeStatus or keyword iDoor didn’t change within 20 min., auto-alert sent.
     
    2. Control option
    Execute actions based on device state, status or value changes. QA supports option like on-line calculations, time modifications, IF THEN and WHEN THEN statements and other features for fully home automation just with one QA (which even doesn’t trigger by the system). 
    Following action tables are available:
    trueAct{} - executed when state status is true. falseAct{} - executed when state status is false. trigAct{} - executed on every value change at any mode, true or false timeoutAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time span counting restarted after state status back to true. timeLoopAct{} - Disables auto-alert notification and executed when elapsed time exceeds time span. Time counting restarted immediately. InitAct{} - Set of specific actions to be executed on startup only. errACt{} - Set of specific actions to be executed if verification failed.  
    Here is an example of most common scenario, to turn on light when motion sensor breached and turn off light when sensor back to safe after few minutes (3 min. in this example)
    jM={0,”`mSensor`”,{state=”value=true”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}}
    Since no need to turn on light during the day, timeslot could be defined
    jM={0,”`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={“`lightSw`”,”turnOn”,””},falseAct={“`lightSw`”,”turnOff”,”180”}}}
    But now could be an issue to turn off the light, if sensor breached few seconds before end of timeslot and back to safe is out of defined time slot, falseAct{} won’t be executed. In this case, turning light off action should be part of trueAct{} table
    jM={0,"`mSensor`”,{state=”value=true”,timeslot=”18:00~07:00”,trueAct={{“`lightSw`”,”turnOn”,””},{“`lightSw`”,”turnOff”,”180”}}}
    Z-wave devices, global variables and keywords could be defined at several lines (no limit). Scene could be defined one time only.
    For more details please download
    AOQ Advanced User’s Guide - complete instructions and information
    AOQ Quick Guide – syntax format reference and examples
    AOQ HC-WebEye Viewer – AOQ browser viewer guide
     
     QA Advantages:
     
    Debug window view:
    On the first run follow information will be displayed at debugger 
    During normal operation every executed command showed at debugger.
    following data shown for every command:
    jM line number: device name: state value and status by color (green - true  |  pink - false); command executed.
    The debug information has special tag "AOQ<QA-ID>" and "TRACE" / "WARNING" / "ERROR" type for filtering.
    AOQ table preview:
     
    Table's header includes:
    startup time stamp, script current version, scene Name, LED as displayed at HC3 front panel, sunrise/set hours. Current home mode (@home or @vacation) System's current profile mode. Elapsed time Total Z-wave events Min, average and max Z-traffic Table columns are:
    Type – device type (Z.Device, G. Variable, Keyword, QA, luaScene, blockScene). ID: Description – room name: device ID: device name. Z-wave devices sorted by rooms, then by device ID. Battery capable device have green background according to current battery level. If device included in alarm circle icon appears before name. green circle - armed, red circle - breached Value – items current value. Criteria – state of evaluation to determine true or false status. If formula included, the state displayed on green background. Last seen – elapsed time since last status change. Alert – by default this column isn’t shown. If any devices have been alerted the column will be shown. Please notice that in some cases the device could be alerted, but after while it could back to normal activity. For example, if motion sensor is breached over specified time-span, alert notification will be sent. But after a while the sensor back to safe and alert is canceled, “back to normal” notification will be sent.  At header of alert column shown current number of alerts Time Span – time span to monitor state of items. If time span set to 0, then this line acts as activity, no timeout alerts reported. If time span set to negative number, this line is suspended and no actions executed. Time Slot – Time slot range to execute related actions. Timestamp to execute specific action at specific time. Active (in range) time slot shown in green fonts. trueAct – list of actions to execute when the state is true. falseAct – list of actions to execute when the state is true. trigAct – list of actions when the value changes timeoutAct – list of actions to execute when time-span reached.  Timer will be restarted when device state changed again to true. timeLoopAct – list of actions to execute when time-span reached.  Timer restarted immediately after actions table executions. initAct – list of actions to execute on QA startup. Active Rules – non default defined rules (initOnStartup, Vacation, timeSpanOn, onClock, lineState, trigAll) jM{#} - line number in jM{} hash table jM{ hash table line} – shows device location in jM{} hash table.  
    At the bottom of the table two execution lines show:
    list of up to 60 last executed actions (in order of execution) are displayed. (like CNN news line). list of delayed commands to be executed (and time left to execute)  
    All global variables, their values and last modification time shows below the table.
    Note:
    After downloading the QA, upload the file into HC3 While updating new version, please save your tables before (from line 1 up to line    --== SAVE ABOVE SECTION BEFORE UPDATE ==) HC2 users migrated to HC3 and have used All-in-One Scene, just copy your jM{} and jS2n{} arrays, change device IDs and you're ready to go. Please note "setArm" and forceArm" commands not supported in HC3. Use alarm control commands.  

    246 downloads

       (0 reviews)

    6 comments

    Updated

  2. RFID Programmer (extension should be .fqa not lua)

    This is a small QuickApp that will allow you to programme the Zipato RFID reader whist Fibaro sort out HC3 to do this.
     
    Put you details in the Variables section and then click TagID Push or Pin Push
     
     

    42 downloads

       (0 reviews)

    0 comments

    Submitted


  • New reviews

    • By Matz1977 · Posted
      Awesome feature... exactly what I was looking for to restart my HC2 on a regular basis!   One question regarding the substitution of values from fibaro globals, if I may: how would you store a time like 10:00 in a global variable? Fibaro does not accept the : character!?   My basic issue is that I need to use the trigger times and days I configured in the %% time header later in my scene code. Say, I want to send a push notification warning 5 minutes before scheduled reboot t
    • By MARCUSP.I.L · Posted
      Great work, just a few recent bugs - easy set up..
    • By rvsteenbergen · Posted
      Fantastic! Thanks a lot for the huge work. Unbelievable one man can build this. And after al the work there above, makes it available for free. Great work. Much respect.
    • By kevin · Posted
      Works great. Easy to setup and control your AC.   Better than 3 separate devices, just 1 VD to control everything
    • By Twannie · Posted
      Fantastic tool to view the lua output on a big screen f.e. to use with Z-Range analizer, ZWave Monitor etc Really happy with this
    • By Azkikr · Posted
      Very glad to have found this coding. Thank you Sankotronic! I have struggled quite some time with the Hue plugin in the Fibaro marketplace. That one is however heavily outdated.  Now devices can be used from within the Fibaro app and even original Hue scenes that I used a lot are now completely controlled from within Fibaro.
    • By Hallamnet · Posted
      Awesome VD for people to check to see what the infection rate is in their own country, foreign country and the world. And for people who are stat hungry like me. I do find that the site where the stats come from a bit delayed in updating to the most up to date stats compared to sky news and other sources and is no way related to the developer of this well written VD.    Just make sure the instructions of the VD are followed properly and read through before you try and install so you kn
    • By Sankotronic · Posted
      Now your scenes that already have nice and advanced debugging finally have big window to display. Excellent work. Thank you very much for contributing to Fibaro community. 👍
    • By AR27690 · Posted
      Excellent addon which makes your view bigger and richer. I have 21" screen and now I can utilize the full advantage of that. 
    • By magicman · Posted
      At first glance I thought using this scene was beyond me, but after downloading it and asking Cag014 questions of which he answered quickly and expertly, I have transferred 90% of my scenes into AOS and it works seamlessly. Would recommend everyone use this!
  • Highest Rated Submitters

    No ratings this week.

    No ratings this month.

    1. 1
      jgab
      jgab
      1 file  · 
    2. 2
      cag014
      cag014
      8 files  · 
    3. 3
      macjoker
      macjoker
      1 file  · 
    4. 4
      baskalex
      baskalex
      1 file  · 
    5. 5
      Sankotronic
      Sankotronic
      4 files  · 
    1. 1
      cag014
      cag014
      17 files  · 
    2. 2
      Rating
      Rating
      1 file  · 
    3. 3
      Dave_H
      Dave_H
      4 files  · 
    4. 4
      baskalex
      baskalex
      1 file  · 
    5. 5
      Sankotronic
      Sankotronic
      42 files  · 
×
×
  • Create New...