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

[Rover 47]

47 minutes ago, cag014 said:

As I understand you're sending a push note in case the door is open over 3 minutes. Using timeoutAct={} AOQ will send push note one time and will wait for door to be closed.

I recommend in this case to use timeLoopAct={}, the AOQ will send push note every 3 minutes till the door will be closed. Some kind loop of reminding to close the door.

This is the main deference between timeoutAct to timeLoopAct.

timeOutAct executed one time and waits for status to be changed.

timeLoopAct continues in a loop (in your case 3 min) to be executed until the status changes.

 

 

Thank you cag014 for thinking about the things I am doing ?

Step by step I learn to build nice automation with AOQ guided by you.

In this case the intention is to start arming the house by pushing a button on the wall and leave the house within 3 minutes. If I have pushed the button and waiting too long, then the arming procedure is getting killed.

The idea is to set a global value if door is open more then 3 minutes. This global can be tested in the arming line.

In HC2 scene now this is LUA with counter; in AOQ the solution is very elegant.

I think for this purpose timeoutAct is most suitable, or not?

[cag014 731]

27 minutes ago, Rover said:

Thank you cag014 for thinking about the things I am doing ?

Step by step I learn to build nice automation with AOQ guided by you.

In this case the intention is to start arming the house by pushing a button on the wall and leave the house within 3 minutes. If I have pushed the button and waiting too long, then the arming procedure is getting killed.

The idea is to set a global value if door is open more then 3 minutes. This global can be tested in the arming line.

In HC2 scene now this is LUA with counter; in AOQ the solution is very elegant.

I think for this purpose timeoutAct is most suitable, or not?

The arming line can be delayed for 3 minutes with condition to check the door status, instead of creating variables.

something like that

{0,"`wallButton`", (state="value=true", trueAct={"alarmZone","armAlarm;else;disarmAlarm","180","{`Voordeur`:value=false}"}}},

Means when push button pressed wait 3 minutes check door state and if closed arm Alarm else disarm.

By the way if you leave home few seconds after 3 minutes how you know that the alarm disarmed?

You can use another condition to armAlarm when the door is closed.

{0,"`wallButton`", (state="value=true", trueAct={"alarmZone","armAlarm","180","={`Voordeur`:value=false}"}}},

Means when push button pressed, wait 3 minutes and arm alarm when door will closed.

But use whatever fits your needs.... I just point on AOQ available options.

 

Edited September 7, 2020 by cag014

[Rover 47]

1 hour ago, cag014 said:

The arming line can be delayed for 3 minutes with condition to check the door status, instead of creating variables.

something like that

{0,"`wallButton`", (state="value=true", trueAct={"alarmZone","armAlarm;else;disarmAlarm","180","{`Voordeur`:value=false}"}}},

Means when push button pressed wait 3 minutes check door state and if closed arm Alarm else disarm.

By the way if you leave home few seconds after 3 minutes how you know that the alarm disarmed?

You can use another condition to armAlarm when the door is closed.

{0,"`wallButton`", (state="value=true", trueAct={"alarmZone","armAlarm","180","={`Voordeur`:value=false}"}}},

Means when push button pressed, wait 3 minutes and arm alarm when door will closed.

The HC2 procedure is now that the counter stops when the door is closed and the arming begin. So the arming does not wait for 3 minutes. After arming a Pushover with sound (including text which windows are open) is generated and a buzzer in the hall, so I know that the arming is successful.

A conditional wait for closing the door seems unavoidable, only doing by a loop?

Another issue is, that after testing that all doors and windows being closed, I want a Pushover messages for all open windows (1 message per window). How to implement this intelligently in AOQ?

[cag014 731]

8 minutes ago, Rover said:

The HC2 procedure is now that the counter stops when the door is closed and the arming begin. So the arming does not wait for 3 minutes.

That almost the same like

{0,"`wallButton`", (state="value=true", trueAct={"alarmZone","armAlarm","180","={`Voordeur`:value=false}"}}},

 

15 minutes ago, Rover said:

Another issue is, that after testing that all doors and windows being closed, I want a Pushover messages for all open windows (1 message per window). How to implement this intelligently in AOQ?

