Breaking change

It's converting to a config_flow, so the existing configuration.yaml will no longer work, the UI appropriately says this and documentation will be updated.

Proposed change

As per @frenck, I've reduced the amount of changes to the minimum to update to ScannerEntity.

So that the upstream synology api still worked asynchronously, I added various polling options, including a setup function and config_flow so that it can work as a ScannerEntity. Prior changes (coordinator, string consts, and code quality improvements, more py tests) will come in a future PR.

• I opted to update the synology srm integration to use config_flow because of the comment chain from a parallel update for tomato (https://github.com/home-assistant/core/pull/143102/files#r2067597924)

I'm still new to the structure of the HA codebase, and open if there are better ways to update such things. I took references to mikrotik, asuswrt, freebox, and fritz to help understand ScannerEntity and router type integrations in general. I found limited documentation on the old DeviceScanner, as well as trying to understand a clear path to update DeviceScanner reserved function names to ScannerEntity.

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 #143038
• This PR is related to issue: #143038
• Link to documentation pull request: Update synology_srm to use config flow home-assistant.io#38972
• Link to developer documentation pull request:
• Link to frontend 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.

To help with the load of incoming pull requests:

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