Reduce polling rate in Blink

[mkmer]

Proposed change

Revert polling rate to previous default 300s
While this was running for a least 2 months, since 2024.1.0 many users have been receiving unexpected 406 errors from the API. Since it may be a resource constraint on Blink side that appeared after HA reached "critical mass" on updates, I think we should revert to pre 2023.11 rate and re-evaluate.
Please tag for next bug fix release.

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

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Blink integration 406 errors / becoming unavailable #107143
• Link to documentation pull request:

Checklist

• 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 the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

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

• The manifest 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 to requirements_all.txt.
  Updated by running python3 -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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

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

Code owner commands

Code owners of blink 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 blink 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.

[fronzbot]

LGTM

[tieskuh]

Problem seems to be solved by changing to user agent fronzbot/blinkpy#848
Maybe polling interval change isn't needed.

[mkmer]

Let's hold off for a bit.
I'm suspect they are rate limiting us via the user agent - this will only be a cat and mouse game if that is the case.

[fronzbot]

Yeah I agree with @mkmer. User agent fixes the problem, but it's best we increase the polling time as well

[jhollowe]

LGTM

[frenck]

Thanks, @mkmer 👍

../Frenck