Add wemo options enable_subscription & enable_long_press

[esev]

Proposed change

Adding ConfigFlow options for Wemo to control subscriptions and the long-press feature.

• Under some circumstances (Wemo switches unavailable in HASS but still controllable by mobile Wemo app #62224) push subscriptions are causing devices to stop responding to requests.
• Subscriptions do not work when the Wemo device is on a different subnet. Having subscriptions enabled seems to increase the flakyness of the device connection. Wemo plugs keep reconnecting to the network pywemo/pywemo#275
• Allowing users to put the device into polling mode, and then controlling the polling frequency, will cut down on large database sizes: Wemo Insight Plug reporting sensor data every few seconds - filling database #63704
• I'd also like to work on improving the long-press feature. Last time, however, the feature caused issues for a few users. Adding an option to disable the feature will be helpful to avoid future issues.

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)
• 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 Wemo switches unavailable in HASS but still controllable by mobile Wemo app #62224
• This PR is related to issue: Wemo Insight Plug reporting sensor data every few seconds - filling database #63704 & Wemo plugs keep reconnecting to the network pywemo/pywemo#275
• Link to documentation pull request: Document WeMo device options home-assistant.io#20951

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
• 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[esev]

I've switched this PR from a feature request to a bug fix. Allowing users to disable push subscriptions fixes #62224.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[maxwellemerson]

Also following closely. Randomly having wemos fall off of HA and was close to abandoning my wemos for zwave tonight. Would rather see if there's a potential fix as wemos are much more affortable.

[silverl]

Hi, @frenck. Is there more the contributor needs to do to get this in shape to merge? Thank you.

[esev]

Thanks @silverl for asking. I've seen the devs do not like to be pinged, so I've just been waiting (on this and other PRs). I'm not sure what more there is to do. This code has been running fine on my HA instance for over a year. But maybe this PR doesn't fit well with the HA config model? I'm happy to change it or re-implement it if given some guidance.

[silverl]

Hi, @esev. Is it hard to replace the native WeMo integration with the modified copy? I'm game to try, but not sure where to start.

[esev]

I think it is possible to take a copy of this code and add it to the custom_components directory. But I haven't done that before. Searching for custom_components may bring up some solutions.

I have a different process where I patch this (and other) code into the monthly official Docker images and produce a new Docker image that contains my code. That makes rollbacks easy/safe for me should I need to go back to a prior release. That's not as easy of a process as I believe custom_components may be.

[silverl]

Anything left to do here? It looks like someone approved the changes...

[marcelveldt]

Code looks good to me.
I do agree with the fact that its cumbersome to ask the user for these kind of options but at the same time understand its hard to detect this properly and by having these options you at least have a solution for users affected by this.

Do note that options like this make the code more complicated and thus harder to maintain in the long run so if you ever find a way to solve it without this, fix it in a future PR ;-)

BTW: The issue sounds to me like device specific (malfunctioning device) or maybe even network related.

[marcelveldt]

@esev sorry for the delay, we're swamped with PR's and so hard to catch up with reviews.

Are you ready for a final review so we can get this merged ? In that case please rebase the PR one more time so its up to date with the dev branch again.

For now, I've marked this PR as draft, awaiting your response.
Once you're ready, click the Ready for review button above.

Thanks! 👍

Learn more about our pull request process.

[esev]

Many thanks for the review! It's much appreciated.

I rebased and fixed two issues. It should be good for a final review now.

[marcelveldt]

LGTM