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

[cag014 731]

46 minutes ago, Rover said:

{0,"`VoordeurSwitch`",{lineState={" if {`VoordeurSwitch`:sceneActivation=`But3Release`}"},

initOnStartup=false,state="sceneActivation=11~45",trueAct={

    {"VoordeurSwitch-%HC3","sendEmail,2","Disarm"}}}}

 

I am not sending emails from But3Hold, but I want to send email only if lineState condition is true, that means only if But3Release and not if But3Hold.

The hold and release events received on same time and as you can see one of the sendEmail occurs while value is Bu3Hold. The reason that when value updated and checked again in lineState it's already changed to Bu3Release. (and executed two times)

Two options:

1. Keep to hold the button little longer... to create a slight delay between hold and release.

2. Why you're using lineState here? The usage for lineState is more correct to screen few buttons in one line. In this case it's straightforward line

{0,"`VoordeurSwitch`",{state="sceneActivation=But3Release",trueAct={

    {"VoordeurSwitch-%HC3","sendEmail,2","Disarm"}}}}

[Rover 47]

37 minutes ago, cag014 said:

2. Why you're using lineState here? The usage for lineState is more correct to screen few buttons in one line. In this case it's straightforward line

{0,"`VoordeurSwitch`",{state="sceneActivation=But3Release",trueAct={

    {"VoordeurSwitch-%HC3","sendEmail,2","Disarm"}}}}

It is your own advice of october 4th:

@Rover

On second thought, that option already exists

