Add known limitations for gios integration

[mik-laj]

Proposed change

Related to discussion: home-assistant/core#155603 (comment)

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logos and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase: Add quality scale for GIOS core#155603 (comment)
• Link to parent pull request in the Brands repository:
• This PR fixes or closes issue: fixes #

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

[home-assistant]

It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the current branch. Please change the target branch of this PR to current and rebase if needed. If this is documentation for a new feature, please add a link to that PR in your description.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	3faffd4
🔍 Latest deploy log	https://app.netlify.com/projects/home-assistant-docs/deploys/6952bb1bdae7f10008a1c411
😎 Deploy Preview	https://deploy-preview-42792--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[mik-laj]

This PR makes changes in documentation that exists only in next branch, so the branch is correct.

[Copilot]

Pull request overview

This PR reorganizes documentation for the GIOS integration by removing a note about sensor availability and data refresh rates from the "Available sensors" section, and adding a new "Known limitations" section that clarifies these constraints more explicitly.

• Moves sensor availability information from an informal note to a dedicated "Known limitations" section
• Adds context about data polling frequency and potential data staleness
• Improves document structure by grouping limitations in a standard section

[bieniu]

PR is targeting the wrong branch

[bieniu]

This PR makes changes in documentation that exists only in next branch, so the branch is correct.

It seems to me that #42740 should be targeted to the current branch.

[mik-laj]

@bieniu Yes. That's right. I chose the wrong branch because I was missing the changes in this mik-laj@67ef18e when I was reviewing whether everything was covered in the final documentation for this integration. This doesn't seem to be a big issues, as it looks like the next and current branches will be synchronized in a maximum of 3 days, as with the new month we have a new release.

Since the previous change was merged into next branch, I cannot merge this change into another branch.

[bieniu]

Currently, the next branch is equivalent to HA 2026.2, so targeting these types of changes to it doesn't make sense. In my opinion, we should wait until the 2026.1 release and open a new PR for the current branch.

[home-assistant]

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.