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

[Rover 47]

4 hours ago, cag014 said:

Forgot about alarm property...

 

Please login or register to see this attachment.

Hi @cag014, 

Looks like you fixed it ?

Disabled motion sensor slaves.

Measurements like before: 1-3 seconds response time .

Disabled Scenemaster slave: 1-2 seconds response time ?

[cag014 731]

3 hours ago, Rover said:

Hi @cag014, 

Looks like you fixed it ?

Disabled motion sensor slaves.

Measurements like before: 1-3 seconds response time .

Disabled Scenemaster slave: 1-2 seconds response time ?

OK, Thanks. Looks ,ike this is the direction...

[gggizmo 6]

15 hours ago, cag014 said:

Forgot about alarm property...

 

Please login or register to see this attachment.

cag@14

 

there's a problem in initialization of hue lights in 7.1

 

[10 Nov 06:09:11] AOQ1385.jM hash table:17:~: {0, "`icucina`"...}
{0,"358",{"state"="centralSceneSupport=2.Pressed","trueAct"={{"1253","changeBrightness,255",""},{"1253","turnOff;else;turnOn","","{1253:on=true}"}}}}

(52) In device ID 1253, property 'on' not found.
To retrieve last modification time, add 'Modified at end of property name (case sensitive)
Available properties:
- value
- effect
- state
- currentProgram
- userDescription
- saturation
- colormode
- reachable
- color

 

[10.11.2020] [06:10:12] [ERROR] [QUICKAPP1385]: QuickApp crashed[10.11.2020] [06:10:12] [ERROR] [QUICKAPP1385]: main.lua:460: attempt to call a nil value (method 'stop')

 

[cag014 731]

2 hours ago, gggizmo said:

cag@14

 

there's a problem in initialization of hue lights in 7.1

 

[10 Nov 06:09:11] AOQ1385.jM hash table:17:~: {0, "`icucina`"...}
{0,"358",{"state"="centralSceneSupport=2.Pressed","trueAct"={{"1253","changeBrightness,255",""},{"1253","turnOff;else;turnOn","","{1253:on=true}"}}}}

(52) In device ID 1253, property 'on' not found.
To retrieve last modification time, add 'Modified at end of property name (case sensitive)
Available properties:
- value
- effect
- state
- currentProgram
- userDescription
- saturation
- colormode
- reachable
- color

 

[10.11.2020] [06:10:12] [ERROR] [QUICKAPP1385]: QuickApp crashed[10.11.2020] [06:10:12] [ERROR] [QUICKAPP1385]: main.lua:460: attempt to call a nil value (method 'stop')

 

Did it work on previous versions?

Pls try attached

 

Please login or register to see this attachment.

Edited November 10, 2020 by cag014

[gggizmo 6]

21 minutes ago, cag014 said:

Did it work on previous versions?

Pls try attached

 

Please login or register to see this attachment.

works in very version before 7.

May be in value init phase hue device give null value. It was a problem in early aos version

25 minutes ago, cag014 said:

Did it work on previous versions?

Pls try attached

 

Please login or register to see this attachment.

yes 7.2 works

 

tnx

[cag014 731]

2 minutes ago, gggizmo said:

works in very version before 7.

May be in value init phase hue device give null value. It was a problem in early aos version

OK... is it works on 7.2?

[SmartLifeSystems 20]

 

2 hours ago, cag014 said:

OK... is it works on 7.2?

 

Hi, @cag014,

 

I'am afraid, in the 7.2 the $profile, and the global variables don't working.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Edited November 10, 2020 by SmartLifeSystems

[Rover 47]

Please login or register to see this spoiler.

V7.1 crash, why?

[cag014 731]

 

@Rover

Due to new scanning, dead devices of slave controllers now take part of the table, fixed.

@SmartLifeSystems

Bug fixed.

 

 

Please login or register to see this attachment.

Edited November 11, 2020 by cag014

[cag014 731]

Attached version includes bug fix for trigAct execution while monitoring scene instances.

 

Please login or register to see this attachment.

[gggizmo 6]

1 hour ago, cag014 said:

Attached version includes bug fix for trigAct execution while monitoring scene instances.

 

Please login or register to see this attachment.

oninit section missing.

[Rover 47]

How to make AOQ_Remote able to react on button doublepressed?

[GaelP 0]

Monring Cag, Morning everyone,

Another beginer question: how to have several action triggered by the same conditions. Use case: turnon a light under certain condition, and then turn it off.

The following kind of works:

{0,"`dEntree`",{state="value=true",trueAct={{"`lSuspensionPressoir`","turnOn","","{{&Jour_Nuit:value=Nuit} and {if{`lSuspensionPressoir`:value=false}}}"},{"`lSuspensionPressoir`","turnOff","180"}}}},

But as webeye show very clearly the Turnoff action is outside the if statement. Will always be executed. In this specific case, not an issue -beside turnoff a light which is already off-, but  there will be case when that's a problem. As a newbie, I don't know how to achieve this. Any suggestion?

Many thanks

Please login or register to see this attachment.

[cag014 731]

1 hour ago, GaelP said:

Monring Cag, Morning everyone,

Another beginer question: how to have several action triggered by the same conditions. Use case: turnon a light under certain condition, and then turn it off.

The following kind of works:

{0,"`dEntree`",{state="value=true",trueAct={{"`lSuspensionPressoir`","turnOn","","{{&Jour_Nuit:value=Nuit} and {if{`lSuspensionPressoir`:value=false}}}"},{"`lSuspensionPressoir`","turnOff","180"}}}},

But as webeye show very clearly the Turnoff action is outside the if statement. Will always be executed. In this specific case, not an issue -beside turnoff a light which is already off-, but  there will be case when that's a problem. As a newbie, I don't know how to achieve this. Any suggestion?

Many thanks

Please login or register to see this attachment.

Yes, it should be outside because the condition defined in turnOn section.

To set condition for all actions in the line use lineState

{0,"`dEntree`",{state="value=true",

lineState={"if {&Jour_Nuit:value=Nuit} and {`lSuspensionPressoir`:value=false}"},

trueAct={{"`lSuspensionPressoir`","turnOn"},{"`lSuspensionPressoir`","turnOff","180"}}}},

 

 

Edited November 11, 2020 by cag014

[GaelP 0]

Thanks for your very swift answer. As usual. 

 

when I add the lineState however, the resulting behaviour is not the one expected.

 

1/ Starting with only one condition:

{0,"`dEntree`",{state="value=true",

lineState={"{`lSuspensionPressoir`:value=false}"},

trueAct={{"`lSuspensionPressoir`","turnOn"},{"`lSuspensionPressoir`","turnOff","15"}}}},

Screen capture 2 here below.

In that case, the light does switch on but never switch off (I reduce to 15 sec for testing). 

In the debug window, I do see the turn on action but never see the turn off:  jM{11} TEntrée:266:Door[true] => turnOn{lSuspensionPressoir)

 

If I take out the line state, in that case the light switch on and then switch off 15 sec after.: 11.11.2020] [15:20:28] [TRACE] [AOQ483]: ^4.1jM{11} _TEntrée:266:Door[true] => turnOn{lSuspensionPressoir)[11.11.2020] [15:20:43] [TRACE] [AOQ483]: ^4.1jM{11} _TEntrée:266:Door[false] => ^15s>turnOff{lSuspensionPressoir)

2/ if I put the two conditions with an "and" -which is indeed what I want- then it looks this is translated as a "or".

See attached screen capture that show web eye showing an "or" instead of a and

as a result the light switch on even if only of the two condition is fulfilled ("jour nuit" value was "nuit" , lsuspensionpressoir was off)

lineState={"if {&Jour_Nuit:value=Nuit} and {`lSuspensionPressoir`:value=false}"},

 

For now, i'll stay with this {0,"`dEntree`",{state="value=true",trueAct={{"`lSuspensionPressoir`","turnOn","","{{&Jour_Nuit:value=Nuit} and {if{`lSuspensionPressoir`:value=false}}}"},{"`lSuspensionPressoir`","turnOff","180"}}}}, which gives the result expected even if the turnoff is useless as always executed even if the light was off. 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Edited November 11, 2020 by GaelP

[gggizmo 6]

On 11/10/2020 at 8:48 AM, cag014 said:

 

Have you checked the 7.4 attachment?

I think that all lines of oninit secton are missing. I downloaded it 3 times...or maybe there's a problem with my browser

[cag014 731]

