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

[cag014 731]

3 minutes ago, silvinnio said:

This is a motion sensor, but I have already modified this line because, when the trueAct was executed and the light was On, the light was changing the lux value over the threshold and the turnOff action was no longer executed, getting the message that the turnOff command skipped.  See the modified line below.

 

{0,"`motionsensor`",{state="value=true",trueAct={{"`lightswitch`","turnOn","{`lightsensor`:value <80}"},{"`lightswitch`","turnOff","10","{`lightswitch`:state=true}"}}}},

Just a thought...

I am wondering why you turn off the lights after 10 seconds? I mean if someone still in the area the light will go OFF in 10 seconds and this someone will find himself in the dark.

Just use the sensor status to turn it Off

{0,"`motionsensor`",{state="true",trueAct={"`lightswitch`","turnOn","{`lightsensor`:value <80}"}, falseAct={"`lightswitch`","turnOff","10","{`lightswitch`:state=true}"}}},

 

 

[silvinnio 6]

@cag014

 

I was so, so close to sell my HC2 and HC3 units and switch to a more user-friendly programming (H Pro) but now, because of you 😊, I'll give one more chance to Fibaro 😁.

 

Edited December 19, 2024 by silvinnio

[silvinnio 6]

What I have seen in my line is that if there is another movement within 10 seconds, the line is true again and then resets the turnOff timer.

This is the light for the stairs and no need to be more than that time, but that's not a problem.

 

How does it work you QA in this case?

 

For example in this line:

{0,"`motionsensor`",{state="value=true",trueAct={{"`lightswitch`","turnOn","{`lightsensor:value <80}"},{"`lightswitch`","turnOff","600","{`lightswitch`:state=true}"}}}},

 

or your line :

 

{0,"`motionsensor`",{state="true",trueAct={"`lightswitch`","turnOn","{`lightsensor`:value <80}"}, falseAct={"`lightswitch`","turnOff","600","{`lightswitch`:state=true}"}}},

 

If by some reason the QA restarted and just before that, there was a movement and turned on the light,  after QA restarted it remembers that needs to tunOff the light after the remaining time?
 

 

 

[cag014 731]

2 minutes ago, silvinnio said:

What I have seen in my line is that if there is another movement within 10 seconds, the line is true again and then resets the turnOff timer.

This is the light for the stairs and no need to be more than that time, but that's not a problem.

That's correct, in case the sensor goes to safe/false and then back to breached/true again the line will be restarted.

But if someone continuously moves more than 10 seconds (no state changes) the light will go off. 

It's up to you how to set that.

 

[silvinnio 6]

7 hours ago, cag014 said:

But if someone continuously moves more than 10 seconds (no state changes) the light will go off. 

Hmmmm, I did not think of that.

I'll modify that.

Thanks. 😊

 

 

 

 

Edited December 20, 2024 by silvinnio

[cag014 731]

Just now, silvinnio said:

About my other question, is there something wrong with my QA?

No, the crashes cause by the code in homeTts function, but we fixed that,

 

23 minutes ago, silvinnio said:

If by some reason the QA restarted and just before that, there was a movement and turned on the light,  after QA restarted it remembers that needs to tunOff the light after the remaining time?

No, when QA restarted it initialize the lines by the defined state, so in case QA restarted and the sensor is false (but the lights are ON) it will stay ON.

While using falseAct, when QA restarted it will turn the lights off after defined delay.

[Rover 47]

Hi @cag014,

This is the first post on this topic this year, somewhat quiet here...

 

I have received a Smart Home Forum e-mail with the announcement of AOQ v20.6.

My actual version is 17.9 and I was not aware of the new versions in between. Is it possible to announce future new versions on this forum topic?

It might also a good idea to add the latest AOQ version to the AOQ initialization screen, like it has been done for the newest HC3 OS versions.

 

Is AOS v9.6 based on v.4.560 still the newest one?

[Rover 47]

Hi @cag014,

Update AOQ v17.9 to AOQ v20.6 delivers:

Please login or register to see this spoiler.

 

[cag014 731]

Oops, my bad

