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


2 Screenshots

About This File

 

🧠 What AOQ (All-in-One QuickApp) Offers

  • Multi-System Control: Seamlessly manages HC3, HC2, and HCL controllers using master/slave architecture.
  • Unified Automation: Replaces scattered Lua and Block scenes with one centralized QA.
  • Device Intelligence: Auto-detects Z-Wave, ZigBee, Nice, QA devices, and scenes.
  • Alarm Zone Management: Identifies breached zones/sensors and triggers actions.
  • Custom Events & Profiles: Supports dynamic profiles and custom rule-based automation.

🛠️ Core Configuration: Job Management - jM{} Hash Table

Each line in jM{} includes:

Field

Description

Time Span

Duration in minutes for monitoring or action. 0 = activity only, negative = suspended

IDs List

Devices/scenes/variables/keywords (e.g., `"137,630"or"_45"` for scenes)

 
Criteria & Rules

Optional conditions like state="value=true" or property="power"

Action Tables

Optional commands: trueAct{}, falseAct{}, trigAct{}, etc.


🔄 Device Aliasing with jS2n{}

Avoid hardcoding device IDs:

jS2n = {mSensor=200, boiler=137, dryer=630, light=230, timeScene="_17"}

Use aliases in jM{}:

jM={ 
{15,"`mSensor`",{state="value=true", trueAct={"`light`", "turnOn"},falseAct={"`light`", "turnOff"}}} 
}

🔍 Monitor Option

Detects inactivity or failure to report:

{8, "`timeScene` and _545", {timeSlot="10:00~22:00"}} -- scenes must be active every 8 min between 10am to 22pm
{10, "`boiler`and 145", {property="power"}} -- must report power every 10 min
{30, "`boiler`", {state="power>100"}} -- alert if power >100 for 30 min

⚙️ Control Option

Example: Turn on light when motion sensor is breached, turn off after 3 min when motion sensor back to safe:

jM={"`mSensor`",{state="value=true",trueAct={"`lightSw`","turnOn"},falseAct={"`lightSw`","turnOff", "180"}}}

To restrict to nighttime:

 

jM={"`mSensor`",{state="value=true",timeslot="18:00~07:00", trueAct={"`lightSw`","turnOn"},falseAct={"`lightSw`","turnOff", "180"}}}

 

Example: Turn on light when motion sensor is breached, turn off after 3 min (regardless of when motion sensor back to safe) 

jM={"`mSensor`",{state="value=true", trueAct={{"`lightSw`","turnOn"},{"`lightSw`","turnOff", "180"}}}}

🧪 Debug & Table View

  • Debugger Output: Shows executed commands with color-coded status.
Spoiler

image.thumb.png.16c62fd7a0e9ee01c432bc41a0b16470.png

  • Table Header: Displays system info, sunrise/sunset, home/vacation mode, system traffic. 
  • Columns:
    • Device type, ID, name, battery status
    • Criteria evaluation
    • Alerts and elapsed time
    • Action tables and active rules
📊 Top Active Monitor (New) 

AOQ now includes an enhanced Top Active Devices monitor designed to identify devices that may destabilize HC3 performance.

It analyzes lifetime activity, current load per hour, and burst behavior to detect devices generating excessive or abnormal traffic.

The table highlights devices that may cause delays, radio congestion, disconnects, or even controller restarts.

A Peak/h column appears only when abnormal bursts are detected, helping users quickly locate problematic devices without cluttering the interface.


📘 Want to Go Deeper?

You can find the full documentation and guides on the Smart Home Forum by FIBARO, including:

  • AOQ Advanced User’s Guide
  • AOQ Quick Guide
  • AOQ HC-WebEye Viewer

Edited by cag014
Updated


What's New in Version 1.2   See changelog

Released

New feature:

  • added ability to use global variables of other Quick Applications. format is &<QA-ID><varName> (e.g. &78myVar)
  • added option to verify states, status of any item in the system after command execution. Verification format is the same as conditional statement format(e.g. {0,"`wTemp`",{state="value<25",trueAct={"`wHeater`","turnOn!{`wHeater`:energy>700}",""}}},
  • added errAct{} array to execute command(s) if verification failed. (e.g.

{0,"`temp`",{state="value<25",trueAct={"`Heater`","turnOn!{`Heater`:energy>700}",""},errAct={"State Error","sendEmail","Heater doesn’t turned ON"}}},

  • added verify! command, recommended to define errAct{} table to execute commands in case verification failed, otherwise warning displayed in debug window and in hcWebEye table.

            {0,"`temp`",{state="value<25",trueAct={"","verify!{`heater`:energy>700}",""},errAct={{"State Err","sendEmail","Heater doesn’t turned ON"},{"`heater`","turnOff",""}}}},

  • added prefix to every displayed command to indicate executed table belonging
Spoiler

image.thumb.png.5e08324286d244c43cce9c750d2db8c1.png

Spoiler

image.thumb.png.c936cc3d0fffa10ee4645f80729de9f1.png

  •  

image.png

  • Like 7
  • Thanks 1


User Feedback

You may only provide a review once you have downloaded the file.


AR27690

   3 of 3 members found this review helpful 3 / 3 members

One of the must application before migrating devices from HC2. The master/slave option is an excellent tool even to control secondary HC3. Provides remote control for any HC3/HC2/HCL at any place on the globe. By using this QA have decided to keep HC2 as is (except few devices) and to expand my smart home with more devices connected to HC3.

Simple slave emulation devices could be used in HC3 Lua/Block scenes regardless AOQ usage.

Thank cag014 for this wonderful QuickApp, makes HC3 better controller. 

  • Like 1
×
×
  • Create New...