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 20.7 See changelog
Released
Here’s a cleaner, more polished rewrite of your release notes for version 5.183.63 (beta), with improved clarity and formatting:
🔧 Hotfix
- Resolved a critical bug in version 5.183.63 (beta) that caused AOQ to crash.
✨ New Features
-
Encrypted QA Device Detection
- A warning is now displayed when encrypted QA devices are identified.
-
Enhanced Numeric State Criteria
-
Improved display of numeric value conditions:
-
Dishwasher:KitchenPwr[0.7] ➯ ... -
Dishwasher:KitchenPwr[0.7>2.4] ➯ ...
-
-
Improved display of numeric value conditions:
-
Inclusive Value Range Logic
-
Value ranges now include both low and high limits:
-
clock=12~20is nowtrueifclock >= 12orclock <= 20 -
Previously:
trueonly ifclock > 12and< 20
-
-
Value ranges now include both low and high limits:
-
Fractional Local Variables
-
Local variables in the
jP2ntable can now be defined with fractional values (up tomax=3.0) to prevent misidentification when the value matches a device ID.
-
Local variables in the
-
Dead Device Indicator
-
When sending a command,
[X]is shown after the device name if it’s unresponsive:-
Example:
Motion'hc2:Foyer[true] ➯ turnOn{cdrLT[X]}
-
Example:
-
When sending a command,
-
Theme-Based Background
- Background now adapts to light/dark theme for version 181 and above.
-
Alarm LED Behavior
- LED remains off (neither green nor red) when no zones are defined.
-
Physical Source Detection for Switches
-
System attempts to identify manual switch activation:
- Useful for motion-controlled lights with delayed OFF behavior.
-
Example logic:
{"light", {state="true", trueAct={"light", "turnOff", "1800;else;30", "{light:srcType=physical}"}}} -
Light turns off after:
- 30 minutes if manually switched ON
- 30 seconds if triggered by motion or other automation
-
System attempts to identify manual switch activation:
🐞 Bug Fixes
- Various minor fixes and performance improvements.
📥 Update Instructions
For New Users:
-
Download
AOQ-v20.7.fqaand add it as a QA device.
For Existing Users:
-
Download
AOQ-main-v20.7.txtand replace your current main QA file. - Refer to the Advanced User's Guide for details.
⚠️ Reminder: Always back up your previous QA configuration before updating.
Let me know if you'd like this formatted for a changelog, email, or documentation page!
