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

[cag014 731]

36 minutes ago, Rover said:

 

 

"the value format is @[ID]>[property]" definition is not to be find in any AOS or AOQ guide. Maybe an addition for the future?

BTW thanks for this information, it has helped ?

It is in document, but probably not highlighted enough 

Please login or register to see this spoiler.

 

[cag014 731]

44 minutes ago, Rover said:

See error picture: alias LinksBoekenkast not found.

Please login or register to see this attachment.

so the issue you are trying to use 3-deep nesting....!

 AlleLichten="`Huiskamer`|`Librije`|`Keukenlamp`|`Bijkeuken`|`LampHal`|`RaamGloriaLamp`|`Achtertuin`|`ZonneschermLicht`|`TuinFlood`",

where Librije nested as well...

 LinksBoekenkast=102, BoekenkastRechts=241, BovenraamLibrije=62, Librije="`LinksBoekenkast`|`BoekenkastRechts`",

Will try to include let's 5-deep nesting option...

[Rover 47]

1 hour ago, cag014 said:

It is in document, but probably not highlighted enough 

Please login or register to see this spoiler.

O.K. I see this (AOQ Quick Guide), but nothing about this in the AOS Advanced User's Guide 3.1 ?‍♂️

[Rover 47]

1 hour ago, cag014 said:

so the issue you are trying to use 3-deep nesting....!

 AlleLichten="`Huiskamer`|`Librije`|`Keukenlamp`|`Bijkeuken`|`LampHal`|`RaamGloriaLamp`|`Achtertuin`|`ZonneschermLicht`|`TuinFlood`",

where Librije nested as well...

 LinksBoekenkast=102, BoekenkastRechts=241, BovenraamLibrije=62, Librije="`LinksBoekenkast`|`BoekenkastRechts`",

Will try to include let's 5-deep nesting option...

If you define the alias  LinksBoekenkast=102 as 1-deep nesting, then Librije="`LinksBoekenkast`|`BoekenkastRechts`", is 2-deep nesting and AlleLichten="`Huiskamer`|`Librije` is 3-deep nesting ?

[Rover 47]

In HC2 I have a scene that lits a light, waits 1 hour and unlit the light. This scene is converted now to AOS.

Within that hour I could put the light out by means of another scene and Killscene the first scene with the waiting period.

What is the equivalent of Killscene in order to kill an AOS-line?

AOS 3.1 failed at Wed Aug 26 17:31:48 2020 last debug message:

/opt/fibaro/scenes/431.lua;413: attempt to index a nil value

?‍♂️

[cag014 731]

1. Currently you cannot "kill" AOS line, but you can set different timeSlot within AOS and this is same as "killing" the line. Set timeSlot to "20:00~20.01"
2. But following your example I don't see any need to kill the line, or I didn't understand the scenario.
3. What you tried to do and receive that error?

 

[cag014 731]

40 minutes ago, Rover said:

O.K. I see this (AOQ Quick Guide), but nothing about this in the AOS Advanced User's Guide 3.1 ?‍♂️

I probably need somehow to highlight this option in both documents... any idea?

Please login or register to see this spoiler.

 

[Rover 47]

7 minutes ago, cag014 said:

1. Currently you cannot "kill" AOS line, but you can set different timeSlot within AOS and this is same as "killing" the line. Set timeSlot to "20:00~20.01"
2. But following your example I don't see any need to kill the line, or I didn't understand the scenario.
3. What you tried to do and receive that error?

 

 

1+2. To be more precise about the scenario:

The hal  dimmer lights are automatically controlled by a Fibaro PIR. With the dimmer wall switch the hal lights can be switched off (and on). With wall switch Up 1x pressed a scene is started that put the hal dimmer lights on for 99% for 1 hour, after that hour the hal lights are switched off and controlled further by the PIR. The wall switch Down 1x pressed scene puts the lights of and kill the scene with the 1 hour program and the lights are controlled further by the PIR. That is converted to AOS now, just without the "killing".

So it is not about killing by programming AOS, but dynamical.

 

3. If I remember well, it was in developing:

