LUA - First few lines?

[rvorsten 0]

Folks -

Can anyone explain that these initial lines at each piece of LUA actually mean or, even better, there the HC2 specific LUA code is documented?

The LUA tutorials on the web tell me that everything between the --[[ and ]] is actually commentary only, so according to that, the three lines starting with %% below have no impact at all...

--[[

%% autostart

%% properties

%% globals

--]]

So that raises the question: why are they there in most of the samples I see here, and also in all the LUA code that gets generated when translating form Blocks to LUA?

Thanks for your insight!

Ronald

[Guest deraaij]

%% autostart --> Start when HC2 Starts (for time based scenes)

%% properties --> Needs to be followed by one or mote properties which are used for this scene as trigger. e.g. 5 value (trigger on change in value of device # 5), 102 valueSensor etc

%% globals --> Needs to be followed by one or more variables of which a state change needs to trigger a scene.

[rvorsten 0]

%% autostart --> Start when HC2 Starts (for time based scenes)

%% properties --> Needs to be followed by one or mote properties which are used for this scene as trigger. e.g. 5 value (trigger on change in value of device # 5), 102 valueSensor etc

%% globals --> Needs to be followed by one or more variables of which a state change needs to trigger a scene.

Thanks!

[HansW 1]

All,

To me it is still strange/unclear how this works.

A. Socha advised in another reply "yes that is a comment line but we took from that information for our scene engene "

So the 'greyed' lines are active. To include a property you have to include them in greyed-out mode. Same for properties. I find it odd to believe but that is how it works. Agree?

Also, when you create new LUA scene and you hit the option 'Start when Home Center starts' then this option is sort of buried in the system. It's active but not visible in the first few lines. The system doesn't generate the %autostart option for you.

Then there is the option 'Active Scene'. I have no clue what that option does.

Is this described anywhere? I know there are quite a few in this forum who understand these basic details. Please help?..

Cheers,

Hans

[rvorsten 0]

All,

To me it is still strange/unclear how this works.

A. Socha advised in another reply "yes that is a comment line but we took from that information for our scene engene "

So the 'greyed' lines are active. To include a property you have to include them in greyed-out mode. Same for properties. I find it odd to believe but that is how it works. Agree?

Also, when you create new LUA scene and you hit the option 'Start when Home Center starts' then this option is sort of buried in the system. It's active but not visible in the first few lines. The system doesn't generate the %autostart option for you.

Then there is the option 'Active Scene'. I have no clue what that option does.

Is this described anywhere? I know there are quite a few in this forum who understand these basic details. Please help?..

Cheers,

Hans

Fully agree, Hans...

@Fibaro: Isn't it time that you guys capture all of this into a proper English manual? That would save many of us many hours of guess-work and trial&error and therefor frustration...

[Guest Lode]

Do you mean the option "Scene Active" at the advanced tab from your scene ?

In that case when it's marked your scene will run.

When it's not marked your scene will never run.

[rvorsten 0]

Do you mean the option "Scene Active" at the advanced tab from your scene ?

.

No, we are referring to the first few lines in LUA scripts.

[HansW 1]

Lode,

Thanks for answering a part of the question. Makes sense that indeed that is how this feature works. I would expect, however, a setting like "disable" this scene or make the setting 'Activate the Scene' the default setting..

Grateful if anyone can shed some light as to how the 'greyed-out' and on face value 'inactive' first lines of the scripts do function.

Cheers,

Hans

[ Added: 2013-03-18, 21:55 ]

Oh oh, overlooked one of robmac's recommendations (Thanks robmac!!!) .... Just followed the link

Please login or register to see this link.

and found quite some very good info. Parts of it translates from Polish to English automagically. Most of I had to run manually through BING translator. (Guess I have to use Google..). So the information is there. In Polish. This language aspect doesn't amaze me anymore.. The product is great, support definitely ok. The documentation and communication.. a disgrace to international customers!

Hans

[Guest sgbirch]

The product is great, support definitely ok. The documentation and communication.. a disgrace to international customers!

Hans

Couldn't agree more. I actually wrote to Fibaro and volunteered to help with the translation, this was rejected, they said they have somebody working on it. Sigh.

Fibaro has not yet learned the value of its community.

[JanJoh 1]

%% autostart --> Start when HC2 Starts (for time based scenes)

%% properties --> Needs to be followed by one or mote properties which are used for this scene as trigger. e.g. 5 value (trigger on change in value of device # 5), 102 valueSensor etc

%% globals --> Needs to be followed by one or more variables of which a state change needs to trigger a scene.

Ok, so does this mean (Yes, complete newbie here) the following:

I have a Aeontec 4-in-1 where the Light sensor is shown as ID 68 in propertied.

If i would like to have a scene that sets a global var "ItsAfterDark" if the value of that sensor falls below 100, i should then do

NOT include %%autostart

Include %%properties 68 value

and then the scene will fire every time the sensor sends a new value to the system?

(At first i thought i needed to have a timed script that checked the value every X minutes).