Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add Uptime Kuma docs #39451

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.

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

Open
wants to merge 1 commit into
base: next
Choose a base branch
from
Open

Conversation

tr4nt0r
Copy link
Contributor

@tr4nt0r tr4nt0r commented Jun 9, 2025

Proposed change

Add docs for Uptime Kuma integration

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • Documentation
    • Added new documentation for the Uptime Kuma integration, including setup instructions, configuration options, available sensors, known limitations, and removal guidance.

@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Jun 9, 2025
Copy link

netlify bot commented Jun 9, 2025

βœ… Deploy Preview for home-assistant-docs ready!

Name Link
πŸ”¨ Latest commit bd7e32c
πŸ” Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/68472accf9960f00074be47f
😎 Deploy Preview https://deploy-preview-39451--home-assistant-docs.netlify.app
πŸ“± Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

coderabbitai bot commented Jun 9, 2025

πŸ“ Walkthrough

Walkthrough

A new documentation file was added for the Uptime Kuma integration with Home Assistant. This file introduces the integration, describes its setup process, available sensors, configuration options, known limitations, and removal instructions, using standard Home Assistant documentation templates.

Changes

File(s) Change Summary
source/_integrations/uptime_kuma.markdown Added documentation for the new Uptime Kuma integration, including setup, sensors, options, and limitations.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HomeAssistant
    participant UptimeKuma

    User->>HomeAssistant: Configure Uptime Kuma integration (provide URL, API key)
    HomeAssistant->>UptimeKuma: Authenticate and fetch monitor data via API
    UptimeKuma-->>HomeAssistant: Return monitor status, response time, etc.
    HomeAssistant-->>User: Display sensors (status, response time, etc.)
    Note over HomeAssistant: Data is updated every 30 seconds
Loading

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share
πŸͺ§ Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
source/_integrations/uptime_kuma.markdown (2)

36-41: Align configuration keys with YAML conventions
In the configuration_basic block, option names should be unquoted, snake_case YAML keys that match the integration’s config schema. Consider updating as follows:

-{% configuration_basic %}
-"URL":
-  description: "Address of your Uptime Kuma instance. Example: `https://uptime.example.com`."
-Verif​y SSL certificate:
-  description: "Enable SSL certificate verification for secure connections."
-"API key":
-  description: "An API key to authenticate with your Uptime Kuma instance."
-{% endconfiguration_basic %}
+{% configuration_basic %}
+url:
+  description: "Address of your Uptime Kuma instance. Example: `https://uptime.example.com`."
+verify_ssl:
+  description: "Enable SSL certificate verification for secure connections."
+api_key:
+  description: "An API key to authenticate with your Uptime Kuma instance."
+{% endconfiguration_basic %}

68-68: Fix list numbering and add trailing newline
Per markdownlint rules, ordered lists should restart at 1. and the file must end with a single newline. Update this line and ensure a newline at EOF:

-4. You can now remove the API key used for Home Assistant from Uptime Kuma, unless it is also used by other integrations or applications.
+1. You can now remove the API key used for Home Assistant from Uptime Kuma, unless it is also used by other integrations or applications.
🧰 Tools
πŸͺ› markdownlint-cli2 (0.17.2)

68-68: Ordered list item prefix
Expected: 1; Actual: 4; Style: 1/1/1

(MD029, ol-prefix)


68-68: Files should end with a single newline character
null

(MD047, single-trailing-newline)

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 5c663af and 7913c4b.

πŸ“’ Files selected for processing (1)
  • source/_integrations/uptime_kuma.markdown (1 hunks)
🧰 Additional context used
πŸͺ› markdownlint-cli2 (0.17.2)
source/_integrations/uptime_kuma.markdown

68-68: Ordered list item prefix
Expected: 1; Actual: 4; Style: 1/1/1

(MD029, ol-prefix)


68-68: Files should end with a single newline character
null

(MD047, single-trailing-newline)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs

description: Instructions on how to integrate Uptime Kuma with Home Assistant.
ha_category:
- Sensor
ha_iot_class: Cloud push
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Correct the ha_iot_class identifier
The ha_iot_class value must use the official enum format (cloud_push), not a human-readable string.

- ha_iot_class: Cloud push
+ ha_iot_class: cloud_push
πŸ“ Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
ha_iot_class: Cloud push
ha_iot_class: cloud_push
πŸ€– Prompt for AI Agents
In source/_integrations/uptime_kuma.markdown at line 6, the ha_iot_class value
is set to "Cloud push" which is a human-readable string. Change this value to
the official enum format "cloud_push" using lowercase letters and underscore to
match the required identifier format.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
source/_integrations/uptime_kuma.markdown (1)

6-6: Correct the ha_iot_class identifier
The ha_iot_class value must use the official enum format, not a human-readable string.

- ha_iot_class: Cloud push
+ ha_iot_class: cloud_push
🧹 Nitpick comments (2)
source/_integrations/uptime_kuma.markdown (2)

37-37: Unify example domain suffix
The document currently mixes .org and .com in examplesβ€”standardize on one. Update the config example to match the prerequisites section:

-   "URL":
-     description: "Address of your Uptime Kuma instance. Example: `https://uptime.example.com`."
+   "URL":
+     description: "Address of your Uptime Kuma instance. Example: `https://uptime.example.org`."

68-68: Use consistent ordered list prefixes
Markdown lint expects all ordered list items to use 1. as the prefix. Change this step accordingly:

- 4. You can now remove the API key used for Home Assistant from Uptime Kuma...
+ 1. You can now remove the API key used for Home Assistant from Uptime Kuma...
🧰 Tools
πŸͺ› markdownlint-cli2 (0.17.2)

68-68: Ordered list item prefix
Expected: 1; Actual: 4; Style: 1/1/1

(MD029, ol-prefix)

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 7913c4b and bd7e32c.

πŸ“’ Files selected for processing (1)
  • source/_integrations/uptime_kuma.markdown (1 hunks)
🧰 Additional context used
πŸͺ› markdownlint-cli2 (0.17.2)
source/_integrations/uptime_kuma.markdown

68-68: Ordered list item prefix
Expected: 1; Actual: 4; Style: 1/1/1

(MD029, ol-prefix)

@c0ffeeca7 c0ffeeca7 added the new-integration This PR adds documentation for a new Home Assistant integration label Jun 12, 2025
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @tr4nt0r πŸ‘

@c0ffeeca7 c0ffeeca7 added the awaits-parent Awaits the merge of an parent PR label Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaits-parent Awaits the merge of an parent PR has-parent This PR has a parent PR in a other repo new-integration This PR adds documentation for a new Home Assistant integration next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants