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

[Rover 47]

8 hours ago, cag014 said:

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

The line is:

{5,"`BewegingHuiskamer`|`BewegingKeuken`",{initOnStartup=false,state="value=false",lineState={"if {&KerstPeriode:value=Ja and &Lichten:value=Uit}"}, 

    timeLoopAct={"`Kerstverlichting`","turnOff","if {`BewegingHuiskamer`,`BewegingKeuken`:lastBreached>900 and `Kerstboom`:value=true}"},}},

Please login or register to see this image.

/monthly_2021_01/screenshot-hc3-00005529.local-2021_01.17-01-44-12.png.6a24d5ce8ff81fb6184df4ab7d96fdfe.png" />

My point was: why displaying this every 5 minutes while the two devices (motion sensors) itself have not been triggered at all?

Please login or register to see this spoiler.

 

[cag014 731]

1 minute ago, Rover said:

The line is:

{5,"`BewegingHuiskamer`|`BewegingKeuken`",{initOnStartup=false,state="value=false",lineState={"if {&KerstPeriode:value=Ja and &Lichten:value=Uit}"}, 

    timeLoopAct={"`Kerstverlichting`","turnOff","if {`BewegingHuiskamer`,`BewegingKeuken`:lastBreached>900 and `Kerstboom`:value=true}"},}},

Please login or register to see this link.

My point was: why displaying this every 5 minutes while the two devices (motion sensors) itself have not been triggered at all?

Please login or register to see this spoiler.

That's strange... lineState tested only when the command is about to be executed.

Could you please post this jM line?

[Rover 47]

7 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...

Display only when device value (or GV) has been changed.

1 minute ago, cag014 said:

That's strange... lineState tested only when the command is about to be executed.

Could you please post this jM line?

I had posted the jM line in the beginning of the message:

{5,"`BewegingHuiskamer`|`BewegingKeuken`",{initOnStartup=false,state="value=false",lineState={"if {&KerstPeriode:value=Ja and &Lichten:value=Uit}"}, 

    timeLoopAct={"`Kerstverlichting`","turnOff","if {`BewegingHuiskamer`,`BewegingKeuken`:lastBreached>900 and `Kerstboom`:value=true}"},}},

[cag014 731]

1 minute ago, Rover said:

Display only when device value (or GV) has been changed.

So it sounds like @gggizmo suggested

[Rover 47]

4 minutes ago, cag014 said:

So it sounds like @gggizmo suggested

No, that is a discussion about the lineState. I only mean that without changes in a device value ("`BewegingHuiskamer`|`BewegingKeuken`") displaying anything has no use.

[gggizmo 6]

12 minutes ago, cag014 said:

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 .

yep, i agree, useless to debug something till it's working as expected

[Rover 47]

18 minutes ago, cag014 said:

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 .

I agree.

16 minutes ago, cag014 said:

That's strange... lineState tested only when the command is about to be executed.

Could you please post this jM line?

It has to do with timeLoopAct. Only this line has the issue.

[cag014 731]

2 hours ago, Rover said:

No, that is a discussion about the lineState. I only mean that without changes in a device value ("`BewegingHuiskamer`|`BewegingKeuken`") displaying anything has no use.

You have time span of 5 minutes, meaning while devices at false state every five minutes timeLoopAct {} executed, that's why LineState displayed altought the command not executed due to its condition.

[Rover 47]

4 hours ago, cag014 said:

You have time span of 5 minutes, meaning while devices at false state every five minutes timeLoopAct {} executed, that's why LineState displayed altought the command not executed due to its condition.

Yes, that's what is does, but how to avoid the display each 5 minutes while the command not executed?

[cag014 731]

That's exactly @gggizmo suggestion, to set dbgTrueState to false and only if the command executed the LineState is deisplayed.

 

Attached version works as suggested by @gggizmo

 

By default 

dbgTrueState=false (show lineState only if the command executed)

dbgFalseState=false (if lineState is false , nothing displayed)

 

Please set dbgTrueState and dbgFalseState per your choice.

 

Please login or register to see this attachment.

[Rover 47]

7 hours ago, cag014 said:

That's exactly @gggizmo suggestion, to set dbgTrueState to false and only if the command executed the LineState is deisplayed.

 

