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

[cag014 731]

17 hours ago, Benrive said:

Hello,

 

I When this scene is launched, the first part is executed 2 times (I imagine that because pressing once (1 sec) recognizes as 2 times.
Is there any way to prevent this? I've already set the Input 1 in smart implant to 1 sec but I can't go down any longer.

 

I think it could be a bug... please try AOQ v12 ( some improvement on monitoring events engine)

let me know if it helps

 

By the way to add state-delay please use as follow (in line below have added 3 seconds to delay state verification), but first try the new version and let me know if it works as needed

Please login or register to see this code.

 

Please login or register to see this attachment.

[Guest Benrive]

6 hours ago, cag014 said:

I think it could be a bug... please try AOQ v12 ( some improvement on monitoring events engine)

let me know if it helps

 

By the way to add state-delay please use as follow (in line below have added 3 seconds to delay state verification), but first try the new version and let me know if it works as needed

Please login or register to see this code.

 

Please login or register to see this attachment.

 

Helo @cag014.

 

First of all, I thank you for your selfless effort.

I have completely changed the main file that you passed me through and I am sending you the screenshots of what happened.

 

1-. Something that may not matter, but because you know, Now 2 local servers come out, I'll pass you how I see them (Although I don't know if it has to do with the slave).

 

2-. In the version you send it says 11.9 and in the log it says 12. It's nonsense but for your knowledge

 

Please login or register to see this attachment.

 

Regarding the scenes, it recognizes them according to WebEye, but it does not execute them. the screenshots.

 

Jm lines.

Please login or register to see this code.

 

Trace log.

Please login or register to see this image.

/monthly_2022_03/image.png.66f3f18cd539e3027a85ff9d45afadd4.png" />

 

WebEye Log

 

Please login or register to see this attachment.

 

 

Please login or register to see this attachment.

 

 

Regarding the delay, everything perfect. 1 second has been enough

 

Please login or register to see this attachment.

Edited March 3, 2022 by Benrive

[cag014 731]

11 minutes ago, Benrive said:

1-. Something that may not matter, but because you know, Now 2 local servers come out, I'll pass you how I see them (Although I don't know if it has to do with the slave).

According to the screenshot I see only one local server?

 

19 minutes ago, Benrive said:

Regarding the scenes, it recognizes them according to WebEye, but it does not execute them. the screenshots.

 

Jm lines.

Please login or register to see this code.

Are you sure the condition "if {`LuzDPrincipal`:state=false}" is true ?

Just for test remove the condition

[Guest Benrive]

38 minutes ago, cag014 said:

According to the screenshot I see only one local server?

 

Are you sure the condition "if {`LuzDPrincipal`:state=false}" is true ?

Just for test remove the condition

 

We had tried this before, if we remove the condition the line is executed.
We also tried changing State=false to Value=0 , but it's when we add the condition that it doesn't work.

But as I told you, I have this same line for another 5 or 6 lights and it works correctly with the condition.

 

Same lines to do the same in different rooms:

 

Please login or register to see this code.

 

And Trace log.

The first light works without the condition.

And the last 2 lines are from another room that should do the same thing and it works.
The parameters are identical, the only difference is that the one that does not work is linked to the slave.

 

I think it's clear that it has to do with not recognizing the state or value .

 

Please login or register to see this image.

/monthly_2022_03/image.png.9fc806af44a601889ce098cfb01483cd.png" />

 

The properties Of D.Principal.

You can see State , Value , and sceneactivation.

Please login or register to see this code.

Edited March 3, 2022 by Benrive

[cag014 731]

9 minutes ago, Benrive said:

Same lines to do the same in different rooms:

 

Please login or register to see this code.

That's strange - the second line does executed while have same condition as in lines that don't work!!!

Could you post please your user_data file?  

[Guest Benrive]

1 hour ago, cag014 said:

That's strange - the second line does executed while have same condition as in lines that don't work!!!

Could you post please your user_data file?  

Yes, of course

Please login or register to see this attachment.

[cag014 731]

Didn't find in your user_data how and when you turn off the LuzDPrincipal?

