Add force_update to timer integration

[akasma74]

Breaking change

It is not a breaking change as far as I understand.

Proposed change

As per this discussion we need to update last_changed when active timer restarted.
One way to do that is to force HA update the state on each request even if it remains the same.

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

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Timer - Remaining attribute is stale #30062
• 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
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

[balloob]

Please add a test.

[akasma74]

@balloob could you point me to the description how to do that - I've never done it.
or tell me who to ask at discord if that's easier ;)

[Adminiuga]

IMO you could tap into https://github.com/home-assistant/home-assistant/blob/e3894d212c8d7b2ab36e33b4911460352625e64a/tests/components/timer/test_init.py#L342-L406

Define another fakelistener and listen for STATE_CHANGED events? Then every time a timer service is called, state_changed listener should get a new result?

[akasma74]

Thanks Alexei, will try my best in finding out how the tests work.

[Adminiuga]

you also may want to install pre-commit for git, so it would take care of formatting and sorting imports
see https://developers.home-assistant.io/blog/2019/07/31/black.html

[stale]

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.

[akasma74]

bump, will deal with it soon

[Adminiuga]

LGTM, once lint is happy