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. |
|
| IDs List |
Devices/scenes/variables/keywords (e.g., `"137,630" |
|
| Criteria & Rules |
Optional conditions like |
|
| Action Tables |
Optional commands: |
🔄 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.
- 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 15.2 See changelog
Released
New features requested by users
- Added an option to define debugging levels for each jM line in order to minimize debugging info on the console and keep user's important information available for quick review.
Please see Advanced Users' Guide:<Rules and options> : <Debugging levels> section.
jM={ {“`motion`”,{state=”true”,dbgInfo=true, trueAct={“`light`”,”turnOn”},falseAct={“`light`”,”turnOff”}}}, }
To set specific level for the specific line regardless global definitions, add dbgInfo=false and [required level]=true.
jM={{“`motion`”,{state=”true”,dbgInfo=false, dbgTrueState=true, trueAct={“`light`”,”turnOn”}}},}
Recommended global debug level setup is for debugged configuration:
dbgInfo =false
dbgTrueState =false
dbgFalseState =false
dbgInitState =false
dbgCmdFalse =false
dbgCmdTrue =true
In case new jM line added and needs to be debugged, inline debug levels definition recommended.
2. During initialization execute tables (trigAct{}, trueAct{}, falseAct{}) if state value has been changed during initialization.
New features
- Major "face lifting" on console view
- Added an option to define conditions "and", "or" on the same line. "if {`sens1`=true and `switch`=false or `switch`=true}"
- Added an option to define number of required verifications in verify statements. {`"switch`,"turnOn!{`switch`=true},6"} - verify up to 6 times if the switch is actually turned ON (true). By default, number of verifications is 4.
- Added an option to define timers for delays that could be controlled (set / re-set) by other devices in different jM lines. Could be used with multiple motion sensors to update same delay definition. Any name could be define, but keep timer prefix
{"`motion1`",{state="true", trueAct={"`lights`","turnOn"}, falseAct={"`lights`","turnOff", "timerLights,300"}}};
{"`motion2`",{state="true", trueAct={"`lights`","turnOn"}, falseAct={"`lights`","turnOff", "timerLights,300"}}};
in example above the last motion sensor that back to safe will update the timer to 300 seconds delay
5. Added new keywords
$lan hub connection to the LAN (true/false)
$wifi hub connection to the WiFi (true/false)
$newSw new SW update available (true/false)
$newBeta new beta SW update available (true/false)
$initMode Indicates if the system is in an initialization process (true/false)
$oldValue Old (previous) value of the device. Very useful to monitor proper action progress of the heating devices by mesauring temperature and to compare between old to new value.
Bugs Fix
-
during verifying initial command not executed.
-
During initialization action states condition are not verified.
-
Cosmetic changes and improvements.
-
minor bug fix
Update Procedure
New users:
Download All-in-One-v15.1.fqa and add to the system as QA device
Exist users:
Download AOQ-main-v15.1.txt and copy to main file in your QA.
