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

[Rover 47]

32 minutes ago, cag014 said:

Yeap, as I though it's now Send_pushOver

cag has the eyes of an owl ?

[cag014 731]

23 minutes ago, Rover said:

cag has the eyes of an owl ?

Almost, typo error Send_PushOver

[Sjakie 156]

59 minutes ago, cag014 said:

It's very confused, from one hand @Sjakie reports fast response with 20-25 slaves and in your case it takes 5 seconds just to identify state change...

Yes but I am talking only HC3 I didt check what happend on HC2.

I was focussed on HC3 to get the job done there.

Goal is to replace HC2 with HC3 or shall I say a dream?

Sorry I cant go back I did a factory restore.

//Sjakie

 

[cag014 731]

6 minutes ago, Sjakie said:

Yes but I am talking only HC3 I didt check what happend on HC2.

I was focussed on HC3 to get the job done there.

Goal is to replace HC2 with HC3 or shall I say a dream?

Sorry I cant go back I did a factory restore.

//Sjakie

 

Exactly, slavesensors on your HC3 react fast, while on @Rover HC3 it takes 5 seconds!

[Sjakie 156]

Guys, with the new slavesensor.LUA

I imported one door sensor aswell in HC2 and HC3 1 sec (manual counting).

Let me import also a motion sensor to compare.

//Sjakie

 

[Rover 47]

16 minutes ago, cag014 said:

Exactly, slavesensors on your HC3 react fast, while on @Rover HC3 it takes 5 seconds!

Could it be useful to reboot HC2 and/or HC3?

[Sjakie 156]

If you ask me Yes!

I do it often if I otice they become slower whats the uptime?

//Sjakie

 

motion sensor instant reaction

wall plug on icon change on HC2

//Sjakie

[Rover 47]

21 minutes ago, Sjakie said:

If you ask me Yes!

I do it often if I otice they become slower whats the uptime?

//Sjakie

 

motion sensor instant reaction

wall plug on icon change on HC2

//Sjakie

HC3 uptime: 6 days

Where can I find the uptime of HC2?

[Sjakie 156]

general information

Its not so long.

I check before changing something what the CPU usage and Mem is

In my case 20% basic with as general piek 40% if HC2 is working very hard I see 60/70 %  Memory 14%

If thats okay I make a new backup afterchanging if not I restore or restart HC

make changes and backup again.

//Sjakie

[Rover 47]

1 minute ago, Sjakie said:

general information

I only see the server status of 12d, 22h, but I think it must be since the last backup to version 4.560 at 2019-11-16.

[Sjakie 156]

Server status is uptime

Reboot will make HC2 faster I think

//Sjakie

[Rover 47]

44 minutes ago, Sjakie said:

Server status is uptime

Reboot will make HC2 faster I think

//Sjakie

Will update of HC2 to 4.600 have a risk of problems?

[Sjakie 156]

I should do one thing at a time.

Reboot see if that sloves

//Sjakie

[cag014 731]

2 hours ago, Rover said:

I only see the server status of 12d, 22h, but I think it must be since the last backup to version 4.560 at 2019-11-16.

May I ask what your table refresh time, did you change it?

Defined in AOQ parameters table

tblRefresh  = 180 --(seconds) table view refresh rate min 120 seconds. 

 

[Rover 47]

18 minutes ago, cag014 said:

May I ask what your table refresh time, did you change it?

Defined in AOQ parameters table

tblRefresh  = 180 --(seconds) table view refresh rate min 120 seconds. 

 

This is the refresh time as specified in one of the early versions of AOQ. I never have changed it.

Please login or register to see this spoiler.

 

[Rover 47]

1 hour ago, Sjakie said:

I should do one thing at a time.

Reboot see if that sloves

//Sjakie

I made the mistake of rebooting HC2 tonight. The alarm was initiated and the siren could not be stopped ?. The WAF is below sea level (not only because we are living below sea level) ?

But the HC2 is somewhat more relaxed, but still with periods of 100% CPU load, because of what??? Besides of being slave of HC3 the HC2 has nothing to do...

 

The response times of HC2 motionsensor into light did not improve.

Edited October 15, 2020 by Rover

[Rover 47]

35 minutes ago, Rover said:

This is the refresh time as specified in one of the early versions of AOQ. I never have changed it.

Please login or register to see this spoiler.

Changing refresh time of 60 to 180 seconds enlarged the response time of motionsensor to lights: HC3 device 5 sec. --> 8 sec. and HC2 devices 10 --> 16 sec.

[cag014 731]

1 minute ago, Rover said:

Changing refresh time of 60 to 180 seconds enlarged the response time of motionsensor to lights: HC3 device 5 sec. --> 8 sec. and HC2 devices 10 --> 16 sec.

No way... it's just table printout... every 180 seconds!

[Rover 47]

2 minutes ago, cag014 said:

No way... it's just table printout... every 180 seconds!

New measurement: response times had not changed, resp. 5 and 10 seconds.

[cag014 731]

3 hours ago, Rover said:

New measurement: response times had not changed, resp. 5 and 10 seconds.

Let's try to measure the response time for API GET, PUT and POST

Attached version has these results... at the end of the table.

@AR27690

Please use this version also. Stable while slave controller has network problems, but notice if you have connection problem do not restart AOQ till problem solved. AOQ will continue to perform all actions (except where no connection), but if you will restarted, AOQ unable to load device data and will stop.

 

 

Please login or register to see this attachment.

Edited October 16, 2020 by cag014