Additional views based on labels; updated sorting of areas

[mtinner]

Update order for areas according to following priority

1. order by strategy config
2. order by floor level
3. order by name

Split domain views

Since entities of different types belong to the same domain in home assistant, this can be a risk for the user.

E.g. window and shutters belongs both to the domain "cover". If I want to open all my shutters by a simple click, for example to prevent damage during a storm, I do not want to open my windows as well.

So in my opinion, users would have a huge benefit, if they can split them into separate views. User can reach this by add the entity to a label with a predefined prefix ms_domain_{{groupName}} (e.g. ms_cover_windows).
To make sure the controls still fits, the label name has to contain the correct same domain as its entry.
The {{groupName}} and the optional given icon in the label will be reused in the tab, navigation and as a name on the view.
Labeled entities are no longer grouped in the "default" view.

This solved this issue as well: #107

Order views incl. extra_views

Not only is it possible to order the new label-based views, but it is now also possible to set an order for extra_views. Solves #61, #139, #142

type: custom:mushroom-strategy
options:
  views:
    climate:
      icon: mdi:thermometer
    ms_cover_windows:
      order: 2
  extra_views:
    - title: Energy
      order: 0
      path: energy
...

illustation.webm

[mtinner]

@AalianKhan, @DigiLive, are you interested in this feature? If so, I can resolve the conflicts to move it forward.

[DigiLive]

I'm always interested in contributions. 😊

However, I've to share my limited free time over this and all other issues and PR's.
What I can say already...

It seems this PR contains multiple changes/additions:

• Grouping Areas by floor (Divide areas into floors #162).
• Change default view to a extra view (Request: Support setting the default view to an extra view #142).
• Create views, based on entity labels (Additional views based on labels; updated sorting of areas #141).

This is against the Github-Flow which we apply to this repository:
https://docs.github.com/en/get-started/using-github/github-flow#make-changes

If possible, please close this PR and create a PR for each set of unrelated changes, so they can be reviewed and committed to the main branch separately. This will also help a lot to prevent merge conflicts.

[DigiLive]

Important

Requires Hass 2024.4.1