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 22.0   See changelog

Released

What's New


🔧 Hotfix

  • When a device in the jM line lacks a defined property or state, AOQ may crash.
  • Resolved fibaro.alert() issues affecting push and email notifications, caused by changes in recent Fibaro platform versions.
  • Using ‘true’ or ‘false’ as the parameter value causes AOQ to misinterpret the input as an error and abort execution.

 New Features

  1. Data table

    • Cosmetic enhancements
    • Popup menu now includes sliders to reduce menu size, addressing the previously bulky and inconvenient layout.
  2. Execution Efficiency Improvement
    • Replaced setInterval() with setTimeout() to improve execution efficiency by an estimated 10–20% and to reduce the likelihood of system restarts caused by accumulated interval callbacks.
    • Several functions have been optimized with the assistance of AI (Copilot) to improve performance.
  3. Enhanced Expression Calculation Accuracy

    • Updated expression evaluation logic to apply multiplication and division before addition and subtraction, removing the need for extra parentheses.
      • As a result, expressions such as 2 + 2 * 2 now correctly evaluate to 6 instead of the previous result of 8.
  4. Theme-Based Background

    • Background now adapts to light/dark theme for version 181 and above.

🐞 Bug Fixes

  • Various minor fixes and performance improvements.

📥 Update Instructions

You’re welcome to download the new AOQ Advanced User’s Guide-AI-v1 created with AI (Copilot). Your thoughts and feedback would be truly appreciated.

  • The Geofence Guide is now included in the Advanced User Guide.

For New Users:

  • Download AOQ-v22.0.fqa and add it as a QA device.

For Existing Users:

  • Download AOQ-main-v22.0.txt and replace your current main file in Quick App

 

⚠️ Reminder: Always back up your previous QA configuration before updating

  • Like 7
  • Thanks 1


User Feedback

Recommended Comments



AR27690

Posted

Hi cag014

I cannot find AOQ HC-WebEye Viewer?

Thanks

Guest cag014

Posted

Sorry... somehow forgot to upload the file..

Will be added today.

 

Guest cag014

Posted

AOQ HC-WebEye Viewer? has been uploaded.

 

AR27690

Posted

Hi,

Thank you for your code. I migrating mine All-in-One from HC2 and have noticed that setArm and forceArm commands are not supported? 

Another question - I have few QA devices with sliders but I don't find any way to use their values in AOQ!? Can you please take a look on that?

Thanks for the scripts, made the migration to HC3 very smooth and 95% is working!!

Guest cag014

Posted

Thanks for input.

Regarding setArm and forceArm, these commands are not supported by HC3 because fibaro has decided not to control every sensor but to use alarm zones instead.

By the way today if sensor breached there is no indication on UI about that and you need to work hard to monitor which sensor breached. (same for arm/disarm states).

It has been quite a challenge to integrate new alarm concept into AOQ. Please take a look on how to use alarm.. https://forum.fibaro.com/topic/51320-hc3-all-in-one-qa-how-to-do-it-better/

Regarding slider value, I'll see what I can do...

Again, thanks for an input

Guest cag014

Posted

On 8/7/2020 at 9:17 AM, AR27690 said:

Hi,

Thank you for your code. I migrating mine All-in-One from HC2 and have noticed that setArm and forceArm commands are not supported? 

Another question - I have few QA devices with sliders but I don't find any way to use their values in AOQ!? Can you please take a look on that?

Thanks for the scripts, made the migration to HC3 very smooth and 95% is working!!

Regarding sliders - currently there is a bug and slider value doesn't updated properly. You can see when you open new tab the slider value is zero!

Let's hope next release Fibaro will fix the issue.

 

gabes

Posted

Hi @cag014,

Actually migrating my own HC2 scripts to my new HC3 box, i discovered your AOQ quickapp, and after reading your multiple docs, i'am very happy of your work, and first of all i want to thank you for your big work at this quickapp.

 