I am curious what happens if the current time is between 23:00~08:00 and you press the button and LuzDPrincipal  now set to value=5, the next line (setValue,40) will never work unless somehow the   LuzDPrincipal  has been turned off (As you stated before the lines work only when you changing the values)

Same if  LuzDPrincipal  has been set to 40, the line to setValue,5 won't work either between 23:00~08:00 (unless somehow the lights have been turned OFF)

 

Maybe be better idea to try that:

 

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="23:00~08:00",trueActState={"if {`LuzDPrincipal`:value>10} or {`LuzDPrincipal`:value=false}"},trueAct={"`LuzDPrincipal`","setValue,5"}}},

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="08:01~22:59",trueActState={"if {`LuzDPrincipal`:value<10}"},trueAct={"`LuzDPrincipal`","setValue,40"}}},

Let me know if it works...

 

 

In any case regarding original lines, please change the line per below 

 

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="23:00~08:00",trueActState={"if {`LuzDPrincipal`:state=false}"},trueAct={"`LuzDPrincipal`","setValue,5"}}}, {0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="08:01~22:59",trueActState={"if {`LuzDPrincipal`:value=0}"},trueAct={"`LuzDPrincipal`","setValue,40"}}},

 

Now you'll see in debug window the condition status  (if it fails) and current value of the LuzDPrincipal (state / value) 

Please post that...

 

 

Edited March 4, 2022 by cag014

[Guest Benrive]

7 hours ago, cag014 said:

Didn't find in your user_data how and when you turn off the LuzDPrincipal?

I am curious what happens if the current time is between 23:00~08:00 and you press the button and LuzDPrincipal  now set to value=5, the next line (setValue,40) will never work unless somehow the   LuzDPrincipal  has been turned off (As you stated before the lines work only when you changing the values)

Same if  LuzDPrincipal  has been set to 40, the line to setValue,5 won't work either between 23:00~08:00 (unless somehow the lights have been turned OFF)

 

The lights turn off when manually pressed by the person.
1 Click SceneActivation=16 and one Click again = TurnOff (although it's a bit weird because it should throw sceneactivation=16 again, but really the light turns off and that's what I want to do).

 

It must be like this, until it has been turned off, you must keep the previous intensity, if you turn off to sleep and turn on to go to the bathroom between those hours, you must change the intensity to the minimum.

 

My intention with all of this is that from one hour to another, the intensity of the bedroom lights will be minimal when they are turned on.

This is working correctly in all except my room which is LuzDPrincipal.

 

I do not know if it is the most correct way, but it is something that occurred to me so as not to wake up my wife if I go to the bathroom.

 

7 hours ago, cag014 said:

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="23:00~08:00",trueActState={"if {`LuzDPrincipal`:state=false}"},trueAct={"`LuzDPrincipal`","setValue,5"}}}, {0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="08:01~22:59",trueActState={"if {`LuzDPrincipal`:value=0}"},trueAct={"`LuzDPrincipal`","setValue,40"}}},

 

I have tried this line in 2 different ways, here I detail it ( only timeSlot="08:01~22:59" ),The rank where I am at the moment.

 

Test One Value=0

Please login or register to see this code.

 

It does nothing, this only appears when I press 2 times to increase the intensity to the maximum and when I press again then it executes the action ( no action ).

When I press it turns on and when I press again it turns off, this always works

I can see the trace when the light is on and I press to turn off In both cases Value or Status

 

Please login or register to see this attachment.

 

Test Two State=false

Please login or register to see this code.

 

The same that value=0 

Please login or register to see this attachment.

 

This Its correct, but i dont know because dont work.

trueActstate is false, but the light turn on witch the last value but not 40

 

Please login or register to see this image.

/monthly_2022_03/image.png.44910a569d48df629f6ea27991eaae6a.png" />

Edited March 4, 2022 by Benrive

[cag014 731]

As you can see the lights are ON...  and lines not executed  

Shows value=99 in condition

Please login or register to see this link.

 

 

Shows state=true in condition

Please login or register to see this link.

 

As I said if no one turns lights off the line won't work

 