Please download v20.7

 

In addition, please follow the instructions for previous versions releases.

A lot of things changed. See Advanced user guide also

Edited September 20, 2025 by cag014

[cag014 731]

10 hours ago, Rover said:

Is AOS v9.6 based on v.4.560 still the newest one?

Yes

[Rover 47]

In v20.7:

Please login or register to see this spoiler.

If I change the last "and" by "|" then (only) this line is accepted.

Edited September 22, 2025 by Rover

[cag014 731]

Are you sure you're using v20.7?

I am unable to regenerate same error, but I see you're using in last command

"if {&Huisstatus=Thuis and $24clock:value>01:58}" and not "if {&Huisstatus:value=Thuis and $24clock:value>01:58}"

In version 20.7  the :value suffix was deprecated for all devices/variables. So using if {&Huisstatus=Thuis ...} should indeed be valid without needing :value.

✅ In v20.7:

• if {&Huisstatus=Thuis} → Correct
• if {&Huisstatus:value=Thuis} → Still valid, but redundant

🚫 In earlier versions:

• if {&Huisstatus=Thuis} → Fail
• if {&Huisstatus:value=Thuis} → Required for proper evaluation

So if the error only appears when using the syntax without :value, it’s likely that the environment isn’t actually running v20.7—or the update didn’t propagate correctly.

I suggest first of all add ":value" to the last if statement. If it works, then looks like it's not v20.7

Try to update AOQ main again to v20.7

[Rover 47]

Yes, I am sure using v20.7:

Please login or register to see this spoiler.

Like I mentioned, the problem is not the ":value" but de development of the "and". If I change the last "and" by "|" then (only) this line is accepted and another line causes a crash of the same type.

 

By the way:

 

🚫 In earlier versions:

• if {&Huisstatus=Thuis} → Fail        → Is not failing in earlier versions, I have used it more then 100 times
• if {&Huisstatus:value=Thuis} → Required for proper evaluation    → Still valid, but redundant

 

[cag014 731]

I think have found the problem.... 

Please try 

Please login or register to see this attachment.

 

Edited September 25, 2025 by cag014

[Rover 47]

10 hours ago, cag014 said:

I think have found the problem.... 

Please try 

Please login or register to see this attachment.

 

[25.09.2025] [14:10:50] [DEBUG] [AOQ386]: AOQ is up and running ...

👏

[Rover 47]

[25.09.2025] [14:15:55] [TRACE] [AOQ387]: QuickApp: 503,504,505,666,687,730,731,732,733,734,735,736,737,738,739,740,741,742,743,744,745,746,747,748,749,750,751,752,753,754,775,776,777,778,779,780,781,782,783,784,785,786,787,788,789,790,791,792,793,794,795,796,797,847,848,849,850,851,852,853,854,855,856,857,858,859,860,861,862,864,865,866,867,868,869,870,871,872,873,874,875,876,877,878,881,882,883, encrypted. Add `+` sign before actions e.g trueAct={"QA-ID","+action[,arg1,arg2..]"}

 

What does this mean?

[cag014 731]

That's strange... it means that all those QAs are encrypted, is it correct?

AOQ cannot degeminate what commands available, so add + sign before command

looks like too many !?

Edited September 25, 2025 by cag014

[Rover 47]

17 minutes ago, cag014 said:

That's strange... it means that all those QAs are encrypted, is it correct?

AOQ cannot degeminate what commands available, so add + sign before command

looks like too many !?

Yes, this is correct. Most of them are childs of encrypted parents. Most of them have not been called by a command, but are information childs for the dashboard.

What is the aim of this message? Should I change something?

Edited September 25, 2025 by Rover

[Rover 47]

{"&tChangeScene","setGlobal","Arm timerArm,600","if {&tVertraagdWeg=Ja}"},

The timer in this line does not function in AOS, but is accepted by AOS.

Wat do I wrong?

[cag014 731]

No.

As I mentioned, this is a reminder that AOQ cannot verify the commands of these QAs, so any command sent to them should be started with "+" sign and verification of proper actions is on you😀