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

[cag014 731]

 

1 hour ago, Rover said:

I am trying to do it also, so till now all could be implemented in AOQ.

But how to implement in AOQ a repeated action where the number of repetitions can be declared and the line can be "called" from several other lines?

Currently you have two options to do it.

1. using timeSpan and timeLoopAct{} -- not sure that exact number of repetitions could be achieved.

2. use  several "runAction" command with delay between them.

 

May I ask you to post an exact example of what you need.. is the time-between executions should be considered? is it the same command to repeat?

 

Edited September 26, 2020 by cag014

[Rover 47]

14 minutes ago, cag014 said:

 

Currently you have two options to do it.

1. using timeSpan and timeLoopAct{} -- not sure that exact number of repetitions could be achieved.

2. use  several "runAction" command with delay between them.

 

May I ask you to post an exact example of what you need.. is the time-between executions should be considered? is it the same command to repeat?

 

Please login or register to see this spoiler.

This is the implementation of buzz 3x in HC2. I should like to have a parametrized AOQ line (or scene or QA) with parameter N that is able to buzz N-times.

Yes, the time-between executions should be considered.

Yes, it is the same command to repeat.

Edited September 26, 2020 by Rover

[Rover 47]

Great day, testing the AOQ disarming for the first time.

But: Big Problem! AOQ got in a loop not to be stopped. AOQ crashes without warning and start initializing on and on. After rebooting HC3 the loop went on...

The only way of stopping was creating a syntax error by editing.

Please login or register to see this spoiler.

The scene in HC2 {"_436'hc2", "startScene"} is not triggert, while the e-mail and Pushover message is repeated on and on...

This is the first time a have used a HC2 scene from HC3.

okAct was activated, but all sensors were stil armed...

Edited September 27, 2020 by Rover

[gggizmo 6]

16 hours ago, cag014 said:

{0,"$blank",{timeSlot="?$sunriseHour+1800?~,~?$sunsetHour-1800?", --execute trueAct 30 min after sunrise and falseAct 30 min  before sunset

trueAct={"$variable","setGlobal","sunrise"},    -- set global variable to value "sunrise"

falseAct={"$variable","setGlobal","sunset"}}},  -- -- set global variable to value "sunset"

 

Assuming you need to set same global to different values at sunrise and sunset.

Please change $variable to your global and "sunrise"/"sunset" values to what you need

 

with $variable you meant &variable or did  i misunderstand another part of manual

Edited September 27, 2020 by gggizmo

[cag014 731]

17 minutes ago, gggizmo said:

with $variable you meant &variable or did  i misunderstand another part of manual

Yes, and it's mine mistake... should &variable.

[Rover 47]

2 hours ago, Rover said:

Great day, testing the AOQ disarming for the first time.

But: Big Problem! AOQ got in a loop not to be stopped. AOQ crashes without warning and start initializing on and on. After rebooting HC3 the loop went on...

The only way of stopping was creating a syntax error by editing.

Please login or register to see this spoiler.

okAct email is getting repeated, this time with all sensors really disarmed.

Edited September 27, 2020 by Rover

• Quote

[cag014 731]

6 minutes ago, Rover said:

This is enough for crashing AOQ:

Please login or register to see this spoiler.

Trying to simulate that... no success

[Rover 47]

8 minutes ago, cag014 said:

Trying to simulate that... no success

In my alarm zones only HC2Proxy sensors are present (others not visible in alarm zones). Maybe your simulation is with real HC3 sensor devices?

Please login or register to see this spoiler.

 

Edited September 27, 2020 by Rover

[Rover 47]

21 minutes ago, Rover said:

In my alarm zones only HC2Proxy sensors are present (others not visible in alarm zones). Maybe your simulation is with real HC3 sensor devices?

Please login or register to see this spoiler.

Changing the 2 alarm zones by one (&Hal) with only 1 D/W sensor (HC2Proxy) makes no difference in crashing result.

• Quote

[gggizmo 6]

@cag14

please can you share a short explanation about use and configuration of aoq_remote?

[cag014 731]

6 hours ago, Rover said:

Please login or register to see this spoiler.

@Rover

Didn't find any reason for that, but did some changes.

In addition this version has a new command rptAction to repeat any table at any line.

Example

