All-in-One Scene: How to do it Better

[cag014 731]

Strange works fine for me.

Regarding the Edge, did you use the command line as described in DISABLE CORS doc? I mean running Edge with disable security option?

[Rover 47]

16 minutes ago, cag014 said:

Strange works fine for me.

Regarding the Edge, did you use the command line as described in DISABLE CORS doc? I mean running Edge with disable security option?

No, I did not, but the Allow CORS extension in Edge shows that CORS has been disabled.

[Rover 47]

1 hour ago, Rover said:

Above you can see that I had already added a port number, what is working in Firefix with webeye 3.0, but not with webeye 4.0 (not implemented 501).

No, I did not mean this debug information, but all the reporting lines of a working webeye.

And the centered layout of the reporting lines is not very conveniant (was also in webEye 3.0), please put the reporting lines to the left.

Edited October 13, 2025 by Rover

[cag014 731]

1 hour ago, Rover said:

No, I did not, but the Allow CORS extension in Edge shows that CORS has been disabled.

in Edge CORS extension doesn't work

Run Edge according to the doc 

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --user-data-dir="C:\EdgeDevProfile" –disable-web-security

1 hour ago, Rover said:

And the centered layout of the reporting lines is not very conveniant (was also in webEye 3.0), please put the reporting lines to the left.

Could you please post what lines we're talking about?

[Rover 47]

32 minutes ago, cag014 said:

in Edge CORS extension doesn't work

Run Edge according to the doc 

"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --user-data-dir="C:\EdgeDevProfile" –disable-web-security

Could you please post what lines we're talking about?

I mean this kind of lines:

Please login or register to see this spoiler.

but as you can see, this time the lines have been lined out to the left :-), but mostly they are centered :-(.

[cag014 731]

Now I confused, these lines displayed in HC2 debug console, why you need them in webEye?

[Rover 47]

29 minutes ago, cag014 said:

Now I confused, these lines displayed in HC2 debug console, why you need them in webEye?

 

31 minutes ago, cag014 said:

Now I confused, these lines displayed in HC2 debug console, why you need them in webEye?

The advantage of webEye is a full screen of the debugging lines, while the HC2 debug console shows a very small part of each line and the display time of the lines is very short.

The webEye lines are visible as long as I do not Reload. But I want to have these lines visible over a longer time at all, also after Reload in webEye.

[cag014 731]

Ok, now I see what do you mean.

 

Please update your AOS with attached file

Please login or register to see this attachment.

 

This version includes many features as AOQ.  

Change-log:

devPrt

$stateTime

timer

$onTimer

else

operator

setTimer

setCondition

 

Currently I'm working on documentation for that, but all above features could be reviewed in AOQ user guide (they are 99% percent the same)

 

Regarding to keep debug lines for a long time, you need to change global 

tblRefresh  = 300 -- (seconds) table view refresh rate. 0-disable

 

By setting to 0 (disable auto refresh) you can keep debug lines forever !!!  But no updates for the data table.

Another option is to set for a few days 

tblRefresh  = 172800 (two days)

 

At any point you can refresh the data table at scene, but the debug lines will be cleared.

Edited October 13, 2025 by cag014

[Rover 47]

1 hour ago, cag014 said:

Ok, now I see what do you mean.

 

Please update your AOS with attached file

Please login or register to see this attachment.

 

This version includes many features as AOQ.  

Change-log:

devPrt

$stateTime

timer

$onTimer

else

operator

setTimer

setCondition

 

Currently I'm working on documentation for that, but all above features could be reviewed in AOQ user guide (they are 99% percent the same)

 

Regarding to keep debug lines for a long time, you need to change global 

tblRefresh  = 300 -- (seconds) table view refresh rate. 0-disable

 

By setting to 0 (disable auto refresh) you can keep debug lines forever !!!  But no updates for the data table.

Another option is to set for a few days 

tblRefresh  = 172800 (two days)

 

At any point you can refresh the data table at scene, but the debug lines will be cleared.

Installed

[Rover 47]

On 9/26/2025 at 5:51 PM, cag014 said:

Sorry, version in progress... thanks for pointing out on that.

AOS does not support number of global variables in one line for setGlobal

You need to update them one by one.

 

Does version 11.0 support it?

[cag014 731]

5 hours ago, Rover said:

Does version 11.0 support it?

Not yet

[Rover 47]

Is HC3 version 5.190.38 without problems with AOQ v20.8?

[cag014 731]

47 minutes ago, Rover said:

Is HC3 version 5.190.38 without problems with AOQ v20.8?

Yes, works fine

By the way regarding your question to update several global variables in HC2, you can do it using HC3 where HC2 defined as a slave hub 

Edited October 31, 2025 by cag014

[Rover 47]

On 10/31/2025 at 9:09 PM, cag014 said:

Yes, works fine

By the way regarding your question to update several global variables in HC2, you can do it using HC3 where HC2 defined as a slave hub 

Did not you make a comment in the HC3 forum that Geofencing does not work in 5.190?

And the periodic restarts?

Edited November 8, 2025 by Rover

[cag014 731]

6 hours ago, Rover said:

Did not you make a comment in the HC3 forum that Geofencing does not work in 5.190?

And the periodic restarts?

Yes, I did

Why?

[Rover 47]

On 11/8/2025 at 11:20 PM, cag014 said:

Yes, I did

Why?

That means that the Geofencing with AOQ in 5.190 does not work and that AOQ restarts periodically also. That is not what I want.

Edited November 10, 2025 by Rover

[cag014 731]

The geofencing malfunction and periodically restarts reported by many users - regardless of AOQ 

This is not an AOQ problem, but looks like the new version issues

Edited November 11, 2025 by cag014

[Rover 47]

On 11/11/2025 at 5:50 AM, cag014 said:

The geofencing malfunction and periodically restarts reported by many users - regardless of AOQ 

This is not an AOQ problem, but looks like the new version issues

So better not updating HC3 to 5.190.38 if you want to use geofencing?

[cag014 731]

15 hours ago, Rover said:

So better not updating HC3 to 5.190.38 if you want to use geofencing?

There are some users reporting that Geofence is working...

Up to you

[Rover 47]

Hi @cag014,

I had a shocking experience:

The house of my son and has family is fully automated for lights and security by means of a HC2 driven by an AOS scene (written and managed by me). Of course a make mistakes in writing AOS lines and then a debugging  error has been shown, but the operational scene is running for years when it is without errors from my side.

At the moment we are visiting my sons family and they wanted to turn on the lights of the room by means of a wall switch coupled with AOS. But it stayed dark...

I had a look in the debugging lines of AOS and I saw that the system was blocked (not crashed and rebooting) showing the next error line:

(empty spoiler}

Please login or register to see this spoiler.

[DEBUG] 15:05:46 2025-12-11 15:05:46.519409[ fatal] LUA error:/opt/fibaro/scenes/451.lua:1807 attempt to perform arithmetic on a nil value

After this line blocked and empty.

Please repair this severe security problem.