Attached version works as suggested by @gggizmo

 

By default 

dbgTrueState=false (show lineState only if the command executed)

dbgFalseState=false (if lineState is false , nothing displayed)

 

Please set dbgTrueState and dbgFalseState per your choice.

 

Please login or register to see this attachment.

v10.3 reboots AOQ every minute...

[cag014 731]

5 hours ago, Rover said:

v10.3 reboots AOQ every minute...

Strange... in any case attached version includes states for action tables also. (just add word  "State" to action table name: initACt={} -> initActState={} )

for example:

Standard format -

{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 can set condition for entire action array separately. 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"}}}},

 

In addition

1. new debug variable have added:

dbgInfo=true by setting to false not states will be displayed. (Default set to true)

 

dbgInfo     = true -- display states conditions according to dbgTrueState/dbgFalseState

dbgTrueState= false -- display line and action states when condition is true

dbgFalseState= true -- display line and action states when condition is false

 

2. ;else; statement could be used in conjunction with action state also

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

 

Please note, when conditional parameter defined in command, action state is ignored as part of else condition

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

in example above device 200 truns on/off according to his own state only. Means if trueActState is false the command will not be executed at all

 

 

3. lineState and action tables state could be defined as a table or as a string

lineState={"{200:value=0}"}     or   lineState="{200:value=0}"

trueActState={"{200:value=0}"}     or   trueActState="{200:value=0}"

and etc.

 

Currently in HcWebEye view every command will be displayed with if condition of action table state.... working to display it correctly.

 

 

 

Please login or register to see this attachment.

Edited January 18, 2021 by cag014

[gggizmo 6]

10.4

 

[18.01.2021] [09:33:17] [ERROR] [QUICKAPP1385]: QuickApp crashed[18.01.2021] [09:33:17] [ERROR] [QUICKAPP1385]: main.lua:729: 'end' expected (to close 'function' at line 726) near 'gData'

[cag014 731]

20 minutes ago, gggizmo said:

10.4

 

[18.01.2021] [09:33:17] [ERROR] [QUICKAPP1385]: QuickApp crashed[18.01.2021] [09:33:17] [ERROR] [QUICKAPP1385]: main.lua:729: 'end' expected (to close 'function' at line 726) near 'gData'

Are you sure?

Have tried on entire new QA - no errors

[gggizmo 6]

5 hours ago, cag014 said:

Are you sure?

Have tried on entire new QA - no errors

i rebooted hc3 and no error anymore

[Rover 47]

9 hours ago, cag014 said:

Strange... in any case attached version includes states for action tables also. (just add word  "State" to action table name: initACt={} -> initActState={} )

for example:

Standard format -

{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 can set condition for entire action array separately. 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"}}}},

 

In addition

1. new debug variable have added:

dbgInfo=true by setting to false not states will be displayed. (Default set to true)

 

dbgInfo     = true -- display states conditions according to dbgTrueState/dbgFalseState

dbgTrueState= false -- display line and action states when condition is true

dbgFalseState= true -- display line and action states when condition is false

 

2. ;else; statement could be used in conjunction with action state also

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

 

Please note, when conditional parameter defined in command, action state is ignored as part of else condition

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

in example above device 200 truns on/off according to his own state only. Means if trueActState is false the command will not be executed at all

 

 

3. lineState and action tables state could be defined as a table or as a string

lineState={"{200:value=0}"}     or   lineState="{200:value=0}"

trueActState={"{200:value=0}"}     or   trueActState="{200:value=0}"

and etc.

 

Currently in HcWebEye view every command will be displayed with if condition of action table state.... working to display it correctly.

 

 

 

Please login or register to see this attachment.

v10.4 installs without issues.

[cag014 731]

12 hours ago, gggizmo said:

i rebooted hc3 and no error anymore

?

[Rover 47]

Isn't time to specify a nice icon for All-in-One?

[cag014 731]

43 minutes ago, Rover said:

Isn't time to specify a nice icon for All-in-One?

You are welcome, I accept any idea

Edited January 20, 2021 by cag014

[cag014 731]

AOQ icons ON/OFF

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Looks OK

Please login or register to see this spoiler.

 

Edited January 20, 2021 by cag014