Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Increase Xbox update interval to 15 seconds and refactor title data handling#158780

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
joostlek merged 2 commits intohome-assistant:devfromtr4nt0r:xbox_rate_limit
Dec 12, 2025

Conversation

@tr4nt0r
Copy link
Contributor

@tr4nt0rtr4nt0r commentedDec 12, 2025
edited
Loading

Proposed change

The social endpoint enforces a rate limit of 10 requests per 15 seconds (burst) and 30 requests per 5 minutes (sustained). With the previous 10-second update interval, the integration issued exactly 30 requests within 5 minutes, which occasionally resulted exceedances of the sustained limit

This PR also adjusts the behavior so that the title info data is fetched only once at the start of a user’s play session, instead of on every coordinator cycle.

This is a temporary fix. I plan to follow up by splitting functionality into separate coordinators to better align with the API’s differing rate limits.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass.Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed thedevelopment checklist
  • I have followed theperfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • Themanifest file has all fields filled out correctly.
    Updated and included derived files by running:python3 -m script.hassfest.
  • New or updated dependencies have been added torequirements_all.txt.
    Updated by runningpython3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

cvroque reacted with hooray emoji
@home-assistant
Copy link

Hey there@hunterjm, mind taking a look at this pull request as it has been labeled with an integration (xbox) you are listed as acode owner for? Thanks!

Code owner commands

Code owners ofxbox can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign xbox Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@joostlekjoostlek added this to the2025.12.3 milestoneDec 12, 2025
@joostlekjoostlek merged commit0d8d466 intohome-assistant:devDec 12, 2025
36 checks passed
@tr4nt0rtr4nt0r deleted the xbox_rate_limit branchDecember 12, 2025 14:11
@frenckfrenck mentioned this pull requestDec 12, 2025
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsDec 13, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@joostlekjoostlekjoostlek approved these changes

@hunterjmhunterjmAwaiting requested review from hunterjmhunterjm is a code owner

+1 more reviewer

@kmk142789kmk142789kmk142789 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@hunterjmhunterjm

Projects

None yet

Milestone

2025.12.3

Development

Successfully merging this pull request may close these issues.

Xbox Integration Issue -Error fetching xbox data: Failed to connect to Xbox Network Xbox Rate Limiting

5 participants

@tr4nt0r@joostlek@kmk142789@frenck@hunterjm

[8]ページ先頭

©2009-2025 Movatter.jp