Remove polling_interval_seconds option from wemo

[esev]

Proposed change

Remove the polling_interval_seconds option added in #56972 based on feedback after that PR was merged. Users can disable automatic polling and set up their own polling interval if needed.

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 is related to issue: Add wemo options enable_subscription & enable_long_press #56972
• Link to documentation pull request: Remove wemo polling interval docs home-assistant.io#28001

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 Black (black --fast 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.

[esev]

Hi @marcelveldt please take a look when you get a chance.

Note: My availability is limited today. I'll try to respond to any feedback, but it's a travel day for me, so it may be several hours before I can respond.

[marcelveldt]

Thanks for the very quick turnaround, appreciated!

I just remembered in your previous PR you mentioned you got some complaints about databases growing too fast due to too many state updates. A solid way to fix that could be to implement "significant_change" logic where you tell the HA recorder what data change is considered significant enough. Maybe also worth taking a look at ?

https://developers.home-assistant.io/docs/core/platform/significant_change

[marcelveldt]

don't forget to update docs PR.

Thanks!

[esev]

Thanks for the reminder. home-assistant/home-assistant.io#28001 is the docs update.

I just remembered in your previous PR you mentioned you got some complaints about databases growing too fast due to too many state updates. A solid way to fix that could be to implement "significant_change" logic where you tell the HA recorder what data change is considered significant enough. Maybe also worth taking a look at ?

Yes, good call. I'll send another PR to add significant_change logic. It's okay if this isn't in the 2023.7.0 release though, correct?

[marcelveldt]

Yes, good call. I'll send another PR to add significant_change logic. It's okay if this isn't in the 2023.7.0 release though, correct?

Yes that is correct. It was just a tip after remembering you reported that issue.

[balloob]

Clearing milestone as it was merged before beta cut.