For one message per window you'll need action for every window in same line  (assuming you have 3 windows)

Please login or register to see this code.

 

or you can send one pushover message if one of the window is open with all windows states and to see what is open

Please login or register to see this code.

[Rover 47]

23 hours ago, cag014 said:

Now you can use HC2 devices. The format is <devID>'<slaveId>. for example device 400 in hc2 should be 400'hc2.

You can use device as standard device in calculations, actions, line device and etc.

You can monitor HC2 sensors as well

(0,"500'hc2",{state="value=true",trueAct={"900'hc2","turnOn",""}..................

Devices could be defined in jS2n={sensor="500'hc2",.....}

It works perfect with controlling HC2-devices. ?

But the proof of the pudding does not succeed: How to add HC2-devices to Alarm zones? Result is: no devices of this type...

[cag014 731]

27 minutes ago, Rover said:

It works perfect with controlling HC2-devices. ?

But the proof of the pudding does not succeed: How to add HC2-devices to Alarm zones? Result is: no devices of this type...

Thanks for finding the bug... fixed.

[gggizmo 6]

hi cag, maybe i found another bug

 

lines like these don't work anymore

{0,"`isoggiorno`",{state="centralSceneSupport=2.Pressed",trueAct={{"`piantanaalta`","+changeBrightness,255",""},{"`piantanaalta`","turnOff;else;turnOn","","{`piantanaalta`:on=true}"}}}},

{0,"`rcamera`",{state="centralSceneSupport=dummy",trigAct={"`lcamera`","turnOff;else;setValue,100","","{`lcamera`:value>0}"}}},

 

every button press act like this. if light is on it switch off and then switch on again. If it's off it switch off and on again.

No issue in previous version of aoq

[gggizmo 6]

12 hours ago, cag014 said:

I  have just two Z-wave devices connected to HC3, so cannot say much about HC3 CPU load.

But I'm running two AOQ on HC3 (one testing and other developing) and CPU load looks not so bad ~45% average

 

45% with just two devices? 

[minsad79 19]

18 hours ago, cag014 said:

Don't see any reason why not.

Just add the second HC3 to the list of slaves

jSlave={

hc3={user="<username>",passwd="<password>",ip="xx.xx.xx.xx"},

}

The second HC3 devices must be listed as <devId>'hc3.

By the way you can use any name that fits you, just use same name as device suffix. (  '<name>  )

Let me know if it works... interesting.

I'll try to do the same on same HC3.

 

Unknown error 

 

 

[08.09.2020] [13:43:02] [ERROR] [QUICKAPP103]: QuickApp crashed[08.09.2020] [13:43:02] [ERROR] [QUICKAPP103]: Unknown error occurred: attempt to index a nil value[08.09.2020] [13:44:03] [ERROR] [QUICKAPP103]: QuickApp crashed[08.09.2020] [13:44:03] [ERROR] [QUICKAPP103]: Unknown error occurred: attempt to index a nil value[08.09.2020] [13:45:03] [ERROR] [QUICKAPP103]: QuickApp crashed[08.09.2020] [13:45:03] [ERROR] [QUICKAPP103]: Unknown error occurred: attempt to index a nil value

 

 

[Rover 47]

On 9/6/2020 at 10:50 PM, cag014 said:

This version could set parameters as json table.

so to use pushover QA please use action

trueAct={"<QA-ID>", '+Send_Pushover,json[["title","priority","sound","message"]]' ,""}...

How to use

--[[

trueAct={"<QA-ID>", '+Send_Pushover,json[["title","priority","sound","message"]]' ,""}...

--]]

[Rover 47]

How to print a value for debugging?

[gggizmo 6]

19 hours ago, cag014 said:

I  have just two Z-wave devices connected to HC3, so cannot say much about HC3 CPU load.

But I'm running two AOQ on HC3 (one testing and other developing) and CPU load looks not so bad ~45% average

After a lot of test i can say the high cpu load is related with aoq e hue light plugin. Aoq push on my system an average cpu load of 30-35%, and hue lights plugin is a real cpu eater.

I tried to delete aoq and mantain hue, cpu load go down to average 50-55%. I tried to delete hue plugin and uase aoq, with average cpu load 45-50%. Without aoq and hue lights i have an average cpu load of 15-20% with some spikes over 60%.

I tried to reduce hue poll timeout to 2 seconds, no change.

 

I tried to soft reconfigure every battery device, again....and now cpu load is always above 80%...

[cag014 731]

7 hours ago, gggizmo said:

 

45% with just two devices? 

Yes... two Zwave devices and few QA.

But two instances of AOQ. By stopping one of them the LOAD drops to ~35%

[cag014 731]

3 hours ago, Rover said:

How to use

--[[

trueAct={"<QA-ID>", '+Send_Pushover,json[["title","priority","sound","message"]]' ,""}...

--]]

What do you mean how to use it?

I thought it works

On 9/7/2020 at 1:57 PM, Rover said:

Hi @cag014,

You are a real champion ?

Pushover works in AOQ 2.0 ?

Is math.lib usable in this version?

The QA-ID is the ID number of your pushover QuickApp.

 

 

 

 

2 hours ago, Rover said:

How to print a value for debugging?

Post an example of what you need to print, but all values of all items  are displayed in HCwebEye...

[cag014 731]

 

1 hour ago, gggizmo said:

After a lot of test i can say the high cpu load is related with aoq e hue light plugin. Aoq push on my system an average cpu load of 30-35%, and hue lights plugin is a real cpu eater.

I tried to delete aoq and mantain hue, cpu load go down to average 50-55%. I tried to delete hue plugin and uase aoq, with average cpu load 45-50%. Without aoq and hue lights i have an average cpu load of 15-20% with some spikes over 60%.

I tried to reduce hue poll timeout to 2 seconds, no change.

 

I tried to soft reconfigure every battery device, again....and now cpu load is always above 80%...

Attached mine CPU load related to AOQ.

Please login or register to see this attachment.

 

By the way both AOQ use HC2 as slave. Means over 200 devices!!!

 

Edited September 8, 2020 by cag014

[cag014 731]

7 hours ago, minsad79 said:

Unknown error 

 

 

[08.09.2020] [13:43:02] [ERROR] [QUICKAPP103]: QuickApp crashed[08.09.2020] [13:43:02] [ERROR] [QUICKAPP103]: Unknown error occurred: attempt to index a nil value[08.09.2020] [13:44:03] [ERROR] [QUICKAPP103]: QuickApp crashed[08.09.2020] [13:44:03] [ERROR] [QUICKAPP103]: Unknown error occurred: attempt to index a nil value[08.09.2020] [13:45:03] [ERROR] [QUICKAPP103]: QuickApp crashed[08.09.2020] [13:45:03] [ERROR] [QUICKAPP103]: Unknown error occurred: attempt to index a nil value

 

 

Please post your jSlave and jM tables

Please remove your credentials from jSlave{} I just need to see the suffix name

[gggizmo 6]

6 minutes ago, cag014 said:

 

Attached mine CPU load related to AOQ.

Please login or register to see this attachment.

 

 

looks coherent with mine...

[cag014 731]

8 hours ago, gggizmo said:

hi cag, maybe i found another bug

 

lines like these don't work anymore

{0,"`isoggiorno`",{state="centralSceneSupport=2.Pressed",trueAct={{"`piantanaalta`","+changeBrightness,255",""},{"`piantanaalta`","turnOff;else;turnOn","","{`piantanaalta`:on=true}"}}}},

{0,"`rcamera`",{state="centralSceneSupport=dummy",trigAct={"`lcamera`","turnOff;else;setValue,100","","{`lcamera`:value>0}"}}},

 

every button press act like this. if light is on it switch off and then switch on again. If it's off it switch off and on again.

No issue in previous version of aoq

You mean both lines?

[gggizmo 6]

1 minute ago, cag014 said:

You mean both lines?

just an example,. Every lines where a condition is present to check if light is on or off by value 

[minsad79 19]

1 hour ago, cag014 said:

Please post your jSlave and jM tables

Please remove your credentials from jSlave{} I just need to see the suffix name

--========================== USER CONFIGURABLE PARAMETERS ===============================

jSlave={ 

    hc3={user="admin",passwd="12345678!",ip="12.10.79.127"},

    } 

 jS2n={sensor="316'hc3"}