Didi you try that?

 

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="23:00~08:00",trueActState={"if {`LuzDPrincipal`:value>10} or {`LuzDPrincipal`:value=false}"},trueAct={"`LuzDPrincipal`","setValue,5"}}},

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="08:01~22:59",trueActState={"if {`LuzDPrincipal`:value<10}"},trueAct={"`LuzDPrincipal`","setValue,40"}}},

 

 

 

[Guest Benrive]

1 hour ago, cag014 said:

As you can see the lights are ON...  and lines not executed  

Shows value=99 in condition

Please login or register to see this link.

 

 

Shows state=true in condition

Please login or register to see this link.

 

As I said if no one turns lights off the line won't work

Ok, I understand what you're saying, but when the light is State=false the line doesn't do anything either.

1 hour ago, cag014 said:

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="23:00~08:00",trueActState={"if {`LuzDPrincipal`:value>10} or {`LuzDPrincipal`:value=false}"},trueAct={"`LuzDPrincipal`","setValue,5"}}},

{0,"`LuzDPrincipal`",{state="sceneActivation=16",timeSlot="08:01~22:59",trueActState={"if {`LuzDPrincipal`:value<10}"},trueAct={"`LuzDPrincipal`","setValue,40"}}},

 

This works but doesn't do what I need.
In the second case, it only sets to 40 when it's below 10. But you should set to 40 always.

In the case of wanting to be above 40, I can regulate by holding down or pressing 2 times for value=99.

 

 

Important:

With what you have put, I have learned to use conditions for the action and I have built this.
And it works and does what I was looking for, albeit in a much more complex way.

 

Please login or register to see this code.

 

So I managed to improve what I wanted to do.

 

The part of falseActState sceneActivation=16 is to prevent that when pressing 2 times ( SceneActivation= 14 ), the light is set to value=99 and does not turn off.

 

Please login or register to see this attachment.

 

Scenario 1 Light Off:
Press once turn On and value = 40
press again
Turn Off

END
Scenario 2 Light Off:
Press 2 times
TurnOn and value = 99 ( Set by device parameters , No Jm Line )
press again value= 40
and press again TurnOff

END

Scenario 3 Light ON and value > 40

Press once

set value to 40 

Press Again TurnOff 

END

 

This fixes it, at least I think.
I am very grateful to you, I think this has been to go crazy

 

Thank you very much ?

 

 

Edited March 4, 2022 by Benrive

[cag014 731]

First of all I glad to hear that it works

 

Just curious if you have an example when state=false and the line doesn't work

Your snapshot shows that current state=true (when the condition displayed, the current state of each device shown also, see red arrow below)

Please login or register to see this spoiler.

[Guest Benrive]

On 3/4/2022 at 6:41 PM, cag014 said:

First of all I glad to hear that it works

 

Just curious if you have an example when state=false and the line doesn't work

Your snapshot shows that current state=true (when the condition displayed, the current state of each device shown also, see red arrow below)

Please login or register to see this spoiler.

 

Hello @cag014. ?

 

After trying this morning, since we spent the weekend away, I can say again that it does not work.

The problem is that when the light goes turnOff both State=false and Value=0.

 

because in this line the state will never be fulfilled trueActState.

Before executing the line we have state=false and value = 0 

So the condition is not met trueActState.

But even if I remove the value>5 condition, the condition is not met either.

 

Here you can see an example of when state = false does nothing, it doesn't recognize what it should do.

 

Please login or register to see this image.

/monthly_2022_03/image.png.2c3ff03e88b72b942b059d684f814425.png" />

 

 

Please login or register to see this code.

 

In this situation, I press the button Result : sceneActivation=16 

The light turns on but does not recognize the scene or change the value to = 5

Time it's 08:39 and push the botton 

In trace log nothing is seen, and in webEye it does not recognize that the scene has been executed but it has updated the values.

 

 

Please login or register to see this attachment.

 

If I remove the conditional value>5 , it should work perfectly since all the conditions are met, but the same thing happens.

 

Please login or register to see this code.

 

 

 

When I push the button, the light comes on, the values change but it still doesn't do anything.

 

 

And value = 99

 

[cag014 731]

Could you post the lines in the debug window?

In WebEye the values are not shown immediately (need to refresh the window, but then the values shown are after line execution )

In debug window you can see the current values before command executed.

[Guest Benrive]

1 hour ago, cag014 said:

Could you post the lines in the debug window?

In WebEye the values are not shown immediately (need to refresh the window, but then the values shown are after line execution )

In debug window you can see the current values before command executed.

I have not published them because nothing appears.  it only shows up when i press the trogle button in webeye.

Please login or register to see this image.

/monthly_2022_03/image.png.2a46b7e7edf9b30f6c9afa667b56757f.png" />

Edited March 7, 2022 by Benrive

[cag014 731]

That's all you see on the window? Looks like AOQ doesn't run at all, can you scroll down the debug window

[Guest Benrive]

13 minutes ago, cag014 said:

That's all you see on the window? Looks like AOQ doesn't run at all, can you scroll down the debug window

Yes, 

It can be seen, as the same action in Luz Marina execute actions. We are the same as before, only now to do the same thing we use a much more complex JM line.

Please login or register to see this attachment.

Edited March 7, 2022 by Benrive

[cag014 731]

7 hours ago, Benrive said:

Yes, 

It can be seen, as the same action in Luz Marina execute actions. We are the same as before, only now to do the same thing we use a much more complex JM line.

Please login or register to see this attachment.

As you can see LuzDPrincipal doesn't meet the conditions and looks like everything works as defined.

As you said you need to work on correct conditions.

[Guest Benrive]

13 hours ago, cag014 said:

As you can see LuzDPrincipal doesn't meet the conditions and looks like everything works as defined.

As you said you need to work on correct conditions.

Hello @cag014,

I understand what you are saying, but something is happening here and it is not because of the conditions.
If I keep the line as simple as possible.

trueActstate condition is never executed when actually pressing State=false and condition it'ss true.

I've made the line as simple as possible, but it still recognizes when it's true.

 

Here when i press , and the state is false ( Turn Off the light )it should do the trueact action, but it doesn't do anything.

That's the problem in all of this.

 

On the contrary, if it recognizes the action trueActState if the state = true . Although in that case, it must execute the action FalseAct.

 

Please login or register to see this code.

 

When status=true , but not when status=false

Please login or register to see this attachment.

 

Its may all be because the initial state when state= false is sceneActivation=16 and does not recognize the change of situation.

 

But in the rest of the same devices, if it does. I think I'm going to forget about this for a while and I'll do it with the fibaro scenes that works well as we already saw.

 

Maybe in some update it will suddenly start working

 

The same in other light, Status=false setvalue,5 

 

Please login or register to see this attachment.

Edited March 8, 2022 by Benrive

[cag014 731]

I've went through files of your configuration and I am confused.

LuzDPrincipal with id=327 is a device located on your slave, while LuzMarina with id=96 is the same device located on your master, is it correct?

Since AOQ runs on master you cannot use device IDs of the slave.... it doesn't seen by AOQ.

If my observations are correct, LuzDPrincipal is not a valid device for AOQ. (you probably have some other device ID=327 on your master, otherwise AOQ should fail)

You said the scene works fine, my question is where the scene runs ? on slave or master?

[Guest Benrive]

Hello @cag014,

I have already found the error.
The problem is that the control device for that light `MandoDPrincipal` is the one that must support the scene=16 .
The error comes when you use it in AOI because it says that it doesn't support this property.

 

Please login or register to see this attachment.

 

But if we see the properties of the device, if it supports them.

Please login or register to see this image.

/monthly_2022_03/image.png.5a94630c40109d5ebb8495d0a53b0079.png" />

 

I have reviewed the AOQ Advanced user document several times, until it occurred to me to try adding the + symbol

 

Please login or register to see this code.

 

 

We have already tested this, but adding it to the light device, not to the control.
Well that's how it works.

 

Now what we can see in webeye has more coherence

Please login or register to see this attachment.

We are left with the question.
Why doesn't it recognize the property? I don't know but once it's solved by adding the + symbol it would be solved.

 

Yes, this can be solved at the AOQ level, could you take a look at it, if not . Once I find the problem I will take it into account for the rest of the things that the same thing happens to me.

 

Once again, thank you for your time and dedication.