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

[cag014 731]

 

3 hours ago, Rover said:

Please login or register to see this spoiler.

That's my biggest dilemma, since this field could include string it should include spaces as well... 

I believe you did something like that

{227'hc2:value=true |227'hc2.....} instead {227'hc2:value=true|227'hc2.....}

In this case the code checks for "true " and not "true" .... (as you can see yo have extra space before the bracket)

This is the option to use spaces at the end, while using "and"  will ignore them, but

since you have the most complicated configuration and never have used space at the end, I think it might be the correct approach to trim the string.

Meanwhile here is an update for you...

I still don't know if it's worth to keep this option for the future... any suggestions from users?

 

 

Please login or register to see this attachment.

Edited November 3, 2020 by cag014

[cag014 731]

10 hours ago, SmartLifeSystems said:

 

Something wrong. Restarted again. I don't understand.

Could you post the part of the debug window when it restarts?

[cag014 731]

@Rover

Question

When you use 32 slave devices do you you use them in AOQ and remove direct access to these devices or you use that in parallel?

I mean fro example when you emulate HC2 switch, you're using that in AOQ and not continue to use in AOQ devID'hc2  for this switch?

 

I think I know why you have delays... you have an issue with network, is a little bit slow to deal with such amount of fast transactions between controllers. I remember you have complained about networks warnings...

I have set HC2 to external IP (takes a little bit longer) and I see same impact, delays over 30-120 seconds... the problem that at some point the command is stuck in the buffer till HC2 responds.

or one of the controller (hc2/hc3) is extremely overloaded..

Edited November 3, 2020 by cag014

[SmartLifeSystems 20]

4 hours ago, cag014 said:

Could you post the part of the debug window when it restarts?

 

OK, I will send you afternoon, or tomorrow.

But I have a question for you. How can I us the if and when conditions together?

 

For example: If the D/S sensor is true and some global variables is true, close the gate, when the MS is breached.

Edited November 3, 2020 by SmartLifeSystems

[cag014 731]

16 minutes ago, SmartLifeSystems said:

 

OK, I will send you afternoon, or tomorrow.

But I have a question for you. How can I us the if and when conditions together?

 

For example: If the D/S sensor is true and some global variables is true, close the gate, when the MS is breached.

