Update known limitations in documentation for Uptime Kuma (#42369)

This commit is contained in:
Manu 2025-12-08 16:02:48 +01:00 committed by GitHub
parent ed4eca4de3
commit e7d9279d26
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -127,7 +127,14 @@ This integration retrieves data from your Uptime Kuma instance every 30 seconds.
## Known limitations ## 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 ## Troubleshooting