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

[cag014 731]

17 minutes ago, Rover said:

Differences v3.5 vs v4.0:

 

main titles changed content.

 

v4.0 (not in v3.5):

Please login or register to see this spoiler.

Yes,

1. USER SHORTCUTS options actually came to me from you... how not to rewrite long lines several times, so this section is for table shortcuts.  (see Tricks and Tips) 

2. &HC3onLine now is part of system keyword. (some users mess with that and I use that as part of jM table release)

3. No problem to change it to email... this is a template.

4. I'm using DIY SMS card to keep communication and to operate HC3 and HC2 by sending/receiving messages, so internet off line goes there also. In addition SMS, TTS, and HC3/HC2 are connected to UPS (220v battery) and in case of power outage my system switched totally to SMS mode and battery operated sensors armed. (One of the intruders'' favor part is to cutoff the power)

5. What numbers hardly visible?

 

 

Edited October 6, 2020 by cag014

[Rover 47]

6 minutes ago, cag014 said:

1. USER SHORTCUTS options actually came to me from you... how not to rewrite long lines several times, so this section is for table shortcuts.  (see Tricks and Tips) 

2. &HC3onLine now is part of system keyword. (some users mess with that and I use that as part of jM table release)

3. No problem to change it to email... this is a template.

4. I'm using DIY SMS card to keep communication and to operate HC3 and HC2 by sending/receiveing messages, so internet off line goes there also.

 

In addition SMS, TTS, and HC3/HC2 are connected to UPS (220v battery) and in case of power outage my system switched totally to SMS mode and battery operated sensors armed. (One of the intruders'' favor part is to cutoff the power)

1. USER SHORTCUTS is a very nice feature ?. Only AOQ users who only are updating with a AOQ-mainCode-v4.0.txt are not aware of that option in the main part. Also is the name of the mainCode file disappeared in the .fqa version and changed into main, maybe confusing for some people without instructions...

4. Did you used an Arduino board or somewhat different?

Yes, all my systems are connected to UPS behind a locked door.

 

Solution for hardly visible numbers in dark mode?

[cag014 731]

25 minutes ago, Rover said:

1. USER SHORTCUTS is a very nice feature ?. Only AOQ users who only are updating with a AOQ-mainCode-v4.0.txt are not aware of that option in the main part. Also is the name of the mainCode file disappeared in the .fqa version and changed into main, maybe confusing for some people without instructions...

4. Did you used an Arduino board or somewhat different?

Yes, all my systems are connected to UPS behind a locked door.

 

Solution for hardly visible numbers in dark mode?

I use USR GRPS module and LAN/RS232 converter.

Please login or register to see this link.

 

Please login or register to see this link.

 

I think you can try  a new idea by using old smartphone (with unique email account) connected to local wifi  and in case no internet, to send email to this smartphone and to forward the message to your email account.

 

 

Can you post a snapshot of number hardly visible?

Edited October 7, 2020 by cag014

[gggizmo 6]

cag are you aware that aoq it's not in forum dowload section any more?

[Rover 47]

7 hours ago, cag014 said:

I think you can try  a new idea by using old smartphone (with unique email account) connected to local wifi  and in case no internet, to send email to this smartphone and to forward the message to your email account.

Super idea! Maybe it is not necessary to use an old old smartphone and is my (not so new) iPhone capable of sending an e-mail in case of switching from WiFi to 4G? But how to implement this?

 

Hardly visible numbers snapshot:

Please login or register to see this spoiler.

 

[Rover 47]

18 hours ago, Rover said:

Please login or register to see this spoiler.

Good morning cag,

Can you help me?

[gggizmo 6]

1 minute ago, Rover said:

Good morning cag,

Can you help me?

Why do you want to poll light level?

If you use light sensor as trigger in a specific time slot, every time light level change and is < than low light value you choose, the state will be set.

Am i wrong or there's something i'm missing?

[SmartLifeSystems 20]

13 hours ago, cag014 said:

Bu using block scenes with the same combination works fine? 

Plaease try again Lua scene, but this time use users ID.

fibaro.alert("push",{id,id}, "test")

 

So, the Block and Lua combinations working fine.

Thanks your help!

[Rover 47]

5 minutes ago, gggizmo said:

Why do you want to poll light level?

If you use light sensor as trigger in a specific time slot, every time light level change and is < than low light value you choose, the state will be set.

Am i wrong or there's something i'm missing?

Indeed gggizmo, maybe I have looked in the wrong direction by tunnel vision...

[Rover 47]

2 hours ago, Rover said:

Indeed gggizmo, maybe I have looked in the wrong direction by tunnel vision...

 

But when does this line trigger?

Please login or register to see this spoiler.

 

[gggizmo 6]

1 minute ago, Rover said:

 

But when does this line trigger?

Please login or register to see this spoiler.

at every lux variation if value <20 trueact will be executed.

 

[Rover 47]

2 hours ago, gggizmo said:

at every lux variation if value <20 trueact will be executed.

 

I have changed the value<20 to value<80: many changes in lux but only one trigger in two hours, why?

[cag014 731]

5 hours ago, Rover said:

Super idea! Maybe it is not necessary to use an old old smartphone and is my (not so new) iPhone capable of sending an e-mail in case of switching from WiFi to 4G? But how to implement this?

 

Hardly visible numbers snapshot:

Please login or register to see this spoiler.

 This is Fibaro's dark theme and not part of the code. Same could be seen in scenes.

[Rover 47]

39 minutes ago, Rover said:

I have changed the value<20 to value<80: many changes in lux but only one trigger in two hours, why?

I see that I have to change somewhat in the device settings of the PIR.

[cag014 731]

5 hours ago, Rover said:

Super idea! Maybe it is not necessary to use an old old smartphone and is my (not so new) iPhone capable of sending an e-mail in case of switching from WiFi to 4G? But how to implement this?

 

Hardly visible numbers snapshot:

Please login or register to see this spoiler.

Yes, the implementation is the tricky part, you need to receive email on WiFi and send it on cellular... phone setup doesn't have that by default

[gggizmo 6]

41 minutes ago, Rover said:

I see that I have to change somewhat in the device settings of the PIR.

Please can you share infos about pir device and post debug screen?

I use a similar line and it' works as expected. My line it's temp triggered but i think it's same concept

[cag014 731]

2 hours ago, Rover said:

I have changed the value<20 to value<80: many changes in lux but only one trigger in two hours, why?

Guys, the trigger works when Lux value cause the status change, only

If lux value below <80 for the first time (was above) the trueAct triggered. If further reports are below 80 as well, nothing triggered.

Next trigger will be only when lux value will be above 80.

The line triggered only on status change....

Do you need to trigger the line on every LUX  change ?

Edited October 7, 2020 by cag014

[gggizmo 6]

25 minutes ago, cag014 said:

Guys, the trigger works when Lux value cause the status change, only

If lux value below <80 for the first time (was above) the trueAct triggered. If further reports are below 80 as well, nothing triggered.

Next trigger will be only when lux value will be above 80.

The line triggered only on status change....

Do you need to trigger the line on every LUX  change ?

And againg i'm missing something:

{0,"`tlab`",{state="value>25",lineState={"{&cooling:value=true}"},trueAct={{"`climamod`","setMode,2",""},{"`climafan`","setFanMode,4",""},{"`climaset`","setThermostatSetpoint,2,24",""}}}},

 

i have this line and it's triggered at every temp report if temp is >25. I can hear the usual beep command sent to air conditioner...

ex: if in first 30,min temp go from 27 to 26 line is triggered again and command is sent again 

 

In aos and first version of aoq...now i have disabled this line

Edited October 7, 2020 by gggizmo

[cag014 731]

7 hours ago, Rover said:

Please login or register to see this link.

On 10/6/2020 at 4:17 PM,

Please login or register to see this link.

said:

Please login or register to see this spoiler.

It  will never work

{30, "&clock",{state="value=$value",onClock=true,lineState={"{&Lichten=Uit}|{$hour>14}|{$hour<23}"},timeLoopAct={"&Lichten","setGlobal","Aan","{`LichtHuiskamer`:value<20}"}}},

Too many errors....

lineState format should be the same as condititons.

$value is the value of the line, in this cas will be always activated.

Why you need to set global variable, just use LUX conditions in line you need it.

Please post the line where LUX value required

As I mentioned, based on mine expirience try to avoid as much as psiible of variables usage. In the future it's very hard and confusin to follow the logic of the line

Edited October 7, 2020 by cag014

[cag014 731]

8 minutes ago, gggizmo said:

And againg i'm missing something:

{0,"`tlab`",{state="value>25",lineState={"{&cooling:value=true}"},trueAct={{"`climamod`","setMode,2",""},{"`climafan`","setFanMode,4",""},{"`climaset`","setThermostatSetpoint,2,24",""}}}},

 

i have this line and it's triggered at every temp report if temp is >25. I can hear the usual beep command sent to air conditioner...

In aos and first version of aoq...now i have disabled this line

Are you sure? Have tested that and it triggered only when state is changed. Not every value above 25