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

[Rover 47]

@cag014 Everything O.K.?

[SmartLifeSystems 20]

Hi cag! Is it possible in the new Yubii Home app the push notifications don't working?

Edited February 22, 2024 by SmartLifeSystems

[SmartLifeSystems 20]

On 2/22/2024 at 7:00 PM, SmartLifeSystems said:

Hi cag! Is it possible in the new Yubii Home app the push notifications don't working?

Have somebody this problem?

[Rover 47]

I am really worried about @cag014, the father of All-In-One. His last reaction was on 27 december 2023...

Who knows more?

[bbolgar 5]

Hi!

 

I wanted to create a line, where if the garden gate (Device ID 306) is in opened, opening or closing state for more than 3 mins, it will send an alert. Instead, I have a line, which warns instantly the garden gate gets into any of the state:
 

{3,"306",{state="state==Closing or Opening or Open",trueAct={"Gardengate open for more than 3 mins","sendPush,429","Please check the gate!"}}},

 

Could someone please recommend a fix for my case?

[SmartLifeSystems 20]

Hi cag!

 

I installed the 5.161 beta version and my CPU usage is very high. Have you any idea what is the problem?

 

Have somebody this problem?

 

Thanks!

Please login or register to see this attachment.

 

[cag014 731]

On 8/5/2024 at 6:32 PM, bbolgar said:

Hi!

 

I wanted to create a line, where if the garden gate (Device ID 306) is in opened, opening or closing state for more than 3 mins, it will send an alert. Instead, I have a line, which warns instantly the garden gate gets into any of the state:
 

{3,"306",{state="state==Closing or Opening or Open",trueAct={"Gardengate open for more than 3 mins","sendPush,429","Please check the gate!"}}},

 

Could someone please recommend a fix for my case?

{3,"306",{state="state==Closing or Opening or Open",timeoutAct={"Gardengate open for more than 3 mins","sendPush,429","Please check the gate!"}}},

[cag014 731]

On 8/9/2024 at 5:12 PM, SmartLifeSystems said:

Hi cag!

 

I installed the 5.161 beta version and my CPU usage is very high. Have you any idea what is the problem?

 

Have somebody this problem?

 

Thanks!

No, no problem at all. Do you have any disconnected devices or do you have unexpected delays on commands execution?

Please login or register to see this attachment.

[Rover 47]

Hi @cag014, please tell me what is wrong:

Please login or register to see this spoiler.

 

Edited October 30, 2024 by Rover

[cag014 731]

Currently the range valuated as value > minimum and < maximum. Means the value 10 is not in range of 10~12.

Please change the range to 9~12 and see if it works.

It might be a good idea to include the value in the range like value >= minimum and <= maximum.  What do you think?

[cag014 731]

Have change the range evaluation as mentioned in the previous post at the next release.

value >= min. range and value<= max. range

 

 

[Rover 47]

On 11/1/2024 at 2:05 AM, cag014 said:

Have change the range evaluation as mentioned in the previous post at the next release.

value >= min. range and value<= max. range

 

 

Thanx @cag014

Yes, that is more logical and intuitive!

In this case I want to select a month range (you could also have wanted to select a day range or a year range or an hour range).

Selecting the range october until march the selection could be $month = 10~3, but this is not value >= min. range and value<= max. range.

Here I should like to have value >= min. range and value<= max. range but if min. range > max. range, then value >= min. range OR value<= max. range.

I know that $month != 4~9 is an alternative way to specify this month range.

Edited November 3, 2024 by Rover

[Rover 47]

On 10/31/2024 at 3:20 AM, cag014 said:

Currently the range valuated as value > minimum and < maximum. Means the value 10 is not in range of 10~12.

Please change the range to 9~12 and see if it works.

It might be a good idea to include the value in the range like value >= minimum and <= maximum.  What do you think?

And what is the effective range at the moment for 9~12? Is that 10 until 11 or 10 until 12?

If it is 10 until 11, how to get a range 10 until 12?  Is it month = 9~13?

Edited November 22, 2024 by Rover

[cag014 731]

On 11/22/2024 at 10:58 AM, Rover said:

If it is 10 until 11, how to get a range 10 until 12?  Is it month = 9~13?

Yes, that the solution right now.

Unfortunately, my HC3 is dead, sent to repair

[Pretender 3]

Happy Tuesday Cag014, 
I have similar requirements as magicman, but somehow the 2nd line is not doing what it's supposed to

 

1st line works as intended. When either condition (iHumid or gvAirChange) is true, switch is set to On 

   {0, "&iHumid|&gvAirChange",{lineState={"{&iHumid:value>0}{&gvAirChange:value=true}"},trigAct={"`BrookventSwitchHigh`","turnOn",""}}},

 

2nd line should switch device off if both conditions are true

   {0, "&iHumid|&gvAirChange",{lineState={"{&iHumid:value=0|&gvAirChange:value=false}"},trigAct={"`BrookventSwitchHigh`","turnOff",""}}},
 