For the story and feedback to other users, at first i have tried to migrate my environnement with ZWave 3 engine, but i need to say that this was a nightmare because my modules, the majority of whom are now a few years old, are not correctly recognized (or in a too generic way to use your framework greatly) or simply not working correctly working in new engine (door sensor are the most problematic)

 

I restarted then my migration to use Engine 2, and now it's working a lot better.

However, I still have a problem now with the trigAct event on sceneActivation events... a this time i have this problem on 2 differents modules (fibaro flush dimmer with scenario enabled, and nodon  wallswitch in sceneactivation mode > for this on in centralscene event the module is working correctly with AOQ).

The problem is : sometimes (one to two times out of five) the action is triggering twice (so if the trigAct is toglle, the device turn on and turn off in one second).

 

I'am thinking you have a bug in watching this event triggering in you engine, because if i make a specific scene in HC3 without using your AOQ, i dont have this problem, the scene triggers only once.

 

So i'am asking you, if you have a little time to check this problem ?

As you can imagine, i dislike the idea for me to use your AOQ for only some devices, because i'am liking your centralization concept 

 

Keep me informed, and thanks in advance

cag014

Posted

Hi,

First of all, thank you for your compliments. 😀

 

Could you please post your lines and I'll test it, to make sure it works properly.

gabes

Posted (edited)

On 1/8/2023 at 10:08 AM, cag014 said:

Hi,

First of all, thank you for your compliments. 😀

 

Could you please post your lines and I'll test it, to make sure it works properly.

 

Yes, i share you my config and log lines with the simplest use case where the bug occurs, configuration is : 

 

{0,"`CuisineIpilPoutre`",{state="sceneActivation=26",trueAct={"`CuisineBar`","toggle",""}}},
 

in this test case i will press 1 time the device every 10 sec during 1 minute to illustrate

 

[12.01.2023] [22:37:23] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ➯ toggle{CuisineBar)
[12.01.2023] [22:37:23] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:37:32] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:37:33] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:37:43] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:37:43] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:37:52] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:37:53] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:38:03] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:38:03] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:38:13] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:38:13] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:38:22] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)
[12.01.2023] [22:38:23] [TRACE] [AOQ246]: jM{9}A   Cuisine:80:Cuisine Telco IPIL Poutre[26] ↪ toggle{CuisineBar)

 

as you can see, the event is triggered two times on every press. The consequence in real usage is that sometimes the toggle change the state to the opposite value, and sometimes not. I thing this is going so :

consider the device is off :

if the first and the second toggle instruction cames exactly at the same instant the result of the two toggle would be to turn the device on, to nothing is visible only the duplication in console log

- on some other press i thing that when the second toggle comes a little milliseconds later that the first the device status is already refreshed so the toggle take it to off state again and the light flashed briefly because first event has turn it on and second off.

 

anyway for me there should only be one trigger event in the log at every press and not two ...

 

Edited by gabes
cag014

Posted

You're absolutely correct...

The dimmer in HC3 has two children light and remote...

Please try attached version

AOQ-main-v15.4.txt

 

Is anyone having keyfob to see if sceneActiviation works fine for remotes also, then please download and test.. thanks

 

gabes

Posted

On 1/15/2023 at 1:48 AM, cag014 said:

You're absolutely correct...

The dimmer in HC3 has two children light and remote...

Please try attached version

AOQ-main-v15.4.txt 230.03 kB · 2 downloads

 

Is anyone having keyfob to see if sceneActiviation works fine for remotes also, then please download and test.. thanks

 

 

It's working ! Thanks a lot... I will now try to set-up more complex scenario with your framework ! 

 

Dann

Posted

Hi Cag014,

 

After installing the latest ( 20.7 ) version, I got the below error message :

[26.10.2025] [11:45:01] [DEBUG] [AOQ3988]: AOQ v20.7

[26.10.2025] [11:45:01] [DEBUG] [AOQ3988]: Gathering AOQ information...550