34 minutes ago, GaelP said:

Thanks for your very swift answer. As usual. 

 

when I add the lineState however, the resulting behaviour is not the one expected.

 

1/ Starting with only one condition:

{0,"`dEntree`",{state="value=true",

lineState={"{`lSuspensionPressoir`:value=false}"},

trueAct={{"`lSuspensionPressoir`","turnOn"},{"`lSuspensionPressoir`","turnOff","15"}}}},

Screen capture 2 here below.

In that case, the light does switch on but never switch off (I reduce to 15 sec for testing). 

In the debug window, I do see the turn on action but never see the turn off:  jM{11} TEntrée:266:Door[true] => turnOn{lSuspensionPressoir)

 

If I take out the line state, in that case the light switch on and then switch off 15 sec after.: 11.11.2020] [15:20:28] [TRACE] [AOQ483]: ^4.1jM{11} _TEntrée:266:Door[true] => turnOn{lSuspensionPressoir)[11.11.2020] [15:20:43] [TRACE] [AOQ483]: ^4.1jM{11} _TEntrée:266:Door[false] => ^15s>turnOff{lSuspensionPressoir)

2/ if I put the two conditions with an "and" -which is indeed what I want- then it looks this is translated as a "or".

See attached screen capture that show web eye showing an "or" instead of a and

as a result the light switch on even if only of the two condition is fulfilled ("jour nuit" value was "nuit" , lsuspensionpressoir was off)

lineState={"if {&Jour_Nuit:value=Nuit} and {`lSuspensionPressoir`:value=false}"},

 

For now, i'll stay with this {0,"`dEntree`",{state="value=true",trueAct={{"`lSuspensionPressoir`","turnOn","","{{&Jour_Nuit:value=Nuit} and {if{`lSuspensionPressoir`:value=false}}}"},{"`lSuspensionPressoir`","turnOff","180"}}}}, which gives the result expected even if the turnoff is useless as always executed even if the light was off.

OK... let's do some reorder...

First of all lineState is always verified, so when you activate turnOff after delay the line is verified again and in this case the lineState is false.

The question is it correct to use lineState in this case.

Why not just:

{0,"`dEntree`",{state="value=true",trueAct={{"`lSuspensionPressoir`","turnOn"},{"`lSuspensionPressoir`","turnOff","180"}}}},

or may I suggest as follwoing

{0,"`dEntree`",{state="value=true",trueAct={"`lSuspensionPressoir`","turnOn"},falseAct={"`lSuspensionPressoir`","turnOff","180"}}},

The idea as I understand is to turn light on when motion detected, but in your case if someone will continue to move in front of the sensor the light will turn off after 180 sec. always and the person will find himself in the dark!!? So when motion sensor back to safe after 180 sec. turn Off the lights better aproach.

 

In second scenario there is a syntax mistake. The and should be in same brackets.

"{&Jour_Nuit:value=Nuit} and {`lSuspensionPressoir`:value=false}"

the correct syntax is

"{&Jour_Nuit:value=Nuit and `lSuspensionPressoir`:value=false}"

In addition please try to keep Lua language syntax, I mean after and sgould be no if

like

if (....) and (...)

not like

if (...) and (if(...)

The syntax is

if {cond1 and cond2 and ….} or {cond1 and cond1 and ….} or..

Please see Advance User guide (Conditional Parameter format) for more info

Edited November 11, 2020 by cag014

[cag014 731]

5 hours ago, Rover said:

How to make AOQ_Remote able to react on button doublepressed?

Why? Just add another button with the action name.

[Rover 47]

9 minutes ago, cag014 said:

Why? Just add another button with the action name.

Then more actions could be triggered by one smartphone screen. But indeed more buttons is no problem.

[cag014 731]

14 minutes ago, Rover said:

Then more actions could be triggered by one smartphone screen. But indeed more buttons is no problem.

Yes, it's correct, but (at least on my phone) there are a lot of space to accommodate about 15 buttons..

54 minutes ago, gggizmo said:

Have you checked the 7.4 attachment?

I think that all lines of oninit secton are missing. I downloaded it 3 times...or maybe there's a problem with my browser

You're absolutely correct...  when last function folded, it's not copied...

Please check CPU load... I think it's decreased even more than before...

 

Please login or register to see this attachment.