Though iHumid is 0 and gvAirChange is false, the switch remains on. What am I missing?

[cag014 731]

On 11/26/2024 at 7:21 PM, Pretender said:

Happy Tuesday Cag014, 
I have similar requirements as magicman, but somehow the 2nd line is not doing what it's supposed to

 

1st line works as intended. When either condition (iHumid or gvAirChange) is true, switch is set to On 

   {0, "&iHumid|&gvAirChange",{lineState={"{&iHumid:value>0}{&gvAirChange:value=true}"},trigAct={"`BrookventSwitchHigh`","turnOn",""}}},

 

2nd line should switch device off if both conditions are true

   {0, "&iHumid|&gvAirChange",{lineState={"{&iHumid:value=0|&gvAirChange:value=false}"},trigAct={"`BrookventSwitchHigh`","turnOff",""}}},
 

Though iHumid is 0 and gvAirChange is false, the switch remains on. What am I missing?

Have tested your 2nd line (using same variable names) and it works fine.

Are you sure that iHumid variable is numeric and gvAirChange has values true/false ?

Anyhow could you please post the debug view

please make sure that debug levels set to 

 dbgInfo =true

dbgFalseState =true 

 

Now we'll see why 2nd line is not executed (I mean the condition will be displayed with current value of each variable)

Edited December 4, 2024 by cag014

[Pretender 3]

Please login or register to see this image.

/monthly_2024_12/image.png.e2edf8dea1856d135cfd5337e2194b6f.png" />

 

I hope this is the information you're asking for, but let me know if not... I hope I put the dbgInfo and dbgFalseState to the right place.  Only additional change I made since I posted the initial line is adding the timeslot 

  {0, "&iHumid|&gvAirChange|`CO2`",{lineState={"{&iHumid:value>0}{&gvAirChange:value=true}{`CO2`:value>800}"},timeSlot="06:00~22:55",trigAct={"`BrookventSwitchHigh`","turnOn",""}}},
 

{0, "&iHumid|&gvAirChange|`CO2`",{lineState={"{&iHumid:value=0|&gvAirChange:value=false|`CO2`:value<=800},dbgInfo=true,dbgFalseState=true"},timeSlot="06:00~22:55",trigAct={"`BrookventSwitchHigh`","turnOff",""}}},

 

 

One other thing I found, but not sure if it matters... for iHummid I added a line 

global4local = {true,gVarName="aosHummid",varArray={iHumid="init:0"}}

 

I tried to do similar for the gvAirChange, but that led to a failure of the script, I assume due to the fact that aosHummid is a Variable (0), but gvAirChange is a predefined Variable (true/false)

global4local = {true,gVarName="gvAirChange",varArray={iAirChange="init:0"}}

[Pretender 3]

Just recognized while letting the script run for a bit... after approx 15 minutes for a moment the high mode is switched off, but within a minute, switched back on... will keep monitoring for a bit longer...

 

[cag014 731]

On 12/4/2024 at 11:20 PM, Pretender said:

One other thing I found, but not sure if it matters... for iHummid I added a line 

global4local = {true,gVarName="aosHummid",varArray={iHumid="init:0"}}

 

I tried to do similar for the gvAirChange, but that led to a failure of the script, I assume due to the fact that aosHummid is a Variable (0), but gvAirChange is a predefined Variable (true/false)

global4local = {true,gVarName="gvAirChange",varArray={iAirChange="init:0"}}

I think you have an issue here.

The gVarName means the global variable to safe your local variables (some kind of container - not a variable for use) 

For example

global4local = {true,gVarName="aosGvar",varArray={iHumid="init:0",gvAirChange="init:true"}}

To use example above please define aosGvar global variable in HC2.

 

Now you can use iHumid and gvAirChange variables in your code.

Please notice that when you restart AOS the iHumid  initialized to 0 and gvAirChange initialized to  true

 

 

[Pretender 3]

Thanks a lot as usual. I assume that this line is building in internal array for variables, but I can't use predefined variables from the Variable Panel, right?
global4local = {true,gVarName="aosGvar",varArray={iHumid="init:0",gvAirChange="init:true"}}

While iHumid is calculated within the script (you helped me earlier with that), gvAirChange should triggered through either of 2 virtual devices which I can use to set the variable from false to true in case I want to start an intense air cleaning in the house (e.g. in the mornings for 30 minutes), or on demand when cooking. After 30 minutes it should be set back to false. 

 

Only alternate solution would be to check the value of a virtual device label, but would like to avoid that, as I would have to check/program 2 different virtual devices.
 

I recognized though that if I try to reference global variables in the AOS script I get issues with other scripts and strange json error messages. After running the FillHomeTable script everything is back to normal.

 

I assume in the AOS script I can't embed global variables through lines like the below at the beginning of the script?

       local iAirChange = fibaro:getGlobal("gvAirChange")

 

Let me know if not well enough described.