Add Mitsubishi WF-RAC integration documentation - #47923
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
🟡 Changes recommended
The integration page is missing required template structure/content (notably the automation examples section), and it needs a few documentation fixes (certificate prerequisite coverage, missing “Configuration options” section heading, and American English spelling).
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR adds the initial documentation page for the new mitsubishi_wf_rac integration to the Home Assistant documentation site, describing setup, configuration, supported features, limitations, troubleshooting, and removal.
Changes:
- Adds a new integration documentation page:
mitsubishi_wf_rac. - Documents configuration flow fields and post-setup options.
- Provides supported functionality, polling behavior, limitations, troubleshooting, and removal guidance.
File summaries
| File | Description |
|---|---|
| source/_integrations/mitsubishi_wf_rac.markdown | New documentation page for the Mitsubishi WF-RAC integration, including setup and usage guidance. |
Review details
Suppressed comments (3)
source/_integrations/mitsubishi_wf_rac.markdown:52
- The second
{% configuration_basic %}block documents options changed after setup, but it is not under a dedicated Configuration options section like the integration docs template expects. Add the missing heading and point readers to where they can change these options in the UI.
Everything else is configured afterwards under **Configure**.
{% configuration_basic %}
source/_integrations/mitsubishi_wf_rac.markdown:79
- The integration docs template expects an "## Mitsubishi WF-RAC automation examples" section (with level-3 "Automation:" headings) before Data updates, but this page jumps straight from Supported functionality to Data updates. Add at least one or two concrete automation examples to help readers get started (and keep them consistent with what this integration exposes).
## Data updates
source/_integrations/mitsubishi_wf_rac.markdown:87
- Use American English spelling: "behaviour" should be "behavior".
- **The unit briefly goes unavailable about once an hour.** The module reassociates with your Wi-Fi on its own; the default retry limit of three polls is chosen to ride through it. This is the module's behaviour, not a network fault.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| - The module has to be on your network already. Set it up once with the manufacturer's app, or through the module's own access point; this integration does not perform that first-time setup. | ||
| - Give the module a fixed address in your router. A changed address is not followed automatically and has to be corrected with **Reconfigure**. | ||
| - The module accepts a limited number of registered controllers. If its account table is full, Home Assistant cannot register and the integration raises a repair issue saying so; free a slot in the app, or factory-reset the module. | ||
|
|
||
| {% include integrations/config_flow.md %} |
d4d2ace to
0dce004
Compare
0dce004 to
109e603
Compare
The docs-examples rule asks the documentation to show what the integration is for, not just what it exposes. Three that need the integration rather than a generic thermostat: pre-cooling triggered by a room sensor instead of the unit's own return-air reading, stopping on an open window, and Home Leave as the away preset with the condition it needs to be unambiguous. Also corrects the consolidation note: actions issued together share one frame, actions awaited one after another do not.
The prerequisites had the module's self-signed certificate nowhere, so a reader had no way to know the connection does not verify it by default or that ac_cert.pem is what changes that. The address line was written before the host moved back into the config entry's data: a module that announces itself again now updates the stored address, and Reconfigure is the fallback rather than the only way.
Proposed change
Documentation for the
mitsubishi_wf_racintegration, submitted to core in home-assistant/core#181403.Covers what the integration talks to (Mitsubishi Heavy Industries indoor units fitted with the WF-RAC wireless LAN module), the certificate the module requires and how to obtain it, discovery and manual setup, the climate entity, and the removal procedure.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information