Improvements to Functions-based workflow

Hello!

I'm not happy with the results when creating new Functions and the group addresses that are automatically created.

We need some sort of flexibility, ability to create our own templates etc.

For example, there is only a single "sun protection" type which creates the following 6 addresses which are numbered in sequence:

• Movement
• Step/Stop
• Wind alert
• Rain alert
• blinds position
• slat position

Now if I create another "sun protection" function, it correctly reuses the "Wind alert" and "Rain alert" GAs created with the first sun protection function. (By the way, perhaps these should be marked as "Central" automatically?)
So the order of addresses for the second function looks like this:

• Wind alert
• Rain alert
• Movement
• Step/Stop
• blinds position
• slat position

This immediately illustrates several issues:

• The two alert (alarm) addresses are not created first (as the first step) when creating the first function, which makes the order of GAs inconsistent for the subsequent sun protection functions (see the screenshot at the bottom).
• There is no way to influence the actual group address numbers. They are just appended to the highest address in the project.
  No way to set e.g. a specific main group for specific Function types.
  No way to place the alert addresses under a different main/middle group (e.g. I like to place my alarms under 0/0/).
  No way to say that I want to place my "Movement" addresses at starting address X and the associated "Step/Stop" addresses at X+50 etc. resulting in the following structure (with e.g. X = 2/0/0):

1. Blind 1 Movemement 2/0/0
2. Blind 2 Movement 2/0/1
3. Blind 3 Movement 2/0/2
4. …
5. Blind 1 Step/Stop 2/0/50
6. Blind 2 Step/Stop 2/0/51
7. Blind 3 Step/Stop 2/0/52
8. …
9. Blind 1 Blind Position 2/0/100
10. etc.

• There is no way to influence the group address names.
  Moreover, the names are inconsistent. Some start with upper-case letters, others start with lower-case letters. Compare: Movement, Step/Stop × blinds position, slat position.
  (not to mention they should be Blind (singular) position and Slats (plural) position)
  For dimmers: Switching, Status, Dimming, Value × dimming value.
  This is inconsistent and not aesthetically pleasing.
• Nowadays, 100% of our projects include some sort of visualization so we need to create more group addresses. E.g. I need at least two more addresses for blind/slats positions - to have both set (command) AND status (feedback) addresses.
• On the other hand, we also integrate drapes, shutters etc. without the step/slats functionality, so I want a simple way of tweaking the Function to create only the addresses I need, no more.
• We may want/need to add more addresses for (non-standardized) objects such as movement status, blocking, DALI ECG error status etc.

Similar with HVAC (thermostats). There is so much variety so just having two (switching variable & continuous variable) just isn't cutting it. Different setpoint shift/change object types, different fan speed object types etc.

Please, let us create custom function templates based off the existing standard Functions to give us the ability to create exactly the group addresses we need, assign some meaningful address structure and address names.

Also, please add the ability (option) when deleting a Function, to also delete the associated group addresses (All vs only Non-Central address?)

If you fix these issues, the Function-based workflow will start making much more sense.

Best regards,
Lukáš Polívka