Try to understand how scene are triggered

[pixys 1]

Hello

 

I've wrote a little scene in LUA, and I still do not figure out how scene are triggered

 

Please login or register to see this code.

 

For the result in the debug windows with this code should loop.

and should look like

 

 

Please login or register to see this code.

 

But the result of the execution is that one

 

Please login or register to see this code.

 

only 1 occurence of the execution.

 

Can someone explains what's triggering the execution of the scene

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

 

I found the explaination.

 

How this is working

 

Scene got activated once. If you want to have a reoccurence of the activation you need to create a function and write inside what the part of the code you want to reexecute.

 

and at the end of the function use the fibaro function

 

    setTimeout(nameofmyfunction, 60*1000)   -> 60 is 60 secondes.

 

The code should looks like

 

Please login or register to see this code.

 

 

 

 

 

 

 

 

Edited September 28, 2017 by pixys
I found the reason

[Momos 103]

yes that is correct  this will make the scene loop continuously.   Try not to have too many of these in the system thou.  My advice would be to have one scene running in a loop - the main scene , and all the others triggered by variables, devices and so on.

 

 

[pixys 1]

I've got 7 in total 1 per heating control.

 

I understand the main loop

 

Please login or register to see this code.

 

 

Do you have any sample of a scene trigger by device or variable ?

 

 

Thanks

Pixys

[cag014 731]

Here an example of scene triggered by devices

Please login or register to see this code.

Please note:

I'm using json table for device IDs, but it's actually the ID numbers of the devices. 

I have changed first two cases to actually ID numbers for your convenience.

 

 

Here an example for global variables

Please login or register to see this code.

I don't use 

%% autostart 

It means the HC2 will not execute the scene on startup (e.g. after reboot),but it will be executed only if triggered.

Although the scene mode  must be set to Automatic

Please login or register to see this attachment.

 

 

Edited September 29, 2017 by cag014

[pixys 1]

Thanks , I will have to read it twice to understand all the concept

 

[cag014 731]

Here is a very simple example for device property trigger

Please login or register to see this code.

Hope it more understandable 

Edited September 29, 2017 by cag014

[pixys 1]

Hello

 

Yes, It looks clear now.

 

Thanks

[BOT 1]

The topic has been moved from "

Please login or register to see this link.

" to "

Please login or register to see this link.

".

 

Temat został przeniesiony z "

Please login or register to see this link.

" do "

Please login or register to see this link.

".