--Licht Hal Manueel
{0,"`DimmerHal`",{state="sceneActivation=10",
      -- 1x op Omhoog klikken
      trueAct={ {"&ConstantHalLicht","setGlobal","1"},{"`DimmerHal`","setValue,99",""},{"`DimmerHal`","turnOff","60*60",false},{"&ConstantHalLicht","setGlobal","0"},{"Dimmerlicht","sendEmail[2]","SceneActivation 10: 1x op Omhoog klikken"} } }},
{0,"`DimmerHal`",{state="sceneActivation=11",
      -- 1x op Omlaag klikken
      trueAct={ {"&ConstantHalLicht","setGlobal","0"},{"`DimmerHal`","turnOff","",false},{"Dimmerlicht","sendEmail[2]","SceneActivation 11: 1x op Omlaag klikken"} } }},

[Rover 47]

26 minutes ago, cag014 said:

I probably need somehow to highlight this option in both documents... any idea?

Please login or register to see this spoiler.

You learned me:

     Now to get value of any item in the system (device/global/) please use value format and not conditional format.

     the value format is @[ID]>[property].

     in your case

     "&DimlevelOverdag","setGlobal","@`DimmerHal`>value"

The difference between value format @[ID]>[property] and conditional format [ID]:[property]  should be elaborated, with examples.

In despite of reading your (fine) guides several times, I could not comprehend the existence of a value format and a conditional format.

[Rover 47]

Now I am a little bit on my way of converting as much HC2 scenes as possible to AOS, in order to facilitate the migration to HC3.

I have started with all scenes about lighting. The question is which type of scenes are suitable for converting to AOS.

Some scenes seem to complicated to convert, f.i. the scene checking of all doors and windows have been locked producing messages about which ones are still unlocked. May be a set of HC2 scenes can better be converted to HC3 scenes than converted to AOS (AOQ).

Also I am puzzled about the alarm system concept. HC3 knows zones, and AOQ has Alarm Control, but AOS has not. How to convert alarm control inHC2 to AOS without the alarm zone concept en AOQ Alarm Control?

In general: how to convert/implement as much as possible in AOS and later on in AOQ? What could be a healthy migration scenario?

Please login or register to see this attachment.

[cag014 731]

1. I think every scene could be converted to AOS/AOQ (except scenes that using HTTP commands). In any case you can write QuickApp functions (same as scenes) inside AOQ and the could be triggered/executed in AOQ line. (next release)

2. To my opinion HC3 Alarm zones is better concept especially using AOQ which provides sensors breaching the alarm

3. Entire AOS coudl be converted to AOQ (excluding alarm control setArmed and ForceArm are not supported)

1 hour ago, Rover said:

 

1+2. To be more precise about the scenario:

The hal  dimmer lights are automatically controlled by a Fibaro PIR. With the dimmer wall switch the hal lights can be switched off (and on). With wall switch Up 1x pressed a scene is started that put the hal dimmer lights on for 99% for 1 hour, after that hour the hal lights are switched off and controlled further by the PIR. The wall switch Down 1x pressed scene puts the lights of and kill the scene with the 1 hour program and the lights are controlled further by the PIR. That is converted to AOS now, just without the "killing".

So it is not about killing by programming AOS, but dynamical.

So it does work as expected, right?

 

Edited August 26, 2020 by cag014

[Rover 47]

47 minutes ago, cag014 said:

1. I think every scene could be converted to AOS/AOQ (except scenes that using HTTP commands). In any case you can write QuickApp functions (same as scenes) inside AOQ and the could be triggered/executed in AOQ line. (next release)

2. To my opinion HC3 Alarm zones is better concept especially using AOQ which provides sensors breaching the alarm

3. Entire AOS coudl be converted to AOQ (excluding alarm control setArmed and ForceArm are not supported)

So it does work as expected, right?

 

1. Which kind of scenes cannot easy be converted to AOS and better waiting to convert to AOQ?

At the moment I have problems converting scenes which are called in other scenes as a sort of function. How to implement this in AOS? AOS can call scenes, but they have to remain scenes and not converted tot AOS-lines, because then they could be called any more.

Is it possible to convert scenes to AOQ before device migration? As long as the devices have not been migrated from HC2 to HC3 the working of AOQ on HC3 is very limited, or does exist a way to emulate devices in AOQ on HC3? Maybe only disable the check in AOQ if jS2n-devices exist in HC3, a kind of dummy devices?

The aim is still to realize the migration HC2 to HC3 as quick as possible (WAF?).

2. "AOQ which provides sensors breaching the alarm", which functionality is needed converting alarm scenes to AOX, so I cannot convert my alarm scenes to AOS on HC2 now.

3. "Entire AOS could be converted to AOQ" but not all HC2 scenes could be converted before to AOS.

