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

[Rover 47]

Please login or register to see this spoiler.

AOS 3.1 reports 17 dead events.

BTW time is correct, but date is 15 Oct?

[cag014 731]

56 minutes ago, Rover said:

Please login or register to see this spoiler.

It might be the problem to delays... when HC2 shows this load it can take minutes till any action executed.

You need to clean up that...

[Rover 47]

1 hour ago, cag014 said:

The date is when the AOS has started....

It might be the problem to delays... when HC2 shows this load it can take minutes till any action executed.

You need to clean up that...

 

I cleaned up the HC2 by deleting some VD's. It is quiet now.

But the delay problem has not gone...

Again with a jM with one line toggling a HC3 wallplug, it takes 3-6 seconds to react.

 

Using a second line 

Please login or register to see this spoiler.

toggling the same wallplug, but now by a Scenemaster ('hc2) : 4-9 seconds to get a reaction on the HC3 wallplug.

Meanwhile the HC2 is quiet.

Something is fundamentally wrong!

Edited October 19, 2020 by Rover

[Rover 47]

New experiment: Toggling another wallplug now included in HC2, with scenemaster, but now fully by HC2 scene: the same delays of average 9 seconds! So HC2 has been disturbed and the delays are HC2 delays and no HC3 delays.

 

The delays arrived when I introduced the SlaveSensors in order to include HC2 devices in HC3 alarm zones. 

How can HC3 QA's influence the working of HC2?

BTW hc2Proxy is removed from HC3 as well as HC2.

Edited October 19, 2020 by Rover

[cag014 731]

I have redesigned the Slave devices and now you have a button to stop/start emulation (could help to check the load)

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

27 minutes ago, Rover said:

New experiment: Toggling another wallplug now included in HC2, with scenemaster, but now fully by HC2 scene: the same delays of average 9 seconds! So HC2 has been disturbed and the delays are HC2 delays and no HC3 delays.

 

The delays arrived when I introduced the SlaveSensors in order to include HC2 devices in HC3 alarm zones. 

How can HC3 QA's influence the working of HC2?

BTW hc2Proxy is removed from HC3 as well as HC2.

The Slave device scanning hc2 (api.get) according to sampleRate. It shouldn't have any impact on HC2 performance.

I think you have some issue that overloads HC2 CPU.

What about HC2 RAM?

Edited October 19, 2020 by cag014

[Rover 47]

1 hour ago, cag014 said:

I think you have some issue that overloads HC2 CPU.

What about HC2 RAM?

Please login or register to see this spoiler.

 

Edited October 19, 2020 by Rover

[Rover 47]

5 hours ago, cag014 said:

I have redesigned the Slave devices and now you have a button to stop/start emulation (could help to check the load)

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

The Slave device scanning hc2 (api.get) according to sampleRate. It shouldn't have any impact on HC2 performance.

I think you have some issue that overloads HC2 CPU.

What about HC2 RAM?

I have changed all slaves to the new ones: delays vanished!!! ?

 

 

On 10/18/2020 at 11:30 AM, Rover said:

Please login or register to see this spoiler.

cag?

Edited October 19, 2020 by Rover

[cag014 731]

32 minutes ago, Rover said:

have changed all slaves to the new ones: delays vanished!!! ?

Good news...

33 minutes ago, Rover said:

Zone $KamerGlo has 2 D/W sensors (SlaveSensor).

Is it normal that when one window is open the armAlarm results in okAct?

Yes, if the sensor is opened before arming, there is no indication in alarm zone and it's armed w/o any warnings?

So in general the alarm is armed and verification is OK and okAct executed.

 

[Rover 47]

4 minutes ago, cag014 said:

Yes, if the sensor is opened before arming, there is no indication in alarm zone and it's armed w/o any warnings?

So in general the alarm is armed and verification is OK and okAct executed.

 

Yes, if the sensor is opened before arming, there is no indication in alarm zone and it's armed w/o any warnings?

       I think the sensor is not armed when sensor was opened. It is sure that in HC2 no open windows could be armed and that is not unlogical, agree?

 

So in general the alarm is armed and verification is OK and okAct executed.

     Yes, that is the behavior.

 

Edited October 19, 2020 by Rover

[cag014 731]

12 minutes ago, Rover said:

 

Yes, if the sensor is opened before arming, there is no indication in alarm zone and it's armed w/o any warnings?

       I think the sensor is not armed when sensor was opened. It is sure that in HC2 no open windows could be armed and that is not unlogical, agree?

 

So in general the alarm is armed and verification is OK and okAct executed.

     Yes, that is the behavior.

 

You're right, in HC2 it's not armed if sensor is open.

In HC3 it does armed. You can arm the zone manually and see no warnings... and it's armed.

[Rover 47]

Just now, cag014 said:

You're right, in HC2 it's not armed if sensor is open.

In HC3 it does armed. You can arm the zone manually and see no warnings... and it's armed.

Does that mean that if a window is open and the alarm zone of the windows is getting armed, that after closing the window and then opening the window an alarm is breached?

[cag014 731]

Just now, Rover said:

Does that mean that if a window is open and the alarm zone of the windows is getting armed, that after closing the window and then opening the window an alarm is breached?

Yes, that's exactly what happens.

[Rover 47]

Old problem: Pushover QA is not triggered by AOQ line, but can be triggered by HC3 scene.

Please login or register to see this spoiler.

Nice!

Edited October 19, 2020 by Rover

[cag014 731]

17 minutes ago, Rover said:

Old problem: Pushover QA is not triggered by AOQ line, but can be triggered by HC3 scene.

Please login or register to see this spoiler.

What's the error? or no response at all

 

[Rover 47]

Just now, cag014 said:

What's the error? or no response at all

 

No response at all. Also in the debug page of the Pushover QA no triggering to be seen.

[cag014 731]

Works fine in my system...

By the way as far as I remember the name has been changed to Send_PushOver,

[Rover 47]

Just now, cag014 said:

Works fine in my system...

By the way as far as I remember the name has been changed to Send_PushOver,

It should be Send_Pushover and that is the case at any place now. There is no error of a not present QA function now. It has worked!

 

[SmartLifeSystems 20]

Hi cag!

 

I am wondering if you have been thinking about the google calendar solution? Do you think it can be created?

[cag014 731]

12 minutes ago, Rover said:

It should be Send_Pushover and that is the case at any place now. There is no error of a not present QA function now. It has worked!

 

Please check `Pushover` ID. It happens only if device ID is Zwave device and not QuickApp. (I mean executed w/o any response)

[Rover 47]

7 minutes ago, cag014 said:

Please check `Pushover` ID. It happens only if device ID is Zwave device and not QuickApp. (I mean executed w/o any response)

Please login or register to see this spoiler.

 

Edited October 19, 2020 by Rover