{0,"$blank",{trueAct={{"`Sirene`"turnOn"},{"`Sirene`"turnOff","1"}}}}, -- let's assume this is the second line in jM

Now

{0,"`ketFob`",{state="centralSceneSupport=5.Pressed",trueAct={"$blank>2","rptAction,3,2","trueAct"}}},   -- $blank on second jM line.

 

rptAction command has two parameters (number of repetitions and delay between in seconds.

rptAction,3,10 -- repeat 3 times with delay of 10 seconds between executions.

 

All, attached version includes also bug fix when ;else; used in command.

 

 

Please login or register to see this attachment.

Edited September 27, 2020 by cag014

[cag014 731]

1 hour ago, gggizmo said:

@cag14

please can you share a short explanation about use and configuration of aoq_remote?

In side AOQ_Remote QA you'll find a table

jLbl={"OpenDoor","GardenLights","Arm","Disarm"}

 

Fill-in any appropriate names for you (up to 10)

Now in AOQ use jM line as follow (assuming AOQ_Remote QAid is 115)

 {0,"115",{state="userDescription=OpenDoor",trigAll=true,trueAct={{....}}}},

 

Same for every button.

[Rover 47]

Please login or register to see this spoiler.

while all sensors have been armed, so alarm zones with HC2Proxy sensors are not reliable in AOQ.

Or alarm zones result are not correct at all...

Anyway wrong conclusion by okAct has been declared.

Edited September 27, 2020 by Rover

[cag014 731]

32 minutes ago, Rover said:

Please login or register to see this spoiler.

I don't think this is related to the sensors. AOQ check the status of the alarm zones in HC3... not sensors.

By the way the data in table refreshed every few minutes, so when alarm armed, you might be see the previous data till next refresh cycle.

If you are using hcWebEyes, please arm the alarm and press "Toggle" button on hcWebEeye to refresh the data manually (another way to refresh the data is to press on/off button in HC3 UI) and see if the states are correct.

What you see printed out on debug window, is the real data. So okAct{} gets the real status and I don't think it is a wrong conclusion.

The problem that I don't understand why it goes to endless loop (don't see any reason in the code for that)

 

 

[cag014 731]

1 hour ago, Rover said:

Please login or register to see this spoiler.

Just to make sure that HC2Proxy is not a problem, you can download attached sensor_QA.

This QA emulates door sensor, bit it could be used for any sensor also (motion/window/door), just replace the icon accordingly (not necessary) and define HC2/HCL sensor ID

The advantage of this QA that it does included in alarm zone list.

Please login or register to see this attachment.

[cag014 731]

2 hours ago, Rover said:

Please login or register to see this spoiler.

Have added HC2Proxy sensor also, working fine. No endless loop on okAct{}

Strange indeed...

[gggizmo 6]

9 hours ago, cag014 said:

In side AOQ_Remote QA you'll find a table

jLbl={"OpenDoor","GardenLights","Arm","Disarm"}

 

Fill-in any appropriate names for you (up to 10)

Now in AOQ use jM line as follow (assuming AOQ_Remote QAid is 115)

 {0,"115",{state="userDescription=OpenDoor",trigAll=true,trueAct={{....}}}},

 

Same for every button.

tnx. aoq remote it's what i need to control slave devices from master controller interface...I missed a lot of posts past week and my idea to use quick apps with global var to control slave devices now sounds like a try to reinvent the wheel..a square wheel compared to your solution

[gggizmo 6]

Again a little help

 

{0,"$24clock",{state="value=05:00",lineState={"{&heating:value=true}"},timeSlot="~07:00",trueAct={"`caldaia`","turnOn",""},falseAct={"`caldaia`","turnOff",""}}},

{0,"$24clock",{state="value=07:30",lineState={"{&vmc:value=true}"},timeSlot="~14:00",trueAct={"`vmcs`","turnOn",""},falseAct={"`vmcs`","turnOff",""}}},

 

these lines are supposed to turnon at time and turnoff at the end of timeslot...but they don't work. What am i doing worng?

[Rover 47]

Now testing an alarm zone with 1 device (your new emulated sensor, indeed to be included in alarm zone).

Please login or register to see this spoiler.

 

Edited September 28, 2020 by Rover

[Rover 47]

Please login or register to see this spoiler.

Does this line with verification sign (!), but without okAct or errAct, also retry if disarming was not succeeded immediately?