It + the rest of your config has given me a pretty good idea how you’ve done it - cant say it will be the same for others though. That said, i’m not one to read the documentation 
One thing that I’m going to do with mine is use reusable partials
Yeah I’m not sure how to do anchors so if be happy to see how you do that to save me some time
I’m using !include
- !include
- partial_docker_info.yaml
- name: "Portainer"
image: "https://developer.asustor.com/uploadIcons/0020_999_1583488696_Portainer_new_256.png"
status_sensor: "sensor.status_vmtbsh02_docker_portainer"
switch: "switch.vmtbsh02_ha_dockermon_portainer"
memory: "{{ (data | fromjson)['docker_portainer_memory']}}"
netrx: "{{ (data | fromjson)['docker_portainer_netrx']}}"
nettx: "{{ (data | fromjson)['docker_portainer_nettx']}}"
and the file - partial_docker_info.yaml
# dwains_theme
# Partial - Docker Info
type: vertical-stack
cards:
- type: markdown
content: >
<center>
<img width="60" src="{{ image }}">
<h4>{{ name }}<br/>
Mem: {{ memory }}</br>
Net: {{ netrx }} / {{ nettx }}</h4>
</center>
style: |
ha-card {
box-shadow: none;
color: teal;
}
- type: custom:bar-card
positions:
name: 'off'
value: 'off'
icon: 'off'
width: 100%
height: 10px
entity: {{ status_sensor }}
tap_action:
action: call-service
service: switch.toggle
service_data:
entity_id: {{ switch }}
severity:
- color: red
from: 0
to: 0
- color: rgb(26,204,147,0.33)
from: 1
to: 100
style: |
ha-card {
box-shadow: none;
--paper-item-icon-color: rgb(47,186,229);
height: 10px;
}
bar-card-backgroundbar {
margin-top: -47px;
border-radius: 2.5px;
}
bar-card-currentbar {
margin-top: -47px;
border-radius: 2.5px;
}
Is there a custom component for Google fit?
I for the life of me can’t remember where I found it, it took alot of searching obscure things to get it to work. I will pm you the custom component edit found it Google Fit
2 Likes
do you used the scooter to get to work?
Not every morning but yeah it takes me 45mins to drive to work and 58mins to scooter and the scooter has less morons for me to get stuck behind.
1 Like
Are you planning on not putting everything up until you document?
I would really enjoy just looking at the code. For example just to see what cards you use 
I am planning on putting it all up soon, there is my ha server dashboard up there already which should give clues as to what the other cards use. I need to get better at using anchor’s would save me time and I can get them up quicker but I am changing them all so I can better scale on smaller screens. BTW your original lovelace home screen was my inspiration to do my very first lovelace layout you’re responsible in half of my life being spent on HA for the last 2 years so thanks.
1 Like
Bit of a WIP of my “Server” view - its a few hours work to manipulate everything
I’m putting all my repeated cards into reusable templates (rather then anchors) like above
Haha, you’re welcome 
Got a bit frustrated with the amount of extra config that was required to maintain that view, so I wrote a custom-card using the monitor_docker sensors
nice overview, would you be able to share your card?
Its not easily shareable, but more then happy for people to use it if they are willing to have a tinker
you will need to change line 42 to point to a default graphic in your setup:
I use the monitor_docker integration to create the entities that power the card
- type: custom:docker-card
name:
logo: /local/systemicons/ubnt.png
entitypart: tbsh01_monitordocker_unifi
name - Name of Container it will pull the name from the Switch entity if not provided
logo - Logo to use, it will use the default (Line 42 of the file) if not provided
entitypart - part of the entity id used to find all the entities (see example below)
2 Likes
Would love to see this docker card added to HACS
Did you make another card for the docker host stats with the running/paused/stopped containers like the previous view?
Very useful card, less code required for each container.
Would be great if you could add the ability to start stop containers.
Yes - but thats just using bar-card and config-template card (Lines 222 to 298)
I’ll see what I can do
1 Like
