HC3 Scenes (not QA) - fibaro:args - how?

[jgab 2,641]

12 minutes ago, Sankotronic said:

Hi @jgab ,

 

Thanks for trying. I think that converting HC2 virtual devices to HC3 quick apps is not easy, specially because VD's are not that advanced as QD. You can use my Sonos API Player VD and Sonos API Player QA and see all the differences. On HC2 I was able to use predefined global variables to store data tables while on HC3 predefined variables can't hold any other data but the one that is initially predefined. That means that code that takes care for global variables must be changed.

 

Another thing that I need is to be able to store my own role types to QD so that they can find each other including scenes. On HC2 I was able to use scene json table to store this in "properties" as a table together with scene version and run type. For virtual devices I had to use global variable. Fibaro provided Role is just not sufficient for me since there are some combinations of roles that can't be covered with their solution. I'm now checking possibilities on HC3 with swagger to see if situation is a bit better with QD's and scenes.

 

Also, there are some solutions on HC2 that required combination of virtual devices and scenes while on HC3 those solutions can be achieved solely with QD's. One example is Philips HUE with new API2 which requires HTTPS calls so all communication between HC2 and Philips HUE bridge I had to move to scene, but on HC3 this can be done with QD. Problem that I'm facing with HC3 and QD child devices are that child devices are rudimentary which is not good enough from my perspective. This is because I want to have possibility to select and activate HUE light scenes at least on group of lights as I have made it for HC2 UHAS. I need that so that users can adjust lighting for specific situation and then save that setting to be used in light automation. This means that When user add QD children for HUE grouped lights then there should be besides default buttons and sliders also buttons and labels to select desired HUE light scene and activation.

 

But of course you know all the above. I think I will manage, specially thanks to your effort and knowledge shared here on forum. Without your help and your posts here on forum everything would be much more difficult. Eternal thanks and respect goes to you Jan! 🙏

 

You can use the QuickAppVariables as "QA properties" - they are readable from Other QAs too. There you could store roles etc. It is possible, with some work, to add custom UI elements "ontop" of the QuickAppChildrens default UI - so you could add additional buttons/sliders/labels etc. I believe it's possible to kill the default UI element of children too, giving complete control of a custom UI. QA Children are also not necessary - just a way to keep all code in one place and have multiple QAs. You could as well have a main QA that creates other standard QAs and receive and update their UIs. I believe that's what @petrkl12 is doing in his Hue QA.