{0,"`VoordeurSwitch`",{lineState={" if {`VoordeurSwitch`:sceneActivation=33} or {`VoordeurSwitch`:sceneActivation=35},

initOnStartup=false,state="sceneActivation=30~40",trueAct={....

 

My goal is to combine push 1x and button hold: 

{0,"`VoordeurSwitch`",{lineState={" if {`VoordeurSwitch`:sceneActivation=`But1Single`} or {`VoordeurSwitch`:sceneActivation=`But1Release`}"},

state="sceneActivation=11~45",trueAct={

Edited October 24, 2020 by Rover

[cag014 731]

11 minutes ago, Rover said:

It is your own advice of october 4th:

@Rover

On second thought, that option already exists

{0,"`VoordeurSwitch`",{lineState={" if {`VoordeurSwitch`:sceneActivation=33} or {`VoordeurSwitch`:sceneActivation=35},

initOnStartup=false,state="sceneActivation=30~40",trueAct={....

 

My goal is to combine push 1x and button hold: 

{0,"`VoordeurSwitch`",{lineState={" if {`VoordeurSwitch`:sceneActivation=`But1Single`} or {`VoordeurSwitch`:sceneActivation=`But1Release`}"},

state="sceneActivation=11~45",trueAct={

OK, if you intend to combine few lines. But as I see But[x]Release  is a problematic event and might be better idea to have all But[x]Release as a different line

[Rover 47]

23 hours ago, Rover said:

Please login or register to see this spoiler.

OK

Edited October 24, 2020 by Rover

[cag014 731]

18 minutes ago, Rover said:

On 10/24/2020 at 2:30 AM, Rover said:

Please login or register to see this spoiler.

I'm a little bit lost here...

What you mean by "10+30+.... ", if it's calculation it should be within question marks "?10+30+...?" . all of them .

Now what is it Uit? Is it parameter? it should be `Uit`...

 

• Quote

[Rover 47]

29 minutes ago, cag014 said:

I'm a little bit lost here...

What you mean by "10+30+.... ", if it's calculation it should be within question marks "?10+30+...?" . all of them .

Now what is it Uit? Is it parameter? it should be `Uit`...

 

What you mean by "10+30+.... ", if it's calculation it should be within question marks "?10+30+...?" . all of them .

      Yes it should be a calculation, so between ? ?.

No, Uit is nothing but a value of a GV, but in the initiation list and in hcWebEye it is in the list of GV's while the real GV &Alarmstatus is not at all to be seen in the lists.

 

Please login or register to see this spoiler.

 

Edited October 25, 2020 by Rover

[Rover 47]

hcWebEye Toggle does not refresh, only after editing the AOQ lines hcWebEye shows the contents for a while.

[Rover 47]

I Toggle hcWebEye, and.....: got an email from Fibaro: 

Please login or register to see this spoiler.

 

[Rover 47]

webEye

Please login or register to see this spoiler.

 

[cag014 731]

11 hours ago, Rover said:

What you mean by "10+30+.... ", if it's calculation it should be within question marks "?10+30+...?" . all of them .

      Yes it should be a calculation, so between ? ?.

No, Uit is nothing but a value of a GV, but in the initiation list and in hcWebEye it is in the list of GV's while the real GV &Alarmstatus is not at all to be seen in the lists.

 

Please login or register to see this spoiler.

What do you mean doesn't refresh?  What indication you're looking for refresh?

[cag014 731]

@Rover  in order to speed up keyfob actions please try to use key-fob emulation for sceneACtivation. (does not support centralSceneSupport).

Looks like even But[x]Release works much better

 

Please login or register to see this attachment.

To all

As I recommended to avoid using slave device as a main item in jM line or using their values directly in conditions, because that slows down the AOQ. (Average API:GET takes ~90mSec. If you have for example 30 items it creates delay of 3 seconds (due to value scanning and retrieve).

The best option is to use emulation for main items. The "slave" idea is to control devices (like turn ON/OFF, set value and etc..)

Edited October 25, 2020 by cag014

[cag014 731]

@Rover

I'm trying to understand regarding error in &Alarmstatus...

By looking on the hcWebEye table it shows like &Alarmstatus'hc2, from other hand you're using &Alarmstatus in the line without hc2 suffix.

Could you please provide more info on this GV?

[cag014 731]

4 hours ago, Rover said:

I Toggle hcWebEye, and.....: got an email from Fibaro: 

Please login or register to see this spoiler.

Could be AOQ sends too many emails?

[Rover 47]

1 hour ago, cag014 said:

any GV must use prefix &. so please change to &Uit

Uit is no GV but a value, like 

{0,"&Alarmstatus",{initOnStartup=false,state="value<>Warning",lineState={"if {&AlarmGeluid:value<>Uit and &Alarmstatus:value<>Uit}"},trueAct={ 

Have a look at the webEye picture above: the two Uit "GV's" (so not real GV's) are coloured green and red.

There should be &Alarmstatus in the list and no Uit!

[cag014 731]

2 minutes ago, Rover said:

Uit is no GV but a value, like 

{0,"&Alarmstatus",{initOnStartup=false,state="value<>Warning",lineState={"if {&AlarmGeluid:value<>Uit and &Alarmstatus:value<>Uit}"},trueAct={ 

Have a look at the webEye picture above: the two Uit "GV's" (so not real GV's) are coloured green and red.

There should be &Alarmstatus in the list and no Uit!

Where &Alarmstatus defined? I mean it is GV of what? HC2, HC3 or QA?

Edited October 25, 2020 by cag014

[Rover 47]

2 hours ago, cag014 said:

What it is? never saw that message!

It is a email from Fibaro: 

Please login or register to see this spoiler.

And no, I do not sent many email from AOQ.

[Rover 47]

16 minutes ago, cag014 said:

Where &Alarmstatus defined? I mean it is GV of what? HC2, HC3 or QA?

Please login or register to see this spoiler.

HC3.

There is also &Alarmstatus'hc2.

 

Edited October 25, 2020 by Rover

[cag014 731]

4 minutes ago, Rover said:

Please login or register to see this spoiler.

Could you please post user_data with jM lines? I will copy these lines and to see what went wrong.

[Rover 47]

9 minutes ago, cag014 said:

Could you please post user_data with jM lines? I will copy these lines and to see what went wrong.

 

Please login or register to see this attachment.

[Rover 47]

2 hours ago, cag014 said:

What do you mean doesn't refresh?  What indication you're looking for refresh?

In webEye I want to see the details in Do Manual refresh for details when you hover to a line showing a yellow rectangle.

After editing jM you are able to see these details for a short time in webEye. When they are not visible I should like to refresh the content of the yellow rectangle by Reload or Toggle or whatever what, but both has no effect on this.