Update lovelace ID status + include and secret support (#7395)

* Revert automatic lovelace IDs

* Add notes about include and secrets

* Add config splitting note

source/lovelace/index.markdown

@@ -84,7 +84,7 @@ excluded_entities:
 views:
     # View tab title.
   - title: Example
-    # Unique id for direct access /lovelace/${id}. If you don't specify one, it is added automatically.
+    # Unique id for direct access /lovelace/${id} and editing it from the UI.
     id: example
     # Optional background (overwrites the global background).
     background: radial-gradient(crimson, skyblue)
@@ -93,7 +93,7 @@ views:
     # The cards to show on this view.
     cards:
         # The filter card will filter entities for their state
-      - id: peoplehome # Every card needs an ID, if you don't specify one, it is added automatically.
+      - id: peoplehome # Every card needs an ID, for it to be edited from the UI.
         type: entity-filter
         entities:
           - device_tracker.paulus
@@ -137,7 +137,10 @@ views:
 Now restart Home Assistant, navigate to `<YOUR HASS URL>/lovelace`. When you make changes to `ui-lovelace.yaml`, you don't have to restart Home Assistant or refresh the page. Just hit the refresh button at the top of the UI.
 
 ## {% linkable_title IDs for cards and views %}
-Every card and view needs an ID, this is used to edit your config from the UI. If you don't specify an ID, Home Assistant will add one. If you don't want Home Assistant to write to your `ui-lovelace.yaml` file, make sure every view and card have an ID.
+If you want to edit your views and cards from the UI, every card and view needs an ID. This ID is used to save your config from the UI. 
+
+## {% linkable_title Configuration splitting %}
+`ui-lovelace.yaml` only supports basic configuration splitting. Only `!include` and `!secret` are supported, be aware that content that is included with `!include` and `!secret` can not be edited from the UI.
 
 ## {% linkable_title Setting Lovelace as the Default UI %}
 Once you are ready to start using Lovelace UI as your main user interface, click on info, the "i" icon under 'Developer Tools" in the Home Assistant side-bar. Next, locate >>Set Lovelace as default page on this device<< under the Home Assistant version information and click it.
@@ -174,3 +177,7 @@ frontend:
 Given examples refer to `/local/example_image.jpg`. That means you should have `www` directory next to your HA `configuration.yaml`. An image kept in `HA_configuration_dir/www/example_image.jpg` will be shown after refreshing Lovelace page.
 
 Restart Home Assistant after creating the `www` directory. Otherwise, HA will not know that you created this directory.
+
+### {% linkable_title My `ui-lovelace.yaml` file suddenly has ID's added to all cards and views! %}
+
+In version 0.81.0 we started preparing for the ability to edit you Lovelace UI from the UI itself. To be able to do this every view and card should have a unique ID. If your cards or views didn't had an ID, Home Assistant would add a random one. This behaviour was changed in 0.81.1, Home Assistant will no longer change your configuration without asking first. You can edit the generated ID, the only restriction is that it is unique. You could even delete the IDs if you don't want to use the UI edit functionality.

source/lovelace/tips.markdown

@@ -36,9 +36,11 @@ you with the ability to split your Lovelace configuration into multiple files.
 The [Lovelace Jinja2 Script][lovelace-jinja] by [@skalavala] is a simple Jinja2 script that you run in the template editor to generate lovelace configuration based on the entities that are already setup. 
 
 <p class='note'>
-  Split configuration is no longer possible in Lovelace since version 0.81, due to the fact that Home Assistant
+  Lovelace only has limited file splitting functionality, due to the fact that Home Assistant
   will be writing directly to the `ui-lovelace.yaml` file.
   
+  Only `!include` and `!secret` are supported at the moment.
+  
   If you want to split your configuration you can use one of the tools listed above, but edits done with the UI will
   be overwritten by those tools, so you should not use both.
 </p>