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

[Rover 47]

12 minutes ago, cag014 said:

3 hours ago, Rover said:

How to attach HC2-devices to Alarm Zone?

This is totally different approach for alarm in HC3.

In HC2 during arming the HC3 alarm, just include command to arm sensors in HC2 and vise versa.

Same way that you did in HC2

So Alarm Zone concept not usable with devices still in HC2.

Is this concept useful at all using AOQ, even when the HC2 devices have been migrated to HC3?

[cag014 731]

4 hours ago, gggizmo said:

may i ask you all of you which browser you use to connect to hc3?

Microsoft Edge -85.0.564.44 (Official build) (64-bit)

Firefox 80.0.1 (64-bit) for hcWebEye

 

4 hours ago, gggizmo said:

@cag only issue i have now is weird toggle light behavior i can't figure out why with aoq1.2 everything works and with aoq 2 not.

I'm trying to simulate that, but it works OK for me. (with Fibaro key-fob)

Just for testing could you please change the follow line in mainCode. Please ignore any delays

fibaro.setTimeout(400, function() self:refreshState(lastNext-1)

to

fibaro.setTimeout(400, function() self:refreshState(lastNext)

Let me know if it helps....

Could you post information about your remotes (brand and model to take a look on manuals)

 

 

Edited September 10, 2020 by cag014

[cag014 731]

21 minutes ago, Rover said:

So Alarm Zone concept not usable with devices still in HC2.

Is this concept useful at all using AOQ, even when the HC2 devices have been migrated to HC3?

When you migrate devices from HC2 to HC3 this is the only concept to use the Alarm.

In HC3 you cannot arm or disarm any sensor by itself. They must be included in Alarm Zone.

But I do suggest to create alarm zones in HC3 and to included in AOQ. After transferring devices to HC3 it takes few seconds to update the zones with sensors.

In addition in HC3 AOQ supports arm/disarm/breached states of the alarm for every included sensor. The breached state of the sensor is not available by default in HC3 as a command or status.

Edited September 10, 2020 by cag014

[cag014 731]

5 hours ago, Rover said:

I am sorry to bother you with my typo. It should be &Huisstatus'hc2 and not &Huisstatus|hc2 and it works. ?

No problem.... I thank you for your help...

[Rover 47]

On 9/5/2020 at 7:42 PM, cag014 said:

To notify on breached sensors at any time could be done as well, but it's a little bit tricky.

1. You need to set variable for every sensor and during the arming alarm to use them.

2.Every sensor will send notification, but no variables required.

Let me know if you do need this option and will provide an example

In HC2 alarm scene each device is tested on breaching and if yes a Pushover message is sent per breached device.

Also in the arming scene each device is tested on being closed and if not a Pushover message is sent per open door/window. After arming is tested if all doors/windows have been armed.

How to implement this in an intelligent way in AOQ?

26 minutes ago, cag014 said:

When you migrate devices from HC2 to HC3 this is the only concept to use the Alarm.

In HC3 you cannot arm or disarm any sensor by itself. They must be included in Alarm Zone.

But I do suggest to create alarm zones in HC3 and to included in AOQ. After transferring devices to HC3 it takes few seconds to update the zones with sensors.

In addition in HC3 AOQ supports arm/disarm/breached states of the alarm for every included sensor. The breached state of the sensor is not available by default in HC3 as a command or status.

So the procedure is to implement all alarming scenes in AOS and not AOQ. After migration of the HC2-devices to HC3 the alarm zones have to be implemented. Right?

[cag014 731]

16 minutes ago, Rover said:

In HC2 alarm scene each device is tested on breaching and if yes a Pushover message is sent per breached device.

Also in the arming scene each device is tested on being closed and if not a Pushover message is sent per open door/window. After arming is tested if all doors/windows have been armed.

How to implement this in an intelligent way in AOQ?

Same in HC3 , you'll need to test every device for status same as in HC2.

By the way it could be done only with AOQ.

The standard alarm trigger in HC3 does not specify which sensor is armed/disarmed/breached, only for entire alarm zone

 

May I ask you if you did find the jP2n{} table?

Edited September 10, 2020 by cag014

[Rover 47]

6 minutes ago, cag014 said:

May I ask you if you did find the jP2n{} table?

6 hours ago, Rover said:

7 hours ago, cag014 said:

7 hours ago, Rover said:

No jP2n in the new version...

Is there... in main. Right above jS2n table

It is not.

The new mainCode has one line more than the previous one.

Sorry again!

I only changed the mainCode and not the main, so it was not there, while you said explicitly it is in main ?.

It is present in main. ?

13 hours ago, Rover said:

Scenario:

A light is started at random time and stopped at random time and started at random time and stopped at random time ...

All this started when a global parameter has been changed and stopped by clocktime or other global parameter.

How to implement this in AOQ? In particular the repeat action bothers me.

Any suggestion?

[cag014 731]

11 minutes ago, Rover said:

Scenario:

A light is started at random time and stopped at random time and started at random time and stopped at random time ...

All this started when a global parameter has been changed and stopped by clocktime or other global parameter.

How to implement this in AOQ? In particular the repeat action bothers me.

Any specific time limit how long the light could be on, random between  10 to 30 minutes? Same for Off

 

[Rover 47]

8 minutes ago, cag014 said:

Any specific time limit how long the light could be on, random between  10 to 30 minutes? Same for Off

 

Please login or register to see this spoiler.

Yes.

[cag014 731]

40 minutes ago, Rover said:

Please login or register to see this spoiler.

Seconds or Minutes ?

[cag014 731]

57 minutes ago, Rover said:

Please login or register to see this spoiler.

Interesting... below the time slot is in minutes... try it... when you'll run first time the AOQ it will be active for 10 minutes...after that it's random

{10,"$gName",{state="value=start", timeLoopAct={{"$lineId","setTimeSpan","?random(`RandomMinTijd`,`RandomMaxTijd`)?"},{"lightId","turnOn;else;turnOff","","{lightId:value=false}"}}}},

 

Now set $gName variable to your variable and set to start or stop. Change lightId to your light device number.

Let me know if it works...

Edited September 11, 2020 by cag014

[gggizmo 6]

6 hours ago, cag014 said:

Microsoft Edge -85.0.564.44 (Official build) (64-bit)

Firefox 80.0.1 (64-bit) for hcWebEye

 

I'm trying to simulate that, but it works OK for me. (with Fibaro key-fob)

Just for testing could you please change the follow line in mainCode. Please ignore any delays

fibaro.setTimeout(400, function() self:refreshState(lastNext-1)

to

fibaro.setTimeout(400, function() self:refreshState(lastNext)

Let me know if it helps....

Could you post information about your remotes (brand and model to take a look on manuals)

 

 

yes it's ok now. 

Any impact of this modification overall system?

 

[Rover 47]

8 hours ago, cag014 said:

Interesting... below the time slot is in minutes... try it... when you'll run first time the AOQ it will be active for 10 minutes...after that it's random

{10,"$gName",{state="value=start", timeLoopAct={{"$lineId","setTimeSpan","?random(`RandomMinTijd`,`RandomMaxTijd`)?"},{"lightId","turnOn;else;turnOff","","{lightId:value=false}"}}}},

 

Now set $gName variable to your variable and set to start or stop. Change lightId to your light device number.

Let me know if it works...

You are really a genius ? , especially in the middle of the night ?

It works!

In minutes is good.

Now I begin to comprehend the possibilities of timeLoopAct and setTimeSpan for loop activities!

[Sjakie 156]

Hello,

Anyone can tell me how to use HUE settings

Brightness,

Hue,

Saturation

Transitiumtime

Color

 

Thanks in advance,

//Sjakie

[gggizmo 6]

9 hours ago, gggizmo said:

yes it's ok now. 

Any impact of this modification overall system?

 

attached remote manual

Please login or register to see this attachment.

[Rover 47]

Please login or register to see this spoiler.

Edited September 11, 2020 by Rover

[gggizmo 6]

5 hours ago, Sjakie said:

Hello,

Anyone can tell me how to use HUE settings

Brightness,

Hue,

Saturation

Transitiumtime

Color

 

Thanks in advance,

//Sjakie

that's the reply cag sent to me for driving hue lights.

 

Now, to add non exist device's command, add plus sign "+" before the command. The command will be added without any verification.

Please be careful, any error in command name won't generate any warning. It's user's responsibility to verify if it works.

for example:

{"817","+changeBrightness,255",""}

{"817","+changeHue,255",""}

{"817","+changeSaturation,255",""}

 

So I think you have simply to put+ in front of the settings you want to push to hue light

 

[cag014 731]

12 hours ago, gggizmo said:

yes it's ok now. 

Any impact of this modification overall system?

 

Yes, It could have delays on slave devices up to 30 seconds, depends on HC3 activities rate.

Let me to try something to solve the problem.

[Rover 47]

This does not work:

Please login or register to see this spoiler.

Does exist a syntax for combining setGlobal operations?

[Rover 47]

What about this puterror?

Please login or register to see this spoiler.