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

[GaelP 0]

Thanks I will review and read again the advance user guide + tips & tricks.

To detail my use case: 

I want the light to be switch on (and off after 3 mn) only if we’re at night (checking against a global variable that I maintain « $journuit ») and if the light was not already on. If the light was already on, I don’t want to execute this jm line as I want to keep the light open as someone would have manually operated it.

I have not started to implement « and stay on if there is still some movement »

[cag014 731]

 

22 minutes ago, GaelP said:

Thanks I will review and read again the advance user guide + tips & tricks.

To detail my use case: 

I want the light to be switch on (and off after 3 mn) only if we’re at night (checking against a global variable that I maintain « $journuit ») and if the light was not already on. If the light was already on, I don’t want to execute this jm line as I want to keep the light open as someone would have manually operated it.

I have not started to implement « and stay on if there is still some movement »

OK, now it's more clear.

By the way for the night hours you can use timeSlot and sunset/rise hours and not to use global variable. More readable in the future for maintenance.

May I ask what version you're using?

Version 7.0 and above works as you need.

 

Edited November 11, 2020 by cag014

[gggizmo 6]

13 minutes ago, cag014 said:

To all, based on @GaelP input regarding lineState behavior, I would like to hear your opinion on following scenario:

 

If lineState is correct and delayed command initiated, after delay before command execution should the lineState to be verified again or command must be executed in any case?

 

As an example:

{0,"`dEntree`",{state="value=true", lineState={"{`lSuspensionPressoir`:value=false}"},

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

The logic here, that when dEntree breached, if the lights are off then turn ON and turn off after 180 seconds.

Currently after delay before turnOff execution, lineState checked and since the lights are on (not false) then command is not executed.

 

What do you think?

 

OK, now it's more clear.

By the way for the night hours you can use timeSlot and sunset/rise hours and not to use global variable. More readable in the future for maintenance.

I'm used to check ( in block scene) if light it's on before send switch off command, just to reduce zwave traffic...so imho it's better to check again before command execution

30 minutes ago, cag014 said:

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

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.

cpu load is pretty the same in all aoq 7.x versions. Or in my configuration differences are not noticeable.  On week end i'll try again to switch from block scene to aoq for lights control and i'll report you back infos about delays

[cag014 731]

46 minutes ago, gggizmo said:

I'm used to check ( in block scene) if light it's on before send switch off command, just to reduce zwave traffic...so imho it's better to check again before command execution

cpu load is pretty the same in all aoq 7.x versions. Or in my configuration differences are not noticeable.  On week end i'll try again to switch from block scene to aoq for lights control and i'll report you back infos about delays

That's will be interesting... I do not expect delays on that version

[Rover 47]

2 hours ago, cag014 said:

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

Yes, it looks even faster , 1 second response time. ?

[cag014 731]

3 minutes ago, Rover said:

Yes, it looks even faster , 1 second response time. ?

Finally WE fixed the problem. and I mean it WE

To all thanks for your inputs.

[Rover 47]

26 minutes ago, cag014 said:

Finally WE fixed the problem. and I mean it WE

To all thanks for your inputs.

??

[gggizmo 6]

@cag014

ithink there's a bug in checking state of hue devices. 

ex.

{0,"`icucina`",{state="centralSceneSupport=2.Pressed",trueAct={{"`lcucina`","+changeBrightness,255",""},{"`lcucina`","turnOff;else;turnOn","","{`lcucina`:on=true}"}}}},

a line like this isn't working. If i  activate a a block scene to toogle on/off works as expected.

It's same line i used in previous aoq versions

 

looks like aoq sees hue lights always off and send turnon command everytime

Please login or register to see this attachment.

 

 

Edited November 11, 2020 by gggizmo

[Rover 47]

2 hours ago, gggizmo said:

If lineState is correct and delayed command initiated, after delay before command execution should the lineState to be verified again or command must be executed in any case?

In order to be able to optimize jM lines, I have two wishes that are familiair to each other:

1.   state="condition-a" or state="condition-b" or state="condition-c",
   • The number of lines with the same action tables could be diminished.
   • Alternative trigAll with conditions in the action lines is not so elegant.
2.   If lineState is correct and delayed command initiated, after delay before command execution should the lineState to be verified again.
   • After delay things could be changed so that the actions could be not desired anymore to execute.
   • Necessary conditions in the action lines to accomplish the same effect are not so elegant.

[SmartLifeSystems 20]

8 hours ago, gggizmo said:

I'm used to check ( in block scene) if light it's on before send switch off command, just to reduce zwave traffic...so imho it's better to check again before command execution

cpu load is pretty the same in all aoq 7.x versions. Or in my configuration differences are not noticeable.  On week end i'll try again to switch from block scene to aoq for lights control and i'll report you back infos about delays

 

@cag014

 

I think the lastBreached function not working correctly. Prev i used the v6.3.

In the 6.3 this globals was in min.

 

Please login or register to see this image.

/monthly_2020_11/image.png.3decc89760331d12ece76faa50933134.png" />

 

Edited November 12, 2020 by SmartLifeSystems

[cag014 731]

12 hours ago, gggizmo said:

@cag014

ithink there's a bug in checking state of hue devices. 

ex.

{0,"`icucina`",{state="centralSceneSupport=2.Pressed",trueAct={{"`lcucina`","+changeBrightness,255",""},{"`lcucina`","turnOff;else;turnOn","","{`lcucina`:on=true}"}}}},

a line like this isn't working. If i  activate a a block scene to toogle on/off works as expected.

It's same line i used in previous aoq versions

 

looks like aoq sees hue lights always off and send turnon command everytime

Please login or register to see this attachment.

 

 

Is it worked on previous versions?

As I understand this is a hue lights on HC3, could you please post device API

hhttp://HC3-IP/api/devices/HUE-ID

Edited November 12, 2020 by cag014

[gggizmo 6]

5 minutes ago, cag014 said:

Is it worked on previous versions?

yes, i can't be sure for 7.x ( too many changhes in a small amount of time) but in 6.x it worked.

From same remotes zwave dimmer or switch work perfectly. That's why i think  it's something in the check state of hue lights

[cag014 731]

27 minutes ago, gggizmo said:

yes, i can't be sure for 7.x ( too many changhes in a small amount of time) but in 6.x it worked.

From same remotes zwave dimmer or switch work perfectly. That's why i think  it's something in the check state of hue lights

Fixed...

 

Please login or register to see this attachment.

[gggizmo 6]

1 hour ago, cag014 said:

Fixed...

 

Please login or register to see this attachment.

It works as expected now.

tnx

[cag014 731]

10 hours ago, SmartLifeSystems said:

 

@cag014

 

I think the lastBreached function not working correctly. Prev i used the v6.3.

In the 6.3 this globals was in min.

 

Please login or register to see this link.

 

Could you please post jM line

[SmartLifeSystems 20]

17 minutes ago, cag014 said:

Could you please post jM line

 

 

Yes, of course.

 

{5, "$blank",{onClock=true,timeLoopAct={"&LivingroomMS","setGlobal","?@`livingroomMS`>lastBreached/60?"}}},

[cag014 731]

29 minutes ago, SmartLifeSystems said:

 

 

Yes, of course.

 

{5, "$blank",{onClock=true,timeLoopAct={"&LivingroomMS","setGlobal","?@`livingroomMS`>lastBreached/60?"}}},

Looks new scanning algorithm cause some bugs... lastBreached value is in seconds...

fixed...

By the way if you want to avoid decimal numbers (20.33333) use

"?ceil(@`livingroomMS`>lastBreached/60)?"

Please login or register to see this attachment.

Edited November 12, 2020 by cag014

[SmartLifeSystems 20]

10 minutes ago, cag014 said:

Looks new scanning algorithm cause some bugs...

fixed...

By the way if you want to avoid decimal numbers (20.33333) use

"?ceil(@`livingroomMS`>lastBreached/60)?"

Please login or register to see this attachment.

 

Thank you.

 

But i'am afraid, this code don't working.

 

"?ceil(@`livingroomMS`>lastBreached/60)?"

 

 

Please login or register to see this attachment.

[cag014 731]

3 minutes ago, SmartLifeSystems said:

 

Thank you.

 

But i'am afraid, this code don't working.

 

"?ceil(@`livingroomMS`>lastBreached/60)?"

 

 

Please login or register to see this attachment.

It works... please close the brackets of ceil correctly

?ceil(...)?

you closed the brackets after ? sign...  syntax error

entire calculation must be within question marks ?.....?

Edited November 12, 2020 by cag014

[SmartLifeSystems 20]

7 minutes ago, cag014 said:

It works... please close the brackets of ceil correctly

?ceil(...)?

you closed the brackets after ? sign...  syntax error

entire calculation must be within question marks ?.....?

 

OK. This was my mistake. Working.

Thank you!