External integration - Uptime Kuma

Hi everyone! :waving_hand:

You self-host a Nextcloud, a Jellyfin, a backup Home Assistant (shh :shushing_face:)… and you find out it’s down when someone complains at home? Here’s Uptime Kuma in Gladys: the status of your services, in widget and trigger. Everything runs locally.

What it does

  • :green_circle: Each Uptime Kuma probe can become a device: service status (yes/no, usable in scene conditions), response time, and days until certificate expiration for HTTPS sites.
  • :bell: Triggers valid for all probes, without a scene per device: « A service goes down », « A service comes back » (with downtime duration), « Certificate about to expire », and « Uptime Kuma is not responding ».
  • :clapper_board: Two scene actions: « Service status » and « Count failed services », to include in a message.
  • :puzzle_piece: A « Uptime Kuma » widget: failed services first, response time, next certificate to renew.
  • :repeat_button: Up to two Uptime Kuma instances, v1 or v2.

The cool part

Nextcloud goes down → « :warning: Nextcloud is down » on Telegram, then « :white_check_mark: back after 7 min » :mobile_phone:
8 a.m. → the morning report with the number of failed services :hot_beverage:
The box probe goes down → the desk lamp turns red :red_circle:

Installation

:warning: Gladys 5.1 minimum. Uptime Kuma 1.23 or 2.x.

:light_bulb: It will be available in the store at the next indexer run. In a hurry? Integrations → Install from GitHub, with the address GitHub - guim31/gladys-uptime-kuma: Uptime Kuma monitors for Gladys Assistant: status, response time and certificates of your services · GitHub

  1. In Uptime Kuma: Settings → API Keys → create a key.
  2. In Gladys: the Uptime Kuma address and the key, then « Test connection ».
  3. Discovery tab: add the probes you want to see.

Honest caveats: it’s read-only (pausing a probe would require the admin password), a downtime shorter than the read interval (30s by default) may go unnoticed, and in v1 renaming a probe creates a new device.

:test_tube: Tested against real Uptime Kuma 1.23 and 2.5 (downtimes, recoveries, update from v1 to v2 without losing devices). Not yet in a real Gladys: your feedback is welcome.

Like the previous ones, coded with the help of Claude Code :robot:. Independent project, not affiliated with Uptime Kuma.

Repository: GitHub - guim31/gladys-uptime-kuma: Uptime Kuma monitors for Gladys Assistant: status, response time and certificates of your services · GitHub

Let me know what’s missing :folded_hands: