2024-10-25 21:58:32 +02:00
# Smart cards
2021-01-13 21:22:35 +01:00
2025-09-19 21:29:09 +02:00
Smart cards provide specific integrations for external services. They display additional information and extra features beyond basic service card. Smart cards are enabled by adding a `type` key to the service item in your YAML configuration.
Each service integration has different requirements and may need additional configuration parameters (see card list below).
2021-12-20 16:11:15 -05:00
2024-10-25 21:58:32 +02:00
> [!WARNING]
2025-09-19 21:29:09 +02:00
> Your `config.yml` file is exposed at `/assets/config.yml` via HTTP. Any sensitive information (like API keys)
> in this file is visible to anyone who can access your Homer instance. Only include API keys if your Homer
> instance is protected by authentication or access controls **or use a proxy like [`CORSair`](https://github.com/bastienwirtz/corsair)
> to inject your credentials safely**, using environment variable on the server side.
2024-10-25 21:58:32 +02:00
2025-09-19 21:29:09 +02:00
Available services are located in `src/components/` :
2021-01-13 21:22:35 +01:00
2024-10-25 21:58:32 +02:00
- [Common options ](#common-options )
2024-11-18 22:17:46 +01:00
- [AdGuard Home ](#adguard-home )
- [CopyToClipboard ](#copy-to-clipboard )
2024-12-20 21:57:03 -08:00
- [Docuseal ](#docuseal )
2025-03-30 16:26:44 +02:00
- [Docker Socket Proxy ](#docker-socket-proxy )
2024-11-18 22:17:46 +01:00
- [Emby / Jellyfin ](#emby--jellyfin )
- [FreshRSS ](#freshrss )
2023-05-21 12:18:22 -07:00
- [Gitea / Forgejo ](#gitea--forgejo )
2024-11-23 07:00:01 -08:00
- [Glances ](#glances )
2024-11-18 22:17:46 +01:00
- [Gotify ](#gotify )
- [Healthchecks ](#healthchecks )
- [Home Assistant ](#home-assistant )
- [Immich ](#immich )
- [Jellystat ](#jellystat )
2024-10-25 21:58:32 +02:00
- [Lidarr, Prowlarr, Sonarr, Readarr and Radarr ](#lidarr-prowlarr-sonarr-readarr-and-radarr )
2025-03-19 22:25:34 +01:00
- [Linkding ](#linkding )
2025-03-26 21:44:50 +01:00
- [Matrix ](#matrix )
2024-11-18 22:17:46 +01:00
- [Mealie ](#mealie )
- [Medusa ](#medusa )
- [Nextcloud ](#nextcloud )
- [OctoPrint / Moonraker ](#octoprintmoonraker )
2024-12-01 05:29:36 -08:00
- [Olivetin ](#olivetin )
2024-11-18 22:17:46 +01:00
- [OpenHAB ](#openhab )
- [OpenWeatherMap ](#openweathermap )
2025-09-21 08:36:04 -04:00
- [Paperless-NGX ](#paperlessng )
2024-11-18 22:17:46 +01:00
- [PeaNUT ](#peanut )
- [PiAlert ](#pialert )
- [PiHole ](#pihole )
2024-10-25 21:58:32 +02:00
- [Ping ](#ping )
2025-03-30 16:26:44 +02:00
- [Plex ](#plex )
2024-10-25 21:58:32 +02:00
- [Portainer ](#portainer )
2024-11-18 22:17:46 +01:00
- [Prometheus ](#prometheus )
2024-10-25 21:58:32 +02:00
- [Proxmox ](#proxmox )
- [qBittorrent ](#qbittorrent )
2024-11-18 22:17:46 +01:00
- [rTorrent ](#rtorrent )
2024-10-25 21:58:32 +02:00
- [SABnzbd ](#sabnzbd )
2024-11-18 22:17:46 +01:00
- [Scrutiny ](#scrutiny )
- [Speedtest Tracker ](#speedtesttracker )
- [Tautulli ](#tautulli )
2024-10-25 21:58:32 +02:00
- [Tdarr ](#tdarr )
2024-12-01 05:29:36 -08:00
- [Traefik ](#traefik )
2025-03-27 00:25:18 +01:00
- [TrueNas Scale ](#truenas-scale )
2024-11-18 22:17:46 +01:00
- [Uptime Kuma ](#uptime-kuma )
2025-03-26 21:55:37 +01:00
- [Vaultwarden ](#vaultwarden )
2024-12-01 05:29:36 -08:00
- [Wallabag ](#wallabag )
2024-11-18 22:17:46 +01:00
- [What's Up Docker ](#whats-up-docker )
2024-10-25 21:58:32 +02:00
> [!IMPORTANT]
2025-09-19 21:29:09 +02:00
> Smart cards that interact with external services are subject to CORS restrictions, therefore require one of the following:
2024-11-24 09:30:55 +01:00
>
2025-09-19 21:29:09 +02:00
> - All services hosted on the **same domain** as Homer (mydomain.tld/pihole, mydomain.tld/proxmox) to avoid cross-domain request entirely.
> - All services configured to **accept cross-site requests** by sending the necessary CORS headers (either directly in service configuration or via proxy).
> - **Use a proxy** to add the necessary CORS headers (lot of options, some of them described [here](https://enable-cors.org/server.html). Also check [`CORSair`](https://github.com/bastienwirtz/corsair), a light and simple solution)
2024-11-24 09:30:55 +01:00
>
2025-09-19 21:29:09 +02:00
> If you experience any issues, see the [troubleshooting](troubleshooting.md#my-service-card-doesnt-work-nothing-appears-or-offline-status-is-displayed-pi-hole-sonarr-ping-) page.
2021-10-11 18:38:13 +02:00
2021-10-10 10:47:23 +02:00
## Common options
```yaml
2021-10-11 18:38:13 +02:00
- name: "My Service"
2025-09-19 21:29:09 +02:00
type: "<type>"
logo: "assets/tools/sample.png" # Optional
url: https://my-service.url # Optional: Card link and API base url unless 'endpoint' is provided (see below)
endpoint: https://my-service-api.url # Optional: alternative base URL used to fetch service data when necessary.
2021-10-10 20:57:04 +02:00
useCredentials: false # Optional: Override global proxy.useCredentials configuration.
2024-10-27 14:40:43 +01:00
headers: # Optional: Override global proxy.headers configuration.
2021-10-10 10:47:23 +02:00
```
2025-09-19 21:29:09 +02:00
If a subtitle is provided, (using the `subtitle` configuration key), **it will override (hide) ** any custom information displayed on the subtitle line by the custom integration.
2024-11-18 22:17:46 +01:00
## AdGuard Home
2021-01-13 21:22:35 +01:00
2025-09-19 21:29:09 +02:00
Displays AdGuard Home protection status and blocked query statistics.
2021-01-13 21:22:35 +01:00
2024-11-18 22:17:46 +01:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "AdGuard Home"
2024-11-18 22:17:46 +01:00
type: "AdGuardHome"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-18 22:17:46 +01:00
```
2025-09-19 21:29:09 +02:00
> **Note**: If AdGuard Home’ s web user is password-protected, you must pass Authorization HTTP header along with all requests. It can be done using a proxy or adding the following to the item configuration:
>
> ```yaml
> headers:
> Authorization: "Basic <base64-encoded for username:password>"
> ```
2024-11-18 22:17:46 +01:00
2025-09-19 21:29:09 +02:00
## Copy to Clipboard
2024-11-18 22:17:46 +01:00
2025-09-19 21:29:09 +02:00
Displays a service card with a copy button that copies the specified text to your clipboard when clicked.
2021-01-13 21:22:35 +01:00
2021-09-25 12:12:22 +02:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Copy me!"
type: "CopyToClipboard"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
subtitle: "Click the copy icon to copy text"
2024-11-18 22:17:46 +01:00
clipboard: "this text will be copied to your clipboard"
2025-09-19 21:29:09 +02:00
url: "https://optional-link.com" # optional: opens when clicking the card (not the copy button)
2021-01-13 21:22:35 +01:00
```
2025-04-22 12:04:55 +01:00
## Docker Socket Proxy
2025-03-30 16:24:06 +02:00
2025-09-19 21:29:09 +02:00
Displays counts of running, stopped, and error containers from Docker Socket Proxy.
2025-03-30 16:24:06 +02:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Docker"
2025-03-30 16:24:06 +02:00
type: "DockerSocketProxy"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
endpoint: "https://my-service-api.url:port"
2025-03-30 16:24:06 +02:00
```
2024-12-20 21:57:03 -08:00
## Docuseal
2025-09-19 21:29:09 +02:00
Displays the Docuseal version.
2024-12-20 21:57:03 -08:00
```yaml
- name: Docuseal
type: Docuseal
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-12-20 21:57:03 -08:00
```
2024-11-18 22:17:46 +01:00
## Emby / Jellyfin
2023-02-19 15:18:56 -05:00
2025-09-19 21:29:09 +02:00
Displays stats from your Emby or Jellyfin server.
The `libraryType` configuration let you choose which stats to show.
2021-01-13 21:22:35 +01:00
2024-11-18 22:17:46 +01:00
```yaml
- name: "Emby"
type: "Emby"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-18 22:17:46 +01:00
apikey: "<---insert-api-key-here--->"
2025-09-19 21:29:09 +02:00
libraryType: "music" # Choose which stats to show. Can be one of: music, series or movies.
2024-11-18 22:17:46 +01:00
```
## FreshRSS
2025-09-19 21:29:09 +02:00
Displays unread article count and total subscriptions from your FreshRSS server.
2021-01-13 21:22:35 +01:00
2021-09-25 12:12:22 +02:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "FreshRSS"
type: "FreshRSS"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2024-11-18 22:17:46 +01:00
updateInterval: 5000 # (Optional) Interval (in ms) for updating the stats
2025-09-19 21:29:09 +02:00
username: "<---your-username--->"
password: "<---your-password--->"
2021-01-13 21:22:35 +01:00
```
2021-01-28 13:02:18 +01:00
2023-05-21 12:18:22 -07:00
## Gitea / Forgejo
2025-09-19 21:29:09 +02:00
Displays a Gitea / Forgejo version.
2023-05-21 12:18:22 -07:00
```yaml
- name: Forgejo
type: Gitea
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2023-05-21 12:18:22 -07:00
```
2024-11-23 07:00:01 -08:00
## Glances
2025-09-19 21:29:09 +02:00
Displays system metrics (CPU, memory, swap, load) from a Glances server.
```yaml
- name: "System Metrics"
type: "Glances"
icon: "fa-solid fa-heart-pulse"
url: https://my-service.url
stats: [cpu, mem] # Options: load, cpu, mem, swap
```
2024-11-23 07:00:01 -08:00
2025-09-19 21:29:09 +02:00
If you don't already have a glances server up and running, here is a sample Docker compose file to get you started:
2024-11-23 07:00:01 -08:00
```yml
---
services:
glances:
image: nicolargo/glances:latest
container_name: glances
environment:
- TZ=Europe/Rome
- GLANCES_OPT=-w
ports:
- 61208:61208
restart: unless-stopped
```
2024-11-18 22:17:46 +01:00
## Gotify
2021-09-13 13:09:40 -07:00
2025-09-19 21:29:09 +02:00
Displays the number of outstanding messages and system health status.
2024-11-18 22:17:46 +01:00
```yaml
- name: "Gotify"
type: "Gotify"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
apikey: "<---insert-client-token-here--->"
2024-11-18 22:17:46 +01:00
```
2025-09-19 21:29:09 +02:00
**API Token**: Use a **client token ** (not an app token).
2024-11-18 22:17:46 +01:00
## Healthchecks
2025-09-19 21:29:09 +02:00
Displays status counts (up/down/grace) from your Healthchecks monitoring service.
2021-09-25 12:12:22 +02:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Healthchecks"
2024-11-18 22:17:46 +01:00
type: "Healthchecks"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2022-11-27 18:41:12 +01:00
apikey: "<---insert-api-key-here--->"
2021-03-11 15:03:56 +01:00
```
2021-09-25 12:12:22 +02:00
2025-09-19 21:29:09 +02:00
**API Key**: Found in Healthchecks web interface under **Settings > API Access > API key (read-only) ** .
2024-11-18 22:17:46 +01:00
## Home Assistant
2025-09-19 21:29:09 +02:00
Displays Home Assistant instance status, version, location, and entity count.
2024-11-18 22:17:46 +01:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Home Assistant"
2024-11-18 22:17:46 +01:00
type: "HomeAssistant"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
apikey: "<---insert-long-lived-access-token-here--->"
items: [] # optional: "name", "version", "entities"
separator: " " # optional
2024-11-18 22:17:46 +01:00
```
2025-09-19 21:29:09 +02:00
**API Token**: Create a long-lived access token in Home Assistant:
1. Go to **Profile > Security > Long-lived access tokens **
2. Click **Create Token **
**CORS Configuration**: Edit Home Assistant `configuration.yml` and add Homer's IP:
```yaml
http:
cors_allowed_origins:
- "http://homer.local:8080"
- "https://your-homer-domain.com"
```
2024-11-18 22:17:46 +01:00
## Immich
2025-09-19 21:29:09 +02:00
Displays user count, photo/video counts, and storage usage from your Immich server.
2024-11-18 22:17:46 +01:00
```yaml
- name: "Immich"
type: "Immich"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
apikey: "<---insert-api-key-here--->"
2024-11-18 22:17:46 +01:00
```
2025-09-19 21:29:09 +02:00
**Requirements**: Immich server version `1.118.0` or later
**API Key**: Create an API key in Immich web interface under **Administration > API Keys **
2024-11-18 22:17:46 +01:00
2025-09-19 21:29:09 +02:00
## Jellystat
2024-11-18 22:17:46 +01:00
2025-09-19 21:29:09 +02:00
Display the number of concurrent streams on your jellyfin server.
2024-11-18 22:17:46 +01:00
```yaml
- name: "Jellystat"
type: "Jellystat"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-18 22:17:46 +01:00
apikey: "<---insert-api-key-here--->"
```
2025-09-19 21:29:09 +02:00
**API Key**: You can create an API key in the dashboard of you jellystat server: settings/API Keys -> Add Key
2021-03-11 15:03:56 +01:00
2023-07-22 22:55:00 +02:00
## Lidarr, Prowlarr, Sonarr, Readarr and Radarr
2021-03-11 15:03:56 +01:00
2025-09-19 21:29:09 +02:00
Displays Activity (blue), Missing (purple) Warning (orange) or Error (red) notifications bubbles from the Lidarr, Readarr, Radarr or Sonarr application.
Two lines are needed in the `config.yml` :
2021-09-25 12:12:22 +02:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Lidarr"
type: "Lidarr" # "Lidarr" "Prowlarr", "Radarr" or "Sonarr"
logo: "assets/tools/sample.png"
url: https://my-service.url
2022-11-20 06:31:03 -05:00
checkInterval: 5000 # (Optional) Interval (in ms) for updating the status
2025-09-19 21:29:09 +02:00
apikey: "<---insert-api-key-here--->"
2021-03-11 15:03:56 +01:00
```
2021-09-25 12:12:22 +02:00
2023-07-22 22:55:00 +02:00
The url must be the root url of Lidarr, Prowlarr, Readarr, Radarr or Sonarr application.
2022-02-01 17:05:23 +01:00
2025-09-19 21:29:09 +02:00
**API Key**: The Lidarr, Prowlarr, Readarr, Radarr or Sonarr API key can be found in `Settings` > `General` . It is needed to access the API.
> [!IMPORTANT]
> **Radarr API V3 support**: If you are using an older version of Radarr or Sonarr which don't support the new V3 api endpoints, add the following line to your service config `"legacyApi: true"`
2021-07-14 15:48:57 +02:00
2025-03-19 22:25:34 +01:00
## Linkding
2025-04-09 12:01:06 +02:00
This integration makes it possible to query Linkding and list multiple results from Linkding.
Linkding has to be configured with CORS enabled. Linkding does not support that, but a reverse proxy in front can fix that.
2025-09-19 21:29:09 +02:00
This integration supports at max 15 results from Linkding, but you can add it multiple times to you dashboard with different queries to retrieve what you need.
2025-03-19 22:25:34 +01:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Linkding"
type: "Linkding"
url: https://my-service.url
token: "<---insert-api-key-here--->"
limit: 10 # Maximum number of items returned by Linkding, minimal 1 and max 15
query: "#ToDo #Homer " # query to do on Linkding. Use #tagname to search for tags
2025-03-19 22:25:34 +01:00
```
2025-03-26 21:44:50 +01:00
## Matrix
2025-09-19 21:29:09 +02:00
Displays a Matrix version, and shows if the server is online.
2025-03-26 21:44:50 +01:00
```yaml
- name: "Matrix - Server"
type: "Matrix"
logo: "assets/tools/sample.png"
url: "http://matrix.example.com"
```
2024-11-18 22:17:46 +01:00
## Mealie
2021-07-14 15:48:57 +02:00
2025-09-19 21:29:09 +02:00
Displays the number of recipes Mealie is keeping organized or the planned meal for today if one is planned.
2024-12-09 08:02:33 -07:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Mealie"
2024-12-09 08:02:33 -07:00
type: "Mealie"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-12-09 08:02:33 -07:00
apikey: "<---insert-api-key-here--->"
```
2024-11-18 22:17:46 +01:00
2025-09-19 21:29:09 +02:00
**API Key**: You will have to set an API key in the field `apikey` which can be created in your Mealie installation.
The API page can be found: Click on hamburger menu -> Click on your profile -> Click on "Manage your API Tokens"
2024-11-18 22:17:46 +01:00
## Medusa
2025-09-19 21:29:09 +02:00
Displays News (grey), Warning (orange) or Error (red) notifications bubbles from the Medusa application.
2021-10-12 11:37:30 +03:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Medusa"
2024-11-18 22:17:46 +01:00
type: "Medusa"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2022-11-27 18:41:12 +01:00
apikey: "<---insert-api-key-here--->"
2021-10-12 11:37:30 +03:00
```
2024-11-18 22:17:46 +01:00
The url must be the root url of Medusa application.
2025-09-19 21:29:09 +02:00
**API Key**: The Medusa API key can be found in General configuration > Interface. It is needed to access Medusa API.
2021-07-14 15:48:57 +02:00
2024-11-18 22:17:46 +01:00
## Nextcloud
2021-07-14 15:48:57 +02:00
2025-09-19 21:29:09 +02:00
Displays Nextcloud version and shows if Nextcloud is online, offline, or in [maintenance
2024-11-18 22:17:46 +01:00
mode](https://docs.nextcloud.com/server/stable/admin_manual/maintenance/upgrade.html#maintenance -mode).
2021-10-06 09:17:46 -07:00
2021-10-06 09:16:17 -07:00
```yaml
2024-11-18 22:17:46 +01:00
- name: Nextcloud
type: Nextcloud
logo: assets/tools/sample.png
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2021-10-06 09:16:17 -07:00
```
2021-10-10 22:20:34 +02:00
2024-11-18 22:17:46 +01:00
## OctoPrint/Moonraker
2021-10-10 22:20:34 +02:00
2024-11-18 22:17:46 +01:00
The OctoPrint/Moonraker service only needs an `apikey` & `endpoint` and optionally a `display` or `url` option. `url` can be used when you click on the service it will launch the `url`
Moonraker's API mimmicks a few of OctoPrint's endpoints which makes these services compatible. See <https://moonraker.readthedocs.io/en/latest/web_api/#octoprint -api-emulation> for details.
2021-10-10 22:20:34 +02:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Octoprint"
type: "OctoPrint"
2025-09-19 21:29:09 +02:00
logo: assets/tools/sample.png
endpoint: "https://my-service-api.url:port"
apikey: "<---insert-api-key-here--->"
display: "text" # 'text' or 'bar'. Default to `text` .
2021-10-10 22:20:34 +02:00
```
2021-10-27 21:53:39 +02:00
2024-12-01 05:29:36 -08:00
## Olivetin
2025-09-19 21:29:09 +02:00
Displays a Olivetin version.
2024-12-01 05:29:36 -08:00
```yaml
- name: Olivetin
type: Olivetin
logo: assets/tools/sample.png
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2024-12-01 05:29:36 -08:00
```
2024-11-18 22:17:46 +01:00
## OpenHAB
2024-11-15 00:09:28 +03:00
2025-09-19 21:29:09 +02:00
Displays OpenHAB system status, things count, and items count.
2024-11-15 00:09:28 +03:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "OpenHAB"
type: "OpenHAB"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-18 22:17:46 +01:00
apikey: "<---insert-api-key-here--->"
2025-09-19 21:29:09 +02:00
things: true # query things API for counts
items: true # query items API for counts
2024-11-15 00:09:28 +03:00
```
2025-09-19 21:29:09 +02:00
**API Token**: Create an API token following the [official OpenHAB documentation ](https://www.openhab.org/docs/configuration/apitokens.html )
**CORS Configuration**: Edit `services/runtime.cfg` and add:
```ini
org.openhab.cors:enable=true
```
2024-11-18 22:17:46 +01:00
## OpenWeatherMap
Using the OpenWeatherMap service you can display weather information about a given location.
The following configuration is available for the OpenWeatherMap service:
2022-04-07 22:06:26 +02:00
2021-10-27 21:53:39 +02:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Weather"
2025-09-19 21:29:09 +02:00
type: "OpenWeather"
apikey: "<---insert-api-key-here--->" # Request one from https://openweathermap.org/api.
2024-11-18 22:17:46 +01:00
location: "Amsterdam" # your location.
locationId: "2759794" # Optional: Specify OpenWeatherMap city ID for better accuracy
units: "metric" # units to display temperature. Can be one of: metric, imperial, kelvin. Defaults to kelvin.
background: "square" # choose which type of background you want behind the image. Can be one of: square, circle, none. Defaults to none.
2025-09-19 21:29:09 +02:00
2021-10-27 21:53:39 +02:00
```
2022-04-07 22:33:20 +02:00
2024-11-18 22:17:46 +01:00
**Remarks:**
If for some reason your city can't be found by entering the name in the `location` property, you could also try to configure the OWM city ID in the `locationId` property. To retrieve your specific City ID, go to the [OWM website ](https://openweathermap.org ), search for your city and retrieve the ID from the URL (for example, the City ID of Amsterdam is 2759794).
2022-03-01 20:55:45 -05:00
2025-09-21 08:36:04 -04:00
## Paperless-NGX
2022-03-01 20:55:45 -05:00
2025-09-19 21:29:09 +02:00
Displays total number of documents stored.
2022-03-01 20:55:45 -05:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Paperless"
2024-11-18 22:17:46 +01:00
type: "PaperlessNG"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2022-11-27 18:41:12 +01:00
apikey: "<---insert-api-key-here--->"
2022-03-01 20:55:45 -05:00
```
2022-03-28 20:41:19 +03:00
2025-09-19 21:29:09 +02:00
**API Key**: API key can be generated in Settings > Administration > Auth Tokens
2022-03-28 20:41:19 +03:00
2024-11-18 22:17:46 +01:00
## PeaNUT
2025-09-19 21:29:09 +02:00
Displays current status and UPS load of the UPS device.
2022-03-28 20:41:19 +03:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "PeaNUT"
type: PeaNUT
2022-03-28 20:41:19 +03:00
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2024-11-18 22:17:46 +01:00
# device: "ups" # The ID of the device
2022-03-28 20:41:19 +03:00
```
2022-04-20 18:13:55 +05:30
2024-11-18 22:17:46 +01:00
## PiAlert
2022-04-20 18:13:55 +05:30
2025-09-19 21:29:09 +02:00
Displays stats from your PiAlert server.
2022-04-20 18:13:55 +05:30
```yaml
2024-11-18 22:17:46 +01:00
- name: "PiAlert"
type: "PiAlert"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-18 22:17:46 +01:00
updateInterval: 5000 # (Optional) Interval (in ms) for updating the stats
2022-04-20 18:13:55 +05:30
```
2022-04-29 14:18:59 -04:00
2024-11-18 22:17:46 +01:00
## PiHole
2022-04-29 14:18:59 -04:00
2025-09-19 21:29:09 +02:00
Displays info about your local PiHole instance right on your Homer dashboard.
2022-04-29 14:18:59 -04:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Pi-hole"
2025-09-19 21:29:09 +02:00
type: "PiHole"
2022-04-29 14:18:59 -04:00
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
# endpoint: "https://my-service-api.url" # optional, For v6 API, this is the base URL used to fetch Pi-hole data overwriting the url
2024-11-18 22:17:46 +01:00
apikey: "<---insert-api-key-here--->" # optional, needed if web interface is password protected
2025-04-19 00:13:05 +02:00
apiVersion: 5 # optional, defaults to 5. Use 6 if your PiHole instance uses API v6
2025-04-19 14:19:28 +02:00
checkInterval: 3000 # optional, defaults to 300000. interval in ms to check Pi-hole status
2022-04-29 14:18:59 -04:00
```
2025-09-19 21:29:09 +02:00
**API Key**: Required only if Pi-hole web interface is password protected. Go to **Settings > API/Web Interface > Show API token **
**API Versions**:
- **v5** (default): Uses legacy API endpoints
- **v6**: Uses modern API with session management - set `apiVersion: 6`
2024-11-18 22:17:46 +01:00
## Ping
2025-09-19 21:29:09 +02:00
Checks if the target link is available and displays the round trip time (RTT) of the request.
By default the HEAD method is used but it can be configured to use GET using the optional `method` property.
Optionally, use `successCodes` to define which HTTP response status codes should be considered as available status.
2022-04-29 14:18:59 -04:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Awesome app"
type: Ping
2022-04-29 14:18:59 -04:00
logo: "assets/tools/sample.png"
2024-11-18 22:17:46 +01:00
url: "https://www.wikipedia.org/"
# method: "head"
2025-01-16 20:40:22 +02:00
# successCodes: [200, 418] # Optional, default to all 2xx HTTP response status codes
# timeout: 500 # Timeout in ms before ping is aborted. Default 2000
# subtitle: "Bookmark example" # By default, request round trip time is displayed when subtitle is not set
# updateInterval: 5000 # (Optional) Interval (in ms) for updating ping status
2022-04-29 14:18:59 -04:00
```
2022-07-11 22:07:15 +02:00
2025-03-30 16:24:06 +02:00
## Plex
2025-09-19 21:29:09 +02:00
Displays active streams, total movies, and total TV series from your Plex server.
2025-03-30 16:24:06 +02:00
```yaml
2025-09-19 21:29:09 +02:00
- name: "Plex"
2025-03-30 16:24:06 +02:00
type: "Plex"
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: "https://my-service.url/web"
endpoint: "https://my-service.url"
token: "<---insert-plex-token-here--->"
2025-03-30 16:24:06 +02:00
```
2025-09-19 21:29:09 +02:00
**Plex Token**: See [How to find your Plex token ](https://www.plexopedia.com/plex-media-server/general/plex-token/ )
2022-07-12 13:28:07 -07:00
2025-09-19 21:29:09 +02:00
## Portainer
2022-06-23 19:07:55 +02:00
2025-09-19 21:29:09 +02:00
Displays container counts (running/dead/misc), version, and online status from your Portainer instance.
2022-06-23 19:07:55 +02:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Portainer"
type: "Portainer"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2022-11-27 18:41:12 +01:00
apikey: "<---insert-api-key-here--->"
2025-09-19 21:29:09 +02:00
environments: # optional: specific environments to check
- "raspberry"
- "local"
2022-06-23 19:07:55 +02:00
```
2025-09-19 21:29:09 +02:00
**Requirements**: Portainer version 1.11 or later
2022-10-31 10:09:59 +01:00
2025-09-19 21:29:09 +02:00
**API Key**: Generate an access token in Portainer UI. See [Creating an Access Token ](https://docs.portainer.io/api/access#creating-an-access-token )
## Prometheus
2022-10-31 10:09:59 +01:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Prometheus"
2025-09-19 21:29:09 +02:00
type: "Prometheus"
2022-10-31 10:09:59 +01:00
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2022-11-14 19:52:33 -03:00
```
2022-10-31 10:09:59 +01:00
2022-10-08 15:54:37 +02:00
## Proxmox
2025-09-19 21:29:09 +02:00
Displays status information of a Proxmox node (VMs running and disk, memory and cpu used).
2022-10-08 15:54:37 +02:00
```yaml
- name: "Proxmox - Node"
type: "Proxmox"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2022-10-08 15:54:37 +02:00
node: "your-node-name"
warning_value: 50
danger_value: 80
api_token: "PVEAPIToken=root@pam !your-api-token-name=your-api-token-key"
2022-11-05 15:21:18 +01:00
# values below this line are optional (default value are false/empty):
hide_decimals: true # removes decimals from stats values.
2022-12-20 20:47:56 +01:00
hide: [] # hides information. Possible values are "vms", "vms_total", "lxcs", "lxcs_total", "disk", "mem" and "cpu".
2022-11-05 15:21:18 +01:00
small_font_on_small_screens: true # uses small font on small screens (like mobile)
small_font_on_desktop: true # uses small font on desktops (just in case you're showing much info)
2022-10-30 18:32:51 +01:00
```
2025-09-19 21:29:09 +02:00
**API Key**: You can set it up in Proxmox under Permissions > API Tokens. You also need to know the realm the user of the API Token is assigned to (by default pam).
The API Token (or the user assigned to that token if not separated permissions is checked) are this:
| Path | Permission | Comments |
|---------------------|------------|-------------------------------------------------------------------|
| /nodes/\<your-node> | Sys.Audit | |
| /vms/\<id-vm> | VM.Audit | You need to have this permission on any VM you want to be counted |
It is highly recommended that you create and API Token with only these permissions on a read-only mode.
2022-10-30 18:32:51 +01:00
## qBittorrent
2025-09-19 21:29:09 +02:00
Displays the global upload and download rates, as well as the number of torrents
2022-10-30 18:32:51 +01:00
listed. The service communicates with the qBittorrent API interface which needs
to be accessible from the browser. Please consult
[the instructions ](https://github.com/qbittorrent/qBittorrent/pull/12579 )
2025-09-19 21:29:09 +02:00
for setting up qBittorrent.
2022-10-30 18:32:51 +01:00
```yaml
- name: "qBittorrent"
type: "qBittorrent"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url # Your rTorrent web UI, f.e. ruTorrent or Flood.
2022-10-30 18:32:51 +01:00
rateInterval: 2000 # Interval for updating the download and upload rates.
torrentInterval: 5000 # Interval for updating the torrent count.
```
2022-11-05 15:11:48 +01:00
2024-11-18 22:17:46 +01:00
## rTorrent
2022-11-05 22:44:25 +01:00
2025-09-19 21:29:09 +02:00
Displays the global upload and download rates, as well as the number of torrents
2024-11-18 22:17:46 +01:00
listed in rTorrent. The service communicates with the rTorrent XML-RPC interface which needs
to be accessible from the browser. Please consult
[the instructions ](https://github.com/rakshasa/rtorrent-doc/blob/master/RPC-Setup-XMLRPC.md )
2025-09-19 21:29:09 +02:00
for setting up rTorrent.
2022-11-05 22:44:25 +01:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "rTorrent"
type: "Rtorrent"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: "https://my-service.url" # Your rTorrent web UI, f.e. ruTorrent or Flood.
xmlrpc: "https://my-service.url:port" # Reverse proxy for rTorrent's XML-RPC.
2024-11-18 22:17:46 +01:00
rateInterval: 5000 # Interval for updating the download and upload rates.
torrentInterval: 60000 # Interval for updating the torrent count.
username: "username" # Username for logging into rTorrent (if applicable).
password: "password" # Password for logging into rTorrent (if applicable).
2022-11-14 19:52:33 -03:00
```
2022-11-19 10:14:22 -05:00
## SABnzbd
2025-09-19 21:29:09 +02:00
Displays the number of currently active downloads on your SABnzbd instance.
2022-11-19 10:14:22 -05:00
```yaml
- name: "SABnzbd"
type: "SABnzbd"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
apikey: "<---insert-api-key-here--->"
2022-11-19 10:14:22 -05:00
downloadInterval: 5000 # (Optional) Interval (in ms) for updating the download count
```
2022-11-27 18:41:12 +01:00
2025-09-19 21:29:09 +02:00
**API Key**: An API key is required, and can be obtained from the "Config" > "General" section of the SABnzbd config in the web UI.
2024-11-11 11:02:17 +03:00
## Scrutiny
2025-09-19 21:29:09 +02:00
Displays info about the total number of disk passed and failed S.M.A.R.T and scrutiny checks
2024-11-11 11:02:17 +03:00
```yaml
- name: "Scrutiny"
type: "Scrutiny"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-11 11:02:17 +03:00
updateInterval: 5000 # (Optional) Interval (in ms) for updating the status
```
2024-11-18 22:17:46 +01:00
## SpeedtestTracker
2022-11-27 18:41:12 +01:00
2025-09-19 21:29:09 +02:00
Displays the download and upload speeds in Mbit/s and the ping in ms.
2022-11-27 18:41:12 +01:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Speedtest Tracker"
type: "SpeedtestTracker"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2023-02-07 02:38:37 -05:00
```
2024-11-18 22:17:46 +01:00
## Tautulli
2023-02-07 02:38:37 -05:00
2025-09-19 21:29:09 +02:00
Displays the number of currently active streams on you Plex instance.
2023-02-07 02:38:37 -05:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Tautulli"
type: "Tautulli"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
checkInterval: 5000 # (Optional) Interval (in ms) for updating the status
2024-11-18 22:17:46 +01:00
apikey: "<---insert-api-key-here--->"
2023-08-06 14:48:52 -05:00
```
2024-02-07 18:09:48 +01:00
2025-09-19 21:29:09 +02:00
**API Key**: An API key is required, and can be obtained from the "Web Interface" section of settings on the Tautulli web UI.
2024-11-18 22:17:46 +01:00
Because the service type and link don't necessarily have to match, you could
even make the service type Tautulli on your Plex card and provide a separate
endpoint pointing to Tautulli!
2024-02-07 18:09:48 +01:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Plex"
type: "Tautulli"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-plex.url/web # Plex
endpoint: https://my-tautulli.url # Tautulli
2024-02-07 18:09:48 +01:00
apikey: "<---insert-api-key-here--->"
```
2024-05-20 19:47:04 +02:00
2024-11-18 22:17:46 +01:00
## Tdarr
2024-06-01 16:10:35 +02:00
2025-09-19 21:29:09 +02:00
Displays the number of currently queued items for transcoding on your Tdarr instance as well as the number of errored items.
2024-06-01 16:10:35 +02:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Tdarr"
type: "Tdarr"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-11-18 22:17:46 +01:00
checkInterval: 5000 # (Optional) Interval (in ms) for updating the queue & error counts
2024-06-01 16:10:35 +02:00
```
2024-05-20 19:47:04 +02:00
2024-12-01 05:29:36 -08:00
## Traefik
2025-09-19 21:29:09 +02:00
Displays Traefik.
2024-12-01 05:29:36 -08:00
```yaml
2025-07-02 12:58:06 +02:00
- name: "Traefik"
type: "Traefik"
logo: "assets/tools/sample.png"
url: "http://traefik.example.com"
basic_auth: "admin:password"
2024-12-01 05:29:36 -08:00
```
2025-07-02 12:58:06 +02:00
- Authentication: If BasicAuth is set, credentials will be encoded in Base64 and sent as an Authorization header (Basic <encoded_value>).
- Format: The value must be formatted as "admin:password".
2024-12-01 05:29:36 -08:00
2025-03-27 00:25:18 +01:00
## Truenas Scale
2025-09-19 21:29:09 +02:00
Displays TrueNAS version.
2025-03-27 00:25:18 +01:00
```yaml
- name: "Truenas"
type: "TruenasScale"
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
api_token: "<---insert-api-key-here--->"
2025-03-27 00:25:18 +01:00
```
2024-11-18 22:17:46 +01:00
## Uptime Kuma
2024-05-20 19:47:04 +02:00
2025-09-19 21:29:09 +02:00
Displays overall status, uptime percentage, and incident information from your Uptime Kuma status page.
2024-10-26 09:48:03 -05:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "Uptime Kuma"
type: "UptimeKuma"
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
slug: "default" # status page slug, defaults to "default"
2024-10-26 09:48:03 -05:00
```
2025-04-09 12:05:16 +02:00
2025-09-19 21:29:09 +02:00
**Requirements**: Uptime Kuma version `1.13.1` or later (for [multiple status pages support ](https://github.com/louislam/uptime-kuma/releases/tag/1.13.1 ))
2025-03-26 21:55:37 +01:00
## Vaultwarden
2025-09-19 21:29:09 +02:00
Displays Vaultwarden version and status.
2025-03-26 21:55:37 +01:00
```yaml
- name: "Vaultwarden - Server"
type: "Vaultwarden"
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2025-03-26 21:55:37 +01:00
```
2024-10-31 16:32:08 -04:00
2024-12-01 05:29:36 -08:00
## Wallabag
2025-09-19 21:29:09 +02:00
Displays Wallabag version.
2024-12-01 05:29:36 -08:00
```yaml
- name: Wallabag
type: Wallabag
2025-09-19 21:29:09 +02:00
logo: "assets/tools/sample.png"
url: https://my-service.url
2024-12-01 05:29:36 -08:00
```
2024-11-18 22:17:46 +01:00
## What's up Docker
2024-10-31 16:32:08 -04:00
2025-09-19 21:29:09 +02:00
Display info about the number of container running and the number for which an update is available on your Homer dashboard.
2024-10-31 16:32:08 -04:00
```yaml
2024-11-18 22:17:46 +01:00
- name: "What's Up Docker"
2025-09-19 21:29:09 +02:00
type: "WUD"
2024-11-18 22:17:46 +01:00
logo: "assets/tools/sample.png"
2025-09-19 21:29:09 +02:00
url: https://my-service.url
2024-11-18 22:17:46 +01:00
subtitle: "Docker image update notifier"
2024-10-31 16:32:08 -04:00
```