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

[cag014 731]

13 hours ago, Rover said:

{"Voordeur","sendEmail,2","Voordeurstatus: @`Voordeur`>value"},

`Voordeur` is a AEON DW-sensor.

Please login or register to see this spoiler.

Because values are intended to use in calculations, so true and false converted automatically to numeric values....

[Rover 47]

On 1/14/2021 at 1:46 AM, cag014 said:

I think this is my bad... if you remember have added extra trigger for $24clock and disabled the standard refreshState trigger.

 

Anyhow try attached version (both triggers in place)

in addition:

1. Added an option to skip time-span definition when not required.

    

Standard format:

 

{0,"DevID", {state="value=true", truAct{…}}},

 

New optional format

 

{"DevID", {state="value=true", truAct{…}}}, 

 

 

 

Please login or register to see this attachment.

Super fast again ?

[cag014 731]

The attached version displays lineState condition before commands execution.

By default true and false states are shown

Please login or register to see this spoiler.

 

By default (if variables are not defined) both states are displayed.

 

In addition I intend to add state for each action array, something like

trueState - condition for all commands in trueAct{}

falseState - condition for all commands in falseAct{}

timeLoopState- condition for all commands in timeLoopAct{}

and etc....

Please login or register to see this attachment.

[AR27690 19]

Works and looks super !!!

What about All-in-One Scene for HC2, is it possible to have same debug information ?

[cag014 731]

Just now, AR27690 said:

Works and looks super !!!

What about All-in-One Scene for HC2, is it possible to have same debug information ?

Yes, work in progress...

In next release user can choose table or debug view, while HcWebEye will support table view (same as for HC3)

[Rover 47]

2 hours ago, cag014 said:

In addition I intend to add state for each action array, something like

trueState - condition for all commands in trueAct{}

falseState - condition for all commands in falseAct{}

timeLoopState- condition for all commands in timeLoopAct{}

and etc...

?

[Rover 47]

2 hours ago, cag014 said:

The attached version displays lineState condition before commands execution.

By default true and false states are shown

Please login or register to see this spoiler.

 

• Quote

[Rover 47]

v10.2 is much faster ?

[Rover 47]

15 hours ago, Rover said:

v10.2 is much faster ?

Amazing fast, what took many seconds before (one action in one second) is done now into 1 second.  what happened?

Edited January 17, 2021 by Rover

[cag014 731]

Just an extra trigger which works when the z-wave is busy or no activity at all.

Now it always respond and not only when the system triggers the events...

[Rover 47]

3 minutes ago, cag014 said:

Just an extra trigger which works when the z-wave is busy or no activity at all.

Now it always respond and not only when the system triggers the events...

????

[Rover 47]

Please login or register to see this spoiler.

 

[cag014 731]

The lineState status is displayed, but commands conditions probably not true and not executed....

[cag014 731]

1 hour ago, Rover said:

Please login or register to see this spoiler.

Do you think this is better when the lineState is true and only when command executed to display the state?

What about displaying lineState false? In this case the commands are not executed also.... but from other hand it could be disabled by setting dbgFalseState to false.

 

To display true lineState when commands executed for me is a matter of seconds to change the code....

Let me know what do you think about it?

I'll be glad to have an opinion of other users also...

Edited January 17, 2021 by cag014

[gggizmo 6]

5 hours ago, cag014 said:

Do you think this is better when the lineState is true and only when command executed to display the state?

What about displaying lineState false? In this case the commands are not executed also.... but from other hand it could be disabled by setting dbgFalseState to false.

 

To display true lineState when commands executed for me is a matter of seconds to change the code....

Let me know what do you think about it?

I'll be glad to have an opinion of other users also...

what about something more granular?

dbgtruestate=true

dbgtruestateaction=true

and aoq shows line state always

if dbgtruestateaction=false

aoq shows linestate if action is excuted.

 

Just a suggestion i really don't  know how complex may be to implement this kind of debug.

 

 

[cag014 731]

5 minutes ago, gggizmo said:

what about something more granular?

dbgtruestate=true

dbgtruestateaction=true

and aoq shows line state always

if dbgtruestateaction=false

aoq shows linestate if action is excuted.

 

Just a suggestion i really don't  know how complex may be to implement this kind of debug.

 

 

Nice Idea... so be it.

By the way I'm adding trueActState, falseActState and etc. (means the trueActState has a condition for entire trueAct{} commands. No need to write same condition for every command)

Should they displayed the same, using same global variable?

 

[gggizmo 6]

3 minutes ago, cag014 said:

Nice Idea... so be it.

By the way I'm adding trueActState, falseActState and etc. (means the trueActState has a condition for entire trueAct{} commands. No need to write same condition for every command)

Should they displayed the same, using same global variable?

 

Sorry cag014 it's not clear to me what do you mean

[cag014 731]

Currently we're talking about displaying lineState condition.

In next version I'm adding condition array for every action table, for example:

Here the standard jM line

{0,"$24clock",{state="02:00", trueAct{{"200","turnOn","{&GV:value=start}"},{"300","open","{&GV:value=start}"},{"400","setValue,90","{&GV:value=start}"}},

falseAct{{"200","turnOff","{&GV:value=stop}"},{"300","close","{&GV:value=stop}"},{"400","setValue,0","{&GV:value=stop}"}}}},

 

Now you'll be able to set condition for every action array separately (of course this is in addition to the lineState defintion). More convenient way to define and to maintain

{0,"$24clock",{state="02:00", trueActState="{&GV:value=start}", trueAct{{"200","turnOn",},{"300","open"},{"400","setValue,90"}},

falseActState="{&GV:value=stop}", falseAct{{"200","turnOff"},{"300","close"},{"400","setValue,0"}}}},

 

So I believe same debug logic goes here as well

 

[gggizmo 6]

19 minutes ago, cag014 said:

Currently we're talking about displaying lineState condition.

In next version I'm adding condition array for every action table, for example:

Here the standard jM line

{0,"$24clock",{state="02:00", trueAct{{"200","turnOn","{&GV:value=start}"},{"300","open","{&GV:value=start}"},{"400","setValue,90","{&GV:value=start}"}},

falseAct{{"200","turnOff","{&GV:value=stop}"},{"300","close","{&GV:value=stop}"},{"400","setValue,0","{&GV:value=stop}"}}}},

 

Now you'll be able to set condition for every action array separately (of course this is in addition to the lineState defintion). More convenient way to define and to maintain

{0,"$24clock",{state="02:00", trueActState="{&GV:value=start}", trueAct{{"200","turnOn",},{"300","open"},{"400","setValue,90"}},

falseActState="{&GV:value=stop}", falseAct{{"200","turnOff"},{"300","close"},{"400","setValue,0"}}}},

 

So I believe same debug logic goes here as well

 

 

I missed previous posts about new version. So you think to use same debug control vars to show linestate and actstate following same logic suggested in my previous post.

 

[cag014 731]

Yes, this is correct...

What do you think should be the default setup for

dbgTrueState=?

dbgFalseState=?

To my opinion both should be set to false by default .

Edited January 17, 2021 by cag014