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

[cag014 731]

3 minutes ago, Rover said:

What could be the reason that at once there are delays between triggering of all sensors and remote controllers (I can see the flickering of a motion sensor) and a very long delay before the actuator has been acting?

 

How can I stop AOQ1 totally so that AOQ2 with one line can show the absolute minimum?

There is a button to stop AOQ

Please login or register to see this spoiler.

 

[Rover 47]

12 minutes ago, cag014 said:

There is a button to stop AOQ

Please login or register to see this spoiler.

Where is the button?

Edited October 28, 2020 by Rover

• Quote

[cag014 731]

7 minutes ago, Rover said:

Please login or register to see this spoiler.

I think the problems started when I've asked you to create user_data and main files. Could be that old  mainCode is still there?

Edited October 28, 2020 by cag014

• Quote

[Rover 47]

9 minutes ago, cag014 said:

What? Are you sure you have copied the version correctly?

Here how it looks on my system

Please login or register to see this spoiler.

 

Edited October 28, 2020 by Rover

• Quote

[cag014 731]

1 minute ago, Rover said:

How is that possible? When changing a version all main code has been replaced by new code. Main v6.2 has 1944 lines.

But you can have many files inside QA... if didn't removed the old it's executed as well.

Did you delete the old mainCode?

AOQ files MUST be like below

Please login or register to see this spoiler.

 

If you have a problem please upload entire QA from scratch. After that copy your user_data

 

Please login or register to see this attachment.

[Rover 47]

2 minutes ago, cag014 said:

But you can have many files inside QA... if didn't removed the old it's executed as well.

Did you delete the old mainCode?

AOQ files MUST be like below

Please login or register to see this spoiler.

 

• Quote

[cag014 731]

1 minute ago, Rover said:

Please login or register to see this spoiler.

 

• Quote

[Rover 47]

4 minutes ago, cag014 said:

I think I know why you don't have the button. When I added the button per @gggizmo request, I posted AOQ.fqa and text code. You probably have picked up the test file only.

Do you see the button like that

Please login or register to see this spoiler.

Yes, now the button is there ?

[cag014 731]

Just now, Rover said:

Yes, now the button is there ?

How come? Where it was it?

[Rover 47]

3 minutes ago, cag014 said:

How come? Where it was it?

How come???? Probably because I indeed only copied the text code, while you had changed the .fqa

 

OK, I see the misunderstanding: the button is there in the new AOQ.fqa

Edited October 28, 2020 by Rover

[Rover 47]

With AOQ1 off the response time of Scenemaster triggered HC3 wallswitch with AOQ2 is stable 11 seconds.

With AOQ1 on the response time of Scenemaster triggered HC3 wallswitch with AOQ2 is stable 2 minutes + 19-55 seconds.

So AOQ with 1 line can hardly run while the other AOQ is on.

Meanwhile looking at the CPU loads of HC2 as well as HC3 is very moderate.

 

[cag014 731]

1 hour ago, Rover said:

With AOQ1 off the response time of Scenemaster triggered HC3 wallswitch with AOQ2 is stable 11 seconds.

With AOQ1 on the response time of Scenemaster triggered HC3 wallswitch with AOQ2 is stable 2 minutes + 19-55 seconds.

So AOQ with 1 line can hardly run while the other AOQ is on.

Meanwhile looking at the CPU loads of HC2 as well as HC3 is very moderate.

 

It's still a mystery why it takes so long...

1 hour ago, Rover said:

With AOQ1 off the response time of Scenemaster triggered HC3 wallswitch with AOQ2 is stable 11 seconds.

With AOQ1 on the response time of Scenemaster triggered HC3 wallswitch with AOQ2 is stable 2 minutes + 19-55 seconds.

So AOQ with 1 line can hardly run while the other AOQ is on.

Meanwhile looking at the CPU loads of HC2 as well as HC3 is very moderate.

 

Have ran two AOQs with 170 line each. same performance.

