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

[cag014 628]

3 hours ago, Rover said:

 What do you mean with point 2: too many commas and curly brackets (not the correct order):

- The number of curly brackets is OK

- The order is correct

- What about too many commas? I am using the commas the make clear what the end is of f.i. trueAct section. The commas do not make trouble, your parsing is fine!

 

You are correct, I just use not to set the commas... sorry my bad. The format is correct.

[Rover 45]

Please login or register to see this spoiler.

It looks like the debug screen is still in wintertime...

[cag014 628]

7 hours ago, Rover said:

Please login or register to see this spoiler.

Time stamp displayed by the system... may be you need to reconfigure the date in HC3.

[Rover 45]

59 minutes ago, cag014 said:

Time stamp displayed by the system... may be you need to reconfigure the date in HC3.

Yes, that was the solution! Changing from [2h] Europe/Warsaw to [2h] Europe/Amsterdam did the job (both in same time zone ?‍♂️).

Strange that the time in the setting/general screen was correct before the reconfiguration...

[hellower 3]

Is it possible to mix AND and OR in the Params_4 section?

I want to use this construction on many commands:
 

Please login or register to see this code.

 

I mean: if (BackBalconyLux < 2000 and YardMainDoorLux < 2000 and day) or night then...

But it's not works and seems parsed not correctly

 

 

Please login or register to see this attachment.

[cag014 628]

3 hours ago, hellower said:

Is it possible to mix AND and OR in the Params_4 section?

I want to use this construction on many commands:
 

Please login or register to see this code.

 

I mean: if (BackBalconyLux < 2000 and YardMainDoorLux < 2000 and day) or night then...

But it's not works and seems parsed not correctly

 

 

Please login or register to see this attachment.

Yes of course

for example (using your statement correctly - assuming day and night are global variables)

" if {BackBalconyLux:value < 2000 and YardMainDoorLux:value < 2000 and &day:value=true} or {&nigh:value=false}"

In general all conditions in curly brackets means "and",  while "or" uses between the brackets

Like below

Two formats are supported (any combination in between supported as well)

1.       [if]{cond1 and cond2 and ….} or {cond1 and cond1 and ….} or..  - human readable

2.       {cond1|cond2|…}{cond4|cond5|….}{..} - short format

 

for more info please download Advance User's Guide  and refer to Conditional Parameters section in the document.

Edited April 12, 2021 by cag014

[hellower 3]

19 minutes ago, cag014 said:

Yes of course

for example (using your statement correctly - assuming day and night are global variables)

" if {BackBalconyLux:value < 2000 and YardMainDoorLux:value < 2000 and &day:value=true} or {&nigh:value=false}"

In general all conditions in curly brackets means "and",  while "or" uses between the brackets

Like below

Two formats are supported (any combination in between supported as well)

1.       [if]{cond1 and cond2 and ….} or {cond1 and cond1 and ….} or..  - human readable

2.       {cond1|cond2|…}{cond4|cond5|….}{..} - short format

 

for more info please download Advance User's Guide  and refer to Conditional Parameters section in the document.

 

Thank you, it works! But only in the human readable format

 

Please login or register to see this attachment.

[hellower 3]

But here is another mystic, both conditions return false in 22:29 (i suppose from 21:06) but should return true:

{$24clock:value<>?$sunriseHour+7200?~?$sunsetHour+3600?}

Please login or register to see this attachment.

 

{$24clock:value=?$sunsetHour+3600?~?$sunriseHour+7200?}

Please login or register to see this attachment.

 

Full part:

Please login or register to see this code.

 

How to fix this?

[cag014 628]

2 hours ago, hellower said:

But here is another mystic, both conditions return false in 22:29 (i suppose from 21:06) but should return true:

{$24clock:value<>?$sunriseHour+7200?~?$sunsetHour+3600?}

Please login or register to see this attachment.

 

{$24clock:value=?$sunsetHour+3600?~?$sunriseHour+7200?}

Please login or register to see this attachment.

 

Full part:

Please login or register to see this code.

 

How to fix this?

Oops... thanks for finding the bug. It was fixed in AOQ (HC3/HC3l).

Please copy/paste attached version 7.1

In order to keep your configuration please copy from the line

--======================Copy form here for updates=============================================================================

to the end of your scene.

Didn't find any problem with standard conditional format vs human format. Let me know what exactly the problem.

In addition in this new version any action table (trueAct{}, falseAct{} and others) could have specific conditions. Please refer to attached Advanced User's Guide (Conditional parameters section)

 

Also will release the new version shortly...

Please login or register to see this attachment.

Please login or register to see this attachment.

Edited April 12, 2021 by cag014

[hellower 3]

Thanks for the fix, I'll try it later.

 

Quote

Didn't find any problem with standard conditional format vs human format. Let me know what exactly the problem.

 

AOS log don't recognise these brackets with standard format:

Please login or register to see this image.

/monthly_2021_04/1760443332_2021-04-1210_44_15.png.bc37df27dc1c0c4fd3691dfeb65cf6b8.png.442af96bd37d479dcb5d43afdbee2d93.png" />

 

For this code:

Please login or register to see this code.

 

[cag014 628]

12 hours ago, hellower said:

Thanks for the fix, I'll try it later.

 

 

AOS log don't recognise these brackets with standard format:

Please login or register to see this link.

 

For this code:

Please login or register to see this code.

 

Now I can see that... there is no need for double brackets as this is not an array just formatted string

"{`BackBalconyLux`:value < 2000|`YardMainDoorLux`:value < 2000|$24clock:value=?$sunriseHour+7200?~?$sunsetHour+3600?} {$24clock:value=?$sunsetHour+3600?~?$sunriseHour+7200?}"

Edited April 13, 2021 by cag014

[Sjakie 135]

Gag,

you fixed my Logitec hub in HC2

Regretly it does not work in HC3

fibaro.call(829, "changeActivityState")

[cag014 628]

4 hours ago, Sjakie said:

Gag,

you fixed my Logitec hub in HC2

Regretly it does not work in HC3

fibaro.call(829, "changeActivityState")

My Logitech still connected to HC2, can you post the Logitech device API on HC3? Let's see maybe they have changed the commands...

[Sjakie 135]

Thanks, in HC3  I cant open it.

In HC3 I download it as QA plugin.

The device has no option to save as fqa

//Sjakie

[cag014 628]

But when you have connected to the Logitech, is it created some Childs?

If so please post theirs APIs

Edited April 15, 2021 by cag014

[jgab 1,954]

21 hours ago, Sjakie said:

Gag,

you fixed my Logitec hub in HC2

Regretly it does not work in HC3

fibaro.call(829, "changeActivityState")

If you try?

Please login or register to see this code.

 

[Sjakie 135]

I tried >>nothing

also with stop, start, play, go

//Sjakie

yes it created Childs

Cag how to find API? I can not open any Child or HUb main

 

 

Hub connected

Hub online

 

[Sjakie 135]

Please login or register to see this code.

 

[Sjakie 135]

I deleted Harmony plugin

reinstalled Harmony plugin

modified HT

Test

Nothing

 

//Sjakie

[Sjakie 135]

Please login or register to see this code.

//sjakie

nothing happens