[SOLVED] How to get scene ID within it's code

[Sankotronic 2,093]

@T.Konopka, @I.Srodka, @A.Socha or anyone with advanced knowledge

 

For virtual devices there is function that can give us ID number within VD code: fibaro:getSelfId()

 

QUESTION: Is there any similar function to get scene ID within it's code?

 

EXPLANATION: I need to find scene ID within it's code. I don't have any references when scene is installed on user HC2. I know that I can use scene name that has to be unique and then search it within response from API call, but that solution is far from good. What if user misspell name or decide that he like to use different name?

Edited December 8, 2017 by Sankotronic

[I.Srodka 4]

There is no such function.

 

I may submit it as a suggestion for a new feature but that doesn't mean it will be implemented.

[jgab 1,957]

Agree, really miss that one...

In version 4.140 that I'm running (don't know about later versions) there is an undocumented variable "__fibaroSceneId" available inside scenes... maybe while you wait for the official function?

 

[I.Srodka 4]

I've checked it. It really works even in versions after 4.140 ; )

[Bodyart 229]

It works even in 4.151

[jgab 1,957]

Well, Sankotronic being in the home automation software business supporting many users on many versions may need to be a bit cautious with this, or have some kind of fallback strategy...

 

[Sankotronic 2,093]

6 hours ago, I.Srodka said:

There is no such function.

 

I may submit it as a suggestion for a new feature but that doesn't mean it will be implemented.

 

Hi @I.Srodka,

 

This is very important feature and you should definitely suggest your team to seriously consider it or at least leave "__fibaroSceneId" as a part of the system. Distribution of future "out of the box" solutions depend on such features and gives developers possibility to make solutions that will not require end users to have any programming skills to install and use them. This can only benefit to Fibaro system in the end.

 

6 hours ago, jgab said:

Agree, really miss that one...

In version 4.140 that I'm running (don't know about later versions) there is an undocumented variable "__fibaroSceneId" available inside scenes... maybe while you wait for the official function?

 

 

Hi @jgab,

 

Thank you for sharing this undocumented feature. BTW there are lot more functions and features that are not documented on Fibaro developer website.

[jgab 1,957]

So, whenever I install a new version I run this in a scene to understand what's available (btw, anyone using the logger?)... (something similar for VDs)

Please login or register to see this code.

 

[alecon 2]

but how you extract the __fibaroSceneId from this table??

It seems to change everytime I run the printTable code....

Thanks.

[jgab 1,957]

Well, you don't need to extract it. Just conclude that it is there and use it in your scene.

Please login or register to see this code.

The _ENV contains all global variables (incl. functions) available in the Lua environment you are given.

[alecon 2]

3 minutes ago, jgab said:

Well, you don't need to extract it. Just conclude that it is there and use it in your scene.

Please login or register to see this code.

The _ENV contains all global variables (incl. functions) available in the Lua environment you are given.

 

Great!!! 

I were supposing the need to extract it from a system table... instead it is ready to use yet... 

many many thanks!!!

[tinman 1,025]

__fibaroSceneId exists since 3.907, and it's still being user by Fibaro, but as they cleaning up the code who knows how long it will stay ...

[Sankotronic 2,093]

1 hour ago, tinman said:

__fibaroSceneId exists since 3.907, and it's still being user by Fibaro, but as they cleaning up the code who knows how long it will stay ...

 

I hope it will stay till the end of days or at least be replaced with function fibaro:getSlefId() that is available in VD. Being able to get scene ID from it's code opens door to a real automation where user setup within code can be reduced to a minimum.

[jgab 1,957]

Well, you could always do something like this...

Please login or register to see this code.

 

[Sankotronic 2,093]

On 12/18/2017 at 7:12 AM, jgab said:

Well, you could always do something like this...

 

Hi @jgab,

 

I though about that solution, but adding this loop to all scenes which ID is needed is not the best choice. It can slow down performance. Maybe adding unique name in scene code and then use separate initialization scene that will make global variable table with all scenes ID and unique name? Unique name then can be used to retrieve scene ID when needed in another code.

[jgab 1,957]

For long running scenes that extra time shouldn't be a problem, for short trigger scenes it can be ”cached” the first time around

Please login or register to see this code.

 

Edited December 19, 2017 by jgab

[RossA 1]

Is it possible to get the scene ID of the scene that was used to trigger another scene?

[Sankotronic 2,093]

2 hours ago, RossA said:

Is it possible to get the scene ID of the scene that was used to trigger another scene?

 

In scene that calls other scene you can use this code to provide calling scene ID:

Please login or register to see this code.

Then in scene that was started by above code you can get scene ID 'sId' with this code:

Please login or register to see this code.

Same way you can send virtual device ID to the scene that was started by that VD.

 

[RossA 1]

Thank you very much.

 

I am new at this and while I have now have written many scripts and learned a lot, I am still not familiar with the finer detail of LUA.  First time I have done any coding.

 

All worked well thanks again.

[RossA 1]

Do you mind if I ask you one more question?

 

Is it possible to send email notification from LUA, from alarm scene, that has the device ID that triggered alarm?  I know you can send pre defined messages but it would be great if I could use the email address already in the HC2, the one used to send pre defended messages, but be able to customise the message.

 

Also, I suppose this makes it 2 questions sorry, as you know when a sensor triggers it may send ,multiple message while it is in alarm state, is there a way of limiting the message to one message per trigger.  That is set a time period where if triggered again within a time period it will not send another message.  Sensor trigger -> send message -> no more messages within xxSeconds -> then send new trigger message.

 

 

 

[RossA 1]

Ok I worked email out, need to test if I can limit the number of messages sent if sensor alarm period causes extra messages.

 

thanks.