Few days ago after replacing slave devices you said all delays gone... may be by mistake you use somewhere old slave devise...

It could be a good idea to delete all slave devices and test AOQ directly with HC2 devices.

Please download latest slave emulation QAs from forum download.

Edited October 28, 2020 by cag014

[Rover 47]

6 hours ago, cag014 said:

It's still a mystery why it takes so long...

Have ran two AOQs with 170 line each. same performance.

Few days ago after replacing slave devices you said all delays gone... may be by mistake you use somewhere old slave devise...

It could be a good idea to delete all slave devices and test AOQ directly with HC2 devices.

Please download latest slave emulation QAs from forum download.

I am busy now with replacing AOQ directly with HC2 devices, almost ready while all slaves are still there.

Meanwhile: 

Please login or register to see this spoiler.

One slave controller is going nuts, but I cannot see here which one...

[Rover 47]

13 hours ago, cag014 said:

It's still a mystery why it takes so long...

Have ran two AOQs with 170 line each. same performance.

Few days ago after replacing slave devices you said all delays gone... may be by mistake you use somewhere old slave devise...

It could be a good idea to delete all slave devices and test AOQ directly with HC2 devices.

Please download latest slave emulation QAs from forum download.

I have finished my delay research:

AOQ1 + AOQ2 active, all devices on direct HC2, a set of slave QA devices running but not coupled to AOQ1 or AOQ2 devices,

timing test button push on Scenemaster direct coupled to HC2 triggering HC3 wall plug switch, measured by stopwatch:

• response time: 1:14-2:44 minutes, response time motionsensor until light: 1-3 minutes.
• Stop all (4) motion sensor slaves: response time: 14-18 seconds.
• Stop also all (4) binary switch slaves: response time: 2-4 seconds.
• Run all (4) motion sensor slaves (without all (4) binary switch slaves) : response times: 7, 8, 2, 12, 8, 2, 14 seconds.
• Run all (4) motion sensor slaves (without all (4) binary switch slaves) + Scenemaster on SlaveRemote_centralScene-v2: response times: 2-4  seconds.
• 14 SlaveSensor QA's coupled to D/W sensors running all the time without delay issues.
• Now 14 SlaveSensor QA's coupled to D/W sensors coupled to AOQ devices again: response time: 2-4 seconds.

 

Edited October 28, 2020 by Rover

[cag014 731]

Looking on that it's seems that slave QA cause the issue, right?

 

Edited October 28, 2020 by cag014

[Rover 47]

2 minutes ago, cag014 said:

Looking on that it's seems that slave QA cause the issue, right?

 

Yes, I have also no other explanation.

[cag014 731]

Let's what will happen if you'll delete all of them...

[Rover 47]

7 minutes ago, cag014 said:

Let's what will happen if you'll delete all of them...

All of them?? What is all?

I already have deleted and installed again the 4 motion sensor slaves and also the 4 binary switch slaves. Stopping a slave QA has the same effect as deleting.

I think we have to concentrate on the binary switch slave issues.

 

BTW: What is the meaning of the green V sign on a slave icon? Even if the slave is not connected to a device it stays green ??

Edited October 28, 2020 by Rover

[cag014 731]

27 minutes ago, Rover said:

All of them?? What is all?

I already have deleted and installed again the 4 motion sensor slaves and also the 4 binary switch slaves. Stopping a slave QA has the same effect as deleting.

I think we have to concentrate on the binary switch slave issues.

 

BTW: What is the meaning of the green V sign on a slave icon? Even if the slave is not connected to a device it stays green ??

 

If you have installed all new slaves, then that's OK

As far as I know the V sign means no communication problems with the device (in case of QA it's always green) in addition by pressing on V, device properties opened.

Edited October 28, 2020 by cag014

[cag014 731]

Have tried again to run two AOQs... 50 lines each.

No issues, both run as expected. (Including delayed commands)

Please login or register to see this spoiler.