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

[cag014 731]

3 hours ago, gggizmo said:

I forgot to mention that after every single step or modification i rebooted hc3 to assure same starting condition

Thank you for such detail test.

By looking on your CPU graph, I can certainly say that new version has better CPU performances.

As I have suspected, more Z-wave device will cause longer delay and this makes sense as HC3 works.

HC3 trigger engine executes in parallel Lua/block scenes. 

In AOQ, I don't have a choice but to react by trigger->device in serial way.

I did an interesting experience by using few AOQs with different jM lines (I mean every AOQ has different z-wave devices) and the delay stays very low.

By the way AOQ has a small advantage over standard scenes. HC3 allows only one single scene instance (HC2 allows up to 10) and if triggered too fast the previous instance killed and an ERROR displayed. Don't think that's so important, but in follow example it does.

by pressing on Fibaro key-fob button one, I turn on or off the lights according opposite to the light state (if lights off-> turnOn, if lights on -> turn off).

By pressing very fast on key-fob no changes on the light according to the number of presses.

Again, , I want to thank you for your time and such a comprehensive testing...

 

 

[gggizmo 6]

23 minutes ago, cag014 said:

Thank you for such detail test.

By looking on your CPU graph, I can certainly say that new version has better CPU performances.

As I have suspected, more Z-wave device will cause longer delay and this makes sense as HC3 works.

HC3 trigger engine executes in parallel Lua/block scenes. 

In AOQ, I don't have a choice but to react by trigger->device in serial way.

I did an interesting experience by using few AOQs with different jM lines (I mean every AOQ has different z-wave devices) and the delay stays very low.

By the way AOQ has a small advantage over standard scenes. HC3 allows only one single scene instance (HC2 allows up to 10) and if triggered too fast the previous instance killed and an ERROR displayed. Don't think that's so important, but in follow example it does.

by pressing on Fibaro key-fob button one, I turn on or off the lights according opposite to the light state (if lights off-> turnOn, if lights on -> turn off).

By pressing very fast on key-fob no changes on the light according to the number of presses.

Again, , I want to thank you for your time and such a comprehensive testing...

 

 

A si previuos siad delay start to be noticeable with 10 devices or more. And from previuos post i reconfigure aoq to drives wall remotes. Block scenes are now used only for motion triggered lights.

At home my family can wait a little if a light is switched on or off manually, but no way, they enter in nothing is working mode if lights don't turn on immediatly when they walk trough the rooms.

So i can bear to have a mixed configuration to accomplish family request. I hope in better perfomance with new firmware but if i correctly understand may be delay is not related to cpu load, but let me say that it's really a pain to control multiple conditions with block scenes so everytime a small dely it's not a problem i'll continue to use aoq to save time and mental sanity.

 

Just a question: any idea to make a slave device visible in hc3 interface: ex. in garden i have 3 or 4 lights and i can't create a motion triggered scene. I did in the past but with  6 cats lights stay on every time. So i need to switch on and off manually. 

So may be a qa toggle global var checked by aoq  a solution? And i know that with this approch delay  on off it's in the range of 3-4 secs. Any hint?

[cag014 731]

5 hours ago, Rover said:

Wat is wrong in the verification?

Please login or register to see this spoiler.

Do you mean to have QA device that simulates slave's light device?

[gggizmo 6]

10 minutes ago, cag014 said:

I just think aloud, do we need confirmation? I think if no error executed it confirms that the action is completed.

I can create another table in case verification succeed, is it necessary?

Do you mean to have QA device that simulates slave's light device?

yes, and the only idea i have to use global var....

[gggizmo 6]

1 hour ago, cag014 said:

 

I did an interesting experience by using few AOQs with different jM lines (I mean every AOQ has different z-wave devices) and the delay stays very low.

By the way AOQ has a small advantage over standard scenes. HC3 allows only one single scene instance (HC2 allows up to 10) and if triggered too fast the previous instance killed and an

 

 

I missed this part...are you suggesting to split devices declarations and related jm lines to multiple instances of aoq?  Now i know what to do on sunday!!!!!!

[cag014 731]

6 minutes ago, gggizmo said:

I missed this part...are you suggesting to split devices declarations and related jm lines to multiple instances of aoq?  Now i know what to do on sunday!!!!!!

?

[gggizmo 6]

5 minutes ago, gggizmo said:

 

 

27 minutes ago, gggizmo said:

1 hour ago, cag014 said:

 

I did an interesting experience by using few AOQs with different jM lines (I mean every AOQ has different z-wave devices) and the delay stays very low.

 

 

and when you say aoq has different z-wave devices you meant in js line? Or it's enough that a specif device is not present in any action in jm lines?

[cag014 731]

8 minutes ago, gggizmo said:

 

and when you say aoq has different z-wave devices you meant in js line? Or it's enough that a specif device is not present in any action in jm lines?

