Will give it a shot in the future. At this moment i am rewriting all my flows into the advanced flows. I also have many flows involving json. They were a hell of a job, so maybe this is THE app for me. In advance thx for creating this. I hope that my old method with this app is easier, had to make 24 calls collecting data about themperature, humidity, wind, etc etc for every hour. For three collections of data that will be 72 calls. And i have many many other data that i wanted to collect. Just a little example how it now worked
Create Global Tags on the fly.
A flowcard would not have Set Text1 = [input], but more something like Set [name]=[input], where you could fill in the name and a Global Tag would be created.
A Virtual/Fake Device with customisable property names ( like AVD), which you could set through flowcards like the current JSON cards.
But both solutions have one very big weakness: Using the same tag at the same time is gonna create issues, because the scope of the Results are outside of the Flow.
This can/will cause “random” feeling errors.
This makes any solutions that i currently can see, not very usefull.
So the Homey code requires the tags from an action card must have static result tag(s)?!
This is why you have different sizes of JSON handler cards.
I hope this will be changed in upcomming Homey releases.