4. Yes the AOS dimmer functionality does work as expected, except for the possibility to disable a "wait" status. Perhaps still an idea to realize this?

[cag014 731]

@Rover

to convert scenes that called in other scenes to QuickApp it's very easy.

Scenes with triggers you'll need to trigger them by AOQ. Again not a big task...

The only issue is the devices IDs. I don't know how you manage IDs today - maybe you have json table or not.

In any case you can use same JS2n for both AOQ and QuickApp (scenes).

Currently there is no emulation for dummy devices. In any case you need dummy readings as well... and it's not an easy task to emulate.

 

By the way what exactly you mean "wait" status? Is it the 1 hour that PIR shouldn't work?

 

[Rover 47]

6 hours ago, cag014 said:

@Rover

to convert scenes that called in other scenes to QuickApp it's very easy.

Scenes with triggers you'll need to trigger them by AOQ. Again not a big task...

The only issue is the devices IDs. I don't know how you manage IDs today - maybe you have json table or not.

In any case you can use same JS2n for both AOQ and QuickApp (scenes).

Currently there is no emulation for dummy devices. In any case you need dummy readings as well... and it's not an easy task to emulate.

 

By the way what exactly you mean "wait" status? Is it the 1 hour that PIR shouldn't work?

 

Hi @cag014,

I get the idea, that instead of the scenario: converting to AOS, migrate devices from HC2 to HC3, copy AOS jS2n and jM to HC3, reconstruct in AOQ using QA's

a better scenario is: start with AOQ, include a wall plug in HC3, copy AOS jS2n and jM to HC3, give all jS2n device ID's the number of the wall plug, convert (rest of) HC2 scenes to QA's in AOQ, save AOS jS2n and jM, migrate devices from HC2 to HC3, replace jS2n with old jS2n with all the different device ID's.

 

"to convert scenes that called in other scenes to QuickApp it's very easy": Do you say that scenes called by other scenes better not be converted to AOQ but preferably to a QA? Or could Emit Custom Event do the job in AOQ?

 

In HC2 a use JSON Hometable for device ID's. For AOS I had to write the table by hand in jS2n.

 

With "wait" status I mean: trueAct={"`DimmerHal`","turnOff","60*60",false}, the hour waiting for turnOff. If I'm going back from AOS-line  to a scene, then it is possible to stop the future turnOff action with KillScene. A AOS-line cannot be stopped, or am I wrong?

[Rover 47]

In AOQ 1.2 on HC3  I tried to add a global variable Huisstatus, but then he hangs in an initializing loop.

global4local= {{false,gVarName="",varArray={onState="init:off",my_Var="isOff"}},{true,gVarName="",varArray={Huisstatus="Thuis"}}}

[cag014 731]

1 hour ago, Rover said:

In AOQ 1.2 on HC3  I tried to add a global variable Huisstatus, but then he hangs in an initializing loop.

global4local= {{false,gVarName="",varArray={onState="init:off",my_Var="isOff"}},{true,gVarName="",varArray={Huisstatus="Thuis"}}}

No... the array already defined. You added another array!

Follow that:

global4local= {{false,gVarName="",varArray={onState="init:off",my_Var="isOff",Huisstatus="Thuis"}},

You can remove the examples....

Edited August 27, 2020 by cag014

[Rover 47]

5 minutes ago, cag014 said:

No... the array already defined. You added another array!

Follow that:

global4local= {{false,gVarName="",varArray={onState="init:off",my_Var="isOff",Huisstatus="Thuis"}},

You can remove the examples....

The aim was to create global value (true), while the onState and my_Var are local values (false). How to accomplish this?

[cag014 731]

System Global value should be created in the system not in AOQ.

Go to General->Variables->Add Variable

Please defined as a Standard Variable.

Enumerated variable could be set only to per-defined values.

Please login or register to see this spoiler.

 

[Rover 47]

9 minutes ago, Rover said:

The aim was to create global value (true), while the onState and my_Var are local values (false). How to accomplish this?

 

 

Please login or register to see this attachment.

[Rover 47]

O.K., Huisstatus is global now. And the trick to give all jS2n devices the same device-ID (23) works. So you can develop in AOQ without having all devices migrated from HC2.

Of course only the structure and syntax could be validated, not the dynamic behavior, but it has its value.

 

BTW, in AOQ edit mode in black theme, the numbers in light grey are hardly to be seen.

 

Please login or register to see this attachment.