jS2n line could be the same (it's just name mapping)

In each AOQ in jM line work with different devices as a line main device in jM (marked bold below) All devices could present in actions of all AOQs.

for example

AOQ-1

jM={

{0,"400",{state="value=true",trueAct={"300","turnOn",""}, falseAct={"300","turnOff",""}}},

}

AOQ-2

Never define 400 as line main device, but you can use it in actions

{0,"500",{state="value=true",trueAct={"300","turnOn","","{400:value=true}"}, falseAct={"300","turnOff",""}}},

Edited September 26, 2020 by cag014

[gggizmo 6]

7 minutes ago, cag014 said:

jS2n line could be the same (it's just name mapping)

In each AOQ in jM line work with different devices as a line main device in jM (marked bold below) All devices could present in actions of all AOQs.

for example

AOQ-1

jM={

{0,"400",{state="value=true",trueAct={"300","turnOn",""}, falseAct={"300","turnOff",""}}},

}

AOQ-2

Never define 400 as line main device, but you can use it in actions

{0,"500",{state="value=true",trueAct={"300","turnOn","","{400:value=true}"}, falseAct={"300","turnOff",""}}},

clear: avoid check of same zwave device in different instances of aoq.

 

Tnx

 

pss. my english is far from good, but i can assure that on monday i'll buy new aaa bateries for my keyboard...i'm loosing keystroke and my post are less than readble...sorry

[cag014 731]

To all, I hope this is the last update (few users have asked for an official release)

Major changes are:

1. Any command must have only two first fields (mandatory), all other fields could be written in any order or not at all if not required for your convenience.

For example

trueAct={"400","turnOff"} -  no delay/conditions/initState required

trueAct={"400","turnOff",false} -no delay/conditions required, only initOnStartup is false

trueAct={"400","turnOff","{300:value=true}"} - only conditions required

trueAct={"400","turnOff","{300:value=true}","10"} - conditions and delay required.

trueAct={"400","turnOff","{300:value=true}",true,"10"} - all parameters in use.

Although any order accepted, please try to keep same order when parameters required for better view later, but do skip unused parameters.

 

2. Conditional parameters could be written in human readable format also

Two formats are supported (any combination in between supported as well)

[when]{cond1 and cond2 and ….} or {cond1 and cond1 and ….} or..  - human readable

[=]{cond1|cond2|…}{cond4|cond5|….}{..} - short format

 

@Rover

Have added okAct{} table for successful verification.

{"all","disarmAlarm!{$Beneden:value=disarmed|$Boven:value=disarmed}",""},errAct={"Arming error","sendEmail,2","Niet alles armed"},okAct={"Arming state","sendEmail,2","Alarm armed"}}},

 

 

Please login or register to see this attachment.

[Rover 47]

31 minutes ago, cag014 said:

@Rover

Have added okAct{} table for successful verification.

{"all","disarmAlarm!{$Beneden:value=disarmed|$Boven:value=disarmed}",""},errAct={"Arming error","sendEmail,2","Niet alles armed"},okAct={"Arming state","sendEmail,2","Alarm armed"}}},

Thank you cag, for this very useful additions ?

Also the two major changes are very useful for me (and for sure other AOQ users) ?

Edited September 26, 2020 by Rover

[gggizmo 6]

Sorry to bother you with a simple question...i was so focused on performance and i don't pay attention to syntax changes and function, or simply i forgot how to create jm lines.

so, i need to create a simple jm line that changes a global var value 30 min after sunrise and 30 minutes before sunset...i'm stuck..i can believe it

[cag014 731]

46 minutes ago, gggizmo said:

Sorry to bother you with a simple question...i was so focused on performance and i don't pay attention to syntax changes and function, or simply i forgot how to create jm lines.

so, i need to create a simple jm line that changes a global var value 30 min after sunrise and 30 minutes before sunset...i'm stuck..i can believe it

{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

 

Edited September 26, 2020 by cag014

[gggizmo 6]

1 hour 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

 

first time i see $blank... I need to read again documentation and every single post in this topic.

 

Tnx again

[cag014 731]

Guys ... sorry... there is a bug when line includes ;else; statement. Please keep that lines in standard order, will fix it.

Other lines works fine

[Rover 47]

14 hours 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?

???

 

 

3 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"

What is the difference between $blank and $24clock?

Please login or register to see this spoiler.

 

Edited September 26, 2020 by Rover

[Rover 47]

7 hours ago, cag014 said:

12 hours ago, Rover said:

 

O.K. errAct is clear, but which line can be activated if all disarming has succeeded?

I just think aloud, do we need confirmation? I think if no error executed it confirms that the action is completed.

I can create another table in case verification succeed, is it necessary?

Yes I need confirmation of no error, because if no error then I can go further with the expansion of arming or disarming operation, while if error occurs the operation should be stopped.

TNX for adding the okAct feature ?

[cag014 731]

3 minutes ago, Rover said:

???

What is the difference between $blank and $24clock?

Please login or register to see this spoiler.

No difference at all... but probably you correct and it's better to use $24clock in this way you can easily to identify time-based lines in jM.

 

[Rover 47]

Is this HC2 command to be translated to AOQ? It concerns a Fibaro RGBW controller.

Please login or register to see this spoiler.

It sets just the W output off and let the other colors unchanged. I need this because the White color is steering the siren and outdoor flashlight.

[cag014 731]

21 minutes ago, Rover said:

Is this HC2 command to be translated to AOQ? It concerns a Fibaro RGBW controller.

Please login or register to see this spoiler.

Ok,

Used as standard command

{"`AlarmstatusRGB'hc2`", "setW,0")

Edited September 26, 2020 by cag014