Uptime Card

Features

• Two cards: a full Uptime Card (custom:uptime-card) and a compact Uptime Mini Card (custom:uptime-mini-card)
• Services found on their own: every Uptime Kuma monitor, Ping host, Healthchecks.io check and Certificate Expiry certificate; or the entities you list (any connectivity or problem binary sensor, any sensor reading up / down / online / offline…)
• Status of each service (up, down, pending, maintenance), with how long it has been down
• Response time (Uptime Kuma, Ping), in orange above a threshold you choose
• Uptime bar of the last 24 hours (48 slices of 30 minutes, each in the color of the worst status seen in it) and the uptime percentage, from the Home Assistant history (or Uptime Kuma's own 1-day uptime sensor when it is enabled)
• SSL certificate expiry (Uptime Kuma, Certificate Expiry): days left on every row, the date in its tooltip, orange then red as the expiry gets close, red when expired or invalid; a Certificate Expiry certificate goes to the row of the service of the same host
• Groups by tag (Uptime Kuma tags and Home Assistant labels), by integration, or none; collapsible groups, a group with a service down always unfolded
• An overview at the top of the full card: a drawn server rack in the color of the worst status, animated by it (see Animations), the status in words, the share of services up, the service down the longest, the most urgent certificate and the integrations the services come from
• Header icon in the color of the worst status (certificates and slow responses included), status chip on the right: All up, 1 down, 1 pending, 1 in maintenance
• Mini card: how many services are up out of how many, a bar of the statuses and the services down; its detail button (top right) switches it to the full card's content and back, a click anywhere outside the card brings the compact view back
• Filters: only the services with a problem, some tags, some integrations, excluded entities; sort by status (problems first) or by name
• Click a service to open its Home Assistant history (more-info dialog)
• Sections view: the full card takes 12 columns by default and at least 9, the mini card 6; narrow widths get their own layout (see Screenshots)
• Visual editor in the dashboard UI for both cards (no YAML needed)
• Light and dark mode, English, French, German, Spanish, Serbian (Cyrillic and Latin), Italian, Dutch, European Portuguese, Polish, Romanian, Danish, Swedish, Bulgarian, Russian, Ukrainian, Hungarian, Slovak, Czech, Slovenian, Latvian and Greek
• Single file, no external dependency; the other languages are loaded on demand

Supported integrations

Integration	What the cards show
Uptime Kuma (core, Uptime Kuma 2.0 or later)	One service per monitor: status (up, down, pending, maintenance), response time, certificate days left, URL or hostname, monitor type; tags when the monitor's Tags sensor is enabled; 1-day uptime when its Uptime (1 day) sensor is enabled
Healthchecks.io (custom, healthchecksio)	One service per check: up or down, time of the last ping
Ping (core)	One service per host: connected or not, round trip time when its Round trip time average sensor is enabled
Certificate Expiry (core)	The expiry of a certificate: on the row of the service of the same host (an Uptime Kuma URL or hostname, a Ping host), else a row of its own (down once expired or invalid)
Any binary sensor or sensor (listed in entities)	A connectivity binary sensor is up when on, a problem one is down when on; a sensor reading up, on, online, ok, connected… is up, down, off, offline, error, problem… is down

The Uptime Kuma Tags, Uptime (1 day) and Ping Round trip time average sensors are disabled by default in Home Assistant: enable them on the device page to get the tags, the uptime and the round trip time. Home Assistant labels on a service's entity or device group it too, whatever its integration.

Prerequisites

Home Assistant 2024.8 or later, with at least one of the supported integrations configured, or entities to list. The uptime bar and percentage read the recorder's history: an entity excluded from the recorder shows no bar.

Configuration

Card types#

Visual editor#

Edit a dashboard, click Add card and search for Uptime Card or Uptime Mini Card. Every service found is shown right away; pick entities in the list to show only those, choose the grouping, the sort, what each row shows, the thresholds and the language. The preview updates live, and options left at their default are kept out of the generated YAML.

Minimal#

type: custom:uptime-card

type: custom:uptime-mini-card

Full options#

type: custom:uptime-card
title: Homelab
group_by: tag              # tag, source or none
sort: status               # status (problems first) or name
tags: [Web, Media]         # only these tags, in this order
sources: [uptime_kuma, ping, healthchecks, cert_expiry]
exclude:
  - binary_sensor.printer
collapsed: [Infrastructure] # or true to fold every group
only_problems: false
show_hero: true
show_latency: true
show_history: true
show_uptime: true
show_ssl: true
hours: 24
ssl_warning_days: 14
ssl_critical_days: 3
latency_warning: 1000
language: en

Listing the services yourself (an Uptime Kuma status sensor keeps its response time, certificate and tags; any other entity becomes a service of its own):

type: custom:uptime-card
entities:
  - sensor.cloud_drive_status
  - entity: binary_sensor.printer
    name: Office printer
    tags: [Office]
  - entity: binary_sensor.website_online
    latency_entity: sensor.website_response_time
    cert_entity: sensor.example_com_cert_expiry
auto: true                 # also add every service found (default: only the listed ones)

Options reference#

How it works

The cards read the Home Assistant entity and device registries instead of entity ids: an Uptime Kuma monitor is the device of a status sensor of the uptime_kuma platform, with its response_time, cert_days_remaining, url, hostname, type, tags and uptime_1d sensors; a Ping host is a ping binary sensor, with the round_trip_time_avg sensor of its device; a Healthchecks.io check is a healthchecksio binary sensor; a certificate is a cert_expiry sensor, whose host comes from its device. Entity ids can therefore be in any language or renamed without breaking the cards. Disabled entities are left out, and so is a service whose status entity is hidden (a hidden URL, response time or certificate sensor still adds to its monitor).

The uptime bar asks the recorder for the history of the status entities (one request for all of them, again every 5 minutes) and splits the window into 48 equal slices, each drawn in the color of the worst status seen in it (grey without data). The uptime percentage is the time up over the time up or down: maintenance, pending and unknown periods are left out.

Support

If you find this project useful, you can support its development:

Features

• First release: Uptime Card (custom:uptime-card) and Uptime Mini Card (custom:uptime-mini-card) to watch services from Uptime Kuma, Healthchecks.io, Ping, any connectivity binary sensor and Certificate Expiry, found on their own in the Home Assistant registries (or listed with entities).
• Each service: status (up, down, pending, maintenance) and how long it has been down, response time with a slow threshold, 24-hour uptime bar and uptime percentage from the history, SSL certificate expiry with warning and critical thresholds (a Certificate Expiry certificate goes to the service of the same host).
• Groups by tag (Uptime Kuma tags, Home Assistant labels), by integration or none, collapsible, a group with a service down always unfolded; filters (only_problems, tags, sources, exclude) and sort by status or name.
• Overview with a drawn server rack animated by the worst status (heartbeat when everything is up, alarm rings when a service is down, blinking dots while pending, swinging wrench in maintenance), honouring prefers-reduced-motion.
• Mini card: services up out of the total, a bar of the statuses and the services down; its detail button switches it to the full list and back.
• Visual editors for both cards, light and dark themes, 22 languages (English in the bundle, the others loaded on demand).