{0,"MS",{state="value=true",trueAct={"`gate`","close"," if {DS:value=ture and Global:value=xxx and ......}"}

[Rover 47]

7 hours ago, cag014 said:

 

That's my biggest dilemma, since this field could include string it should include spaces as well... 

I believe you did something like that

{227'hc2:value=true |227'hc2.....} instead {227'hc2:value=true|227'hc2.....}

In this case the code checks for "true " and not "true" .... (as you can see yo have extra space before the bracket)

This is the option to use spaces at the end, while using "and"  will ignore them, but

since you have the most complicated configuration and never have used space at the end, I think it might be the correct approach to trim the string.

Meanwhile here is an update for you...

I still don't know if it's worth to keep this option for the future... any suggestions from users?

 

 

Please login or register to see this attachment.

Indeed I have used {"&DimlevelAvond","setGlobal","@`DimmerHal`>value","if {`LampHal`:value=true | `LampHal`:powerModified>?15*60?} OR {&Huisstatus:value=Slapen | `LampHal`:powerModified>?15*60?}. But it is obvious that nobody has the intention of using "true ", so trim always all words from spaces before and after. It only introduces errors, which only can be detected by @cag014.

This is an extra reason to replace all | by AND.

[Rover 47]

5 hours ago, cag014 said:

Question

When you use 32 slave devices do you you use them in AOQ and remove direct access to these devices or you use that in parallel?

I mean fro example when you emulate HC2 switch, you're using that in AOQ and not continue to use in AOQ devID'hc2  for this switch?

By using one jS2n definition there is always only interpretation of `<devID>`, either device=12 or device=20'hc2.

[cag014 731]

1 minute ago, Rover said:

By using one jS2n definition there is always only interpretation of `<devID>`, either device=12 or device=20'hc2.

That's what I'm asking, when you run slave device you do use it in AOQ?

[Rover 47]

6 hours ago, cag014 said:

I think I know why you have delays... you have an issue with network, is a little bit slow to deal with such amount of fast transactions between controllers. I remember you have complained about networks warnings...

I have set HC2 to external IP (takes a little bit longer) and I see same impact, delays over 30-120 seconds... the problem that at some point the command is stuck in the buffer till HC2 responds.

or one of the controller (hc2/hc3) is extremely overloaded..

I do not think that I have an issue with my 1Gbps network. The problem is that not by AOQ used slaves are able to compromise the working of AOQ!

That a command is stuck in the buffer till HC2 responds sounds reasonable, but because AOQ do not send commands via this slaves, which commands could it be?

For these HC2 devices I use <deviceID>'hc2 while also a slave (SlaveSwitch) is active coupled to the same HC2 device.

 

 

11 minutes ago, cag014 said:

That's what I'm asking, when you run slave device you do use it in AOQ?

The 4 troublesome SlaveSwitches are not used (anymore) in AOQ.

Edited November 3, 2020 by Rover

[cag014 731]

8 minutes ago, Rover said:

I do not think that I have an issue with my 1Gbps network. The problem is that not by AOQ used slaves are able to compromise the working of AOQ!

That a command is stuck in the buffer till HC2 responds sounds reasonable, but because AOQ do not send commands via this slaves, which commands could it be?

For these HC2 devices I use <deviceID>'hc2 while also a slave (SlaveSwitch) is active coupled to the same HC2 device.

May be I need to rephrase it.  It's not actual commands sent to devices, but the getting value of the devices from HC2 (api.get) mostly to get current value and conditions. That's what stuck in the buffer.

The purpose of slaves usage is to reduce that traffic. When you use slaves , AOQ doesn't run api.get in the loop, but waits for HC3 trigger.

When you use <deviceID>'hc2  while also have a slave coupled to the same device it's doubles the traffic.

Please try to use slaves only in AOQ.

Edited November 3, 2020 by cag014

[Rover 47]

42 minutes ago, Rover said:

Indeed I have used {"&DimlevelAvond","setGlobal","@`DimmerHal`>value","if {`LampHal`:value=true | `LampHal`:powerModified>?15*60?} OR {&Huisstatus:value=Slapen | `LampHal`:powerModified>?15*60?}. But it is obvious that nobody has the intention of using "true ", so trim always all words from spaces before and after. It only introduces errors, which only can be detected by @cag014.

This is an extra reason to replace all | by AND.

Please login or register to see this spoiler.

OK, I will use the 4 SlaveSwitches in AOQ and do the measurements again.

Edited November 3, 2020 by Rover

[cag014 731]

12 minutes ago, Rover said:

Please login or register to see this spoiler.

It should be much better, as I said I did the simulation with external IP (to slowdown the communication) and have received delays over 2 minutes. By using just one slave, all delays are gone!!!

[Rover 47]

38 minutes ago, cag014 said:

It should be much better, as I said I did the simulation with external IP (to slowdown the communication) and have received delays over 2 minutes. By using just one slave, all delays are gone!!!

New measurements with Scenemaster as HC2 Slave and Wallplug switch direct on HC3, AOQ1 and AOQ2 with all lines active and also 4 slave switches active:

• response time 42 seconds.

Delay between motion before motion sensor and lights on:  

• after 128 seconds notification on screen
• after 165 seconds lights on

Delay between notification motion sensor off and lights off:  

• 64 seconds

[cag014 731]

2 hours ago, Rover said:

New measurements with Scenemaster as HC2 Slave and Wallplug switch direct on HC3, AOQ1 and AOQ2 with all lines active and also 4 slave switches active:

• response time 42 seconds.

Delay between motion before motion sensor and lights on:  

• after 128 seconds notification on screen
• after 165 seconds lights on

Delay between notification motion sensor off and lights off:  

• 64 seconds

You need to use more slaves

[Rover 47]

47 minutes ago, cag014 said:

You need to use more slaves

With also 4 slave switches I ment also the other slaves (except for the 6 smoke sensor slaves (off)).

New measurements with Scenemaster as HC2 Slave and Wallplug switch direct on HC3, AOQ1 and AOQ2 with all lines active and 27 slaves, inclusively 4 slave switches active:

• inclusively 4 slave switches active: response time 44 seconds.
• inclusively 2 slave switches active: response time 45 seconds.
• inclusively 1 slave switch active: response time 13,3,8,25,32 seconds.
• inclusively 0 slave switches active: response time 1,1,1,1 second.

With all measurements all devices were either <deviceID>'hc2 or slave.

 

Conclusion stays: SlaveSwitches and SlaveSensors with smokesensor is a nogo!

Edited November 3, 2020 by Rover

[SmartLifeSystems 20]

14 hours ago, cag014 said:

Could you post the part of the debug window when it restarts?

 

I tried with the 6.6. After some minutes the update, the AOQ restarted.

Here is the debug window. Can you see something?

 

With the 6.3 working normaly.

 

Please login or register to see this attachment.

[Rover 47]

Today I have reached a new milestone in the development of my AOQ system. After lightning, arming and disarming features now the testing of the active alarm features, so how AOQ lines are working  when an alarm zone has been breached. And, very important, how to end an alarm procedure when the alarm by breaching has begun?

The answer is NOT. The system was paralyzed, no wall switch controller or motion sensor was working. So the disarming procedure could not be started! Even after stopping the alarm zones by a pin code the system stay paralyzed. Only by booting AOQ1 and AOQ2 the system came back responsive.

It made me think of the pecularities of the HC2 alarm system: in each scene you have to check whether the scene could be stopped by an alarm, also a HC2 scene cannot be called in an active alarm status, only by toggling a GV a scene can be started in an active alarm status.

Could it be that also the HC3 has its special treatment in an active alarm status? Is AOQ alarm resistant?

[cag014 731]

50 minutes ago, Rover said:

Today I have reached a new milestone in the development of my AOQ system. After lightning, arming and disarming features now the testing of the active alarm features, so how AOQ lines are working  when an alarm zone has been breached. And, very important, how to end an alarm procedure when the alarm by breaching has begun?

The answer is NOT. The system was paralyzed, no wall switch controller or motion sensor was working. So the disarming procedure could not be started! Even after stopping the alarm zones by a pin code the system stay paralyzed. Only by booting AOQ1 and AOQ2 the system came back responsive.

It made me think of the pecularities of the HC2 alarm system: in each scene you have to check whether the scene could be stopped by an alarm, also a HC2 scene cannot be called in an active alarm status, only by toggling a GV a scene can be started in an active alarm status.

Could it be that also the HC3 has its special treatment in an active alarm status? Is AOQ alarm resistant?

What do you mean by "system was paralyzed"? 

Have checked that and every thing works as expected...

 

[Rover 47]

13 hours ago, cag014 said:

What do you mean by "system was paralyzed"? 

Have checked that and every thing works as expected...

 

With paralyzed I mean that motion sensors and controller switches did not react anymore.

After rebooting AOQ apparently the action queue came to life: 

Please login or register to see this spoiler.

It may be of importance to know that the Alarm actions run from AOQ2 while the ("paralyzed") controllers run from AOQ1 (=AOQ204).

As you can see in the trace recording above, not the controllers were paralyzed but the action queue of AOQ1 was blocked, while new button presses were added to the action queue...

Edited November 4, 2020 by Rover

[cag014 731]

On 11/3/2020 at 7:12 PM, SmartLifeSystems said:

 

I tried with the 6.6. After some minutes the update, the AOQ restarted.

Here is the debug window. Can you see something?

 

With the 6.3 working normaly.

 

Please login or register to see this attachment.

Could you please post your jM table?

 

Edited November 5, 2020 by cag014