SleepIQ add core climate for SleepNumber Climate 360 beds #36717
Conversation
dferg
requested review from
bachya,
fabaff,
starkillerOG,
Danielhiversen,
andrewsayre,
mib1185,
edenhaus and
a team
as code owners
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThis pull request represents a comprehensive documentation update for Home Assistant, focusing on reorganizing and enhancing backup-related documentation. The changes span multiple files across the documentation, with a primary emphasis on consolidating backup instructions into a more generalized, accessible format. The modifications include updating links, adding new integration features, introducing new documentation sections, and improving the clarity of existing content. Changes
Sequence DiagramsequenceDiagram
participant User
participant HA as Home Assistant
participant Backup as Backup System
User->>HA: Request Backup
HA->>Backup: Initiate Backup Process
Backup->>Backup: Encrypt Backup Data
Backup-->>HA: Generate Backup
HA-->>User: Provide Backup Location/Options
User->>Backup: Store Backup Emergency Kit
This sequence diagram illustrates the high-level backup process, highlighting the key interactions between the user, Home Assistant, and the backup system, including encryption and backup generation. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (8)
source/_integrations/bang_olufsen.markdown (2)
492-503: Add blank lines around the list for better readabilityThe markdown list of available event entities should be surrounded by blank lines for better formatting and consistency with markdown best practices.
Apply this formatting:
Available event entities: - Bluetooth - Microphone - Next - Play / Pause - Favourite 1 - Favourite 2 - Favourite 3 - Favourite 4 - Previous - Volume🧰 Tools
🪛 Markdownlint (0.37.0)
493-493: null
Lists should be surrounded by blank lines(MD032, blanks-around-lists)
504-510: Add blank lines around the list for better readabilitySimilarly, the list of event types should be surrounded by blank lines.
Apply this formatting:
All of these event entities support the following event types: - Release of short press - Long press - Release of long press - Very long press - Release of very long press🧰 Tools
🪛 Markdownlint (0.37.0)
505-505: null
Lists should be surrounded by blank lines(MD032, blanks-around-lists)
source/_integrations/ohme.markdown (2)
75-85: LGTM: Well-structured switches documentationThe new Switches section follows the established documentation pattern and provides clear descriptions for each switch entity. The device availability information is particularly helpful for users.
Consider adding a brief introductory line before listing the switches, similar to other sections:
#### Switches +The following switches are available:
91-97: Add usage example for the actionThe action documentation is clear and well-structured. Consider adding a YAML example to show how to use this action in automations:
| `config_entry` | No | The config entry of the account to get the charge list from. | +#### Example + +```yaml +service: ohme.list_charge_slots +data: + config_entry: "ohme_account_1" +```source/_integrations/mill.markdown (1)
24-26: Minor style refinement for clarity.Consider rewording line 25 for an imperative style:
- A number entity can configure the maximum power of the heaters. + Use the number entity to configure the maximum power of the heaters.source/_integrations/sleepiq.markdown (1)
52-52: Add more details about core climate featuresWhile the addition of core climate control is correctly documented, consider adding more details about:
- The available heat/cool modes (low, medium, high)
- The timer's default duration (4 hours) and maximum limit (10 hours)
This would help users better understand the feature's capabilities.
Example addition:
- - Select/Number - Set core climate heat/cool modes and timeout + - Select/Number - Set core climate heat/cool modes (low, medium, high) and timeout (default: 4 hours, max: 10 hours)source/_integrations/ecovacs.markdown (1)
52-52: Remove extra spaces after the entity nameThere are extra spaces after "Station actions" which should be removed for consistent formatting.
- - `Station actions`: For each supported station action, a button entity will be created. + - `Station actions`: For each supported station action, a button entity will be created.🧰 Tools
🪛 LanguageTool
[uncategorized] ~52-~52: Loose punctuation mark.
Context: ...manual relocation. -Station actions: For each supported station action, a bu...(UNLIKELY_OPENING_PUNCTUATION)
source/_integrations/swiss_public_transport.markdown (1)
29-36: Well-documented configuration options with clear use casesThe new time management options are thoroughly documented with practical examples. The configuration is clear and user-friendly.
However, there's a minor opportunity to improve the description's clarity:
- description: "The time offset added to the earliest possible connection (e.g. add +00:05:00 offset, taking into account the time to walk to the station)" + description: "The time offset added to the earliest possible connection (e.g. add +00:05:00 offset to account for walking time to the station)"🧰 Tools
🪛 LanguageTool
[style] ~36-~36: ‘taking into account’ might be wordy. Consider a shorter alternative.
Context: ... connection (e.g. add +00:05:00 offset, taking into account the time to walk to the station)" {% en...(EN_WORDINESS_PREMIUM_TAKING_INTO_ACCOUNT)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (5)
source/images/more-info/backup_emergency_kit_01.pngis excluded by!**/*.pngsource/images/screenshots/network-storage/backup_locations_all.pngis excluded by!**/*.pngsource/images/screenshots/network-storage/backup_select_local_default.pngis excluded by!**/*.pngsource/images/screenshots/network-storage/change_backup_dark.pngis excluded by!**/*.pngsource/images/screenshots/network-storage/change_backup_light.pngis excluded by!**/*.png
📒 Files selected for processing (35)
source/_docs/configuration.markdown(1 hunks)source/_includes/common-tasks/backups.md(5 hunks)source/_includes/common-tasks/data_disk.md(2 hunks)source/_includes/common-tasks/network_storage.md(1 hunks)source/_includes/common-tasks/specific_version.md(1 hunks)source/_includes/common-tasks/update.md(1 hunks)source/_integrations/aemet.markdown(3 hunks)source/_integrations/backup.markdown(2 hunks)source/_integrations/bang_olufsen.markdown(2 hunks)source/_integrations/cookidoo.markdown(1 hunks)source/_integrations/ecovacs.markdown(2 hunks)source/_integrations/harvey.markdown(1 hunks)source/_integrations/heos.markdown(1 hunks)source/_integrations/iotty.markdown(1 hunks)source/_integrations/iron_os.markdown(4 hunks)source/_integrations/mill.markdown(2 hunks)source/_integrations/music_assistant.markdown(1 hunks)source/_integrations/ohme.markdown(2 hunks)source/_integrations/overseerr.markdown(1 hunks)source/_integrations/reolink.markdown(1 hunks)source/_integrations/sleepiq.markdown(1 hunks)source/_integrations/swiss_public_transport.markdown(2 hunks)source/_integrations/tile.markdown(1 hunks)source/_integrations/twinkly.markdown(1 hunks)source/_redirects(1 hunks)source/common-tasks/container.markdown(1 hunks)source/common-tasks/core.markdown(1 hunks)source/common-tasks/general.markdown(1 hunks)source/common-tasks/os.markdown(1 hunks)source/common-tasks/supervised.markdown(0 hunks)source/dashboards/views.markdown(3 hunks)source/getting-started/configuration.markdown(2 hunks)source/installation/index.html(1 hunks)source/more-info/backup-emergency-kit.markdown(1 hunks)source/more-info/free-space.markdown(2 hunks)
💤 Files with no reviewable changes (1)
- source/common-tasks/supervised.markdown
✅ Files skipped from review due to trivial changes (5)
- source/common-tasks/container.markdown
- source/_includes/common-tasks/update.md
- source/_docs/configuration.markdown
- source/common-tasks/core.markdown
- source/_includes/common-tasks/data_disk.md
🧰 Additional context used
📓 Path-based instructions (1)
source/_redirects (6)
Pattern */**(html|markdown|md): - For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted.
- Apply the Microsoft Style Guide to ensure documentation maintains clarity and conciseness.
- In step-by-step instructions, front the location phrase in the instructional sentence.
- In step-by-step instructions, front the 'goal' in the instructional sentence.
- In step-by-step instructions, if in doubt what to front, front the 'goal' before the location phrase in the instructional sentence.
- do not hyphenate terms like 'top-right' or 'bottom-left' with 'corner'
Pattern */**(html|markdown|md): - Use bold to mark UI strings.
- If "" are used to mark UI strings, replace them by bold.
Pattern */**(html|markdown|md): - Be brief in your replies and don't add fluff like "thank you for..." and "Please let me know if"
Pattern */**(html|markdown|md): - Use sentence-style capitalization also in headings.
Pattern */**(html|markdown|md): do not comment on HTML used for icons
Pattern */**(html|markdown|md): Avoid flagging inline HTML for embedding videos in future reviews for this repository.
🪛 LanguageTool
source/_integrations/ecovacs.markdown
[uncategorized] ~52-~52: Loose punctuation mark.
Context: ...manual relocation. - Station actions: For each supported station action, a bu...
(UNLIKELY_OPENING_PUNCTUATION)
source/_integrations/swiss_public_transport.markdown
[style] ~36-~36: ‘taking into account’ might be wordy. Consider a shorter alternative.
Context: ... connection (e.g. add +00:05:00 offset, taking into account the time to walk to the station)" {% en...
(EN_WORDINESS_PREMIUM_TAKING_INTO_ACCOUNT)
source/dashboards/views.markdown
[typographical] ~199-~199: After the expression ‘for example’ a comma is usually used.
Context: ...let you pick an image from the web. For example `https://www.home-assistant.io/images/f...
(COMMA_FOR_EXAMPLE)
[uncategorized] ~253-~253: A comma is probably missing here.
Context: ...CSS variable lovelace-background. For wallpapers you probably want to use the example be...
(MISSING_COMMA_AFTER_INTRODUCTORY_PHRASE)
source/_includes/common-tasks/backups.md
[uncategorized] ~19-~19: Possible missing comma found.
Context: ...migrate the system to new hardware, for example from a Raspberry Pi Compute Module ...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~45-~45: As an alternative to the over-used intensifier ‘quite’, consider replacing this phrase.
Context: ... restore. - Some add-ons may also be quite large. 7. [Define the location for backups](#...
(EN_WEAK_ADJECTIVE)
[uncategorized] ~52-~52: Possible missing comma found.
Context: ...s recommended to keep a copy on another system and ideally also one off-site. #### Ab...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~75-~75: As an alternative to the over-used intensifier ‘quite’, consider replacing this phrase.
Context: ... restore. - Some add-ons may also be quite large. 4. Provide a name for the backup. 5. C...
(EN_WEAK_ADJECTIVE)
[uncategorized] ~133-~133: Possible missing article found.
Context: ...igrate your setup to a new device or to device on which you performed a factory reset....
(AI_HYDRA_LEO_MISSING_A)
[uncategorized] ~196-~196: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...- You will lose the connection to the UI and it will return once the restart is comp...
(COMMA_COMPOUND_SENTENCE)
🪛 Markdownlint (0.37.0)
source/_integrations/twinkly.markdown
41-41: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
24-24: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
46-46: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
51-51: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
56-56: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
60-60: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
63-63: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
68-68: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
45-45: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
50-50: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
55-55: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
59-59: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
62-62: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
source/dashboards/views.markdown
196-196: Expected: 0; Actual: 3
Unordered list indentation
(MD007, ul-indent)
197-197: Expected: 0; Actual: 3
Unordered list indentation
(MD007, ul-indent)
198-198: Expected: 2; Actual: 5
Unordered list indentation
(MD007, ul-indent)
199-199: Expected: 0; Actual: 3
Unordered list indentation
(MD007, ul-indent)
191-191: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
195-195: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
204-204: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
216-216: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
221-221: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
223-223: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
226-226: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
231-231: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
196-196: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
source/_integrations/bang_olufsen.markdown
493-493: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
505-505: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
🔇 Additional comments (29)
source/_integrations/bang_olufsen.markdown (1)
489-512: LGTM! Well-documented event functionalityThe new Events section provides clear and comprehensive documentation about:
- Physical controls that trigger events
- Supported event types for each control
- Device compatibility information
The documentation will help users effectively implement automations using these events.
🧰 Tools
🪛 Markdownlint (0.37.0)
493-493: null
Lists should be surrounded by blank lines(MD032, blanks-around-lists)
505-505: null
Lists should be surrounded by blank lines(MD032, blanks-around-lists)
source/_integrations/ohme.markdown (2)
15-15: LGTM: Platform declaration matches implementationThe addition of the "switch" platform in
ha_platformscorrectly reflects the new switches functionality documented later in the file.
87-90: LGTM: Clear section structureThe Actions section header and introduction are well-formatted and follow the documentation standards.
source/_redirects (1)
403-405: Redirects updated to reflect new backup structure.These redirects move references from "snapshots" to "backups," aligning with the new backup approach and documentation structure. No issues found.
source/_integrations/harvey.markdown (1)
1-19: Front matter is consistent with style guidelines.The metadata is correctly formatted, and sentence-style capitalization is used in the title. Nicely done.
source/_integrations/tile.markdown (1)
13-13: Adding binary_sensor platform is correct.Introducing the binary sensor platform expands the integration's capabilities. Looks good.
source/_integrations/mill.markdown (1)
15-15: Addition of 'number' platform is aligned with documentation structure.This clear platform extension follows Home Assistant’s standard. No issues found.
source/_integrations/twinkly.markdown (1)
23-30: LGTM! Clear and concise capability list.The added capability list provides a clear overview of the integration's features.
🧰 Tools
🪛 Markdownlint (0.37.0)
24-24: null
Lists should be surrounded by blank lines(MD032, blanks-around-lists)
source/_integrations/backup.markdown (2)
22-24: LGTM! Improved clarity and inclusivityGood improvements:
- Clarified applicability to all installation types
- Streamlined reference to common tasks
31-32: LGTM! Better user guidanceGood addition directing users to the UI-based automatic backup setup instead of manual automation.
source/common-tasks/general.markdown (1)
8-9: LGTM! Good documentation centralizationGood addition of centralized backup documentation through the include statement.
source/_integrations/iotty.markdown (2)
44-46: Updated product links for iotty Smart Switch.The product links are properly updated with correct variants and regional versions.
65-65: Updated switch entity description to include outlet functionality.The description now correctly covers both light switches and outlet switches.
source/_integrations/aemet.markdown (2)
13-13: Added image platform support.The image platform is correctly added to the list of supported platforms.
23-27: Updated entity types section with clear formatting.The entity types are well-organized and properly listed.
source/_integrations/cookidoo.markdown (1)
59-63: Well-documented button entity section!The new "Button entities" section is clear, concise, and follows the documentation standards. It effectively explains:
- The purpose of the button entity
- Its functionality
- How it appears in Home Assistant
- How users can utilize it
source/getting-started/configuration.markdown (1)
11-11: LGTM: Backup documentation links updated consistentlyThe links to backup documentation have been updated to point to the new generalized location
/common-tasks/general/#backups, maintaining consistency across different installation types.Also applies to: 43-44
source/common-tasks/os.markdown (1)
28-28: LGTM: Backup link updated consistentlyThe backup link has been updated to point to the new generalized location
/common-tasks/general/#backups, maintaining consistency with other documentation changes.source/_integrations/ecovacs.markdown (1)
52-52: LGTM! Well-documented new entitiesThe new "Station actions" button entity and "Station state" sensor entity are well-documented and properly categorized.
Also applies to: 74-74
🧰 Tools
🪛 LanguageTool
[uncategorized] ~52-~52: Loose punctuation mark.
Context: ...manual relocation. -Station actions: For each supported station action, a bu...(UNLIKELY_OPENING_PUNCTUATION)
source/_integrations/music_assistant.markdown (1)
138-220: LGTM! Comprehensive documentation of new actionsThe new actions (
search,get_library, andget_queue) are thoroughly documented with:
- Clear descriptions of each action's purpose
- Well-structured parameter documentation
- Helpful examples
- Consistent formatting
source/_integrations/heos.markdown (1)
46-46: LGTM! Clear and well-structured documentation updatesThe updates improve clarity with:
- More precise host description
- Well-organized reconfiguration steps
- Standard removal instructions
- Proper use of Home Assistant terminology and icons
Also applies to: 49-63
source/installation/index.html (1)
335-335: LGTM: Link update aligns with documentation reorganization.The change to redirect the backup documentation link to the general section is consistent with the broader documentation restructuring.
source/_integrations/reolink.markdown (1)
102-102: LGTM: Well-documented new feature.The addition of AI baby crying detection is properly documented with the push update indicator (+).
source/_integrations/swiss_public_transport.markdown (1)
49-49: Clear and concise explanation of via stationsThe documentation effectively explains the optional via stations feature.
source/_includes/common-tasks/network_storage.md (2)
74-74: Clear explanation of backup storage typeThe description effectively explains the automatic/manual backup functionality and default target behavior.
81-91: Well-structured instructions for changing backup locationThe steps are clear and include helpful troubleshooting information. The addition of the screenshot enhances user understanding.
source/more-info/free-space.markdown (3)
50-54: Clear backup management instructionsThe documentation effectively guides users through backup management while emphasizing proactive maintenance.
58-58: Concise external backup storage explanationThe paragraph effectively communicates the benefits of external backup storage while providing relevant links to detailed instructions.
76-76: Clear backup restoration instructionsThe documentation provides a clear path for users to restore from backup when expanding storage.
| ## Operation Modes | ||
|
|
||
| Modes can be switched using the select entity. | ||
|
|
||
| For most use cases, "Color", "Movie" and "Playlist" modes are the most relevant. | ||
|
|
||
| **Color Mode** | ||
| - Displays a static color | ||
| - Controlled through the light entity | ||
| - Color can be set via RGB/RGBW | ||
|
|
||
| **Movie Mode** | ||
| - Plays effects previously uploaded through the Twinkly app | ||
| - Effects must be created and transferred to the device first using the app | ||
| - Effect selection is done through the light entity | ||
|
|
||
| **Playlist Mode** | ||
| - Sequential playback of multiple effects | ||
| - Playlist must be uploaded through the Twinkly app first | ||
|
|
||
| **Off Mode** | ||
| - Turns off the lighting | ||
|
|
||
| **Demo Mode** | ||
| - Shows predefined demo effects | ||
| - Primarily intended for presentation purposes | ||
| - Limited practical use | ||
|
|
||
| **Unsupported Modes:** | ||
| - Effect Mode: predefined effects built into the device. Alternatively, you can use Movie Mode | ||
| - RT (Real-Time): Live control of individual LEDs | ||
| - Music: Music-controlled light show |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix markdown formatting issues
While the content is well-structured and informative, there are several markdown formatting issues to address:
- Convert emphasized section titles to proper markdown headings:
-**Color Mode**
+### Color Mode
-**Movie Mode**
+### Movie Mode
-**Playlist Mode**
+### Playlist Mode
-**Off Mode**
+### Off Mode
-**Demo Mode**
+### Demo Mode
-**Unsupported Modes:**
+### Unsupported Modes- Add blank lines around lists for proper formatting
- Remove trailing spaces (particularly on line 41)
📝 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.
| ## Operation Modes | |
| Modes can be switched using the select entity. | |
| For most use cases, "Color", "Movie" and "Playlist" modes are the most relevant. | |
| **Color Mode** | |
| - Displays a static color | |
| - Controlled through the light entity | |
| - Color can be set via RGB/RGBW | |
| **Movie Mode** | |
| - Plays effects previously uploaded through the Twinkly app | |
| - Effects must be created and transferred to the device first using the app | |
| - Effect selection is done through the light entity | |
| **Playlist Mode** | |
| - Sequential playback of multiple effects | |
| - Playlist must be uploaded through the Twinkly app first | |
| **Off Mode** | |
| - Turns off the lighting | |
| **Demo Mode** | |
| - Shows predefined demo effects | |
| - Primarily intended for presentation purposes | |
| - Limited practical use | |
| **Unsupported Modes:** | |
| - Effect Mode: predefined effects built into the device. Alternatively, you can use Movie Mode | |
| - RT (Real-Time): Live control of individual LEDs | |
| - Music: Music-controlled light show | |
| ## Operation Modes | |
| Modes can be switched using the select entity. | |
| For most use cases, "Color", "Movie" and "Playlist" modes are the most relevant. | |
| ### Color Mode | |
| - Displays a static color | |
| - Controlled through the light entity | |
| - Color can be set via RGB/RGBW | |
| ### Movie Mode | |
| - Plays effects previously uploaded through the Twinkly app | |
| - Effects must be created and transferred to the device first using the app | |
| - Effect selection is done through the light entity | |
| ### Playlist Mode | |
| - Sequential playback of multiple effects | |
| - Playlist must be uploaded through the Twinkly app first | |
| ### Off Mode | |
| - Turns off the lighting | |
| ### Demo Mode | |
| - Shows predefined demo effects | |
| - Primarily intended for presentation purposes | |
| - Limited practical use | |
| ### Unsupported Modes | |
| - Effect Mode: predefined effects built into the device. Alternatively, you can use Movie Mode | |
| - RT (Real-Time): Live control of individual LEDs | |
| - Music: Music-controlled light show |
🧰 Tools
🪛 Markdownlint (0.37.0)
41-41: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
46-46: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
51-51: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
56-56: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
60-60: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
63-63: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
68-68: null
Lists should be surrounded by blank lines
(MD032, blanks-around-lists)
45-45: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
50-50: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
55-55: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
59-59: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
62-62: null
Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
home-assistant
bot
added
in-progress
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
home-assistant
bot
removed
the
needs-rebase
home-assistant
bot
removed
the
in-progress
Proposed change
This is a document change for feature addition PR home-assistant/core#134718
This adds the capability to control the Core Climate feature of SleepNumber Climate 360 beds. These beds have forced air, configurable on the two sides. The air can be heated or cooled with low / medium / high levels. There is a timer that defaults to 4 hours and maxes out at 10 hours.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit
Based on the comprehensive summary of changes, here are the release notes:
Documentation
Integrations
General Improvements