Solution unRaid - ArveVM/MyAssistedHome GitHub Wiki

• I'm actually rather fond of facts,, so looking at server/docker performance ,, is a must ;)

• Thomas,, pointed me to https://github.com/EvisHome where I started picking up the smallest of things,,,

Click to unfold list of booring requirements, tips etc

How to copy/install one of my solutions

Functionality required (other than what is builtin in my version of HA):

• HACS: Lovelace-Mushroom card-package
• HACS: browser mod - for popup-functionality
• Unraid API
• Glances
• Monitor Docker
• HACS: custom:auto-entities
• Packages-folder, to copy entire yaml-config in one file
• YAML-dashboard - easy share config, can use !include and re-use cards
  • as an option you can copy dashboard-config to UI-dashboard/card - but not if !include is used,,

template-editor test-code:

n/a

• unRaid dockers running - View al dockers not running,, can turn them on
• unRaid dockers not running - View al dockers not running,, can turn them on
• unRaid dockers running - View al dockers not running,, can turn them on

• Created sensors to count different KPI's of my HA-installations "growth". Added sensors as long term statistics - so we can see (and graph) long term trends
• Adding sub-solutions for each type of stats, so that it is easier to grasp concept of each "kpi-group"
  • Adding card for each sub-solution
• Adding tabbed card to combine all sub-solutions in one card - with link to documentation.
  • and a chip to easily place link on dashboard.

Card/chip preview	Card	Config	Use case(s)
insert card-picture	insert card-link	link to yaml-config	list use-cases - Link to Solution documentation
	HAstats-card	n/a	- Overview of all cards in a tabbed-card - Link to Solution documentation

• Sub-solution, own card and config-yaml
• Start-time integration gives sensor with attributes of all loaded integration and their "startup-time".
• Using history-explorer-graph with long-term statistics enabled, so the configured sensor with long term statistics enabled are visible.

Card/chip preview	Card	Config	Use case(s)
	HAstats_integrations_card	HAstats_integrations.yaml	- view development in number of integrations - click to list all integrations
	Popup "Integrations by startup-time"	- list all integrations - see startup-times (dependencies will heavily skew this!!)

• Sub-solution, own card and config-yaml
• Manually created sensors to count entities pr respective domains.
• Using history-explorer-graph with long-term statistics enabled, so the configured sensor with long term statistics enabled are visible.

Card/chip preview	Card	Config	Use case(s)
	HAstats_ebd_card	hastats_ebd.yaml	- Overview of count in entities - click for details
	Popup "Total"
	Popup "Sensors"
	Popup "Automations"
	etc on scripts and lights

NB; sensor.hastats_ebd_total_checksum - counts sum of grouped-sensors in sensors against total number of sensors and if not 0 then you are missing sensor-count for one "entity-type" - look in troubleshooting for code

• Sub-solution, own card and config-yaml
• Organized yaml-config in separate folder, and the same with Dashboard
• Manually created sensors to count yaml-lines pr respective folders.
• Using history-explorer-graph with long-term statistics enabled, so the configured sensor with long term statistics enabled are visible.
• Please note that YAML-count includes empty lines and comments,,, but I'll further invest in using wiki and not config/dashboard-yaml for comments,, so it will get realistic sometime in the future.

Card/chip preview	Card	Config	Use case(s)
	HAstats_yaml_lines_card	hastats_yaml_lines.yaml	- see development in config/dashboard #lines

• Sub-solution, own card and config-yaml
• Created sensor to monitor db-size
• Using history-explorer-graph with long-term statistics enabled, so the configured sensor with long term statistics enabled are visible.

Card/chip preview	Card	Config	Use case(s)
	HAstats_db_card	hastats_db.yaml	view development in: - DB-size - states - longterm-statistics - short-term-statistics

• might want to move the system_monitor.yaml sensors here (as there is no config of the integration)
• general performance on server,,,

• Oct 2023: improved dockumentation, setup autoenties pr docker
• Aug 2023: Initial setup