Start scene with certain attributes through http api

[3JL 7]

Hi,

Is it possible to start a scene through an http command with specific attributes?

e.g. /api/SceneControl?action=start&id=sceneID&var1=5

 

Or should I change a global variable using /api/globalVariables first?

I feel I will then get in trouble when multiple instances of a scene are ran simultaneously.

 

Thanks, J

[tinman 1,070]

No, you can't do both at same time, but:

 

you can add in scene trigger section

 

Please login or register to see this code.

 

to let only the current one instance, or you can trigger directly based on variable change (of course if possible) if you worry about extern triggering.

 

[jakub.jezek 370]

1 minute ago, tinman said:

you can add in scene trigger section

Please login or register to see this code.

to let only the current one instance, or you can trigger directly based on variable change (of course if possible) if you worry about extern triggering.

 

Wow, that is great we could use that. I wonder why Fibaro developers did not use it in generating lua code after making block scene. This could save a lot of troubles from my point of view, instead of limiting instances to 10.

[tinman 1,070]

it is by default for magic scenes, but they have only one trigger. For block scenes one need sometimes to trigger even twice without killing the already running (e.g. to not break up something middle of the process, but simply run both one after the other or block before run with max. instances). 

 

 

[Sankotronic 2,370]

I don't know if my case is isolated one, but when I try to use %% killOtherInstances with my Very Smart Light scene (LUA) that is triggered by either device or global variable it didn't work as I expected. First instance that was triggered with motion sensor breached was killed by scene instance that was triggered by motion sensor going to safe. So at the end I had lights remaining turned on and no running instances of the scene.

 

In short, it seems to me that using this option only last triggered instance stay running while instance that was running before is killed. This is OK for some cases but not if you want to keep first instance running and prevent other instances to start.

[jimicr 90]

2 minutes ago, Sankotronic said:

I don't know if my case is isolated one, but when I try to use %% killOtherInstances with my Very Smart Light scene (LUA) that is triggered by either device or global variable it didn't work as I expected. First instance that was triggered with motion sensor breached was killed by scene instance that was triggered by motion sensor going to safe. So at the end I had lights remaining turned on and no running instances of the scene.

 

In short, it seems to me that using this option only last triggered instance stay running while instance that was running before is killed. This is OK for some cases but not if you want to keep first instance running and prevent other instances to start.

If I remember correctly, this %%Killotherinstances was introduced in the (Beta?) FW that had auto scene creation. But this was removed at the next update.

You could only see this when you used the HC2 toolkit to backup the scene.

 

Jim

[Sankotronic 2,370]

1 minute ago, jimicr said:

If I remember correctly, this %%Killotherinstances was introduced in the (Beta?) FW that had auto scene creation. But this was removed at the next update.

You could only see this when you used the HC2 toolkit to backup the scene.

 

Jim

 

Don't know when was this introduced, but it can be used at least in LUA scenes on FW 4.120 (tested on that version), but as I noted when this is added to the code then Max. running instances is set to 1 and only last started instance is running while instance that was already running is killed with shotgun. Buuum! 

I still have it added in Main scene FTBE on 4.130, but it doesn't have any influence since scene is anyway running only one instance. To check if there is any influence I need to run test.

[jakub.jezek 370]

2 minutes ago, Sankotronic said:

 

Don't know when was this introduced, but it can be used at least in LUA scenes on FW 4.120 (tested on that version), but as I noted when this is added to the code then Max. running instances is set to 1 and only last started instance is running while instance that was already running is killed with shotgun. Buuum! 

Ok, i will not using these .

 

3 minutes ago, Sankotronic said:

I still have it added in Main scene FTBE on 4.130, but it doesn't have any influence since scene is anyway running only one instance. To check if there is any influence I need to run test.

Maybe some unnoted "update". There is few of them. Eg. i was restarting HC2/HCL during 503 by calling GET method folowing URL "http://HC_IP/restart.php". Now, that will give me 503, when i try to call it.