2025.3: Beta release notes #37717
2025.3: Beta release notes #37717
Conversation
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 |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
bramkragten
requested review from
bdraco,
allenporter,
zweckj,
fabaff,
abmantis,
ctalkington and
epenet
as code owners
📝 WalkthroughWalkthroughThis pull request updates the documentation and configuration for multiple integrations. The changes include updates to code ownership in the CODEOWNERS file, release version and date modifications in the global configuration, and various metadata updates across integration markdown files. New attributes such as quality scales and platform entries have been added, several release fields have been adjusted or rolled back, and formatting and title updates have been applied. A new beta release notes file has also been introduced. Changes
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: 3
🧹 Nitpick comments (6)
source/_posts/2025-03-05-release-20253.markdown (5)
98-108: Dashboard headers section review.
The “Dashboard view headers” section clearly explains the new capabilities. However, the image alt text (“TODO: Replace.”) should be updated with a final description before release.
113-148: Tile cards enhancements and tone adjustment.
This section does an excellent job outlining tile card updates. A couple of suggestions:
• On line 121, the word “awesome” may be replaced with a more professional term.
• On line 113, consider avoiding overused phrases such as “a lot of touches” for a more concise description.
These adjustments will help maintain a polished tone throughout the document.🧰 Tools
🪛 LanguageTool
[style] ~114-~114: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...ult) or above the text. ## Tile cards A lot of touches and improvements have been made...(A_LOT_OF)
[style] ~121-~121: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ... card can be controlled Tile cards are awesome! It is arguably the best and most versa...(AWESOME)
[style] ~137-~137: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ng cards, we gained the ability to make very wide tile cards. These cards would have a lo...(EN_WEAK_ADJECTIVE)
[style] ~146-~146: Consider using a different adverb to strengthen your wording.
Context: ...ard-inline-feature.png" /> This brings a completely new look and feel which we are sure you...(COMPLETELY_ENTIRELY)
211-227: Assist chat streaming responses and pending TODO.
The section explaining the streaming responses for Assist chat is clear and informative. Keep in mind the “TODO” marker on line 227—ensure that the final clip or a finalized placeholder is provided before the official release.
395-397: Graph zoom functionality terminology.
The phrase “double clicking” should be standardized to “double-clicking” to adhere to conventional usage.🧰 Tools
🪛 LanguageTool
[grammar] ~395-~395: This expression is usually spelled with a hyphen.
Context: .... You can now also zoom in and out, by double clicking on a graph. If you want more control ov...(DOUBLE_CLICK_HYPHEN)
100-599: General style and formatting recommendations.
Overall, while the release notes are rich in detail, several static analysis suggestions note minor style improvements:
• Avoid overused or informal terms like “awesome” and “a lot of” where a more professional tone is preferred.
• Ensure that terms like “shout out” are correctly hyphenated (e.g. “shout‐out”) when used as modifiers.
• Review and update any placeholder text such as “TODO: Replace” in alt attributes and image descriptions.
• Also, check that exclamation marks are used judiciously to avoid an overly casual style.
Please review the document against your style guide for consistency before final release.🧰 Tools
🪛 LanguageTool
[style] ~114-~114: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...ult) or above the text. ## Tile cards A lot of touches and improvements have been made...(A_LOT_OF)
[style] ~121-~121: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ... card can be controlled Tile cards are awesome! It is arguably the best and most versa...(AWESOME)
[style] ~137-~137: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ng cards, we gained the ability to make very wide tile cards. These cards would have a lo...(EN_WEAK_ADJECTIVE)
[style] ~146-~146: Consider using a different adverb to strengthen your wording.
Context: ...ard-inline-feature.png" /> This brings a completely new look and feel which we are sure you...(COMPLETELY_ENTIRELY)
[uncategorized] ~159-~159: When ‘shout-out’ is used as a noun or modifier, it needs to be hyphenated.
Context: ...been contributed by [@jpbede], so a big shout out to him! [@jpbede]: https://github.com/...(VERB_NOUN_CONFUSION)
[grammar] ~206-~206: The verb form ‘give’ does not appear to fit in this context.
Context: ...more clear and easier to use. The new control give you a better overview of what the optio...(SINGULAR_NOUN_VERB_AGREEMENT)
[uncategorized] ~313-~313: This expression is usually spelled with a hyphen.
Context: ...@awahlig]! - UniFi version 9 introduced zone based rules. These are now supported in the ...(BASED_HYPHEN)
[style] ~340-~340: Consider an alternative to strengthen your wording.
Context: ...ther noteworthy changes There are many more improvements in this release; here are some of the o...(IMPROVEMENTS_REFINEMENTS)
[misspelling] ~347-~347: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ange with a big impact. When you set up an new integration for a new device, Hom...(EN_A_VS_AN)
[style] ~378-~378: This phrase might be unnecessarily wordy.
Context: ... in Home Assistant. Things changed, but our aim was to make it look and feel similar. Howe...(MY_HOPE_IS)
[grammar] ~395-~395: This expression is usually spelled with a hyphen.
Context: .... You can now also zoom in and out, by double clicking on a graph. If you want more control ov...(DOUBLE_CLICK_HYPHEN)
[style] ~400-~400: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...f your entities. However, when you have a lot of entities on the map, especially when th...(A_LOT_OF)
[style] ~410-~410: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...[@jpbede] and [@marcinbauer85] for this awesome improvement! [@jpbede]: https://github...(AWESOME)
[style] ~424-~424: Using many exclamation marks might seem excessive (in this case: 41 exclamation marks for a text that’s 18817 characters long)
Context: ...-assistant/core/issues), to get it fixed! Or, check our help page for gu...(EN_EXCESSIVE_EXCLAMATION)
[style] ~433-~433: Consider shortening or rephrasing this to strengthen your wording.
Context: ...atible changes We do our best to avoid making changes to existing functionality that might unexp...(MAKE_CHANGES)
🪛 markdownlint-cli2 (0.17.2)
204-204: Trailing spaces
Expected: 0 or 2; Actual: 1(MD009, no-trailing-spaces)
229-229: Bare URL used
null(MD034, no-bare-urls)
254-254: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"(MD053, link-image-reference-definitions)
366-366: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"(MD053, link-image-reference-definitions)
412-412: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"(MD053, link-image-reference-definitions)
415-415: Trailing punctuation in heading
Punctuation: '!'(MD026, no-trailing-punctuation)
464-464: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Diegorro98"(MD053, link-image-reference-definitions)
475-475: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Diegorro98"(MD053, link-image-reference-definitions)
488-488: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Diegorro98"(MD053, link-image-reference-definitions)
544-544: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@joostlek"(MD053, link-image-reference-definitions)
source/_integrations/roborock.markdown (1)
27-27: Addition ofscenePlatform: Verify Documentation and Consistency.The
sceneplatform has been added to theha_platformslist, which enhances the integration by enabling scene entities. Please ensure that:
- The "### Scene" section (lines 134–137) accurately reflects how users should configure and use scene entities.
- Any special configuration or usage notes for scene entities are documented either in this file or the integration’s broader documentation.
- You verify that the release version in the header (line 15, currently
ha_release: 2023.5) is intended for the 2025.3 beta release, or update it accordingly.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (12)
Gemfile.lockis excluded by!**/*.locksource/images/blog/2025-03/temp-graph-legend.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-marker-clustering.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-tile-card-counter-actions.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-tile-card-editor.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-tile-card-inline-feature.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-tile-card-inline-settings.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-tile-card-keyboard-navigation.mp4is excluded by!**/*.mp4source/images/blog/2025-03/temp-tile-card-micro-interactions.mp4is excluded by!**/*.mp4source/images/blog/2025-03/temp-tile-card-shapes.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-tile-card-switch-toggle.pngis excluded by!**/*.pngsource/images/blog/2025-03/temp-view-header.pngis excluded by!**/*.png
📒 Files selected for processing (31)
CODEOWNERS(13 hunks)_config.yml(1 hunks)source/_integrations/azure_storage.markdown(1 hunks)source/_integrations/bring.markdown(2 hunks)source/_integrations/burbank_water_and_power.markdown(1 hunks)source/_integrations/electric_kiwi.markdown(1 hunks)source/_integrations/esera_onewire.markdown(1 hunks)source/_integrations/habitica.markdown(1 hunks)source/_integrations/heicko.markdown(1 hunks)source/_integrations/home_connect.markdown(1 hunks)source/_integrations/iometer.markdown(1 hunks)source/_integrations/jellyfin.markdown(1 hunks)source/_integrations/linak.markdown(1 hunks)source/_integrations/linx.markdown(1 hunks)source/_integrations/mastodon.markdown(1 hunks)source/_integrations/minecraft_server.markdown(1 hunks)source/_integrations/nut.markdown(1 hunks)source/_integrations/onedrive.markdown(2 hunks)source/_integrations/pglab.markdown(1 hunks)source/_integrations/picnic.markdown(1 hunks)source/_integrations/qbus.markdown(1 hunks)source/_integrations/roborock.markdown(1 hunks)source/_integrations/smart_rollos.markdown(1 hunks)source/_integrations/snoo.markdown(2 hunks)source/_integrations/tado.markdown(2 hunks)source/_integrations/thermopro.markdown(1 hunks)source/_integrations/ublockout.markdown(1 hunks)source/_integrations/velbus.markdown(1 hunks)source/_integrations/vesync.markdown(1 hunks)source/_integrations/weatherflow_cloud.markdown(1 hunks)source/_posts/2025-03-05-release-20253.markdown(1 hunks)
✅ Files skipped from review due to trivial changes (13)
- source/_integrations/azure_storage.markdown
- source/_integrations/velbus.markdown
- source/_integrations/heicko.markdown
- source/_integrations/linx.markdown
- source/_integrations/electric_kiwi.markdown
- source/_integrations/nut.markdown
- source/_integrations/minecraft_server.markdown
- source/_integrations/burbank_water_and_power.markdown
- source/_integrations/weatherflow_cloud.markdown
- source/_integrations/smart_rollos.markdown
- source/_integrations/jellyfin.markdown
- source/_integrations/habitica.markdown
- source/_integrations/pglab.markdown
🧰 Additional context used
🪛 LanguageTool
source/_posts/2025-03-05-release-20253.markdown
[style] ~114-~114: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...ult) or above the text. ## Tile cards A lot of touches and improvements have been made...
(A_LOT_OF)
[style] ~121-~121: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ... card can be controlled Tile cards are awesome! It is arguably the best and most versa...
(AWESOME)
[style] ~137-~137: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...ng cards, we gained the ability to make very wide tile cards. These cards would have a lo...
(EN_WEAK_ADJECTIVE)
[style] ~146-~146: Consider using a different adverb to strengthen your wording.
Context: ...ard-inline-feature.png" /> This brings a completely new look and feel which we are sure you...
(COMPLETELY_ENTIRELY)
[uncategorized] ~159-~159: When ‘shout-out’ is used as a noun or modifier, it needs to be hyphenated.
Context: ...been contributed by [@jpbede], so a big shout out to him! [@jpbede]: https://github.com/...
(VERB_NOUN_CONFUSION)
[grammar] ~206-~206: The verb form ‘give’ does not appear to fit in this context.
Context: ...more clear and easier to use. The new control give you a better overview of what the optio...
(SINGULAR_NOUN_VERB_AGREEMENT)
[uncategorized] ~313-~313: This expression is usually spelled with a hyphen.
Context: ...@awahlig]! - UniFi version 9 introduced zone based rules. These are now supported in the ...
(BASED_HYPHEN)
[style] ~340-~340: Consider an alternative to strengthen your wording.
Context: ...ther noteworthy changes There are many more improvements in this release; here are some of the o...
(IMPROVEMENTS_REFINEMENTS)
[misspelling] ~347-~347: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ange with a big impact. When you set up an new integration for a new device, Hom...
(EN_A_VS_AN)
[style] ~378-~378: This phrase might be unnecessarily wordy.
Context: ... in Home Assistant. Things changed, but our aim was to make it look and feel similar. Howe...
(MY_HOPE_IS)
[grammar] ~395-~395: This expression is usually spelled with a hyphen.
Context: .... You can now also zoom in and out, by double clicking on a graph. If you want more control ov...
(DOUBLE_CLICK_HYPHEN)
[style] ~400-~400: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ...f your entities. However, when you have a lot of entities on the map, especially when th...
(A_LOT_OF)
[style] ~410-~410: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...[@jpbede] and [@marcinbauer85] for this awesome improvement! [@jpbede]: https://github...
(AWESOME)
[style] ~424-~424: Using many exclamation marks might seem excessive (in this case: 41 exclamation marks for a text that’s 18817 characters long)
Context: ...-assistant/core/issues), to get it fixed! Or, check our help page for gu...
(EN_EXCESSIVE_EXCLAMATION)
[style] ~433-~433: Consider shortening or rephrasing this to strengthen your wording.
Context: ...atible changes We do our best to avoid making changes to existing functionality that might unexp...
(MAKE_CHANGES)
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-03-05-release-20253.markdown
204-204: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
229-229: Bare URL used
null
(MD034, no-bare-urls)
254-254: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"
(MD053, link-image-reference-definitions)
366-366: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"
(MD053, link-image-reference-definitions)
412-412: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"
(MD053, link-image-reference-definitions)
415-415: Trailing punctuation in heading
Punctuation: '!'
(MD026, no-trailing-punctuation)
464-464: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Diegorro98"
(MD053, link-image-reference-definitions)
475-475: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Diegorro98"
(MD053, link-image-reference-definitions)
488-488: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Diegorro98"
(MD053, link-image-reference-definitions)
544-544: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@joostlek"
(MD053, link-image-reference-definitions)
🔇 Additional comments (43)
source/_integrations/picnic.markdown (1)
11-11: New Code Owner Added.
The addition of the code owner@codesalatdevto theha_codeownerslist is correctly implemented and helps ensure proper review oversight for the Picnic integration documentation.source/_integrations/mastodon.markdown (1)
15-15: New Platform 'notify' Added.
Introducing thenotifyplatform in theha_platformslist enhances the functionality of the Mastodon integration by enabling notification capabilities. This aligns well with similar platform expansions across other integrations.source/_integrations/esera_onewire.markdown (1)
22-22: Zeroconf Support Enabled.
The addition of the propertyha_zeroconf: truecorrectly indicates that the ESERA 1-Wire integration now supports Zero Configuration Networking, facilitating automatic device discovery on local networks.source/_integrations/thermopro.markdown (1)
15-15: New Platform 'button' Added.
The inclusion of thebuttonplatform in theha_platformslist now allows for additional interactions (such as setting device time), which is consistent with the enhanced feature support seen in other integrations.source/_integrations/snoo.markdown (2)
2-2: Integration Title Updated.
The integration title has been updated fromSnootoHappiest Baby Snoo, which improves clarity and better reflects the product branding.
15-15: Quality Scale Attribute Added.
The new propertyha_quality_scale: bronzehas been added successfully. This enhancement provides an additional layer of categorization regarding the integration’s quality, helping users gauge its maturity.source/_integrations/qbus.markdown (2)
7-8: New Platform Addition:
The addition oflightto theha_platformslist is a welcome enhancement that broadens the integration’s capabilities. Please verify that the accompanying sections (such as the "Available entities" section) correctly document the new functionality and that the ordering of platforms is intentional.
13-13: Release Version Consistency:
The file still listsha_release: 2025.2even though the overall PR is for the 2025.3 beta. Confirm that this value is intentional or update it if the integration is part of the upcoming 2025.3 release._config.yml (1)
110-112: Release Details Update:
The updates tocurrent_minor_version,current_patch_version, anddate_releasedare consistent with the release notes for version 2025.3. Please double-check that these values are coordinated with all related documentation and deployment configurations.source/_integrations/bring.markdown (2)
16-18: Platform Update:
The addition of theeventplatform extends the integration’s functionality. Ensure that any new event-related features are clearly explained in the documentation and that any dependent automations or integrations reflect this update.
28-28: Quality Scale Update:
Settingha_quality_scaletoplatinumhighlights the enhanced reliability or performance of the integration. Verify that this categorization is consistent with other integrations and that all stakeholders agree with the quality rating changes.source/_integrations/vesync.markdown (1)
26-26: New Platform Addition:
Introducing theselectplatform in theha_platformslist is a logical expansion of supported entity types. Please confirm that any new configuration requirements or behavioral specifics for select entities are reflected in the user documentation.source/_integrations/home_connect.markdown (2)
20-21: Code Owner Update:
Adding@MartinHjelmareto theha_codeownerslist is a positive change that should improve oversight for this integration. This update ensures that the appropriate expert is looped in for future reviews and changes.
33-33: Minor Formatting Adjustment:
The removal of the extraneous blank line at the end of the document improves the file’s formatting consistency.source/_integrations/onedrive.markdown (2)
2-2: Title update is clear.
Changing the title from “Microsoft OneDrive” to “OneDrive” nicely simplifies the integration’s name.
16-18: Enhanced metadata with quality scale and platforms.
Updatingha_quality_scaleto “platinum” and addingha_platformswith “sensor” correctly reflect the improved categorization of the integration. Make sure that any documentation or downstream consumers of this metadata are updated accordingly.source/_integrations/linak.markdown (3)
3-3: Updated description clarity.
The new description now states: “Connect and control your LINAK devices using the IKEA Idasen Desk integration.” Ensure that the actual functionality (e.g. integration with the Idasen Desk) matches this description.
10-10: Release version update review.
Changingha_releaseto'2023.10'is a significant update. Please verify that this new release version is consistent with the overall release timeline and related documentation.
18-19: New properties for extended functionality.
The addedha_iot_class: Local Pushandha_bluetooth: truehelp define the integration’s behavior and supported features. Confirm that the integration’s logic and any user interface elements properly account for these new properties.source/_integrations/tado.markdown (3)
10-10: Category list update.
The addition of “Switch” in theha_categorylist better reflects the integration’s supported device types. This should help clarify functionality for users and maintainers alike.
25-25: Platform enhancement noted.
By adding “switch” to theha_platformssection, the metadata now explicitly indicates support for switch functionality.
15-17: Codeowners update verified.
The codeowners section now only lists “@erwindouna”, which appears to reflect the intended ownership change.source/_integrations/iometer.markdown (4)
5-7: Refined integration categorization.
Retaining “Energy” and now adding “Sensor” in theha_categorysection provides a clearer picture of the integration’s scope. Cross-check that similar integrations follow the same categorization logic.
8-9: Codeowner update.
The update to list only “@MaestroOnICe” as the codeowner is appropriate given the current maintenance responsibilities.
12-12: Integration type modification.
Switching theha_integration_typefrom “integration” to “device” is a pivotal change. Please ensure that any backend or UI logic relying on this field is updated accordingly.
16-17: Platform support addition.
The newha_platformssection with the “sensor” entry reinforces the integration’s support for sensor data.source/_posts/2025-03-05-release-20253.markdown (4)
1-14: Metadata consistency check.
The front-matter correctly lists key metadata; however, note that thedate(“2025-02-26”) anddate_formatted(“March 5, 2025”) appear inconsistent. Please verify that the dates match the intended release timeline.
16-27: Effective intro with rich media.
The embedded YouTube snippet and the introductory note set a friendly tone for the beta release. Before release, replace any “TODO” placeholders in alt texts or notes as needed.
78-97: Comprehensive table of contents.
The table of contents is detailed and covers each section of the release notes. Double-check that every anchor link points to the correct section.
295-317: Noteworthy improvements details.
The section detailing improvements to existing integrations is informative. Ensure all inline GitHub username references and links are up-to-date and correctly formatted.🧰 Tools
🪛 LanguageTool
[uncategorized] ~313-~313: This expression is usually spelled with a hyphen.
Context: ...@awahlig]! - UniFi version 9 introduced zone based rules. These are now supported in the ...(BASED_HYPHEN)
CODEOWNERS (13)
98-98: New Azure Storage integration ownership assigned.The Azure Storage integration documentation is now owned by @zweckj, ensuring proper review assignment for future changes.
137-137: New Burbank Water and Power integration ownership assigned.The Burbank Water and Power integration documentation is now owned by @tronikos, who already maintains several other utility-related integrations.
353-353: New Heicko integration ownership assigned.The Heicko integration documentation is now owned by @starkillerOG, who maintains numerous other smart home device integrations.
424-424: New IOmeter integration ownership assigned.The IOmeter integration documentation is now owned by @MaestroOnICe, ensuring clear review assignment for future changes.
443-443: Updated Jellyfin integration ownership.The ownership for Jellyfin integration has been transferred from @j-stienstra to @RunC0deRun, with @ctalkington maintained as a co-owner.
492-492: New Linx integration ownership assigned.The Linx integration documentation is now owned by @starkillerOG, who maintains several other smart home integrations.
606-606: Updated NUT integration ownership.An additional owner (@tdfountain) has been added to the NUT integration documentation, alongside the existing owners.
656-656: New PGLab integration ownership assigned.The PGLab integration documentation is now owned by @pglab-electronics, likely representing the vendor or official maintainer.
660-660: Updated Picnic integration ownership.An additional owner (@codesalatdev) has been added to the Picnic integration documentation, alongside the existing owner.
809-809: New Smart Rollos integration ownership assigned.The Smart Rollos integration documentation is now owned by @starkillerOG, who maintains multiple other blind/shade-related integrations.
819-819: New Snoo integration ownership assigned.The Snoo integration documentation is now owned by @Lash-L, ensuring proper review assignment for future changes.
926-926: New UBlockout integration ownership assigned.The UBlockout integration documentation is now owned by @starkillerOG, aligning with their maintenance of various other smart home device integrations.
980-980: New WebDAV integration ownership assigned.The WebDAV integration documentation is now owned by @jpbede, ensuring proper review assignment for future changes.
| @@ -7,7 +7,7 @@ ha_domain: ublockout | |||
| ha_integration_type: virtual | |||
| ha_supporting_domain: motion_blinds | |||
| ha_supporting_integration: Motionblinds | |||
| ha_release: 2025.3 | |||
| ha_release: 2020.12 | |||
There was a problem hiding this comment.
Clarify the Release Version Downgrade
The ha_release field was changed from 2025.3 to 2020.12. Please verify that this downgrade is intentional. Given that the PR is for beta release notes of version 2025.3, it’s important to confirm if this integration is meant to remain on a legacy release version or if there’s an accompanying explanation to avoid confusion to maintainers and users.
| ### Editor improvements | ||
|
|
||
| Not just the tile card itself has been improved, but also the editor for | ||
| the tile card has been improved. It is now more clear and easier to use. | ||
|
|
||
| The new control give you a better overview of what the option will do for | ||
| the tile card. | ||
|
|
||
| <img class="no-shadow" alt="TODO: Replace." src="/images/blog/2025-03/temp-tile-card-editor.png" /> |
There was a problem hiding this comment.
Editor improvements—minor grammar fix.
In the sentence on line 206, “The new control give you a better overview…” should be corrected to “gives you a better overview” to fix the subject–verb agreement.
🧰 Tools
🪛 LanguageTool
[grammar] ~206-~206: The verb form ‘give’ does not appear to fit in this context.
Context: ...more clear and easier to use. The new control give you a better overview of what the optio...
(SINGULAR_NOUN_VERB_AGREEMENT)
🪛 markdownlint-cli2 (0.17.2)
204-204: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
| ### New integrations | ||
|
|
||
| We welcome the following new integrations in this release: | ||
|
|
||
| - **[Azure Storage]**, added by [@zweckj] | ||
| Use Azure Storage as a target location for your backups. | ||
| - **[IOmeter]**, added by [@MaestroOnICe] | ||
| Read out your [IOmeter device] data locally. | ||
| - **[PG LAB Electronics]**, added by [@pglab-electronics] | ||
| Control your [PG LAB Electronics devices] from Home Assistant. | ||
| - **[SensorPush Cloud]**, added by [@sstallion] | ||
| Integrate your [SensorPush devices] with Home Assistant, using their | ||
| cloud service. | ||
| - **[SNOO]**, added by [@Lash-L] | ||
| Get the state of your [SNOO Smart Sleeper Bassinet] into Home Assistant. | ||
| - **[WebDAV]**, added by [@jpbede] | ||
| Use any WebDAV compatible service as a target location for your backups. | ||
|
|
||
| [@jpbede]: https://github.com/jpbede | ||
| [@Lash-L]: https://github.com/Lash-L | ||
| [@MaestroOnICe]: https://github.com/MaestroOnICe | ||
| [@pglab-electronics]: https://githb.com/pglab-electronics | ||
| [@sstallion]: https://github.com/sstallion | ||
| [@zweckj]: https://github.com/zweckj | ||
| [Azure Storage]: /integrations/azure_storage | ||
| [IOmeter device]: https://iometer.de/produkt/ | ||
| [IOmeter]: /integrations/iometer | ||
| [PG LAB Electronics devices]: https://www.pglab.dev/ | ||
| [PG LAB Electronics]: /integrations/pglab | ||
| [SensorPush Cloud]: /integrations/sensorpush_cloud | ||
| [SensorPush devices]: https://www.sensorpush.com/ | ||
| [SNOO Smart Sleeper Bassinet]: https://www.happiestbaby.com/ | ||
| [SNOO]: /integrations/snoo | ||
| [WebDAV]: /integrations/webdav |
There was a problem hiding this comment.
New integrations listing review.
The list of new integrations is concise and well organized. One note: on line 257 there appears to be a typo in the URL for “[PG LAB Electronics]” (it reads “githb.com” instead of “github.com”). Please verify and correct any such URL errors.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
254-254: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jpbede"
(MD053, link-image-reference-definitions)
home-assistant
bot
removed
in-progress
Proposed change
Beta release notes for 2025.3
Summary by CodeRabbit
New Features
Chores