I use the Average Temperature and Average Humidity app driver. It is clean, smooth and efficient.
As my HE interface continues to improve, I would benefit by this tool being a Parent / Child app. Currently I load multiple iterations and it adds to my App list depth. If it were built more like - for example only - the Button Controller I'd have all my iterations rolled up under it.
As you can see from my small screen cap, each iteration of Average Temp I begin with "AT-" to group them as well as identify them when used in rules etc. The same with Average Humidity - which all begin with "AH-". Also visible is the nicely collapsed Button Controller (I have 4)
I don't have high expectations - I recognize that HE sourced apps and drivers rarely change and/or are from legacy environs.
A feature request can have 2 effects. Besides the obvious idea that may offer improvement in/around these 2 particular apps I use in their current form, it also puts an 'ear worm' for future items that HE may create or supply that may benefit from a similar criteria.
So simply just the act of submitting a feature request may help HE improve their product long term. Consider it a form of feedback. (it is, after all, in the feedback category).
Writing the apps myself would indeed solve my desires, but helps no one else. I submit feedback as a way to communicate with HE possible ideas to improve their product over time.