[26.10.2025] [11:45:01] [DEBUG] [AOQ3988]: local gateway: HC3-0xxxxxxxxx HC3-0xxxxxxxxv5.190.36... Zwave e2.0v4.33

[26.10.2025] [11:45:07] [ERROR] [QUICKAPP3988]: QuickApp crashed

[26.10.2025] [11:45:07] [ERROR] [QUICKAPP3988]: main.lua:297: attempt to index a nil value

As you can see I am on HC3 v 5.190.36.

 

I inserted in my user_data, beside ( not instead ) of your default variables, some of mine ( solely on jS2n and jM ).

With or without those additions, I got the same message.

Can you help me to identify were should I change or modify ?

 

Looking forward to hear you back,

 

With best regards,

Dan

 

 

cag014

Posted (edited)

Looks like you have a very strange QuickApp. 

Any idea what it can be? Did you add any QA lately?

Please try version below and let me know if it works.

AOQ-main-v20.71.txt

 

Edited by cag014
Dann

Posted

Thanks Cag014.

 

I get the same error message using 20.71 ver.

 

And yes, I am working and implementing a QA monitoring ( thru local LAN ) of IMEON 9.12 hybrid inverter ( for which verry little documentation is available ). Therefore I am on a back-engineering process and maybe this could interfere with AOQ.

Anyhow, I disabled my IMEON QA and got the same error message from AOQ. Same crash at 297 line for the same reason.

Maybe Ishould erase completelly IMEON QA ?

 

Looking forward to hear you back,

 

Kind regards,

Dan

 

 

Dann

Posted

I removed IMEON QA and got the same error message on AOQ.

I am running-out of ideas.

Dann

Posted

Thanks Cag014,

 

I see some progress here. See attached the response within console ( the screen-shot looks better instead of a copy/paste solution ).

 

On the other hand, I see nothing in the Device Preview ( regardless if " The new views in mobile application" is set On of Off ) . See attached as well.

 

Your help and effort is highelly appreciated and I continue to count on it ( as much as you can give me a hand ). Maybe it would be used by some other Fibaro users.

 

Looking forward to hear hyou back,

 

With best regards,

Dan

 

Screenshot 2025-10-29 at 14.15.41.png

Screenshot 2025-10-29 at 14.11.25.png

Dann

Posted

Maybe an interesting additional detail to underline : HC3 local IP address is not 127.0.0.1 ( as indicated by AOQ ) but 192.168.x.x

cag014

Posted

127.0.0.1 is the IP address for your own hub, commonly known as "localhost" or the "loopback address."

It’s used to refer to the device you're currently using, without accessing any external network.

 

The idea to use it, that if the user doesn't define local hub in user_data the AOQ still works.

Another point that if you change the IP and not change it in user_data it will continue to work.

 

Now I can see that AOQ works for you, correct?

 

Dann

Posted

OK clear.

 

Correct. It works and I can see the details in the Console.

I recall that in some old AOQ versions, all details were seen in the "Preview mode" as well. Is it still possible to have that possibility as well in 20.7x ?

 

cag014

Posted (edited)

Based on users experience it was a messy info.

Please download WebEye application to view all necessary data with popup and dropdown menus and other extra information

Please make to use NO CORS option on your browser. Read Disable CORS document

 

Edited by cag014
Dann

Posted

Thanks. 

Will do so once I will return back at home. Remotelly seems not to be possible to use HC-WebEye or do I miss something ?

 

cag014

Posted (edited)

You can do it, but you need to go to fibaro home page, remotely to connect to your hub and then to copy the http address in webEye (remote ip)

 label: "HC3",
    hubType: "HC3",
    local: "http://10.1.0.178",
    remote: "https://home.fibaro.com/newProxyLite?user=11793&temp=XXXX&req=" },
Edited by cag014
cag014

Posted (edited)

By the way you can port forward in your router to access HC3 from anywhere and no rely on Fibaro site remote access  

That's the way I am doing

Edited by cag014

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

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