-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Add known limitations to NUT #38388
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
Add known limitations to NUT #38388
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThe update adds a new "Known limitations" section to the NUT integration documentation. The section details that the integration supports only a subset of NUT variables and commands, does not permit setting variables, and excludes commands that require parameters. It also clarifies that the integration communicates with a NUT server (which interacts with power devices) rather than managing devices directly or installing the server within Home Assistant. Changes
Tip ⚡💬 Agentic Chat (Pro Plan, General Availability)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (3)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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: 0
🧹 Nitpick comments (1)
source/_integrations/nut.markdown (1)
100-116
: Clear and Informative "Known limitations" SectionThis new section clearly and concisely documents the limitations of the NUT integration, which aligns well with the PR objectives. The bullet list format makes each limitation easy to parse, and the text accurately communicates that only a subset of NUT functionality is supported.
A small stylistic suggestion: for consistency and enhanced clarity, consider wrapping key terms such as
variables
andcommands
in backticks (i.e.`variables`
and`commands`
) if similar formatting is used elsewhere in the documentation.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
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
🧹 Nitpick comments (1)
source/_integrations/nut.markdown (1)
104-123
: Addition of Known Limitations SectionThe new "Known limitations" section comprehensively outlines what NUT functionality is unsupported (e.g., a subset of "variables" and "commands", lack of support for setting variables and commands requiring parameters) and clarifies that the integration does not install the NUT server. For additional clarity, consider including a reference link to the official NUT documentation for users seeking more detailed information on supported features.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/nut.markdown
(2 hunks)
🔇 Additional comments (1)
source/_integrations/nut.markdown (1)
31-34
: Clarify Integration Communication ApproachThe added block clearly explains that the integration communicates with a NUT server using the NUT protocol rather than interfacing directly with power devices. This clarification helps set the right context for users regarding data flow and control.
A merge conflict popped-up. Could you take a look, @tdfountain? |
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.
Seems like something went wrong in your latest merge/rebase. There are now many unrelated commits in this PR. Could you take a look?
Thanks 👍
../Frenck
02c19b6
to
63895fa
Compare
63895fa
to
2440c8f
Compare
Thanks! The rebase issue has been fixed, sorry about that. |
Emphasize use of NUT server Co-authored-by: J. Nick Koston <nick+github@koston.org>
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.
Thanks, @tdfountain 👍
../Frenck
Proposed change
The NUT integration doc lacks a known limitations section. This PR creates a new "Known limitations" section and describes the functionality supported by a NUT server but not supported by this NUT integration. This new "Known limitations" section also further reinforces that this integration does not install the NUT package.
Additionally, added to existing introduction an explanation that this integrations interacts with a NUT server and not directly with a power device.
Type of change
current
branch).current
branch).next
branch).next
branch).Additional information
Checklist
current
branch.next
branch.Summary by CodeRabbit