-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
base: next
Are you sure you want to change the base?
Add Uptime Kuma docs #39451
Conversation
β Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
π WalkthroughWalkthroughA 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
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
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. πͺ§ TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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 theconfiguration_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 at1.
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
π 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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.
There was a problem hiding this 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 theha_iot_class
identifier
Theha_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 use1.
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
π 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)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @tr4nt0r π
Proposed change
Add docs for Uptime Kuma integration
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit