Customise Access to Settings/Dev Tools

With the new and improved settings & dev tools menus in the 2022.5 release generating some mixed reactions, I thought I’d share the approach I’ve been using for some time for quick access to things I use most when reconfiguring my set up. It is just a simple template Markdown card with URL links to the resources (both in Home Assistant itself and external reference web pages), arranged in an order that makes sense for my personal workflow (for the tasks I’m working on at the time). Then I added the page to the sidebar so it is always easily accessible (also for other Markdown cards tools on the page like automatically generating YAML scenes from the current states of entities).

For the record, this is not bashing the new settings menu - I think the improvements are great, especially having all the logs accessible from a single location! I just had to track down the new URL for ‘Server controls’ and update it.

If you want to create a layout that meets your own needs, here is one way to do it. Here is the YAML Lovelace for creating the card in Lovelace - enter your own ***MY_HA_URL*** at the top of the template, then customise the links and arrangement to suit your own tasks/needs:

# Quick links for managing HA
- type: markdown
  title: HA Quick Links
  content: |
    {#- CONFIGURATION CONSTANT #}
    {%- set HA_URL = 'https://***MY_HA_URL***:8123' %}
    ---
    <ha-icon icon='mdi:microsoft-visual-studio-code'></ha-icon>&nbsp;&nbsp;&nbsp;[YAML/Python editing]({{HA_URL}}/a0d7b954_vscode "VScode config editor")
    <ha-icon icon='mdi:code-braces-box'></ha-icon>&nbsp;&nbsp;&nbsp;[Jinja2 Templates testing]({{HA_URL}}/developer-tools/template "Test Jinja template")
    <ha-icon icon='mdi:pound-box'></ha-icon>&nbsp;&nbsp;&nbsp;[Markdown preview](https://markdownlivepreview.com/ "Check Markdown text")
    <ha-icon icon='mdi:file-tree'></ha-icon>&nbsp;&nbsp;&nbsp;[YAML Tree viewer](https://www.treedoc.org/#/ "Check YAML structure")
    ---
    <ha-icon icon='mdi:checkbox-marked-outline'></ha-icon>&nbsp;&nbsp;&nbsp;[Server control (Check Config)]({{HA_URL}}/developer-tools/yaml "Check & reload configs")
    <ha-icon icon='mdi:card-bulleted'></ha-icon>&nbsp;&nbsp;&nbsp;[HA Logs]({{HA_URL}}/config/logs "HA Logs")
    <ha-icon icon='mdi:home-assistant'></ha-icon>&nbsp;&nbsp;&nbsp;[System]({{HA_URL}}/hassio/system "System controls, info & logs")
    <ha-icon icon='mdi:backup-restore'></ha-icon>&nbsp;&nbsp;&nbsp;[Backups]({{HA_URL}}/hassio/backups "Manage HA backups")
    ---
    <ha-icon icon='mdi:view-grid-plus'></ha-icon>&nbsp;&nbsp;&nbsp;[Addons]({{HA_URL}}/hassio/dashboard "Install & config Addons")
    <ha-icon icon='mdi:home-group-plus'></ha-icon>&nbsp;&nbsp;&nbsp;[Integrations]({{HA_URL}}/config/integrations "Install & config Integrations")
    <ha-icon icon='mdi:devices'></ha-icon>&nbsp;&nbsp;&nbsp;[Devices]({{HA_URL}}/config/devices/dashboard "List of devices")
    <ha-icon icon='mdi:lightbulb'></ha-icon>&nbsp;&nbsp;&nbsp;[Entities]({{HA_URL}}/config/entities "List of Entities")
    <ha-icon icon='mdi:gauge'></ha-icon>&nbsp;&nbsp;&nbsp;[States]({{HA_URL}}/developer-tools/state "States & Attributes of Entities")
    <ha-icon icon='mdi:sigma'></ha-icon>&nbsp;&nbsp;&nbsp;[Statistics]({{HA_URL}}/developer-tools/statistics "List of Entity Stats")
    ---
    <ha-icon icon='mdi:home-assistant'></ha-icon>&nbsp;&nbsp;&nbsp;[HomeAssistant.IO](https://www.home-assistant.io/docs/automation/ "HA configuration")
    <ha-icon icon='mdi:home-assistant'></ha-icon>&nbsp;&nbsp;&nbsp;[HASSIO API](https://developers.home-assistant.io/docs/dev_101_hass/ "HA Python programming")
    <ha-icon icon='mdi:vector-square'></ha-icon>&nbsp;&nbsp;&nbsp;[MDI Icons](https://materialdesignicons.com "Material Design Icons")
    <ha-icon icon='mdi:github'></ha-icon>&nbsp;&nbsp;&nbsp;[HA Github](https://github.com/home-assistant "Home Assistant Github page")

    <ha-icon icon='mdi:overscan'></ha-icon>&nbsp;&nbsp;&nbsp;[Nextion instruction set](https://nextion.tech/instruction-set/ "Nextion HMI programming")
    <ha-icon icon='mdi:github'></ha-icon>&nbsp;&nbsp;&nbsp;[Nextion Handler](https://github.com/krizkontrolz/Home-Assistant-nextion_handler "Nextion Handler on Github")
    ---
    **e**: Entitiy Filter (hotkey)
    **c**: Command Palette
    **c th**: Reload Themes

1 Like

Nice work!
Do you want to tell me what the Markdown tools in the top are all about?

Thanks. The tools at the top are:

  • YAML/Python editing : Opens the VSCode editor (HA addon).
  • Jinja2 Template testing: Opens the HA page for testing templates (I spend a lot of time in there - templating is awesome).
  • Markdown preview: A website for checking your Markdown code renders properly (I use a lot of template Markdown cards to customise displayed information nicely, so it is good to be able to check formatting).
  • YAML Tree viewer: A great website for visually showing the structure of your YAML data (I used it a lot when I initially rewrote my all my YAML configs from first principles - I was getting frustrated not understanding YAML well enough to debug cut-and-paste code when it went wrong).

I concur with you on this. Having said that, I’ve copied you YAML and created a “Tools” card!

1 Like

Sorry, I think you meant the Markdown cards that were disabled - here are the two I use the most:

The one on the left generates the YAML for scenes based on the current states of entities. I find it an easier way to create and fine tune scenes, especially to get light colours just the way I want them. I set the scene I want to modify/adapt, adjust everything the way I want it in Home Assistant, then copy and past the generated YAML into my scenes.yaml. (I know HA now has this feature built in, but I still use my approach because I was finding the HA version was copying over a whole lot of entity attributes I did not want to set in scenes.)

The card on the right adds missing attributes for new devices that I copy into customise.yaml (so that things like stats, energy tracking, device filtering in other templates etc. work properly).

(I create/comment in/out other task-specific Markdown tools as needed, and put new template cards here for testing until they are ready to include in the main UI pages).

Ah, good idea. For exactly the same reasons, I also never want the UI Editor, too few options with too much superfluous data. :wink: