Lua code for press button of Virtual device

[PavelU 0]

Hello!

I have Virtual device with id 83 and button with id btnToggle that toggling power state of virtual device.

I want with pressing button on device with id 107 toggling power state of virtual device.

Code:

Please login or register to see this code.

In debug I see 1 and 2, but Virtual device doesn`t change its power state.

Please login or register to see this attachment.

Please login or register to see this attachment.

[cag014 731]

To press button of VD, you need to use the number of the button (not ID).

To find out the number, you just need to count all elements (buttons, labels,sliders) from upper left corner to the right and down.

Please login or register to see this spoiler.

 

For example if your button is number 2 then the command line is:

Please login or register to see this code.

[pogo 3]

Giving IDs to buttons feels so useless while you can't use it in lua

No way to reorder buttons, add new ones etc. without rewriting all associated code

[cag014 731]

Yes, you're absolutely correct....but this is the way it works

Edited January 16, 2019 by cag014

[jgab 2,642]

9 hours ago, pogo said:

Giving IDs to buttons feels so useless while you can't use it in lua

No way to reorder buttons, add new ones etc. without rewriting all associated code

You could do something like this - a bit expensive but you don't have to rely on order of buttons.... ('api.get', so only for calling from scenes)

Please login or register to see this code.

 

Edited January 16, 2019 by jgab

[PavelU 0]

14 hours ago, cag014 said:

To press button of VD, you need to use the number of the button (not ID).

To find out the number, you just need to count all elements (buttons, labels,sliders) from upper left corner to the right and down.

Please login or register to see this spoiler.

Thanks a lot! It`s working!

 

Thanks to all.

[pogo 3]

@jgab I know it and I can write a few more ways to do this, but I would need to copy this code to every scene and VD button/slider. I don't like it. 

And, as you said, it's expensive... I used to work as game dev, so I hate expensive solutions.

One day I will find the easy and fast way for this... but for now the Fibaro license agreement limits me with my actual ideas...

[jgab 2,642]

1 minute ago, pogo said:

@jgab I know it and I can write a few more ways to do this, but I would need to copy this code to every scene and VD button/slider. I don't like it. 

And, as you said, it's expensive... I used to work as game dev, so I hate expensive solutions.

One day I will find the easy and fast way for this... but for now the Fibaro license agreement limits me with my actual ideas...

Can't copy it to VDs as it uses api.get - but I understand what you mean. 

Well, what's expensive always depends. Almost all my scene are long running (

Please login or register to see this link.

), and doing the mapping once when the scene starts up is negligible. Otherwise you could cache the id map by patching the scene code with the table (checking date if the VD been updated) - similar to this selfID hack that don't rely on __fibaroSceneId

...because the only thing we want to avoid is putting things in fibaro global variables 

 

[cag014 731]

42 minutes ago, pogo said:

@jgab I know it and I can write a few more ways to do this, but I would need to copy this code to every scene and VD button/slider. I don't like it. 

No, you don't need to copy that....

I'm doing the same with one scene, which scans and holds all VD buttons (and other stuff) as JSON table in one global variable.

All other scene and VDs are using this global variable.... working fine, no issues so far