Skip to content

Update known limitations in documentation for Uptime Kuma #42369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dannytsang merged 2 commits into from
Dec 8, 2025
Merged

Update known limitations in documentation for Uptime Kuma #42369

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
63a2134
Update documentation for Uptime Kuma
tr4nt0r Dec 7, 2025
7a785e9
Merge branch 'current' into kuma_2
dannytsang Dec 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion source/_integrations/uptime_kuma.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,14 @@ This integration retrieves data from your Uptime Kuma instance every 30 seconds.

## Known limitations

- Uptime Kuma's API does not expose unique identifiers for monitors. Because of this, using the same name for multiple monitors will cause only one of them to appear in Home Assistant. Renaming a monitor will result in new entities being created, while the old (stale) entities will remain unless manually removed.
- When using Uptime Kuma versions prior to v2.0.0, Uptime Kuma's API does not expose unique identifiers for monitors. Because of this, using the same name for multiple monitors will cause only one of them to appear in Home Assistant. Renaming a monitor will result in new entities being created, while the old (stale) entities will remain unless manually removed.
- Paused monitors are not exposed by the API, so Home Assistant cannot distinguish between a deleted monitor and a paused one. As a result, if you delete an Uptime Kuma monitor, the corresponding device entry in Home Assistant must be removed manually.

{% note %}

To remove a monitor from Home Assistant, go to {% my integration domain="uptime_kuma" title="**Settings** > **Devices & services** > **Uptime Kuma**" %} select the three dots {% icon "mdi:dots-vertical" %} menu next to the device entry you want to remove. Then select **Remove device**.

{% endnote %}

## Troubleshooting

Expand Down